hexcolour text control box at palette window

[GoogleCodeExporter]

from the palette window we can only adjust colours from sliders - this would 
be hugelly helped if we can have a text control box for writing or 
copy/pasting from the clipboard - for example, when we pick a colour from 
gcolor2, we get a hexcolour like #FAA342 (like picking colours from 
colourlovers.com, for example, or anywere else) , and it's very hard to 
paste it inside grafx2... :(

Original issue reported on code.google.com by nitrofur...@gmail.com on 26 Jan 2010 at 2:08

[GoogleCodeExporter]

Copypaste will never work inside GrafX2, as far as I know, as we are using 
custom 
SDL widgets for everything.
The space in the palette screen is very limited and I don't think we can add 
more 
things to it...

Original comment by pulkoma...@gmail.com on 26 Jan 2010 at 7:59

[GoogleCodeExporter]

Original comment by pulkoma...@gmail.com on 27 Jan 2010 at 12:41

• Added labels: Milestone-NotPlanned, OpSys-All, Priority-Low, Type-Enhancement
• Removed labels: OpSys-, Priority-Medium, Type-Defect

[GoogleCodeExporter]

besides there is not clipboard support on Grafx2, the rearrangement of colour 
sliders
in horizontal instead of vertical, maybe would provide more space for the 
hexcolour
text control, or reducing the size of 'color number:' to 'color id', or alike, 
would
surelly give more room to a hexcolour text field - an user having also this 
hexcolour
text field available would surelly hugelly help on their artwork productivity, 
which
i think is hugelly welcome! :)

Original comment by nitrofur...@gmail.com on 27 Jan 2010 at 1:07

[GoogleCodeExporter]

I'd relate this to issue 240 where I proposed a Copy and Paste function in 
palette.
This could use the clipboard and store/parse the colors as a series of "#RRGGBB"
strings. For this issue, you could cut such string in any application, and when 
you
Ctrl-V in the Palette, the current color would receive the RGB value.

Clipboard is easy on Windows but tricky on Linux: to avoid dependencies on Qt or
anytyhing, it seems I could use system() to run "dcop klipper" (KDE) or "xsel" 
(X11)

Original comment by yrizoud on 27 Jan 2010 at 1:27

[GoogleCodeExporter]

kde depends on Qt.
There is an X aPI to do it under linux (that won't work on the GP2X as there's 
no X) 
that should be fine. Here is the spec : 
http://tronche.com/gui/x/icccm/sec-2.html

Note we already depend on X for ttf fonts listing, so using that should be fine.

Original comment by pulkoma...@gmail.com on 27 Jan 2010 at 4:55

[GoogleCodeExporter]

Issue 308 has been merged into this issue.

Original comment by yrizoud on 2 Feb 2010 at 1:21

[GoogleCodeExporter]

I looked a bit more at the palette screen, and it's definitely impossible to 
add more buttons to it. Most of the existing ones already use short names that 
are barely readable.
I think the best solution is to have two "views" in the palette screen :
 * One with buttons to edit colors,
 * The other with info such as the used count, the current color id and pixelcount, ...
And a small widget on the side to switch between these modes. The keyboard 
shortcuts would always work, so experimented users would likely keep the 
"status info", while beginners would prefer the buttons at hand.

Others ideas about that ?

Original comment by pulkoma...@gmail.com on 14 Jun 2010 at 6:04

[GoogleCodeExporter]

I had made tests with "hierarchical" menu buttons, but I really didn't like the 
result. (It was hiding many buttons at all times)

Current color # is pretty important every time.
By the way, "Color number:" can probably be shortened as "Current:", it avoids 
mistaking it with a "number of colors".

I think the global "Used : N" can be moved to histogram.
Histogram screen is still pretty basic, If it allowed the user to select ranges 
and then see color numbers and number of pixels, it would free up that much 
space in main screen. I'll try a mockup.

Original comment by yrizoud on 14 Jun 2010 at 7:18

[GoogleCodeExporter]

"Used:N" is helpful because of the "Reduce" button, even if they are not so 
near anymore in the current screen (they were in the beta96.5).
But moving things to the histogram window sounds like a good idea.
Not sure about selecting ranges, because the colors may be as small as 1px 
wide, in a 320x200 screen, and that's not really selectable. But for global 
operations like reduce it makes sense.

Original comment by pulkoma...@gmail.com on 14 Jun 2010 at 7:21

[GoogleCodeExporter]

Ok, I don't know what's possible with input - but here's an idea for a layout:

Original comment by annas...@hotmail.com on 14 Jun 2010 at 8:00

Attachments:

• pal.png

[GoogleCodeExporter]

Color # is larger when you select a range of colors, it displays things like 
"210>255". But maybe we can use the small font here too ?

Original comment by pulkoma...@gmail.com on 14 Jun 2010 at 8:05

[GoogleCodeExporter]

Move Color# to the left and there is room for the 7 chars in xxx-xxx, even with 
the "big" font I think?

Original comment by annas...@hotmail.com on 14 Jun 2010 at 8:15

[GoogleCodeExporter]

I agree that the displayed numerical RGB values could double as input boxes. 
What would be neat is if it were possible to paste a RRGGBB string in such a 
manner that all three are filed at once. Similar to pasting a serial number for 
commercial software, extra digits would 'spill' from one input field to the 
next.

Original comment by ilija.melentijevic on 14 Jun 2010 at 8:40

[GoogleCodeExporter]

AFAIK, the only usual input is RRGGBB in hexa, allowing both upper and lower 
letters.

Here's a screenshot: It keeps all current functions, except the display of 
pixel count, that I'd move to the histogram (that you would open using the 
'Used:xxx' button)
"HSV" is obtained by clicking directly above the sliders.

Original comment by yrizoud on 19 Jun 2010 at 5:29

Attachments:

• pal.gif

[GoogleCodeExporter]

Solid idea.

Original comment by ilija.melentijevic on 19 Jun 2010 at 5:38

[GoogleCodeExporter]

The "used" count was useful in this screen to quickly see if a color is used at 
all. But this mockup looks a lot more readable, so, go for it!

Original comment by pulkoma...@gmail.com on 19 Jun 2010 at 6:12

[GoogleCodeExporter]

An idea: When you hover the mouse on the area with the buttons Used / Zap 
unused / Reduce, it could highlight the used colors : Display a white mark on 
the left of each color that is used. This display should coexist with the 
selection marker, because even when the mouse is away you can hit the next/prev 
color hotkeys to move the selection marker.

Original comment by yrizoud on 21 Jun 2010 at 9:33

[GoogleCodeExporter]

I like that. Having a direct overview of how the palette is used would be 
powerful and a timesaver.

Original comment by annas...@hotmail.com on 21 Jun 2010 at 12:55

[GoogleCodeExporter]

The input is possible as of r1523. Still have to:
- do something when user enter dummy value... or not? 0 characters is like 
cancel; but 1,2, 4 or 5 characters are user error, Grafx2 silently ignores it.
- Implement the 'used colors' indicators
- Improve the Histogram screen.

Original comment by yrizoud on 24 Jun 2010 at 11:59

• Changed state: Started
• Added labels: Milestone-2.3
• Removed labels: Milestone-NotPlanned

[GoogleCodeExporter]

Small update/display bug of the colors-used number after a reduce.

Original comment by annas...@hotmail.com on 29 Jun 2010 at 3:07

Attachments:

• palbug.png

[GoogleCodeExporter]

Thanks, fixed now.
I tested with hover, but these symbols that appear and disappear are painful 
when what you want to do is "stack" the used colors together. In r1526, I made 
the Used button toggle the usage markers on/off. Right-clicking the button 
calls the histogram. This is temporary, until I find a better idea.

Original comment by yrizoud on 29 Jun 2010 at 11:36

[GoogleCodeExporter]

Original comment by pulkoma...@gmail.com on 9 Aug 2010 at 9:40

• Added labels: Component-GUI

[GoogleCodeExporter]

Original comment by pulkoma...@gmail.com on 22 Aug 2010 at 1:34

• Added labels: Milestone-2.4

[GoogleCodeExporter]

This was completed a few months ago.

Original comment by yrizoud on 18 Jan 2011 at 7:49

• Changed state: Fixed
• Added labels: Milestone-2.3
• Removed labels: Milestone-2.4