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
Just got a new gaming trackball, the "Elecom Huge", and was disappointed that Piper wouldn't allow me to map the extra buttons on the mouse.
Rather than, or in addition to, having configurations for specific mice (and possibly keyboards?) I'd like to suggest you have a universal method for configuring mice.
What I'd suggest is having a very basic image of a mouse, as well as a "test pad", where when the mouse pointer is above the pad, all button presses / scroll wheel movements are captured. If the performance hasn't already been captured it will create a new "button" for the mouse, which can be moved around on the image. If the performance were already captured it would instead hilight that "button". You'd then assign actions to those "buttons" much like you would on your current set-up. This wouldn't be pretty but would allow for much more functionality for people with odd equipment.
The only alternative would be to get companies to write their own drivers for their mice, which would be great but probably not feasible (yet) and would likely result in closed-source garbage.
The text was updated successfully, but these errors were encountered:
Hi! get companies to write their own drivers for their mice - sorry to say, that's how libratbag works, by setting up mouse using vendor-specific driver.
Just got a new gaming trackball, the "Elecom Huge", and was disappointed that Piper wouldn't allow me to map the extra buttons on the mouse.
Rather than, or in addition to, having configurations for specific mice (and possibly keyboards?) I'd like to suggest you have a universal method for configuring mice.
What I'd suggest is having a very basic image of a mouse, as well as a "test pad", where when the mouse pointer is above the pad, all button presses / scroll wheel movements are captured. If the performance hasn't already been captured it will create a new "button" for the mouse, which can be moved around on the image. If the performance were already captured it would instead hilight that "button". You'd then assign actions to those "buttons" much like you would on your current set-up. This wouldn't be pretty but would allow for much more functionality for people with odd equipment.
The only alternative would be to get companies to write their own drivers for their mice, which would be great but probably not feasible (yet) and would likely result in closed-source garbage.
The text was updated successfully, but these errors were encountered: