This is such a hard problem...there's no simple solution, and people
have been thinking about it for over ten years.
I'd advise against a configuration file that chooses conformance or
performance on a feature-by-feature basis, for at least these reasons:
Sometimes you need to choose conformance or performance
dynamically, or at least on a per-context basis, rather than for
an entire installation or application.
There are a *lot* of potential configuration options. If it's
hard for the app developer to figure out which ones to use, just
imagine how much harder it is for an end user to figure out
which ones to use.
Version skew. If you need a config file to run an app
successfully, then the apps tend to ship with the config file.
As drivers change, the config file tends to get out-of-date.
This gets worse if apps try to share config files.
The ARB once reached a compromise that involved marking Visuals as
either conformant or nonconformant, then allowing the app to make the
choice. (See the glXChooseFBConfig() function man-page or the GLX spec
for more information.) Might be worth a try...
Allen
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
