On Mar 6, 2013, at 10:42 AM, Arshdeep Singh wrote:

Regarding the bug: I found the piece of code that handles the CMYK values to be scaled as [0,1]. Now making a change to scale values in [0,1]-->[0,100] (though mentioned as a more industry friendly standard) shall require changes to generic codes which also handle the CMS sliders of RGB Color profiles. Also, the interconversions b/w floats of [0,1] to rounded of integers in [0,100] shall cause some loss of accuracy as well.

Can people who are more experienced in the designing fields be brought together for poll ? If many people want this change, I am up for tweaking the source file in question. Pardon my audacious attempt of suggesting an idea of taking a vote, but in my respect it does seem important.

PS: For the more experienced developers, am I right in thinking that the scaling will cause a loss of accuracy ?

Thankyou for the help.

I don't have the bug number off hand, but I do know that this came up in regards to the HSL values, etc.

The main problem is that the simple ways to solve this cause color jumping and/or noticeable loss of accuracy.

The main point would be to avoid integer slider values. You can set up labels to show as integers but on a float range (or in C/C++ terms we want to stick with double).

In general it is possible to change the UI appearance without affecting the data as it is currently stored.