|T O P I C R E V I E W
||Posted - 12/16/2000 : 9:42:18 PM
When screen is set for 256 colors, then the custom color dialog box does all kinds of crazy things.
It returns colors that don't match what you selected, and the little preview window displays the wrong
color, often close to black, and when you've closed it, the color showing in the main picker reflects
RGB values (in the box that shows up when you put the mouse over it) that are quite different.
Obviously the code is not designed for the color table used in 256-mode.
Any more information you can supply about this? E.g., is a fix planned? How do I go about disabling
this button only when in 256-mode?
BTW, I have my program hide the mouse cursor when user starts typing, and redisplay it when the mouse is moved.
It's standard practice to keep mouse cursor from getting in the way of the typing.
But when detached color picker (or any toolbar) is where the mouse was last used, I don't seem
to be receiving the mouse-moved messages. So the mouse doesn't re-appear, which is very confusing, since
the only way to tell which button you'll get is by the highlighting it performs when the mouse floats
I didn't have this problem with standard windows toolbars only with BCG.
I may come up with my own solution, but if you have a quick answer, I'd appreciate it.
|2 L A T E S T R E P L I E S (Newest First)
||Posted - 12/19/2000 : 9:26:47 PM
Yes, please do send. And see my e-mail to firstname.lastname@example.org for details.
||Posted - 12/18/2000 : 12:21:48 PM
Yes, you're right: there is a problem with the color-picker in 256-colors mode. The fix will be available in the next library release. If you would like to get an updated files now, please let us know and you'll send you patch by e-mail.
Regarding mouse events. Please check, that you call all "default" mouse events properly (e.g., if you've you own PreTranslateMessage or OnMouseMove, the parent event is celled always).