Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | RPT : no warning dialog when hide a group with content | ||||||
---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | marc.neumann | ||||
Component: | code | Assignee: | marc.neumann | ||||
Status: | CLOSED FIXED | QA Contact: | issues@dba <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues | ||||
Version: | recent-trunk | Keywords: | new_implementation | ||||
Target Milestone: | OOo 2.3 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
marc.neumann
2007-05-09 13:38:31 UTC
add keyword new_implementation Could you please check if we need an message box even when the action the user did is undo able. The Report Designer iTeam decided that this issue is a show stopper for the release of the report designer. Targeting to 2.3, thus. Created attachment 45203 [details]
database w/example report Report3
If someone could remove that attachment - mistakenly attached to wrong issue. > If someone could remove that attachment ...
No, removing (or even only deprecating) attachments is no supported feature in
IssueTracker :(
grabbing as we agreed in the iTeam, this issue is solved by renaming the "Show"/"Hide" entries to something else, which does not suggest that the header/footer is made invisible, but better shows that it is removed. /me thinks "Present" / "Not present" is a halfway good wording ... fixed in CWS oj14 find more information about this CWS, like when it is available in the master builds, in EIS, the Environment Information System: http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Foj14 reassign to msc . verified in CWS oj14 version 0.4.0 The strings have been changed - but I can not concur that it adequately addresses the situation. This is something that has cost me added work on at least two occasions and from a usability stand point is most likely to happen when a user is creating a complicated report, often on a deadline and under stress. This 'easy to hang yourself type of feature' is in other words it is most likely to happen to users at the absolute worst possible time. In the iTeam, we decided this were the best compromise. A modal warning box is not really good user experience, too. Preserving the content is pretty difficult, core-wise. Finally, there's UNDO, isn't it? Well - Yes there is undo |