|
|
|
|
|
by DungFu
4879 days ago
|
|
I have had one way before they shipped out the SDK, and all I have to say is that it is quite a bit more janky than the hype lets it seem. Fingers will disappear without notice when nothing all that crazy is happening and the frame rate of the device (which is speced at 120+ fps) is much closer to around 45-55 fps. This leads so some major problems with long term finger acquisition that has to be handled by the developer. Quite frustrating to do things yourself that should be handled by the SDK. While I understand that this SDK batch is a "beta/alpha" test, it is much buggier than it should be. The SDK will hang the entire OS quite often, and there is simply no way to detect if the device is actually plugged in. It will report invalid finger data rather than telling you that no device exists. And the javascript API is so new, that it is borderline useless. It doesn't even properly report finger width, which is kind of sad since that worked many versions ago. Overall a cool device with lots of hype, but needs a lot more work to even be mildly useful for anything more than just simple gestures. |
|
The JavaScript API doesn't do much for you, but the data is still quite good coming over the WebSocket. I've used it to create some galleries of gestures, and a gesture diagnostic tool. I've been trying to come up with solutions to the problems you've described... if it starts working out I'll release a 3rd-party JavaScript library for better finger permanence and filtering out noisy data.
http://fleetinbeing.net/leap-play/recorder-gallery.html
http://fleetinbeing.net/leap-play/recorder-diagnostic.html