You are completely circumventing the driver, and thus the GUI, when you use DI, or any of the MS APIs. You are going directly to the device. In fact, the user doesn't even need to install any 3Dconnexion software to work with your app.
OTOH, there is a 3Dx driver in testing that will allow your users to adjust many of these parameters if they install the 3Dx drivers.
Issues using DirectInput
Moderator: Moderators
-
simplyRubbish
- Posts: 13
- Joined: Fri Oct 02, 2009 7:25 am
- Location: Daytona Beach, FL
Thanks for the clarification. I just need to know this for when the project lead asks me why it can't be adjusted through the 3DConnexion application.jwick wrote:You are completely circumventing the driver, and thus the GUI, when you use DI, or any of the MS APIs. You are going directly to the device. In fact, the user doesn't even need to install any 3Dconnexion software to work with your app.
OTOH, there is a 3Dx driver in testing that will allow your users to adjust many of these parameters if they install the 3Dx drivers.