On Wed, 2009-02-25 at 11:54 -0700, McDonald, Michael-p7438c wrote:
>
> No problem. I was just trying to make sure you had intended the
> byte_order field to be user accessable. Since the Ximage structure was
> defined, I had assumed yes.
Yes, though that was not really the original intent; the p
> -Original Message-
> From: Jim Gettys [mailto:j...@freedesktop.org]
> Sent: Wednesday, February 25, 2009 11:47 AM
> To: McDonald, Michael-p7438c
> Cc: Pat Kane; xorg@lists.freedesktop.org
> Subject: RE: Ximage's byte_order field
>
> You should be able
, 2009 1:02 PM
> > To: McDonald, Michael-p7438c
> > Subject: Re: Ximage's byte_order field
> >
> > Mike,
> >
> > How is your frame buffer connected to your little endian machine?
>
> It's a shared memory area generated by a COTS software package. A
> -Original Message-
> From: Pat Kane [mailto:pekan...@gmail.com]
> Sent: Friday, February 20, 2009 1:02 PM
> To: McDonald, Michael-p7438c
> Subject: Re: Ximage's byte_order field
>
> Mike,
>
> How is your frame buffer connected to your little endian
McDonald, Michael-p7438c wrote:
> Am I allowed to change the value of the XImage byte_order field? And if
> I do, will subsequent XPutImage() calls do the "right thing"?
Yes, you can change the byte_order field to match the byte order of your
image. XPutImage will take care of swapping your bits a
On Thu, 2009-02-19 at 10:54 -0700, McDonald, Michael-p7438c wrote:
> Am I allowed to change the value of the XImage byte_order field? And if
> I do, will subsequent XPutImage() calls do the "right thing"? Does the
> value of byte_order default to the client's byte order?
The default byte order is
Am I allowed to change the value of the XImage byte_order field? And if
I do, will subsequent XPutImage() calls do the "right thing"? Does the
value of byte_order default to the client's byte order?
I have a memory based frame buffer from another app that I'd like to
use XCreateImage() and XPut
