• Replies 24 replies
  • Subscribers 18 subscribers
  • Views 4146 views
  • Users 0 members are here
Options
Related

UX Guide entry for Vivoactive 3

Alan.raceQs
Is there a hidden agenda to the VA-3 being ignored in the UX Guide Appendix A Devices and B Font Specs, or is it just an oversight?
  • OK, I have it, thanks.
    It's not brilliantly tested: it doesn't clear the Event line before each input.
    But does demonstrate the confusion that has been implemented with the VA-3:
    The behaviorDelegate concept of "next/previous page" is implemented on the VA-HR and Approach S60 as a horizontal swipe and on the VA-3 a vertical swipe!

    And can you please confirm there's no behaviorDelegate response to the body swipe on the VA-3 please?

  • With the input sample, the case swipe shows Swipe_Up/Next_Page and Swipe_Down/Previous_page just like the screen swipes do.
  • With the input sample, the case swipe shows Swipe_Up/Next_Page and Swipe_Down/Previous_page just like the screen swipes do.


    Thanks.
  • One more question about the VA-3. (I don't have one to test on:mad:)
    Which BehaviorDelegate callback is called on a press of the button?
    The wording of the User Manual is obscure:
    Hold to turn on the device.
    Hold to view the controls menu, including device power.
    Press to return to the watch face from any screen, except during an activity.
    During an activity, press to pause the activity.

    From that description, I would expect a button press to raise onBack() butit doesn't raise any BehaviorDelegate callback the the Sim (SDK 3.0.6).
    Is that a Sim bug, or am I misinterpreting the user manual?
  • The va3 is a bit odd with one button.

    Run the "input sample" from the SDK on it and you'll see it's KEY_ENTER with no behavior
  • Run the "input sample" from the SDK on it and you'll see it's KEY_ENTER with no behavior


    My problem is I don't have a device to run it on, and I know the sim is not reliable in its interpretation of the buttons: the VA-HR triggers onMenu() with a single press of the right button, but onSelect() on the device.
    Is your response based on a physical device or the sim?
  • Run it in the sim. The single press of the right button on the vahr was a bug in the sim that's now fixed in 3.0.7. Yes, the sim and the va3 match.
  • Seems there's a problem with the 3.0.7 update for Mac. The Eclipse Connect IQ SDK manager tells me the 3.0.7 update is available, and makes all the right noises as I download and then accept "Use 3.0.7 as the SDK manager", but it doesn't!
    SDK manager still tells me it's running 3.0.6 and tells me 3.0.7 is available!
    When I caught the download, I saw that it's downloading 3.0.6.
    (I've done it three times and restarted Eclipse in between)

    So I'm still in the dark.

    Thanks for the confirmation about VA3. It really is an odd one eh?


  • Run it in the sim. The single press of the right button on the vahr was a bug in the sim that's now fixed in 3.0.7.


    I have installed 3.0.7(manually as the SDK download process for 3.0.7 is broken) but the Sim VAHR still returns onMenu from the right button press.
  • I have installed 3.0.7 but the Sim VAHR still returns onMenu from the right button press.

    I've just verified that with the 3.0.7 SDK, the vivoactive_hr shows KEY_ENTER/NO_BEHAVIOR for a right button press, and KEY_MENU/ON_MENU for a right button hold.

    As suggested previously, you should assume that the definitions in ${SDKROOT}/bin/devices.xml are correct.

    Travis