To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=82110
------- Additional comments from [EMAIL PROTECTED] Mon Mar 10 14:18:16 +0000 2008 ------- Ah, yes, we have a problem here ... There were two bugs: One is that the MacroExecutionMode as passed to the loaded forms was ignored. The other was that there were separate macro warnings for each and every form, instead of having one for the DB doc as a whole. The first issue (this one here) was fixing by respecting the parameter. However, it was only allowed to downgrade the MacroExecutionMode, not to upgrade it: If the whole DB doc was loaded with "don't execute at all", then an "always execute" for a particular form was rejected. But if the DB doc was loaded without explicit macro execution mode, then the mode as passed to form was taken unchanged. The second issue (whose number slips me ATM) changed the behaviour so that the warning came when the DB doc was opened, not for every single form. Now, passing ALWAYS_EXECUTE_NO_WARN to a particular form became senseless: At time of loading the DB doc, it was decided whether or not to execute macros - "yes" or "no", nothing inbetween. As before, the mode passed to a form did allow downgrades (from "yes" for the DB doc to "no" for the particular form), no upgrades. So, the only thing which can reasonably passed to the form is NEVER_EXECUTE nowadays. --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
