jonathon wrote:
Joe Smith wrote:
...
OOo can and should do better--and until a better strategy is available,
the default should be all macros off, no questions asked.
Isn't that the current default?
I don't remember configuring that option. Every time I open
a document that contains a macro, I am asked if I want to
enable macros.
Yes, the default behavior is to ask. I'm saying we should not even pop
the dialog because at current the only good answer is 'No'.
C) provide a distinct facility that would allow the macro
writer to manipulate the open document, and nothing else,
One practical issue with that approach.
I've got a macro that converts ODF format to Duxbury File
Format. With your proposal there is nowhere for the output
of that macro to be placed.
I've got another macro that opens a file in Duxbury file
format, converting it to ODF in the process. With your
proposal that macro could not run.
I don't know anything about Duxbury File Format, but is it necessary or
appropriate to bundle that as a macro in a document? It seems to me
that--as you also said--a separate download as macro code or as an
extension, would be the best way to handle something like this.
I was suggesting a limited macro facility so that the dialog could say
"The macros in this document cannot change anything other than this
document or it's window." That would give the user some useful
information toward choosing whether to allow the macros or not.
The full programming facilities would still be available, and if
present, the macro dialog could then warn "The macros in this document
are capable of making changes to other documents and files on your system."
<Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
