>>>
>>>Given how many people have some form of colorblindness, it's generally not a good idea to use only color to show something. There should be another way to determine the meaning, whether it's text alongside, a tooltip, or something else.
>>>
>>>Tamar
>>
>>Colour-blindness as such is rare. Most is a red - green problem, but not full blindness. So, since I have a problem with red only let me tell you.
>>
>>I can see most "red". Only some combinations are invisible. So red fruits in green leaves will not jump in my eyes. An other bad example is this web site. The little numbers on top switch from black to a red-like colour. I had a row with Michel, because he was all the time talking about it. To me this is all black. The f.. black on brown text. The highlighted nodes in the tree I can see, they are large enough. (The impression is more bold-odd vs thin black). So red on brown, shades of brown or lilac. Red/lilac wires are the best.
>>DynamicBack just RGB(255,0,0) by foreground (0,0,0) I can not read. I need a "lighter" red - what I normally use in my programs.
>>
>>The trick is as simple: All DynamicBack colours could be changed by user. We never had somebody full colour blind. And even then there are many shades of grey, something a colour blind one is usually good in. Guess why my first task on GoFish was a mimic to change colours.
>
>Allowing user customization is a good idea, but even better to use both color and something else, so users don't have to make the change. My experience is that most users won't customize most stuff.
>
>Tamar

I see your point. Only if you have 8 colours, it means eight columns more. Most of them more HEADER then VALUE. The idea was to have lesser columns. Or the user moves them out of sight. Customer skipped this approach long time ago.

Lutz