Re: [dev] Security: how to avoid to pop up the Basic IDE?

Peter Eberlein wrote: > Hi Mathias, > > Mathias Bauer schrieb: >> Peter Eberlein wrote: >> > >> Macro security is about macro execution, not about availability of the >> BasicIDE. > > And that's the point. You cannot forbid the execution of internal > non-document-bound macros with the secur

Re: [dev] Security: how to avoid to pop up the Basic IDE?

Hi Mathias, Mathias Bauer schrieb: Peter Eberlein wrote: Macro security is about macro execution, not about availability of the BasicIDE. And that's the point. You cannot forbid the execution of internal non-document-bound macros with the security settings. Regards Peter ---

Re: [dev] Security: how to avoid to pop up the Basic IDE?

Peter Eberlein wrote: > Hi, > > we want to restrict the use of the Basic IDE, but because of a missing > error handling in OpenOffice's macros, it is simple to produce an error > and to access the IDE (e.g. bind the macro > Depot.Depot.AddShortCuttoControl() to a field, a frame, a graphic). >

[dev] Security: how to avoid to pop up the Basic IDE?

Hi, we want to restrict the use of the Basic IDE, but because of a missing error handling in OpenOffice's macros, it is simple to produce an error and to access the IDE (e.g. bind the macro Depot.Depot.AddShortCuttoControl() to a field, a frame, a graphic). The only way I see is to manipulat