1. Win32Lib: color constants
On Mon, 2 Oct 2000 13:44:02 -0400, I wrote:
>Because, if I run my flood fill demo in 16-bit color, I get dithered
>remnants of the previous color, meaning that (127,0,0), (0,127,0), etc. are
>not 'pure' colors. If they were defined with 128 instead of 127, there
>would be no dithering in 16-bit color (they would be pure colors) and my
>demo would work 'properly' (i.e. there would be no dithered remnants left
>over). Follow?
On the other hand, this seems to be a platform and/or system specific
issue. This was the behavior I was seeing on my Win98 system at home. I
am not seeing the same problem on my Win2000 system at work. Oh well...
that's windows for ya.
-- Brian
2. Re: Win32Lib: color constants
>>Because, if I run my flood fill demo in 16-bit color, I get dithered
>>remnants of the previous color, meaning that (127,0,0),
>(0,127,0), etc. are
>>not 'pure' colors. If they were defined with 128 instead of 127, there
>>would be no dithering in 16-bit color (they would be pure colors) and my
>>demo would work 'properly' (i.e. there would be no dithered remnants left
>>over). Follow?
>
>On the other hand, this seems to be a platform and/or system specific
>issue. This was the behavior I was seeing on my Win98 system at home. I
>am not seeing the same problem on my Win2000 system at work. Oh well...
>that's windows for ya.
It may be influenced by the video driver as well. But in any case, I'll
change win32lib. As a "special", I just might include a "htmlcolor.ew" file
with the next release. This gives names and RGB values for each of the
defined HTML colors.
-----
cheers,
Derek Parnell
