"Jon M. Taylor" <[EMAIL PROTECTED]> writes:
> On Thu, 2 Nov 2000, [iso-8859-1] Niklas H�glund wrote:
> > At that time I found that using a main loop looking like this does sort of
> > proper double-buffering using GGIMesa. Note that the SetMode call sets the
> > virtual width to twice the physical width.
Why in the world would you want to use SetOrigin to just flip pages
when there's a perfectly good API for handling multiple frames?
> Thanks for the input, but I'm afraid that the "pageflip using
> SetOrigin" hack won't work on all targets.
Neither does normal multiple frames, so?!?
If we'd only support features that works on every piece of hardware
the entire project would fit into an empty file...
*Of course* you should implement back/front buffering by simply
having two separate buffers and switch between them! If that's not
possible with the current target/mode then touch luck, you just have
to fall back to:
> allocate a DirectBuffer or a memory_visual and use that as a
> backbuffer on every target.
I'd like to have a look at this "problem", but yesterday the Mesa
CVS didn't compile at all. :(
//Marcus
--
-------------------------------+------------------------------------
Marcus Sundberg | http://www.stacken.kth.se/~mackan
Royal Institute of Technology | Phone: +46 707 452062
Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
