Eike Rathke wrote: > Hi Mathias, > > On Mon, May 29, 2006 at 17:41:52 +0200, Mathias Bauer wrote: > >> > I'm not sure whether the .xcu UserData element could even be used for >> > such mechanism, could someone from the framework team shed some light on >> > this? Is there a way to transport that in an SID_FILE_FILTEROPTIONS >> > SfxStringItem? >> >> Yes, there is. Here's an example in Basic: >> [...] >> args(1).Name="FilterOptions" >> args(1).Value="XXXX" > > Well, yes, I know about the FilterOptions property, forget about > SID_FILE_FILTEROPTIONS, the question was more whether there is some > automatism to transport the .xcu UserData as a FilterOptions' value, > without the need of macros or alike. With such a mechanism it would be > relatively easy to modify the initialization of the dialog to obtain the > settings in ScFilterOptionsObj::execute().
Sorry, I don't understand. Why transport configuration data if it works with the FilterOptions parameter? Or does the userdata contain something that can't be set through FilterOptions? Besides that there *is* a way to transport user data to a filter, the "FilterData" property. Of course the filter must support it. "FilterData" is an "any" and can transport any data the filter defines, the framework code doesn't interpret it. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
