Robert Reif reif@earthlink.net writes:
Add a [dinput] section to your config file and provide a line with the following information:
"your device name" = "X,Y,Z,Rx,Ry,Rz,Slider1,Slider2,POV1,POV2,POV3,POV4"
where "your device name" is what you get from /bin/jstest and the axes list are the axes supported by your joystick.
For example, here is part of my config file:
[dinput] "Logitech Logitech Extreme 3D Pro" = "X,Y,Rz,Slider1,POV1"
You should add this in the registry instead of the config file, this way we won't have to move it later on. HKLM/Software/Wine/Dinput should be a good place for it.
You should add this in the registry instead of the config file, this way we won't have to move it later on. HKLM/Software/Wine/Dinput should be a good place for it.
Hmm, we're going to have to move all the registry keys? I thought we were just going to convert Software/Wine/Wine into a standard key rather than loaded at startup.
If we're going to start scattering the options around in the registry this has some implications for winecfg - currently all its settings are rooted at HKLM/Software/Wine/Wine
Mike Hearn m.hearn@signal.QinetiQ.com writes:
Hmm, we're going to have to move all the registry keys? I thought we were just going to convert Software/Wine/Wine into a standard key rather than loaded at startup.
No, the keys will be moved, so that we can handle the transition properly.
If we're going to start scattering the options around in the registry this has some implications for winecfg - currently all its settings are rooted at HKLM/Software/Wine/Wine
That will have to be changed.
No, the keys will be moved, so that we can handle the transition properly.
OK, but why do the keys have to be copied across. What's wrong with:
if (config file is present && !key exists("HKLM/Software/Wine/Wine")) { mount config at( "HKLM/TempWineConfig" ) copy tree( "HKLM/TempWineConfig" to "HKLM/Software/Wine/Wine" ) }
ie we check if the standard .reg files contain the config branch and if not, copy it across.
thanks -mike
Mike Hearn m.hearn@signal.QinetiQ.com writes:
OK, but why do the keys have to be copied across. What's wrong with:
if (config file is present && !key exists("HKLM/Software/Wine/Wine")) { mount config at( "HKLM/TempWineConfig" ) copy tree( "HKLM/TempWineConfig" to "HKLM/Software/Wine/Wine" ) }
ie we check if the standard .reg files contain the config branch and if not, copy it across.
Because we want to have the two systems coexist, so that we don't have to change all the code at the same time. In fact there are already some parameters under HKLM/Software/Wine today. It also allows moving back to an older Wine without conflicts.
Alexandre Julliard wrote:
Because we want to have the two systems coexist, so that we don't have to change all the code at the same time. In fact there are already some parameters under HKLM/Software/Wine today. It also allows moving back to an older Wine without conflicts.
OK, makes sense. I'll work on adapting winecfg. I'll also try compiling a list of the registry entries we use, I don't think there is any such list currently is there?
One thing: if things like Version/AppDefaults/DllOverrides are going to move, where are they going to go? HKLM/Software/Wine/Version, HKLM/Software/Wine/AppDefaults etc would be easy, it just means moving them up a level.
Though then in each place we check for keys we have to check two locations instead of one.
On Fri, Sep 10, 2004 at 09:46:42AM +0100, Mike Hearn wrote:
OK, makes sense. I'll work on adapting winecfg. I'll also try compiling a list of the registry entries we use, I don't think there is any such list currently is there?
Please work on this one, it needs love: http://winehq.org/site/status_options
-
Alexandre Julliard -
Dimitrie O. Paun -
Mike Hearn