Even if I disable this 3D Mouse functionality in the Properties context menu, sometimes the event is fired anyway (I don't know if it is a bug of the SpaceNavigator ).
There is a feature in the driver included in 3DxWare 10 that emulate a mouse wheel. The event injection is done at a very low level and I believe, by the time the application is called back, the events are indistinguishable from a mouse wheel.
You probably have 3D mouse support using a system interface and the driver ends up feeding data to your application through two pathways: mouse wheel emulation and real 3D mouse data. Is that a fair assessment? It may be possible to address this by changing the driver configuration when your application is on the foreground.
My application is using .NET Framework 4 (C#) and I'm listening to the 3D mouse input events by using the RegisterRawInputDevices windows API, how can I use the API to perform that driver's setting change?
You would use the driver API to replace Raw Input.
If you can share, could you let us know why Raw Input is requirement?
You're probably using the driver in the "3DxSoftware" suite. Can you try using the driver in the newer 3DxWare 10 for Windows package? You will find the latest version (10.0.17) in the download section for the SpaceMouse Wireless.
I'm using the RawInput method because I didn't see any examples of using the 3DxWare in a .NET application. The C# example in ftp:/ *** *** uses this method.
Also, I've heard that TDxInput is been deprecated. Is this incorrect?
Moderator Edit: the sample code is no longer available from the FTP service. Please contact 3Dconnexion API Support if you need further assistance.
A different profile is probably being used than you think. Hover over the systray icon while your application is running to see what profile is being used.