nanogui: How pixmaps will work


Previous by date: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Greg Haerr
Next by date: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Vidar Hokstad
Previous in thread: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Greg Haerr
Next in thread: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Vidar Hokstad

Subject: RE: How pixmaps will work
From: Greg Haerr ####@####.####
Date: 15 Oct 1999 19:16:51 -0000
Message-Id: <796896539E6CD311B0E70060083DFEFB033E0E@NBA-SLAM.CenSoft.COM>

: I was referring more to the time/space tradeoff.  Keeping bitmaps
offscreen
: will require more memory, doing redraws will require more CPUs.  This
: decision is more important in embedded systems than in larger machines.

In both the X and MSWindows models, there are drawing methods that
allow either way to be used by the application programmer.  That's exactly
the point, in that a programmer can pick which method they prefer.  Now, 
in some situations, an offscreen draw is required to prevent flicker.  Also,
there are cases when a window wants to have "savebits" for the its'
contents,
maintained without the need to generate paint/expose events.  At this point,
I am implementing just the base level offscreen draw capability, which will
be required no matter which direction the engine or api's go.

Greg

Previous by date: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Greg Haerr
Next by date: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Vidar Hokstad
Previous in thread: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Greg Haerr
Next in thread: 15 Oct 1999 19:16:51 -0000 Re: How pixmaps will work, Vidar Hokstad


Powered by ezmlm-browse 0.20.