You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Home button that is labeled "..." and is present on both Flip KB and Flip DS emits Guide from the device's built-in Xbox 360 controller. See image at the bottom of this post to see the button clearly identified.
Output from evtest of Microsoft X-Box 360 pad:
Event: time 1734670596.808366, type 1 (EV_KEY), code 316 (BTN_MODE), value 1
Event: time 1734670596.808366, -------------- SYN_REPORT ------------
Event: time 1734670596.928392, type 1 (EV_KEY), code 316 (BTN_MODE), value 0
Event: time 1734670596.928392, -------------- SYN_REPORT ------------
Because the Aya button is also emitting Guide through InputPlumber, I would like to change the behavior of this button if possible. It would be possible to change the behavior of the Aya button instead, but because IP has the Aya button emit Guide on every other device with this button, it seems logical to stick with the current behavior and instead change the behavior of the "..." button.
If I insert the following into the capability map (using Keyboard just as a test)
what happens is that the behavior of the "..." button remains unchanged. However, The Aya button now emits Guide+West and the "=" button emits Guide+West+South. It seems what is happening is that InputPlumber is intercepting and modifying the emitted Guides into Keyboard calls (Guide -> Guide+West) while ignoring the inputted Guide call from the controller. Ideally this behavior should be reversed if possible.
The text was updated successfully, but these errors were encountered:
The Home button that is labeled "..." and is present on both Flip KB and Flip DS emits Guide from the device's built-in Xbox 360 controller. See image at the bottom of this post to see the button clearly identified.
Output from
evtest
ofMicrosoft X-Box 360 pad
:Because the Aya button is also emitting Guide through InputPlumber, I would like to change the behavior of this button if possible. It would be possible to change the behavior of the Aya button instead, but because IP has the Aya button emit Guide on every other device with this button, it seems logical to stick with the current behavior and instead change the behavior of the "..." button.
If I insert the following into the capability map (using Keyboard just as a test)
what happens is that the behavior of the "..." button remains unchanged. However, The Aya button now emits Guide+West and the "=" button emits Guide+West+South. It seems what is happening is that InputPlumber is intercepting and modifying the emitted Guides into Keyboard calls (Guide -> Guide+West) while ignoring the inputted Guide call from the controller. Ideally this behavior should be reversed if possible.
The text was updated successfully, but these errors were encountered: