Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4451
------- Additional Comments From [EMAIL PROTECTED] 2005-09-15 01:13 -------
(In reply to comment #4)
> > > [...] but the code as-is seems to be specifically designed so it can
> > > handle
> > > the case when pfCurrentPage stays at 1 and buffer swapping happens.
> >
> > Sure, it can handle it, but it's far from ideal nonetheless.
> Well I just guessed there's a reason things are handled that way :-)
If you think about what would happen if the X server decided to do a pageflip
(rather than the application doing one), it should be clear - you'd end up on
page 0, sure, but there would be a half-rendered scene in what the application
thought was the backbuffer.
You could jump through all sorts of hoops trying to get things to work out -
perhaps tell the app to abandon that frame, generate expose events to make sure
that it really is rendering a new frame. Or backcopy the old frontbuffer over
the top of what was the backbuffer, etc. In short it would be a mess.
The only real choice is to leave pageflipping to the application and have the X
server and everybody else deal with the possibility that you might end up on
page 1 after a session of flipping.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
