3Dconnexion Forum

Thanks Nuno,
I will do that.

I won't add the DLL to output, just make it available to the compilation. Built targets will still match their CoCreateInstance to the installed DLL (if any) on the runtime machine.

If 3Dx software is installed, then CoCreateInstance is expected to succeed. Regardless of whether a SpaceXXX device is plugged in, we expect dev->Connect() to succeed after that. So ... how to tell whether the user has a real device plugged in, or software installed but device unplugged? (This is qu...

we have started with the top end SpacePilot device (nice!) (we were given one...) I note the SpacePilot has lots of buttons and an LCD display Google SketchUp and similar sophisticated client-apps both respond to the extra buttons, and display in the LCD I also note a distinct lack of display or ext...

The sample code to build against the COM control uses #import of an installed driver DLL, located via the Windows Registry (so must be installed . This only works on a machine which has the 3Dx driver installed... It does not easily support a SVN repository with branches and labelled code points... ...

I have struggled through the ghastly mess of COM in a non-ATL environment, and now get the callbacks from the 3Dx driver... Ugh!!! (The "Documentation" from 3Dx on COM programming is simply not up to sorting this out in anything other than a trivial one-purpose application, like the sample...