https://issues.apache.org/ooo/show_bug.cgi?id=86541
Andreas Säger <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from Andreas Säger <[email protected]> --- (In reply to cno from comment #5) > Setting a more realistic priority. I won't argue about the priority of a shameful defect which wrongly suggests that the whole macro functionality depends on Java. It affects Tools>Macros>Run... Tools>Customize... at any point where you assign a macro to some document event, menu item, toolbar button or shortcut. All the places where you asign some object's script event (sheet tab events, form controls, certain Writer fields and many more). With Java disabled you get a sequence of error messages (one per library?) with Yes|No|Cancel. [Yes] leads to the Java options, [No] and [Cancel] do the same (nothing at all). After you canceled all the error messages without canceling the initial macro dialog, you can see all non-Java macros and use them anyway. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
