I tackled MS about their color inconsistency with typing in the value sto the color wheel ( likewhen you use Fill with color or texture > More solid colours). Below is the correspondance for those that are interested in how to work out the problem.

>>> Here's the info you requested, I hope it's useful:
>>>
>>> ===
>>> The Windows color palette, which is what the user first refers to, uses
>>> the HSL model where H, S, and L (Hue, Saturation, and Luminosity) all
>>> have ranges from 0 to 240 (Hue goes from 0 to 239, but that is because 0
>>> and 240 are the same Hue).
>>>
>>> This model differs Slightly from the HSB model (Hue, Saturation,
>>> Brightness). In this model, Hue has a range of 0 to 359 which
>>> represents the 360 degrees available in the color wheel. Saturation and
>>> Brightness have values ranging from 0 to 100 which are basically
>>> percentage measures.
>>>
>>> To map Hue from the HSL color space (found in the color palette) to the
>>> HSB color space (found in tasks such as 'Change Hue') in Digital Image
>>> Pro, the user can do the following:
>>>
>>> Take the H value from HSL and multiply by 1.5.
>>> Subtract the result from 360.
>>>
>>> Example: Magenta has RGB values of (255,0,255) and HSL values of
>>> (200,240,120). To find the same Hue value in the 'Change Hue' task, one
>>> would do the following calculation: 360-(200*1.5)=60.
>>> ===
>>>
>>> --
>>>
>>> John Inzer
>>> MS Picture It! MVP
>>>
Hi John
>> I appreciate you getting that information however ...
>> Can you ask the team then why when you use a color chart as a reference,
>> while if you type in the RGB code you get the right color but if you type
>> in
>> the equivelent HSL code or the HSB code the colors are completely wrong?
>> I have tried this tool http://www.carto.net/help/netscape_colorpicker/ as
>> well as a couple of other color charts i have found on the web that show
>> RGB
>> values and their equivelents and while the RGB code gives accurate color
>> representation the HSl and HSB values don't which means i must always
>> start
>> with the RGB value, to get the HSl values , perform the calculation which
>> still only gives me the Hue and I would still have to guess the correct S
>> and
>> B values.
>> Do the team have some sort of color chart they can make available or
>> recommend or explain how to resolve the whole thing other than wait for
>> the
>> next version lol.
>> I work extensively with DIP and have since PI 99. I do not have the
>> technical programming understanding but i certainly have the experience
>> as a
>> user given that i also teach classes on using DIP and have written the
>> largest tutorial collection regarding DIP on the web
>> http://scrapbook-bytes.com/cgi-scrip...index_25.shtml
>> I'm frustrated with these type of anomalies - not you John You are
>> awesome Any info you can get for me would be appreciated
>>
>> "John Inzer" wrote:

Shelleyrae asks some fantastic questions below. What it all boils down
to is that there are some inconsistencies in the way applications
describe color spaces, especially HSL and HSB. I would advise users to
use the RGB color space whenever they can, as that is the one color
space that every application is consistent with.

The inconsistency in our application is what I had mentioned in my
previous email. Our status bar uses the Windows HSL color model, which
maps H, S, and L to ranges of 0 to 240. Unfortunately, this is
inconsistent with other HSL models which map H to the color wheel (0 to
360), and S and L to percentages (0 to 100).

However, using HSB is a more intuitive way to select colors than using
RGB. We use the HSB model in tasks such as 'Change Hue' and 'Fill with
Texture or Color.' Shellyrae can use the tool she mentions below to
convert RGB to HSB. The only difference is the Hue is reversed in our
application. So let's say she wants pure yellow, which has RGB values
of (255, 255, 0). The HSB values will be (60, 100, 100). In our app,
you have to subtract the Hue from 360 (since it's reversed) to get the
right color, so you would use (300, 100, 100) to get pure yellow.

In short, I recommend that she use the RBG space because that color
space has the most consistent implementation across the board. In the
meantime, we're working on standardizing the way we expose HSB and HSL.

__________________
see my gallery here My Gallery!
Need help with your program? Check out the new Tutorials!

Sign Up for the FREE Newsletter!

This is very interesting. Looks like they are well aware of this inconsistency - but why the heck aren't they changing it? I'd love to see maybe a DIP10.1 or DIP11 that uses only the RGB model throughout the entire program with maybe HSB as an secondary option.

__________________
Jana
Please visit my gallery.