Path: utzoo!attcan!uunet!decwrl!mcnc!ncsuvx!news
From: willis@ecovsb.ncsu.edu (Bill Willis)
Newsgroups: comp.windows.x
Subject: Re:  GXxor problems on Xqvss
Message-ID: <1990Nov12.082050@ecovsb.ncsu.edu>
Date: 12 Nov 90 13:24:24 GMT
References: <9011112344.AA21683@Larry.McRCIM.McGill.EDU>
Sender: news@ncsuvx.ncsu.edu (USENET News System)
Reply-To: willis@ecovsb.ncsu.edu (Bill Willis)
Organization: Digital Equipment Corporation
Lines: 28

--
               We have met the enemy, and they are us --- Pogo
In article <9011112344.AA21683@Larry.McRCIM.McGill.EDU>,
mouse@LARRY.MCRCIM.MCGILL.EDU writes:
|> Path: ncsuvx!gatech!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
|> From: mouse@LARRY.MCRCIM.MCGILL.EDU
|> Newsgroups: comp.windows.x
|> Subject: Re:  GXxor problems on Xqvss
|> Message-ID: <9011112344.AA21683@Larry.McRCIM.McGill.EDU>
||> Hmmm.  Okay then, I have another possibility...
|> 
|> Do the qvss and Sun servers use different values for black and white?
|> It's possible the program is doing xor with a foreground value set to
|> (say) black, determined experimentally by the author.  When transported
|> to a server that has (say) black being 0 instead of 1, it breaks....
|> 
|> 					der Mouse
||> 

Yep, they sure do use different values... We ran into that problem in an
application we have been working
on....

Bill Willis, Director                 willis@ecovsa.ncsu.edu
Engineering Computer Operations       willis%ecovsa@ncsuvx.ncsu.edu
Box 7901, School of Engineering
North Carolina State University
(919) 737-2458