3Dconnexion Forum

Right, and I also forgot to add the " embedded_idl"-switch in the #import-statement. Works now - thanks.

Regards,
Joachim

Hi, I've tried to write my application using the COM api so far and now I have the same output about the event not being resolved as above. Is there any mayor case for this to happen? Are there any specific project settings/defines that have to be taken? Or does it even only work when the project is...

In the meantime I've read a thread in the windows-developer forum that it might be possible to get callbacks by using the HID-api directly. Since I've no experience with this API in linux: Is something like that also possible there (without too much work)? That means that maybe one could put a callb...

Hello, I'm currently making a small app which uses the spacepilot and shall be compilable for windows and linux. What I've recognized is that both API's do not have the same power, especially, the Windows-API supports callbacks through the COM-interface. Is there any decent way for callbacks in the ...

Thanks for the help

Regards,
Joachim

... just realized: When the event is a KeyPress event it should better not be casted as a XClientMessage-Event (as I did), so this error is gone.

Basically this explains everything - thanks for the help.

btw: the other questions about a way to access the newer features of the device remain .

Hello, Thanks for the reply. The buttons were on "Custom 1" - "Custom 6" when I tested it. Now with "Button 1" - "Button 6" things are working. Currently I'm trying to make the thing window independent, so the window that is passed to the driver to receive the events is an invisible InputOnly-window...

Hello, I'm using a SpacePilot and try to write some small demos for it. What I've recognized is that many features are not covered in the API (such as sending a custum configuration and stuff). Also it seems that button handling works different for the space pilot. Normally in the magellan-driver li...