Issue 92088

Summary: "Close document" event nonfunctional (when used in a single document)
Product: General Reporter: Frank Schönheit <frank.schoenheit>
Component: uiAssignee: AOO issues mailing list <issues>
Status: REOPENED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, Mathias_Bauer
Version: OOo 2.4.1Keywords: usability
Target Milestone: AOO Later   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
document to reproduce the bug case none

Description Frank Schönheit 2008-07-24 14:03:09 UTC
- open the attached document (ensure macro execution is allowed)
- via Tools / Customize / Events, verify it has three macros assigned to the
  events "Open Document", "Close Document", and "Document is closing"
- close the document
=> the macro for the "Document is closing" event is called, the one for
   "Close Document" is *not* called.
Comment 1 Frank Schönheit 2008-07-24 14:05:36 UTC
fs->as: not sure this event is useful at all, at least on document level: How
should this work: notifying an in-document macro about the document just having
been closed? I mean, the document is (for practical purposes) dead at the moment
the event is fired.

And while we are at it: "Start Application", "Close Application", "Create
Document" also do not seem to make sense as document-level macros events ...
Comment 2 Frank Schönheit 2008-07-24 15:18:04 UTC
Created attachment 55346 [details]
document to reproduce the bug case
Comment 3 Mathias_Bauer 2008-07-24 15:25:41 UTC
There are not only in-document macros. :-)

We could discuss whether the UI should prevent in-document macros from being
assigned, but IMHO that isn't worth the effort.
Comment 4 Frank Schönheit 2008-07-24 16:11:51 UTC
I disagree.

I know the difference between in-document and application-wide macros/events.
The point is, the events in question are included in both lists, though they do
not work in the former.

For the user, this means he has an UI which suggests there is a difference
between in-document and application-wide: For instance, "Print form letters" is
available in-document only, so this really looks like "what works is available,
and what is available works".

Either we say that all events are available everywhere, no matter whether they
work there or not, or that we only display those events which actually work.
Everything else is a crappy UI, IMO.
Comment 5 Mathias_Bauer 2008-07-24 16:28:15 UTC
I just wanted to consider effort, available resources and importance. Odds are
low that we will have time to fix that. Just another one on the big pile.
Comment 6 Rob Weir 2013-07-30 02:38:43 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.