Bug #16910 for Gimp: Changing Perl-Fu input parameter list causes type conflicts

Wed Jan 04 12:35:40 2006 Guest - Ticket created

Subject:

Changing Perl-Fu input parameter list causes type conflicts

If I alter the input parameter list to my perl-fu script, (for example swapping a COLOR parameter with an INT parameter), then when the script loads, there is stored information in the plug-in 'parasite' that caches the last used parameters when run. This can cause errors such as 'cannot grok "50" as a color...', which makes it IMPOSSIBLE to actually run the script. This is something hardly documented, yet something that probably happens frequently. Perhaps the parasite data should be flushed when gimptool --install-bin is called?

Sun Apr 13 00:18:42 2014 ETJ [...] cpan.org - Taken

Sun Apr 13 00:19:36 2014 ETJ [...] cpan.org - Correspondence added

On Wed Jan 04 12:35:40 2006, guest wrote: Show quoted text

> If I alter the input parameter list to my perl-fu script, (for example > swapping a COLOR parameter with an INT parameter), then when the > script loads, there is stored information in the plug-in 'parasite' > that caches the last used parameters when run. This can cause errors > such as 'cannot grok "50" as a color...', which makes it IMPOSSIBLE to > actually run the script. > > This is something hardly documented, yet something that probably > happens frequently. > > Perhaps the parasite data should be flushed when gimptool --install- > bin is called?

Still an issue with GP 2.3. Good report.

Sun Apr 13 00:19:36 2014 The RT System itself - Status changed from 'new' to 'open'

Sun Apr 13 03:37:35 2014 ETJ [...] cpan.org - Correspondence added

Now fixed for 2.3001.

Sun Apr 13 03:37:36 2014 ETJ [...] cpan.org - Status changed from 'open' to 'resolved'

Sun Apr 13 03:37:37 2014 ETJ [...] cpan.org - Fixed in 2.3 added