[comp.windows.x] 0, 1, black, white, BlackPixel

mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse) (07/01/89)

>> Since black and white seem to have become synonomous with 0 and 1
>> (or 1 and 0)

> Stomping this out was one of the differences between X10 and X11.
>...
> Applications that presume any particular values for BlackPixel() and
> WhitePixel() are guaranteed to break.

What's almost as annoying is applications that use BlackPixel() and
WhitePixel() directly.  For example, `bitmap'.  I positively loathe
having windows in reverse video, but bitmap uses the WhitePixel of the
screen as its background and the BlackPixel as its foreground, meaning
that short of hacking the server to display the WhitePixel as black and
vice versa, I *can't* get bitmap to use white-on-black.  (In direct
contradiction to the manual page, by the way, which documents -fg and
-bg as working as they ought to.)

Or xmazewar, which comes up white-on-black very nicely but then
displays the mouse cursor as a black shape against a mostly black
window - how *useful*.

(Eventually I got fed up and wrote my own replacement for bitmap, so it
doesn't bother me now except for the sake of poslfit, but perhaps this
will raise some programmers' awareness of the issue....)

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu