G'day fellow Leapers and benevolent Leap Creators,
I've been mucking around with the new SDK and trying to put together a project with the JavaScript API when I think I stumbled across an as-yet unreported issue. The timeVisible
property on hand objects seems a bit awry when a hand first comes into view. I output it through console.log on Chrome and alongside the expected entries counting up from 0 seconds, there were also a bunch of entries interspersed that started at 146276.
Is there any explanation/reason for this (maybe I've missed something or haven't RTFM'd properly) or is this a legit bug?
Cheers,
Adam
EDIT: Further investigation (restarting my Macbook) reveals that the errant numbers seem to match the current uptime of the computer (or potentially the browser).
EDIT WITH DIAGNOSIS: The errant numbers are the frame timestamp / 1000, in other words the number of seconds the Leap has been on.