It wouldn't be possible, because it would be completely ineffective.
Patrick Le lundi 26 avril 2010, Fernand Vanrie a écrit : > Patrick , > > Why not using "com.sun.star.configuration.ConfigurationProvider" to > store your global variables ? > I learned from Danny B. and uses it mostyl to store some Pathsettings > who must een remembered by opening and closing some Dialogs. > Your new exention can check if the "data" writen by the previous is the > correct version ? > Give a hint and i can post a small Basic Module to do the job > > Fernand > > > The scenario is the following : when OOo is started, the extension (which > > is written in C++) uses the OnStartApp event to initialize global > > variables. However, if the extension is updated while OOo is running, the > > code and the global variables are replaced with the ones from the new > > version of the extension. The global variables are thus left > > uninitialized. > > > > More generally, installing an extension while OOo is running may lead to > > problems, since the extension may rely on the OnStartApp event to > > initialize itself. However, when the extension is installed, the event is > > not fired and the state of the extension is inconsistent. > > > > Clearly, there can be a contradiction between allowing extensions to > > catch events when OOo is started, and allowing the user to add extensions > > to a running OOo and to use them immediately. There should at least a way > > to tell OOo that the newly installed extension can be used only when OOo > > is restarted. > > > > > > Patrick > > > > Le lundi 26 avril 2010, Joachim Lingner a écrit : > >> Could you give more detail (scenario, programming language)? Maybe a > >> code example?. > >> > >> Joachim > >> > >> Patrick Bernard wrote: > >>> Hello > >>> > >>> > >>> Updating an extension while it is used by OpenOffice.org can wreak > >>> havoc if the extension uses global variables. Is there a way to avoid > >>> this problem ? > >>> > >>> > >>> Patrick > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
