On Wed, May 7, 2008 at 5:19 PM, Dmitry Torokhov wrote: > Hi Michael, > > On Mon, May 05, 2008 at 12:34:00PM +0200, Michael Gruber wrote: >> From: Michael Gruber <lists.mg@xxxxxxxxxxxxxx> >> >> If the new module option force_dpad_to_buttons is set, the directional pad will >> be mapped to 4buttons instead of 2axes for all controllers. This includes those >> in the list of known controllers which are not affected by the existing option >> dpad_to_buttons. >> > > The option was there to adapt mappings for the new controllers we > don'ty know about yet. Coudl you explain why one would want to map > axes to buttons on a controller that is known to be not a d-pad? > > Thanks! > > -- > Dmitry For me being able to choose between 2axis or 4buttons is an additional feature. Currently this feature is only offered if the controller is unknown which means that if you have a known controller you end up with less features, which is paradox. Possible usage scenario: A user wants to play a first person shooter; he needs 2axes to look around and 2axes to move. Those 4axes are provided by the two thumbsticks; the dpad and the trigger axes are useless for this player but he might need a lot of buttons: fire, zoom, jump, duck, sprint, reload, switch weapons, grenades, flashlight, and more; hence he would profit from having more buttons; if the triggers acted as buttons then he could bind fire to the trigger and if the directional pad acted as 4 buttons then he could for example use them as shortcuts to his four favourite weapons. A lot of Xbox360 games use the triggers and dpad axes for actions that can usually only be bound to buttons in PC games. Thus a Xbox-user might be expecting an easy way to get the same functionality with the linux driver. -- 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
