While not listed, it's the same as the Approach S60 which is there. And it's the same for a bunch of the newer devices, such as the f5+ devices and 645 that are the same as the f5, as are the D2 Delta devices.
RaceQs Yes, I agree that's annoying. However, you'll find much of the same information is available in SDKROOT/bin/devices.xml, in a slightly different form.
In fact I'm looking now and noticing that the fonts for Asia-Pacific are different than rest of the world, which is not mentioned in the appendices.... (I mean it should've been obvious to me....)
RaceQs Yeah, that's why I said "Yes, I agree that's annoying."
But rather than let you sit here and wait forever for the docs to be updated, I thought I'd point you to the one authoritative place that gives you device info for VA3. As a matter of fact, devices.xml controls how the sim works, so in a way it's more authoritative than any doc....
We always wish the code was based on the doc/specs, but in reality it's often the other way around, as we all know too well.
The only other way to know that "VA3 is just like Approach S60" is to ask someone or try it out in the sim. I sure wouldn't have known that without trying, and in fact I wish I had consulted devices.xml for VA3 while I was coding a recent app, but whatever.
I checked real quick tho, and VA3 is not exactly like Approach S60 (obviously), for things like how gestures are mapped to behaviours, and the touch area.
So I think devices.xml is as good as it's gonna get for now.
Yes, the va3 only has one button, so it's different than the s60 when it comes to input mapping. Also a swipe to the right is seen as onBack on a va3. And these's the case swipe (swiping the side of the case opposite the button - where the button can be on the right or left). It's seen as a series up swipe up/down. But that's not on the va3m.
There are other things like the s60 doesn't have a baro ot OHRM, so things like getHeartRateHistory and SensorHistory in general isn't there.
For input mapping, using the input sample in the SDK will show you the differences. The sim doesn't demonstrate the case swipe.
And these's the case swipe (swiping the side of the case opposite the button - where the button can be on the right or left). It's seen as a series up swipe up/down. But that's not on the va3m.
So can you confirm that it generates an inputDelegate:swipe() from testing on the device? But what about a BehaviorDelegate callback?
For input mapping, using the input sample in the SDK will show you the differences. The sim doesn't demonstrate the case swipe.
Yes, onSwipe() in the delegate, with the event containing direction. It was no extra code after just using onSwioe() for the swipes in the screen. ----- The input simple is in the SDK you have on your system
