I noticed that winecfg is still reporting that it "does not modify your configuration", and in winecfg.h WINE_KEY_ROOT isn't set to the configuration key. Is there some reason why we haven't enabled writing to the actual configuration yet? Are there some bugs or lack of features that need to be resolved before it goes active? Without a ~/.wine/config file it seems like winecfg is the only way to let users easily adjust their configuration.
Chris
On Sat, 05 Mar 2005 23:35:35 -0500, Chris Morgan wrote:
I noticed that winecfg is still reporting that it "does not modify your configuration", and in winecfg.h WINE_KEY_ROOT isn't set to the configuration key. Is there some reason why we haven't enabled writing to the actual configuration yet? Are there some bugs or lack of features that need to be resolved before it goes active? Without a ~/.wine/config file it seems like winecfg is the only way to let users easily adjust their configuration.
Somebody needs to write a patch to migrate the configuration branch across to a new one, disable the pre-existing config file (renaming it?) and then use it.
At least, I think that is what is needed. Alexandre may have other ideas.
-
Chris Morgan -
Mike Hearn