Backward support dilema

[azakharov49]

leap motion software v2:
+ supports most applications
- buggy hand tracking

leap motion software v4:
- doesn't support most applications
+ good hand tracking

Which version of leap motion software is:
+ supports most applications
+ good hand tracking
?
or
How to run applications that use older version of leap motion software api on fresh version?

[AlexColgan]

Version 3 is probably your best bet. From our docs:

• The V2 software may be used to build with our standard tracking on OSX or Linux, or with tool tracking or touchscreen-style gestures. However, many of the development assets associated with V2 are outdated, and the software is no longer supported. We strongly recommend using the more recent software versions.
• The V3 software, aka the first major Orion tracking release, is optimized for VR. However, it also preserved many of the legacy APIs out of the box, i.e. C++, C#, Objective-C, Java, Python, and JavaScript. Applications that rely on these APIs require the V3 software, though there is a fix for developers outlined below.
• The V4 software, or the second generation of Orion, is further optimized for performance on VR platforms. With V4 we deprecated the older APIs in favor of the LeapC API, which is significantly closer to the metal. The newest demos such as Cat Explorer require V4. As part of the V4 release we also shared our wrapper for the legacy language bindings, which makes it easy to integrate legacy-reliant applications with LeapC. You can find the binding tool here: github.com/leapmotion/LeapCxx.