Multiple issues with the Generic Picker on Vivoactive 3

Hello,

I'm trying to port my almost 2 year old app to the Vivoactive 3 (app: https://apps.garmin.com/en-US/apps/e...c-b554bf90865b)
The app has been running fine on a Vivoactive, Vivoactive HR, Fenix 3 & Fenix 5 (and in the sim on all supported devices).

One part of the code uses the generic Picker for a time selection in the HH:MM format, and is based on the sample code provided with the SDK (2.3.4)
Although the app runs fine in the simulator, on the actual VA3 device running V2.60, I have the following problems:

- Time is displayed in HH format (the minutes are missing)
- Need to press multiple times on the "+" symbol to increase a value (the "-" symbol works fine)
- Swiping left to access the confirmation check mark works 1 time out of 5
- The Side swipe does not work at all to increase / decrease values (on the sim neither for this one).

I've side loaded the "Picker" sample provided with the SDK and have the same issues.The attached photo is the comparison of the sample Picker code on the sim and device.

Am I missing something ? Should I switch to the Number Picker (or is it really being deprecated ?)

Thanks for you help

Greg.
community.garmin.com/.../1267397.jpg

HerrRiebmann over 7 years ago

+1 on that!
Received my VA3 today and after setting it up, checked how my app works... It doesn´t!

The picker is not initialized with the stored values. It shows 0. If you successfully hit + or -, it directly shows the expected value. Or at least a small part of it.
Unusable. The Numberpicker in the running app is great and looks like it should.
A Forerunner 230HR user (FW7.50) mentioned the same, yesterday.

Start recoding via Button also does not work. The App will be closed. Against the behaviour in the simulator.
And against all other devices, my app is successfully running on (which were more or less all).

jim_m_58 over 7 years ago

Start recoding via Button also does not work. The App will be closed. Against the behaviour in the simulator.
And against all other devices, my app is successfully running on (which were more or less all).

A few folks have seen this, and a common reason for it is that you aren't doing a proper return in the delegate. Try doing a

return true;

after you handle the button.

HerrRiebmann over 7 years ago

You are totally right, Jim!
And selfexplaining, if the device only has a single button for "Enter" and returning to the main-menu... I could even come up with it :rolleyes:

Greg, the Ui Picker is not deprecated. Checked it right now in the documentation.
My attempt to use a single, generic picker looks like that :
Github-GenericPicker.mc
Everything stock picker development, I guess. Nothing we could do about :(

ars.fabula over 7 years ago

It's not the Generic Picker but the Number Picker that is being deprecated. The Number Picker works fine, but it seems that the Generic Picker is broken on the VA3.
Anybody got an example of a Picker that works on a VA3 (and that's not deprecated)?

HerrRiebmann over 7 years ago

As you can see in my posted link above, I dont use the number picker. Just the Ui.Picker (which seems not deprecated anywhere), but the ugly not usable result is the same:

Ui.pushView(new Ui.Picker({:title=>new Ui.Text({:text=>title}),
                               :pattern=>[new NumberFactory(99)],
                               :defaults=>[value]}),
                new MyPickerDelegate(mode, object, symbol),
Ui.SLIDE_UP );

Both, simulator and device got exactly the same setup and both should show 0 Minutes and 45 Seconds.
As you can see, the simulator does (even when it is cut off a bit) and the real device doesn't.
If I try to switch to the second number (which is not possible by swiping), I have to hit the green check. Then: Nothing happens, except the dot above indicates, that I'm on the second value.
Now, hitting + or - it jumps from blank to 46 or 44.

Again, setting up the Auto. Lap in stock apps, looks great and works fine!community.garmin.com/.../1268400.jpg

HerrRiebmann over 7 years ago

Any update on this?

Newest SDK 2.4.1 and Firmware 2.70.
The FW Update changelog says:

Made improvements to the number editor

Whatever that means... I hope they did not improve the depreciated numberPicker...
For me, it looks the same as before. Awful!
And is not usable, how everything is dearranged and reacts to swiping.
And it shows still wrong values!

I still do not understand why it is not the same picker in connect IQ & in stock apps.

Coleman.Apps over 7 years ago

Hey HerrRiebmann,

Sorry I've been a little long on getting back to you on this one. It looks like the vivoactive 3 team is looking at it currently and they are prepping it for one of the upcoming maintenance releases. Sorry this one has moved a little slow. That was not the deprecated number picker that was addressed.

Thanks,
-Coleman

ars.fabula over 7 years ago

With the release of FW 3.30 for the Vivoactive 3, the generic picker has vastly improved. Thanks!

Greg

Coleman.Apps over 7 years ago

ars.fabula,

That's fantastic news!

Thanks,
- Coleman