To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105500
User fs changed the following:
What |Old value |New value
================================================================================
CC|'' |'mba'
--------------------------------------------------------------------------------
------- Additional comments from f...@openoffice.org Thu Oct 1 06:43:30 +0000
2009 -------
I am not sure the other documents behave correctly here.
API-wise, "Document is closing" is the OnPrepareUnload event. What comes closest
to a definition of this event is at
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OfficeDev/Document_Events,
but this doesn't answer the question at which point the event is to be fired.
My problem with firing the event earlier is that the called macro then cannot
rely anymore on the document being *really* closed: When there still exists a
controller for the document, then other listeners are yet to be called. And
those other listeners have the right to veto the closing. Which means the macro
called by OnPreareUnload/"Document is closing" would have *no* chance finding
out whether the document is really to be closed, or just - unsuccessfully -
attempted to the closed.
So I am tempted to say that when you work with controllers, then
OnPrepareUnload/"Document is closing" is the wrong event to rely upon.
OnViewCreated/OnViewClosed would be the proper events (since controllers really
represent views to the document; Note that there can be multiple of them for a
single document, which can be opened and closed in an arbitrary order, so any
your code relying on "one controller per document" is doomed to fail, anyway).
Unfortunately, those two events are not available in Tools/Customize/Events at
the moment, but this could be fixed.
fs->mba: I'd appreciate your input here - Do you have an opinion 'bout this?
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
