Apache OpenOffice (AOO) Bugzilla – Issue 98467
Impossible to remove event assigned action
Last modified: 2009-02-25 08:32:53 UTC
Regression found on DEV300m39 From a document, open Tools > Customize > Event tab. Assign a macro to event Open Document of the document. Check that it works, save the document. Reopen Tools > Customize > Event tab Remove the assigned action from event Open Document. Close the dialog window. Reopen Tools > Customize > Event tab : Assigned Action is still there ! Next attachment is an example. You can't remove the event action with DEV300m39. But you can remove it with OOo 3.0.0.
Created attachment 59663 [details] This document has a Hello macro attached to event Open Document
Problem still exists on DEV300m40.
Proposing this issue as 3.1 release stopper.
Confirming. It has not been officially accepted as show stopper, but I take the liberty to set the target already ...
Created attachment 59847 [details] suggested patch
fs->mba: Would you please review the attached patch? I suppose it's me who introduced the bug: I refactored the Tools/Customize dialog a while ago, namely the macro assignment page, so that resetting a macro is not done by passing a one-element sequence with an empty script type, but by passing an empty sequence. I would have sworn that I also adjusted SfxEvents_Impl::replaceByName to recognize this, but alas ... Anyway, the attached patch fixes the problem, but just to be sure this time :), I would be grateful if you could have a look at it. Thanks.
fs->mba: Ping. This is a 3.1 issue, and the "dead line for exceptional code fixes" is less than a week away. I *really* want to get this issue fixed. Please review the attached patch, or name somebody else who you think could do the review. Thanks.
patch committed to CWS dba31i. fs->mba: Will correct if you veto it, for the moment I assume the patch is okay. Sorry, but the deadline is too near for further waiting ...
fs->jsk: please verify in CWS dba31i
Verified in CWS dab31i/m41.
The patch looks fine.
thanks for the review
Hi, this is fixed in master OOO310_m2. I close this issue now. Bye Marc