Skip to content

Latest commit

 

History

History
18 lines (16 loc) · 1.98 KB

BROKEN_API_FEATURES.md

File metadata and controls

18 lines (16 loc) · 1.98 KB
Raw

Some of the features specified in the LeapC API reference are broken or non-existent in the current Leap SDK (v. 5.6.1). These things are probably not issues with LeapJNA, but the Leap SDK itself. A list of these features can be found below.

Broken features

These are features in the API which do not seem to work in the expected way.

  • Device statuses are set to eLeapDeviceStatus.None instead of eLeapDeviceStatus.Paused when the service is paused (verified by dumping the memory of LEAP_DEVICE_STATUS_CHANGE_EVENTs).
  • Clock rebasing does some weird stuff (verified using the SDK's InterpolationSample).
    1. Let's say that you create a clock rebaser and update it with the current application time and Leap Motion time.
    2. Now you wait 0.1 seconds and then pass the current application time to LeapRebaseClock() along with your rebaser.
    3. You would expect the result after rebasing the current application time to be close to the current Leap Motion time, yet the rebased time will be 0.1 seconds in the past (but not identical to the time you used when updating the rebaser in step 1).
    • If you had waited 1 second in step 2, the rebasing in step 3 would give you a rebased time 1 second in the past instead.
  • Changing and requesting configuration flags with LeapSaveConfigValue and LeapRequestConfigValue do not appear to work properly with Gemini 5.6.1. It is possible that the configuration keys and values have changed since Orion, but I can't find any documentation about it. - Saving a value can freeze the tracking service for several seconds. - No change event is produced after saving a configuration value. - No request response is produced after requesting a value.

Missing features

These are features listed in the API reference and the leapc.h file in the SDK but do not exist in the SDK binaries (and can therefore not be used).

  • eLeapEventType.ImageComplete and .ImageRequestError (as far as I know there is no function to request an image)