[Gimp-developer] "quit" signal for plugins
Glimmer Labs
glimmer07 at gmail.com
Tue Feb 3 08:27:32 PST 2009
I have been thinking about this and it does seem to be a somewhat thorny
issue.
One possible solution would be to call the quit functions of the plugins but
have a timeout set
so that you could pop up a dialog if they did not quit after a second or two
asking if the user wanted
to terminate the plugin. But this seems messy.
Another thought:
If a plugin has a quit function that hangs or takes a long time, won't that
affect the gimp when
the quit function is normally called (on closing of plugin)? If so, the
gimp is already exposed to the problem
of poorly written plugins, and it might as well call the quit functions of
active plugins when it exits.
Or does the gimp have some way of protecting against this issue that
wouldn't work if it was closing?
Thank you for your assistance,
-Soren Berg
On Sun, Feb 1, 2009 at 12:49 PM, Sven Neumann <sven at gimp.org> wrote:
>
> I am not entirely sure how plug-ins are quit by the core when the GIMP
> core exits. It would probably make sense to make sure that the plug-in's
> quit function is called. On the other hand we don't want the application
> to hang there waiting for plug-ins to quit. If you want to investigate
> this further, we could try to help you to fix this issue.
>
>
> Sven
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /lists/gimp-developer/attachments/20090203/d832c48b/attachment.html
More information about the Gimp-developer
mailing list