Committed with modifications (MatchConfig() and MatchVisual() failures remain fatal, and also I made it so that the invalid arguments will appear in the tracing output, thus making them easier to pinpoint in cases where the app doesn't check the return value.) Your test app should work correctly now.
On 5/13/11 12:11 PM, Nathan Kidd wrote: > Rather than ripping out the rug from under the user, worst-case the app > doesn't draw correctly but at least the user has a chance to save. The > trace logs will still give necessary info to know something went wrong. > > This is the logical follow-up to the previous patch. Given enough time, > I suggest an app that triggers one of these cases will be encountered. > While we don't want to start baby-sitting bad applications, we should at > least be as lenient as other known GL drivers. > > -Nathan > > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > > > > _______________________________________________ > VirtualGL-Devel mailing list > VirtualGL-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtualgl-devel ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
