Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: XImages
Message-ID: <9012172158.AA07950@expire.lcs.mit.edu>
Date: 17 Dec 90 21:58:31 GMT
References: <935@attc.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 14


   Than how do you explain that the Sun's Open Windows (2.0) server and
   DECwidnows(Ultrix or VMS) servers report oposite ImageByteOrder, but the 
   first *byte* in returned image (accessed as (char*))is my pixel[0,0] for 
   both servers ?

Stop, do not pass Go, Contemplate for a long time.  Take a look at the
table that's embedded in comments in mit/lib/X/XPutImage.  Study it.
Convince yourself of its correctness (or incorrectness, I recall someone
has submitted a bug report on part of it).  Perhaps then you will attain
enlightenment. :-)  Image formats are a tricky business.  So tricky, that
in the X10 Sun server images got bytes reversed *twice*, even though they
didn't really need to get reversed at all)!  Since it took us at least 11
times around to understand that, don't be worried if it takes you a while. :-)