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 =
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.
by looking up pixmap formats, but it's
easier to just have XShmCreateImage fill it in for you.
Mark.
On Mon, 3 Nov 2003, Callum Prentice wrote:
1) Does your X-server have SHM support? MIT-SHM should show up in
the list of extensions reported
i'm attempting to put together a simple test that creates a window, allocates a buffer
in
memory and using an XImage and XShmPutImage () displays it on my screen.
i have a tiny piece of code that (as far as i know) does all the right things - it
creates the
window but when i try to display the
i'm attempting to put together a simple test that creates a window, allocates a buffer
in
memory and using an XImage and XShmPutImage () displays it on my screen.
i have a tiny piece of code that (as far as i know) does all the right things - it
creates the
window but when i try to display the
1) Does your X-server have SHM support? MIT-SHM should show up in
the list of extensions reported by xdpyinfo.
Yep - that extension is listed when i run xdpyinfo.
2) Does your operating system have SHM support? This sort of thing
is often disabled for security reasons.
i'm
7 matches
Mail list logo
