kicad-developers team mailing list archive

[Clemens Koller <cko@xxxxxxxxx>]

Hello, Jost!

I would be glad to test Kicad with 3D Mouse support, too.
(An Wacom Intuos Pro pen tablet is also laying around.)

Maybe it's wise to talk to the devs of spacenav and check their sparse mailing list at http://spacenav.sourceforge.net
how i.e. axis mapping will be abstracted across applications.
It doesn't seem appealing to me that each application on Linux will have to implement it's own 3D Mouse configuration.
On Linux, we have at least Blender, FreeCAD, Calligra using the libspnav stuff.
libspnav was initially targeted to be cross-platform, but the current status seems unknown regarding that.
There are other applications which might be worth to checkout: OpenSceneGraph, GoogleEarth and Ogre.

Some issues to consider:
- Seemless switching in between FreeCad and Kicad (and all the other 3D Mouse apps) should / need to be possible.
(I was reading lots about user level driver vs. system driver issues.)
- WGOIS and VRPN might be worth to check out?

Some more links:
http://janoc.rd-h.com/archives/74
https://github.com/vrpn/vrpn/wiki/Troubleshooting-VRPN
https://groups.google.com/forum/#!topic/liquid-galaxy/ThdQ-g4B5g8
https://sourceforge.net/p/wgois/patches/30/
https://sourceforge.net/p/wgois/patches/34/

We are adding more and more features even some "professional" 10kEUR+ software doesn't support!
(Or they say it's all there, but the implementation is just crap.)
Great!

Regards,

Clemens

On 2017-05-17 12:26, mrkenhoff wrote:
> Hi all,
> 
> thanks for your feedback.
>> If you can meet these requirements, I see no reason why we would not
>> include the spacenavigator mouse support.
> I think there shouldn't be any problem meeting these requirements. Thanks Wayne!
>> As far as libspnav goes, look through the source, it's actually pretty 
>> simple. I'm not sure how blender is doing it, or whether this is a good 
>> idea, but the device handling is actually pretty thinly veiled around 
>> evdev.
> After I looked at the source I found out that Blender uses a different approach for each OS:
> 
>   * Windows: RawInput (Low level HID API)
>   * Linux: Uses spnav library
>   * OSX: Dynamically links to the original 3Dconnexion driver
> 
> In my opinion the cleanest solution for KiCad would be to connect to the low level HID API of each OS and do not use any spacenav specific driver at all. That way there are no additional dependencies and the implementations for all three operating systems share a great ammount of code.
> As Dan noted, the libsnav "driver" (actually a deamon, to be more precise) is quite simple. It will serve as a good inspiration.
> 
> Jost
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>