brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

glx: Clarify *why* we need the dummy window

Browse Source 
The reason why we have a dummy, offscreen Window when we create the
GLX context is that GLX does not like it when you ask the context for
features if it's not made current to a Drawable. Maybe in the future
it will allow us to do so, but right now we have to make do with what
GLX offers us.
This commit is contained in:
Emmanuele Bassi 2010-02-04 13:59:39 +00:00
parent ea5e33cf3a
commit 466b00a806
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
clutter/glx/clutter-backend-glx.c
View File

@ -519,6 +519,12 @@ clutter_backend_glx_create_context (ClutterBackend *backend,
* to make sure that a GLX context exists and is made current, we use * to make sure that a GLX context exists and is made current, we use
* a dummy, offscreen override-redirect window to which we can always * a dummy, offscreen override-redirect window to which we can always
* fall back if no stage is available * fall back if no stage is available
*
* XXX - we need to do this dance because GLX does not allow creating
* a context and querying it for basic information (even the function
* pointers) unless it's made current to a real Drawable. it should be
* possible to avoid this in future releases of Mesa and X11, but right
* now this is the best solution available.
*/ */
xvisinfo = glXGetVisualFromFBConfig (xdisplay, config); xvisinfo = glXGetVisualFromFBConfig (xdisplay, config);
if (xvisinfo == None) if (xvisinfo == None)