Kristian Høgsberg <k...@bitplanet.net> writes: > On Mon, Feb 8, 2010 at 1:25 PM, Francisco Jerez <curroje...@riseup.net> wrote: >> The spec says (regarding glXCreateWindow): "If there is already a >> GLXFBConfig associated with win (as a result of a previous >> glXCreateWindow call), then a BadAlloc error is generated.". It will >> also come useful to implement DRI2InvalidateBuffers for the indirect >> case. > > Can you just use the existing __glXDrawableRes for tracking this? > I don't think so. To implement DRI2InvalidateBuffers we need a way to map an X11 window to its GLX window: In the GLX1.3 world the client decides the IDs of its GLX drawables so in general GLX and X11 drawable IDs aren't going to be the same.
> cheers, > Kristian
pgpyicwY7Peai.pgp
Description: PGP signature
------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com
_______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
