Forerunner 235 sample widget animation

Hi, I've tried to run some of the sample projects that come with the SDK (2.2.6) on my watch (FR235 1.4.1), and I found some odd behaviors.
Specifically, I ran the 'Drawable' sample project (it's a widget) on the simulator and everything went smoothly.
I could see the small cloud moving from one corner of the screen to the other, thanks to the Ui.animate(...) API.
However, compiling and executing the same widget on my watch yielded a different result, i.e., the animation did not work and the small cloud did not move.

Searching in the forum, it seems that some people had similar issues in designing watchfaces, where entering and exiting sleep mode is clearly defined.
How about apps and widgets?
What am I missing?
Thanks!

ftrimboli over 7 years ago

Welcome to CIQ!

This post might be useful...
https://forums.garmin.com/showthread.php?377031-animation&p=992254#post992254

That being said, I've never really used Ui.animate() to animate any drawables.
What are you trying to build?

travis.vitek over 7 years ago

The Ui.animate() functionality behaves as if it calls Ui.requestUpdate() as frequently as the device will allow while modifying a value by interpolation. It runs until animation period is complete. It is not complicated. If you are still having trouble, you should post some code.

ianno over 7 years ago

Thanks to the both of you!

I'm just starting to learn the basics of the ConnectIQ SDK, and I wanted to make sure I understand the APIs before committing to anything bigger.
So far I'm playing with the sample projects, and this is why I'm so puzzled.
I'm talking about the code provided by Garmin!!! How is it possible that it doesn't work on their own devices? --I've tried the one called "Drawable" on my FR235.

ftrimboli, I looked at your projects and the github sample. I found your style very elegant. Thanks for posting it!
However, watchfaces are different than widgets, as you can clearly identify when the device is entering or exiting sleep mode, and reacting accordingly.

TRAVIS.VITEK, I'm not saying that the code is complicated. In fact, it's quite simple.
It just doesn't work on the real device as it does on the simulator. Not even the sample projects provided with the SDK.
How are developers supposed to create apps etc. supporting several devices if the simulator is not trustworthy? Buying all of them?

Frankly speaking, as a novice, this doesn't feel very inspiring...
Yet, you people are developing amazing things! And this is great!
I'll experiment a bit and see how this goes, and keep you in the loop while doing so.

Thanks again!

travis.vitek over 7 years ago

It just doesn't work on the real device as it does on the simulator. Not even the sample projects provided with the SDK.

This looks like a bug to me. The Ui.animate() call is updating the cloud position, but it is no longer forcing the screen to redraw as it did previously.

You'll notice that the cloud animates until the page transition animation is complete, then it stops. If you wait a second or more, and then scroll to the next widget, you'll see the cloud jump to the position it would have been had the animation continued running.

I've filed something in the bug reports forum on this for you.

Travis

ianno over 7 years ago

I've filed something in the bug reports forum on this for you.

Thanks, Travis!

Coleman.Apps over 7 years ago

Hey,

Just wanted to note that the bug reported in the Bug reports forum was been ticketed and is being worked on. Thanks for the catch and sorry that that was one of your first experiences with Connect IQ. We found that it was only affecting a select set of devices which your 235 was a part of. Keep an eye out on the bug forum post for updates.

Thanks!
-Coleman

ianno over 7 years ago

I will,

Thanks, Coleman!