Bug 330471 - Color selectors not locking properly.
Summary: Color selectors not locking properly.
Status: RESOLVED DUPLICATE of bug 317648
Alias: None
Product: krita
Classification: Applications
Component: Color Selectors (show other bugs)
Version: 2.8 Beta
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-27 15:51 UTC by Eli Vasquez
Modified: 2014-01-28 11:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eli Vasquez 2014-01-27 15:51:17 UTC
I've noticed that there is a lot of movement in the hue slider of the color selectors when changing the color within the triangle/square. The same is true of the inside of the color selector in the less saturated range while changing the hue. If you move the circle within the selector around enough it will stop at certain points (six points from what I saw) and finally lock. I've tested this at different bit rates in hopes that it would help but the result was the same. This makes it very difficult to select the exact color wanted as the hue is constantly randomly jumping around.

Thanks for looking into it.

Reproducible: Always

Steps to Reproduce:
1. Create a new document.
2. Change the hue (even just a bit).
3. Start changing the color from within the main portion of the color selector.
4. Notice how the hue is changing as well.
5. Keeping moving the circle within the selector.
6. Eventually the hue slider will decide to settle and lock at one of six points from my observation (red, yellow, green, cyan, blue, magenta). 
Actual Results:  
The hue slider ends up locking at one of six points but will move every time the slider is not at one of these six points.

Expected Results:  
I would imagine that the hue slider is not suppose to move while choosing color when the hue slider isn't being used.
Comment 1 Halla Rempt 2014-01-28 11:33:37 UTC

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