Hi Simon, > > 2). The original does Y then 3 others, the replacement does Y + RZ then 1 > > other. > > OK I missed that you had 'disabled' the first byte value after the hat > switch (which is presumably the combined acc-brake), in preference for the > seperate ACC and Brake. > > Is there a reason to prevent the combined acc-brake being reported to the > system? > > Surely it would be best to report all options so that the app can decide > which one to use.... I can see that you might want to relabel them for > consistance with Windows. Well, i thought about this also and normally i would agree with your statement. But my conclusion was to remove the combined axis. Looking at Windows all wheel controllers i saw so far have a setting in their driver to enable or disable the separate axis. But i never saw a controller which provided both separate and combined at the same time. I am pretty sure there will be trouble when assigning these controls within an application. Often the control assignement works like this: User clicks "set axis for acceleration", application asks "please move the desired axis" and then automatically choses the "moving" axis. If we report both combined and separate at the same time, the application will have a hard time deciding which one to use, as they both will change their values. > Do you know what the 4th (and last) byte value is? > Simon No idea - But I never observed any change being reported on this byte, so at the moment i assume it is completely unused. Best regards Michael -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
