Sven Neumann wrote:
> Hi,
> On Tue, 2010-02-16 at 14:11 +0200, LightningIsMyName wrote:
>>> "A temporary procedure is a procedure which is only available while one
>>> of your plug-in's "real" procedures is running. "
>> That is correct - If you will look at line 107
>> you will see that the plugin is registerd as an extension and not as a
>> regular GIMP plugin. On line 217 and 221, the plugin registers itself
>> as an extension, and this way it allows itself to run from the moment
>> gimp starts up, untill GIMP is exited.
>> When registering an extension instead of a "normal" GIMP plugin, the
>> run procedure will be called during GIMP's start-up, and the plugin
>> will then be able to register temporary procedures (exactly like the
>> Script-Fu scripts) that will be available untill GIMP exits.
> Just to make this clear. The point of being an extension is not being
> run at start-up. You can have that without making your plug-in an
> extension. The point of registering as an extension is that your plug-in
> will install temporary procedures. If you want to be called at every
> startup, you can get that simply by installing an init_proc handler in
> the GimpPlugInInfo struct.
> I don't think though that the extension mechanism should be used for the
> purpose of being able to install changing menu procedures. It seems like
> quite some overkill to keep a plug-in process running just for this.
I agree, it's not very clean and is a waste of resources.

I'd gladly avoid this if there was a clean way for a
plugin to modify it's menu without hanging all the time in memory as an 

For instance GIMP could introduce an internal procedure one could call 
from a plugin that would trigger plugin's query() again.
I think this would be a nice non-intrusive add-on without the need to 
modify the API.

Anyone interested to add this functionality to the mainline?

Kind regards, Gena
> Sven

Gimp-developer mailing list

Reply via email to