After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 166650 - Error in python plug-ins
Error in python plug-ins
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Gimp-Python
2.2.x
Other All
: Normal minor
: ---
Assigned To: Manish Singh
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-02-08 10:54 UTC by Piet van Oostrum
Modified: 2008-01-15 12:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Piet van Oostrum 2005-02-08 10:54:54 UTC 
Start a Gimp which includes python-fu. Execute Xtns/Python-Fu/Test/Sphere.
(Probably opening another image is also OK). Now close the image such that no
images are open. The menu Xtns/Python-Fu/Test/Sphereis now grayed out as are the
Python-Fu Console and PDB Browser.

The solution is simple: In sphere.py, gimpcons.py and pdbbrowse.py change the
8th parameter from "RGB*, GRAY*, INDEXED*" or "*" to the empty string "".
Comment 1 Sven Neumann 2005-02-08 13:05:24 UTC 
"RGB*, GRAY*, INDEXED*" and "*" should be equivalent to ""
Comment 2 Sven Neumann 2005-02-08 13:08:12 UTC 
On a related note, Xtns/Python-Fu/Test/Sphere should probably not be installed
in a stable release (same for the respective Script-Fu script).
Comment 3 Sven Neumann 2005-02-08 13:21:02 UTC 
Please ignore comment #1, it's complete bullshit. You are of course right, the
script should always be available and thus should use the empty string for the
image-type.
Comment 4 Manish Singh 2005-02-08 19:25:15 UTC 
Committed to both branches:

2005-02-08  Manish Singh  <yosh@gimp.org>

        * plug-ins/pygimp/plug-ins/sphere.py
        * plug-ins/pygimp/plug-ins/gimpcons.py
        * plug-ins/pygimp/plug-ins/pdbbrowse.py: Just leave imagetypes empty,
        since we don't operate on existing images here. Fixes bug #166650.