To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113403
User fs changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |WONTFIX
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Tue Sep 14 09:33:45 +0000
2010 -------
I tend to say that the macro in the sample document is flawed. What happens here
is that in the "Document is going to be closed" event of the form, the database
document which the form belongs to, and thus the form, is closed
programmatically. This is something a mere text document also doesn't survive,
and which I'd consider a bug in the macro: Closing the document from within the
routine which closes it is ... well, prone to errors, at least.
Fixing this in the application framework requires *a lot* of work, since the
whole code in SFX simple isn't prepared for that.
I'll commit the fix in the scripting framework (see the above comment - for the
"easy" one of the crashes), to be on the safe side.
However, to programmatically close the database document when the form closes,
I'd say another approach is to be used by the macro.
Alternative solutions which come to my mind:
- close the database document asynchronously, using css.awt.AsyncCallback
- don't bind the macro to the "document is going to be closed" event of
the form, but to the "Closed a sub component" event of the database
document
I tried the second approach with the above bug doc, it seems to work fine.
(Didn't try the first approach.)
Resolving the issue as WONTFIX.
---------------------------------------------------------------------
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: [email protected]
For additional commands, e-mail: [email protected]
