Issue 103 in gpick: Gpick generates gpl files with out of bounds colour-ranges for Krita and Gimp.

4 views
Skip to first unread message

gp...@googlecode.com

unread,
Apr 17, 2013, 10:04:59 AM4/17/13
to gp...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 103 by griffinv...@gmail.com: Gpick generates gpl files with out
of bounds colour-ranges for Krita and Gimp.
http://code.google.com/p/gpick/issues/detail?id=103

I initially thought this was solely a Krita bug, so I first reported it to
the Krita bugtracker:
https://bugs.kde.org/show_bug.cgi?id=318345

Basically, Krita and Gimp register rgb to go from 0 to 255, while Gpick and
Mypaint go from 1 to 256, resulting in swatches with any of the colours at
256 to throw errors in Krita and Gimp.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

gp...@googlecode.com

unread,
Apr 22, 2013, 8:48:55 AM4/22/13
to gp...@googlegroups.com

Comment #1 on issue 103 by fintic...@gmail.com: Gpick generates gpl files
with out of bounds colour-ranges for Krita and Gimp.
http://code.google.com/p/gpick/issues/detail?id=103

It's extremely likely you are simply using an out of date version of GPick.
GPick 0.2.5 includes a fix for this issue. (note that in a slight
oversight, the About dialog for 0.2.5 still reports "0.2.4", so you'll need
to look at your package manager to be sure. Or just check whether 'Group
and Sort' is shown in the palette's rightclick menu.

gp...@googlecode.com

unread,
Apr 23, 2013, 3:11:35 AM4/23/13
to gp...@googlegroups.com
Updates:
Status: WaitingConfirmation

Comment #2 on issue 103 by 00a...@gmail.com: Gpick generates gpl files with
out of bounds colour-ranges for Krita and Gimp.
http://code.google.com/p/gpick/issues/detail?id=103

(this is my old login. Comment #1 was also by me.)

Please confirm whether updating to 0.2.5 fixes the problem for you.

If not, please give specific step-by-step examples of creating colors that
export wrongly.

I have not, for example, been able to produce this bug by saving or
exporting a palette containing black, white, and full intensity red,
green, blue, cyan, yellow, and magenta (ie. #f00, #0f0, #00f, #0ff, #ff0,
#f0f), created using the RGB sliders. All values reported as 0 by GPick are
also 0 in the GPL, and all values reported as 255 by GPick are also 255 in
the GPL.

Sample GPick 0.2.5 output attached.



Attachments:
burntcolors.gpl 167 bytes

gp...@googlecode.com

unread,
May 2, 2013, 11:42:18 PM5/2/13
to gp...@googlegroups.com

Comment #3 on issue 103 by fintic...@gmail.com: Gpick generates gpl files
with out of bounds colour-ranges for Krita and Gimp.
http://code.google.com/p/gpick/issues/detail?id=103

Note that the claim made in comment #1 is incorrect -- GPick 0.2.5 does in
fact report the correct version number, and it was my build which was out
of date.
Reply all
Reply to author
Forward
0 new messages