We need an action that allows users to temporarily disable most (or perhaps all) bindings. For example, a user may want to use their controller on a site that responds to joystick input, without having the gamepad navigator respond. Ideally, this would be a single action that acts as a toggle, whose wording onscreen clearly indicates the current status as well as what will happen if the action is launched.
We need to ensure as much as possible that the user can reenable the gamepad navigator afterwards. One solution is to require that a control be bound to the "action launcher" (#112 ). If we add a "configuration" action to the launcher, then as long as the user can reach the launcher, they can reconfigure anything they need to.
This suggests that we should avoid having a "set all to none" option in the new configuration panel (see #104), perhaps having a "minimum" schema where only the launcher is bound.
We need an action that allows users to temporarily disable most (or perhaps all) bindings. For example, a user may want to use their controller on a site that responds to joystick input, without having the gamepad navigator respond. Ideally, this would be a single action that acts as a toggle, whose wording onscreen clearly indicates the current status as well as what will happen if the action is launched.
We need to ensure as much as possible that the user can reenable the gamepad navigator afterwards. One solution is to require that a control be bound to the "action launcher" (#112 ). If we add a "configuration" action to the launcher, then as long as the user can reach the launcher, they can reconfigure anything they need to.
This suggests that we should avoid having a "set all to none" option in the new configuration panel (see #104), perhaps having a "minimum" schema where only the launcher is bound.