On Thu, 4 Dec 2003, Callum Prentice wrote:
I think you've misinterpreted this. Aside from corruption of
the ximage data structure, the only time BadValue is returned
is if your source rectangle passed to XShmPutImage lies outside
of the XImage (or if you pass junk for the send_event).
that's the conclusion i came to late last night too.
now, for each of my XImage helper class instances, i declare a XShmSegmentInfo* in the
ctor
and point it to a new'd buffer so it hangs until the class dtor gets rid of it as my
app is
ending.
seems to work okay for now.
Looking through
i have a methods in a class to create a shared memory x image - it creates and stores
an
xImage in the usual way:
XShmSegmentInfo shminfo;
ximage = XShmCreateImage(..., shminfo);
shminfo.shmid = shmget (.., ximage-height * ximage-bytes_per_line, ...);
shminfo.shmaddr = ximage-data =
On Thu, 4 Dec 2003, Callum Prentice wrote:
i have a methods in a class to create a shared memory x image - it creates and
stores an
xImage in the usual way:
XShmSegmentInfo shminfo;
ximage = XShmCreateImage(..., shminfo);
shminfo.shmid = shmget (.., ximage-height * ximage-bytes_per_line,
I think you've misinterpreted this. Aside from corruption of
the ximage data structure, the only time BadValue is returned
is if your source rectangle passed to XShmPutImage lies outside
of the XImage (or if you pass junk for the send_event). Check
your dimensions passed to XShmPutImage.
5 matches
Mail list logo
