Hi,
On Wed, 2009-02-04 at 08:12 -0600, Glimmer Labs wrote:
It seems like several different plugins could take advantage of that
because they make temporary images.
(or would this still be only on plugin quit and not gimp quit?)
I think it would make sense to call the quit method in all
Thank you for the link to that thread, it was very informative.
I have yet to find any sort of workaround. I tried trapping all the TERM
type signals but no luck there.
Is doing a non blocking wait still under discussion?
Actually, for my purposes it doesn't matter whether the wait is blocking,
Hi,
On Tue, 2009-02-03 at 10:27 -0600, Glimmer Labs wrote:
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)?
I very much doubt that any real-world plug-in is actually using the quit
On Fri, Jan 30, 2009 at 12:33 PM, Glimmer Labs glimme...@gmail.com wrote:
I have been developing a plugin that involves users editing files and I need
to be able to prompt them to save when the gimp closes.
[...]
I don't think there is any way to do this using current functionality.
Hi,
On Fri, 2009-01-30 at 14:33 -0600, Glimmer Labs wrote:
I have been developing a plugin that involves users editing files and
I need to be able to prompt them to save when the gimp closes.
I have tried using the quit signal in pluginInfo:
GimpPlugInInfo PLUG_IN_INFO =
{
NULL,
I have been developing a plugin that involves users editing files and I need
to be able to prompt them to save when the gimp closes.
I have tried using the quit signal in pluginInfo:
GimpPlugInInfo PLUG_IN_INFO =
{
NULL,
quit,
query,
run
};
This only seems to be called, however, when
