RE: guidance to write a unit test for SetMacroSecurityLevel()

> [nicholas ferguson]
> in sc/qa/.../qahelper.cxx 
> line 544
> SfxItemSet* pSet = pSrcMed->GetItemSet();
> pSet->Put(SfxUInt16Item(SID_MACROEXECMODE,::com::sun::star::document::MacroExecMode::ALWAYS_EXECUTE_NO_WARN));
>
> and add include
> #include <com/sun/star/document/MacroExecMode.hdl>
> This does work. But someone needs to write a CPP Unit test of opening up a s/h, then dynamically 
> changing MacroExecMode's and checking that they are ok.

[Bergmann]
] >>No idea what you mean with "dynamically changing MacroExecMode's and checking that they are ok" 
(the macro security settings are checked once, when the document is opened, if that is where you're 
heading).
[nicholas ferguson] 

It appears you don't code spreadsheets for computations. People who work with VB code in 
spreadsheets understand that enabling macros is essential.  
        open up an excel with macros enabled.
        open up an excel s.h ...macros were not enabled.  Enable them, without closing the s/h.

Tests like...
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice