Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: XCreateImage/XDestroyImage question
Message-ID: <8906191214.AA02626@expire.lcs.mit.edu>
Date: 19 Jun 89 12:14:11 GMT
References: <14737@pasteur.Berkeley.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 13


    I can't say for sure, but
    it sounds like you're making assumptions on the bit/byte ordering of your
    image and when you eventually try to XPutImage this thing to a drawable,
    you might not get what you want if you are talking to an X server on a
    different architecture.

This is incorrect.  XPutImage goes to great pains to handle transformation
from source bit/byte ordering to the server's, and in fact to handle
bits-per-pixel differences.  So long as the depths match, there is nothing
inherently evil with using canned images.  The only tradeoff is that you
will take the transformation cost on every XPutImage call, rather than
once up front.