<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Macro not receiving event for form modification" href="https://bugs.documentfoundation.org/show_bug.cgi?id=140155#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Macro not receiving event for form modification" href="https://bugs.documentfoundation.org/show_bug.cgi?id=140155">bug 140155</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>> Macro not receiving event for form modification This title looks wrong. The event is received (and setting a breakpoint to SUB ChangeData would trigger the breakpoint when editing the data). But I am inclined to call this NOTABUG. The macro calls oDiag.Component.setmodified(true), abusing its side effect of updating the component. Not setting its "modified" flag looks legitimate in a locked document with modifications disallowed; and instead, its XUpdatable::update() should be called: > oDiag.Component.update() which works as expected. Trying to fix this could be either reverting the fix for <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - FILEOPEN: User asked to save changes upon exit from unmodified XLS file (because of chart)" href="show_bug.cgi?id=77007">tdf#77007</a> (and then trying to implement some more complex fix to make sure to mark loaded charts unmodified in different scenarios), or introducing some more complex logic to the check in the mentioned fix, which would try to guess if parent "IsEnableSetModified = false" does not apply to this element, which would be likely difficult to implement correctly.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>