Hi,
On Thu, 20 Nov 2003, Mark Vojkovich wrote:
Current XAA only supports rendering to a single surface where the
location to draw at is indicated by pDrawable-x and pDrawable-y.
Yeah, I figured that too after staring at the xaa sources for a day ;-)
Hmm.
It doesn't know anything about
Optimally this would be done completely with OpenGL using pbuffers and
texture hardware.
Alex
--- Mark Vojkovich [EMAIL PROTECTED] wrote:
Current XAA only supports rendering to a single surface where the
location to draw at is indicated by pDrawable-x and pDrawable-y.
It doesn't know
On Fri, Nov 21, 2003 at 10:09:11AM -0800, Alex Deucher wrote:
| Optimally this would be done completely with OpenGL using pbuffers and
| texture hardware.
It's also worthwhile to remember that using OpenGL buys you a lot of
other functionality that otherwise you'd have to reinvent -- things like
Hi,
[please leave me CC'ed, I'm not (yet?) subscribed to this list]
I ported over Keith Packards new extensions (COMPOSITE and DAMAGE) from
the freedesktop Xserver to Xfree86, which seems to have worked more or
less. See http://ktown.kde.org/~matz/BuntX.png which shows XFree86 on a
mga card,
Current XAA only supports rendering to a single surface where the
location to draw at is indicated by pDrawable-x and pDrawable-y.
It doesn't know anything about alternate storage locations for windows.
And it probably blows all the GC validation out of the water because
drawables that it
