On 11-11-29 05:47 PM, DRC wrote: > I'm fine with implementing the patch. Just mainly wanted your feedback > on it. What do you think of the more long-term proposal to fake > XGet/MatchVisualInfo()?
I haven't thought too far through this, but to make an app that uses glXGetConfig to choose its own visual do the right thing we must make the app see a variety of visuals. If the server only has one visual, then, as I understand your direction of thought, we fake the XGet/MatchVisualInfo to list as many visuals as we want, and populate them with the local opengl attribs. To do this we need to make up fake visual IDs. The moment we give a fake visid to the app we have no control what it does with it. This ID will get used in the whole Xlib api. Any call that sends the visid must be hooked to do the translation to a real visid, and any reply back must also be hooked, again for translation. I didn't look exaustively, but I think that's a whole lot of APIs to hook. If we consider going down the road XCB will likely need to be supported I think it will only get more complex. Now, I haven't done my grepping to get hard numbers on how many places need hooks; maybe it isn't as bad as I'm imagining, but that's my initial reaction. -Nathan ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
