Created attachment 117419 [details] presence.ods (macro on open document) Hi Description: registerContextMenuInterceptor does not work when run in a macro on "Open Document". The presence.ods attached launches a procedure on "Open Document". This procedure changes the context menu for the range C2:E8. Launched manually *after* opening the document continues to function. Associated with the event "Open Document" it no longer works. The procedure is launched (verified by print statements and xray on objects) but the menu is not displayed. Steps to reproduce: 1. Open the presence.ods attached 2. Accept macros if prompted 3. Right click somewhere in range C2:E8 Expected result: customized context menu Actual result: standard context menu This worked fine until version 4.3.4 4. Tools> Macros> Run macros> registerContextMenuInterceptor 5. Right click somewhere in range C2:E8 Expected & actual result: customized context menu Also reproduced on: - windows 7 & 4.4.2.2 - windows 7 & 4.4.4.3 - windows 7 & Version: 5.0.0.3 Build ID: f79b5ba13f5e6cbad23f8038060e556217e66632 Locale: fr-FR (fr_FR) So I set status to New May be related to bug 92770 ? Regards Pierre-Yves
please don't confirm your own bugs.
(In reply to Luke from comment #1) > please don't confirm your own bugs. As explained the bug was reproduced on different platforms by different people. Please do not change the status again.
Hi, I confirm this bug : registerContextMenuInterceptor does not work when run in a macro on "Open Document" since 4.4.2.
This seems to have begun at the below commit. Adding Cc: to Stephan Bergmann ; Could you possibly take a look at this one? Thanks cc0baee6acfd3166332690fb25404fa440b76abc is the first bad commit commit cc0baee6acfd3166332690fb25404fa440b76abc Author: Matthew Francis <mjay.francis@gmail.com> Date: Sat Mar 14 20:38:34 2015 +0800 source-hash-6b4c596b01039324cfe78f38c4e3ffb9080bcd34 commit 6b4c596b01039324cfe78f38c4e3ffb9080bcd34 Author: Stephan Bergmann <sbergman@redhat.com> AuthorDate: Mon Jun 2 11:12:11 2014 +0200 Commit: Stephan Bergmann <sbergman@redhat.com> CommitDate: Mon Jun 2 11:12:11 2014 +0200 Fix memory leak for BASIC sub (as well as void function) d88593af59d9126cdbcd6c0a5b06fb9c673dc6f9 "INTEGRATION: CWS ab34: #i73457# Prevent sub from beeing set as param 0 for return type void" to fix i#73457 "Memory Leak in all Basic type void Method calls" had made the PutDirect call dependent on != SbxVOID only (which would cover void functions) but not also on != SbxEMPTY (which would apparently be required to also cover subs, as seen with CppunitTest_basic_vba run under lsan). Either this was an oversight with the original fix, or subs have meanwhile changed from GetType() == SbxVOID to SbxEMPTY? Change-Id: I3e5dbf79bfd5eea3cfec8ed3fa984d13167aa501
(In reply to raal from comment #4) > commit 6b4c596b01039324cfe78f38c4e3ffb9080bcd34 > Author: Stephan Bergmann <sbergman@redhat.com> > AuthorDate: Mon Jun 2 11:12:11 2014 +0200 > Commit: Stephan Bergmann <sbergman@redhat.com> > CommitDate: Mon Jun 2 11:12:11 2014 +0200 > > Fix memory leak for BASIC sub (as well as void function) That commit got reverted again to fix bug 92446 that it had caused, and the revert landed in LO 4.4.6 according to bug 92446 comment 9. Can somebody please check whether this issue is fixed in LO 4.4.6?
Migrating Whiteboard tags to Keywords: (bibisected) [NinjaEdit]
Hi WORKSFORME on windows 7/64 &nd: - Version: 5.1.2.2 Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f Threads CPU : 2; Version de l'OS :Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR) -Version: 5.2.0.0.alpha1 (x64) Build ID: 902b28a39528b6c92602e9b521a1d0861be1caf9 Threads CPU : 2; Version de l'OS :Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR) Thank you Regards Pierre-Yves