Post by nick2253 » 05.06.2010 03:12:40
sgtevmckay:
Your workaround does have merit, but unfortunately, it doesn't work in all situations. In my case, I don't like what the Setpoint software does to my acceleration curves, so I don't use it. I also don't like defining key combination to my back and forward buttons as I use them as back/forward buttons. There exists a similar problem to redefining the scroll wheel.
Also, redefining the buttons in that manner limits their usefulness in games and the like, where you want to use the mouse buttons without activating, say...DexCube, for example.
Lastly, for ease of use, Dexpot should be an all-in-one solution, not reliant on external software. Capturing Mouse input should be just as easy as keyboard input (please correct me if I'm wrong. In all my coding experience, the difference between mouse and keyboard was trivial), so it shouldn't do much to "bloat" or slow down Dexpot in any way.
--Nick
sgtevmckay:
Your workaround does have merit, but unfortunately, it doesn't work in all situations. In my case, I don't like what the Setpoint software does to my acceleration curves, so I don't use it. I also don't like defining key combination to my back and forward buttons as I use them as back/forward buttons. There exists a similar problem to redefining the scroll wheel.
Also, redefining the buttons in that manner limits their usefulness in games and the like, where you want to use the mouse buttons without activating, say...DexCube, for example.
Lastly, for ease of use, Dexpot should be an all-in-one solution, not reliant on external software. Capturing Mouse input should be just as easy as keyboard input (please correct me if I'm wrong. In all my coding experience, the difference between mouse and keyboard was trivial), so it shouldn't do much to "bloat" or slow down Dexpot in any way.
--Nick