On Wed, Dec 04, 2002 at 01:39:19PM -0800, Ian Romanick wrote: | | Now, imagine the drivers having an interface that a tool (for creating app. | profiles) could query. The driver would send back (perhaps using XML or | something similar?) a list of "knobs" that is has in the form: | | - Short name | - Long description | - Type (boolean, range, etc.) | - Default value (perhaps as mandated by the OpenGL standard)
That's a good design for controlling driver-level preferences, if you're determined to spend time on that approach. Before coding it up, a good exercise (which we could do online) is to generate a list of "knobs" that would apply to all drivers. I think that'll be instructive. :-) Allen ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
