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 345849 - plug-in grid gives boundary error
plug-in grid gives boundary error
Status: RESOLVED DUPLICATE of bug 344431
Product: GIMP
Classification: Other
Component: Tools
git master
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-06-25 02:46 UTC by Seth Burgess
Modified: 2006-06-26 05:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Seth Burgess 2006-06-25 02:46:39 UTC 
Substitute your image/drawable into the below 2nd and 3rd params and enter at the console:

(plug-in-grid 1 1 4 1 10 0 '(0 0 0) 255 1 10 0 '(0 0 0) 255 1 10 0 '(0 0 0) 255)

it gives a dialog of:
PDB calling error for procedure 'plug-in-grid':
Argument 'hopacity' (#8, type GimpInt8) out of bounds (validation changed '4294967295' to '255')

(same happens for python bindings, gimp-perl, etc)
Comment 1 Manish Singh 2006-06-25 03:56:04 UTC 

*** This bug has been marked as a duplicate of 344431 ***
Comment 2 Joao S. O. Bueno 2006-06-26 03:31:34 UTC 
Still borken, even after bug #344431 had been fixed.

I get errors at random when trying to call plug_in_grid from the python console. This time, the parameter with error is said to be one of the gimp-colors.

NB: the error is at random. It may fail twice in a row, it may work 20 times, and then fail, with the same parameters.

Function call:


>>> pdb.plug_in_grid (img, drw, 2, 4,0, (0,0,0), 0, 2 ,4,0,(255,0,0), 1, 0,1,0,(0,0,0),0)

Error:
PDB calling error for procedure 'plug-in-grid':
Argument 'vcolor' (#12, type GimpRGB) out of bounds (validation changed '<not transformable to string>' to '<not transformable to string>')
Comment 3 Manish Singh 2006-06-26 05:21:08 UTC 
Reresolving as duplicates. Colors not working in pygimp is a separate issue.

Please don't hijack bugs, the fix to #344431 did fix the the original issue filed.

*** This bug has been marked as a duplicate of 344431 ***