On 2/20/12 1:43 AM, Arthur Huillet wrote: >> Cool. If they can establish that it's something we're doing wrong, I am >> of course keen to fix it. It would just take a lot of me futzing with >> the app to discover what that might be, and they're in a better position >> to do that. Keep me posted. > > Just a suggestion: the apitrace tool could help you figure out what the > application is trying to do. You'd see all the GL calls it does and would be > able to copy paste them in a test program.
I have many tricks up my sleeve, but the time is not really the issue. It's the unpaid time. :) My only source of income is open source sponsorships, support contracts, and funded development. I have only 200 hours a year to use on general project development, that is, on fixing minor issues and doing releases and non-sexy stuff like build system overhauls that no one wants to specifically pay for. Realistically, the needs of VirtualGL and TurboVNC take about double that (I really need more general sponsors.) Thus, I have to really budget what I am able to contribute to the project for free, and that means that I am not generally going to be able to spend a lot of time diagnosing/fixing commercial apps unless the work is sponsored or unless the issue is something I believe to have a very broad impact. ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users