input-remapper icon indicating copy to clipboard operation
input-remapper copied to clipboard

Some capture of mouse buttons are wrong. Basilisk V2

Open Amdarin opened this issue 1 year ago • 1 comments

Hi.

I trying to mapping some keys of mouse and it doesn't work properly.

Event code 6 (REL_HWHEEL) Event code 8 (REL_WHEEL) Event code 11 (REL_WHEEL_HI_RES) Event code 12 (REL_HWHEEL_HI_RES)

In the screenshot you can see what I mean. Left and right wheel button are capture as wheel Down +Wheel hi res. So if i move the wheel up and down it will do the mapped shift_L+1 too.

Could you help me with it?

Share some logs please:

  1. input-remapper-control --version input-remapper-control --version input-remapper 2.0.1 568f56cdb438f4ad6db9e96b2900d1228ea736ee https://github.com/sezanzeb/input-remapper python-evdev 1.6.1

  2. If a button on your device doesn't show up in the GUI, verify that the button is reporting an event via sudo evtest. If not, input-remapper won't be able to map that button. keys

  3. If yes, please run input-remapper-gtk -d, reproduce the problem and then share the logs. keys2

Amdarin avatar Jan 15 '24 12:01 Amdarin

Did you find a solution? Testing the mouse wheel scroll up function on my Razer Mamba, the code you wrote does produce an exclamation point. I changed the number to a 4 and indeed got a dollar sign. I then re-wrote the keybind to "KEY_LEFTSHIFT+KEY_1" and it still worked properly for me.

Maybe the Basilisk is outputting something that input-remapper is not expecting? The last picture you have shows an error at the bottom of the input-remapper window suggesting that the program is expecting an analog axis. Try remapping the scroll wheel to a simpler keybind (like "KEY_M") and see if it outputs an 'm' as expected.

edit: after looking at other posts, maybe the hi-res mouse entry is causing an issue Issue #746 . Maybe that will shed a light on a possible fix for you.

TherinS avatar Jan 27 '24 21:01 TherinS