Am Mittwoch, 17. Februar 2010 15:33:23 schrieb Gena Batsyan:
[...]
> > 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.
>
>
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
>> http://g
LightningIsMyName wrote:
Thanks a lot for your help!
With a just a little of refactoring I've managed to let the plugin be
launched at startup as an extension,
and handling procedures as temps. Works great and I could dynamically
change the menu items after a procedure
has been executed.
The o
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
> http://git.gnome.org/browse/gimp/tree/plug-ins/sc
Hello Gena,
I tried to browse the source of the script-fu plugin to answer your
question, and this is what I came up with:
> "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
Hi!
I've been trying to find a way for a plugin to update menu entries it
has initially registered from query() via gimp_install_procedure()
When the plugin is being run it wishes to update the menu entries, for
instance putting some named presets previously selected in the plugin
interface to
Hi !
Is it possible to dynamically insert plug-ins while Gimp is running ?
Any pointer to that topic would be appreciated !
Regards,
Fabian
--
Sent through GMX FreeMail - http://www.gmx.net
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
