Created attachment 147933 [details] demo macro worksheet change i noticed the problem while investigating issue https://bugs.documentfoundation.org/show_bug.cgi?id=122378 - open attached "demo_ macro_worksheet_change.xlsm" (created with excel 2016) - enter text in cell A1 - Worksheet_Change() Macro will execute on cell change - save as *.xlsm, close and reload - enter text in cell A1 - nothing happens
Thank you for reporting the bug. I can not confirm the bug with Version: 6.3.0.0.alpha0+ Build ID: 3c964980da07892a02d5ac721d80558c459532d0 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45 Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Confirm with Version: 6.3.0.0.alpha0+ Build ID: ef58bf56ad292656ad2de0a417eda72cc170f782 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: cs-CZ (cs_CZ.UTF-8); UI-Language: en-US Version: 6.0.3.0.0+ Build ID: a1b3ae95e35fe0669bcc9df020fa606e6a3cca75 In version Version: 5.4.0.0.beta2+ Build ID: 721efbeb117962e9b0cd547b51ede4a6736042a6 this Worksheet_Change() Macro doesn't work. Macro started to work after commit: author Tamas Bunth <tamas.bunth@collabora.co.uk> 2017-07-06 10:46:48 +0200 committer Tamás Bunth <btomi96@gmail.com> 2017-07-06 22:37:12 +0200 commit 5ee6862ee420f13133ade382d7ef2be319414d40 (patch) tree dc255b1cf96f9e8f99d77c3a92b488af87c938db parent 388041695d9626970b0d4dce89241c849eeffd0e (diff) Create vba library if it did not exist before Adding Cc: to Tamás Bunth ; Could you possibly take a look at this one? Thanks
*** Bug 122378 has been marked as a duplicate of this bug. ***
Dear Oliver Brinzing, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still rerpo in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 18771471f75685a6d3838a22d16dcff5c398e652 CPU threads: 4; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded
Dear Oliver Brinzing, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug