Thank you guys, so far! This is really a big help! I will try and rebuild it. And maybe cut out the on off in the left hand, if it is even necessary... I did try to take the on/off out at one point - but I will start trying to rebuild and see if I can get it to work again! Thanks for the support!!!
@Mark - what I can say right now is, that if the leap motion freezes - usually it happens for all the scenes and I have to restart my computer... but this time it was only this one - so I think it is another problem. but I will go through the comments so far and see if I can work it out:)
I have verified that our Leap Motion Watcher actor does not work with the Leap Motion v4.0.0 Drivers, but that it does work with the Leap Motion Orion Beta v3.1.2 and the LeapMotion v2.3.1 SDKs under Windows 10. (MacOS is not affected by these changes.)
They seem to have radically changed things in the corresponding SDK, removing all interface options except for the Windows only C# (C-Sharp) and moving to a C language only interface. Our Leap Motion Watcher relied on the C++ interface so perhaps this is why it will not work with this latest Leap Motion Orion SDK. I will be posting on the Leap Motion forums to find out if there is some way to get our existing code working with the 4.0.0 system -- though I am not terribly hopeful. Leap Motion seems to be going in an entirely new direction (AR/VR) and the tracking API's all seem to be getting thrown under the bus. :-(
To get your Leap Motion working with isadora, the simplest route is to install the Leap Motion Orion Beta v3.1.2 SDK. You will need to create an account with Leap Motion to download this file.