Issue 100 in aseprite: Hue is lost when either saturation or brightness is brought to 0, then brought back up.

[asep...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Bug Priority-Medium

New issue 100 by kirby...@gmail.com: Hue is lost when either saturation or
brightness is brought to 0, then brought back up.
http://code.google.com/p/aseprite/issues/detail?id=100

What steps will reproduce the problem?
1.Pick any hue value that's not 0 (Pure red).
2. Take saturation or brightness to 0.
3. Move saturation or brightness to any number that's not 0.

The visual hue of the color will be 0 (Pure red). If the hue slider is not
reclicked after this change, the hue of the color is set to 0 upon closing
the palette editor.

What is the expected output? What do you see instead?
When saturation or brightness is restored from 0, the color should match
the selected HSB values rather than red.

What version of the product are you using? On what operating system?
ASEprite 0.9.1, Windows Vista

Please provide any additional information below.
N/A

[asep...@googlecode.com]

Updates:
Status: Accepted
Owner: davidcapello
Labels: -Priority-Medium Priority-High Milestone-0.9

Comment #1 on issue 100 by davidcapello: Hue is lost when either saturation

or brightness is brought to 0, then brought back up.
http://code.google.com/p/aseprite/issues/detail?id=100

(No comment was entered for this change.)

[asep...@googlecode.com]

Updates:
Status: Fixed

Comment #2 on issue 100 by davidcapello: Hue is lost when either saturation

or brightness is brought to 0, then brought back up.
http://code.google.com/p/aseprite/issues/detail?id=100

Fixed in commit 5e94f9193cc2c186519c38af80fec673102bf9ab:
https://github.com/dacap/aseprite/commit/5e94f9193cc2c186519c38af80fec673102bf9ab