nanogui: regarding banner


Previous by date: 31 Jan 2006 15:40:08 +0000 Re: Images not drawn (FLTK+nxlib app with nano-X), Greg Haerr
Next by date: 31 Jan 2006 15:40:08 +0000 Re: segmentation fault, Greg Haerr
Previous in thread: 31 Jan 2006 15:40:08 +0000 regarding banner, sai baba
Next in thread:

Subject: Re: [nanogui] regarding banner
From: "Greg Haerr" ####@####.####
Date: 31 Jan 2006 15:40:08 +0000
Message-Id: <045201c6267c$9ad02410$6401a8c0@winXP>

: i implemented banner application based on your idea of
: 2 buffers.one problem i have is during loading of the
: image banners stops on the screen for moment and then
: moves how to solve this problem

I'm not sure yet whether the delay is a slow processor
in decoding the image again each time, or whether its
as your suggesting, slow in transferring image data.
Since all image decoding is done in the server,
its not likely slow in transferring data, unless you're
doing the decoding in the client.



: can i use shared
: memory for the offscreen buffers.if yes can u give me
: some idea how to do.

If you set HAVESHAREDMEM, then nano-X will use 
shared memory for all buffered commands (including data
for GrArea image data) from client to server.  Remember
that all nano-X image decoding occurs in the server anyway,
so this won't probably help.

If you really need to write offscreen buffers directly
from the client (which would likely only be the case
when otherwise using GrArea), then you'd need to
implement the third parameter to GrNewPixmap,
and send a shared memory address to the server
for the pixmap.

Regards,

Greg


Previous by date: 31 Jan 2006 15:40:08 +0000 Re: Images not drawn (FLTK+nxlib app with nano-X), Greg Haerr
Next by date: 31 Jan 2006 15:40:08 +0000 Re: segmentation fault, Greg Haerr
Previous in thread: 31 Jan 2006 15:40:08 +0000 regarding banner, sai baba
Next in thread:


Powered by ezmlm-browse 0.20.