3Dconnexion Forum

I'm using pyglet (trunk) with its capability to handle HID over operating system HID interfaces (such as evdev, *wink* *wink* 3dconnexion), which works for me. I also wrote a device configuration framework to handle many devices.

@uludwig there seems to be some 3dconnexion terminal reality disconnect. 1) you recommend using the "official" broken way of doing things in the linux developer forum 2) you get thread upon thread in the linux user forum about how utterly hard it is to configure and use the device with any...

As for application support, I've written about this quite a lot. In danger of repeating myself, I make it short. 1) get rid of stupid custom proprietary software that opens windows and requires a special API in your application 2) Use standard driver support systems of linux, such as evdev properly....

The evdev stuff is rather simple, plus if you do it with evdev you get support for any Human Interface Device, not just space pilots etc. (Joysticks, gamepads and whatnot too). Sure the "official" recommendation would be to use the "official" SDK and the "official" usbf...

You could follow the evdev examples , it works ( somewhat ). If udev doesn't mount it as readable for users, add such a rule: KERNEL=="event*", SUBSYSTEM=="input", ATTRS{name}=="3Dconnexion SpaceNavigator", MODE="0666" To a /etc/udev/rules.d/99-joysticks.rules...

Support of an operating system for a Human Interface Device means: You plug it in and it works Working in the context of an application dealing with Human Interface Devices is that the information reported by the driver about the device are correct. Linux supports HID in a variety of fashions: - usb...

I think we can agree that "support" for an operating system for a Human Interface Device means: You plug it in and it works Working in the context of an application dealing with Human Interface Devices is that the information reported by the driver about the device are correct. Linux suppo...

If 3dconnexion would fix their linux driver support there'd be no need to put up with that, see this thread

Ubuntu users have the same problem with X hotplug, see this post and this post

There is a launchpad bug about it too

This is because the new hotplug support of ubuntu 8.10 lts attempts to add the navigator as a pointing device, subscribe/comment on this bug on launchpad https://bugs.launchpad.net/ubuntu/+sour ... bug/297264

The new hotplug support attempts to add this device as a pointer, therefore any other event source (evdev, usbfs) does not get any events anymore and it is effectively broken.

Subscribe/Comment on this bug https://bugs.launchpad.net/ubuntu/+sour ... ug/297264/

The linux evdev driver reports the axes of the space navigator as relative instead of absolute. Therefore min/max values are not read out and it's impossible to use as a absolute axis.
The wrong relative axis does report a value, but it is clearly an absolute value.