- How to customize mouse buttons razer how to#
- How to customize mouse buttons razer install#
- How to customize mouse buttons razer serial#
You can look how to do this in google (I cannot post more than two links, but in the reddit link you have the link with a page explaining this). Using C++, some sys linux libraries and input.h. I did this by grabbing the raw input from the event device node. Where is the id of the keypad as seen with xinput (maybe 13 in your case?)Ĭatch the event triggered by the button pressing. $xinput set-int-prop "Device Enabled" 8 0 Silence the device so the buttons "do nothing" using: The idea is to implement these three steps:
How to customize mouse buttons razer install#
I wrote a little daemon in C++ and put it into a github repository that you can download and install from here My solution is probably not the best but it surely worked for me. The thing is that maybe my solution works for you too even if your system marks the device as a pointer instead of a keyboard. I do not fully understand the situation (not that you didn't explained it well), but I came across the Naga mapping issue and after finding no solution in the web I decided to give it a try and actually got it working.
Root 0x9d, subw 0x3a00002, time 16537199, (31,58), root:(625,365),Īt this point I don't really know where to proceed (I don't even know which of the two devices listed in xinput is the one mapped to the buttons), so any advice or pointers would be greatly appreciated!
How to customize mouse buttons razer serial#
KeyRelease event, serial 37, synthetic NO, window 0x3a00001, State 0x0, keycode 10 (keysym 0x31, 1), same_screen YES, Now the mysterious "1" button on the side: KeyPress event, serial 37, synthetic NO, window 0x3a00001, Here's an example of me clicking the left mouse button: ButtonRelease event, serial 37, synthetic NO, window 0x3a00001, I tried using xev to show the output of what happens when I press one of these buttons but it didn't really help me. Other resolutions have suggested running a script to replace the keymappings for the keyboard entry, which won't work for me, I think. As you can see in mine there are two listed, only in the pointer section. In other people's output, I noticed that there is one "Razer Naga" present in the pointer section and one in the keyboard section. So far, I've done a lot of Googling, but one key difference I notice when other people have solved this is the difference in my xinput output: ⎡ Virtual core pointer id=2 My ultimate goal is to bind at least 3 of the buttons (1-3) to something else, let's say F1, F2 and F3 for argument's sake. I should also mention that I am experiencing the same situation across two entirely different machines but with the same physical mouse. There is an option to change these to the Numpad mappings (configurable by a physical switch on the mouse itself) which would solve my problem but inadvertently causes my right clicks to fail 60% of the time. There are 12 buttons on the side of the Naga, which are currently mapped 1-12. I'm currently having an issue trying to map the side buttons on my Razer Naga, I'm running Elementary OS but from what I understand that's a Ubuntu and I should add that this is all very new to me too!
0 kommentar(er)
