[1/6] WineD3D: Add a more formal framework for driver quirks
stefan at codeweavers.com
Tue Apr 14 17:33:25 CDT 2009
I implemented most of Henri's suggestions in this patchset. I originally
disliked the idea of applying two quirks on top of each other because I was
afraid that the output might be unpredictable on new card/driver
combinations, but this is something we cannot completely avoid anyway.
The quirk structure how has one match function, an apply function and a
description for debugging help. I could technically merge all 3 into one
function, but I prefer to keep detection and application separate because it
seems cleaner to me and makes it easier to add new things if needed in the
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3009 bytes
Desc: not available
More information about the wine-patches