"Jon M. Taylor" <[EMAIL PROTECTED]> writes:
> On 3 Nov 2000, Marcus Sundberg wrote:
>
> > "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?
>
> QuickHack.
Requesting multiple frames properly is much quicker to implement
and works on more targets.
> > > 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?!?
>
> So the point was to find a QH which would always enable
> doublebuffering on all targets, no matter the inefficiency. Lots of GL
> code requires doublebuffering.
Sure, I'm not arguing against the reason for the original malloc()
hack. I just find the current discussion about how to fix things
strange, when there is exactly one obviously correct way to do it.
> > I'd like to have a look at this "problem", but yesterday the Mesa
> > CVS didn't compile at all. :(
>
> Yeah, they chose yesterday to add a whole new separated software
> rasterizer cut-in layer to Mesa CVS |-/. I wish Brian had decided to keep
> that stuff in the 3.5 branch only - kind of odd, when he said that he
> wanted to release 3.4 a few days ago....
Ah well, hope it will start working again soon then...
//Marcus
--
-------------------------------+------------------------------------
Marcus Sundberg | http://www.stacken.kth.se/~mackan
Royal Institute of Technology | Phone: +46 707 452062
Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
