On 11/26/14 9:47 AM, Nathan Kidd wrote: >> 1) just disallow any non-3D-server GLX traffic, and loose the >> VGL_PROBEGLX benefits. Hmmm, this looks like it kills the possibility >> of stereo support, though I've never seen a stereo user. >> >> 2) Introduce a global (TLS-based should work) don't-fake-xcb-for-now >> flag that the VGL_PROBEGLX code sets and the XCB hooks honour. > > Simplifying a little, if VGL is preloaded then there is no way for an > application to ever use the 2D server for GLX, apart from rolling their > own protocol which isn't supported anyway. > > There is just one specific instance, the VGL_PROBEGLX code, that will > ever use GLX on the 2D server. If we called buildVisAttribTable() from > XOpenDisplay (and later, if more support is added, from xcb_connect()) > then we could use a per-connection flag like you suggested, and we'd be > guaranteed to be thread safe since we didn't return the > connection/Display handle yet. > > Did I miss something?
Overlays, as you pointed out, but also, the table that buildVisAttribTable() builds is screen-dependent. If the application is switching screens, then the attribute table has to be rebuilt every time the switch happens. NOTE: This is really not a very clean solution. It would be better to cache a separate table for each active screen. But in either case, that's why it isn't prudent to build the table within the body of XOpenDisplay(). ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ VirtualGL-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
