On Thursday 25 September 2003 12:21 pm, Alexandre Julliard wrote:
Mike Hearn mike@theoretic.com writes:
Annoying isn't it? The config file is not the right place to do this anyway, better to have it hardcoded into loader/loadorder.c IMHO, otherwise users will always forget to update their config.
No, that hardcoded list is only for dlls that we know will never work as native. We don't want to have to change it every week depending on the progress of some other dll. There are plenty of things that you may have to add in the registry or config when upgrading Wine, that's just one of them; we'll need a general mechanism to do that anyway.
Perhaps we want to distinguish between "defaults" and "settings," which override the defaults. For example, we could just return default registry values (of the settings with defaults) when they aren't really there. That way new defaults could be hardcoded in source or winedefault.reg, and updating your wine would update any defaults you haven't overridden... such an approach could make things a little screwy from winecfg's perspective however.