[compiz] [Mesa3d-dev] The direct/indirect rendering stuff and compiz

Michel Dänzer michel at tungstengraphics.com
Tue Apr 17 03:19:17 PDT 2007

[ Apologies for the late followup, I've been away over the weekend ]

On Fri, 2007-04-13 at 12:17 -0600, Brian Paul wrote:
> Michel Dänzer wrote:
> >
> > I wonder why I didn't get any feedback on my proposal: Make
> > glXQueryExtensionsString take the current context into account when
> > appropriate. Would it be feasible for compiz to make the context current
> > before calling glXQueryExtensionsString?
> I'm hesitant to change the parameters or semantics for 
> glXQueryExtensionsString() since some apps may depend on it working just 
> the way it does.

The spec seems ambiguous about this, or am I missing something? If not,
such apps rely on undocumented behaviour of specific implementations.

Moreover, it would seem odd for an app to force indirect rendering and
rely on not knowing which extensions are really supported then, but I
guess weirdness like that does exist...

> I'd be happier with a new function that queried the GLX extensions 
> supported by the current context.

That sounds fine if the above is really intractable.

> Ian overhauled the extension-related code in GLX a while back and might 
> have extra insight.  I haven't looked at this stuff in years.  Ian?

Indeed, I'm very interested in hearing his opinion as well.

Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer

More information about the compiz mailing list