[..BUGS]More CIQ bugs in beta 3.03 on Forerunner 920xt

Garmin never announced that App support was available, it was discovered. I think it is unfair, and possibly wasteful, to be posting about bugs in something that doesn't officially exist.

Travis

Garmin never announced that App support was available, it was discovered. I think it is unfair, and possibly wasteful, to be posting about bugs in something that doesn't officially exist.

Travis

I think that we should report all the issues we encounter... this way we can help the test team at Garmin better and get a stable - and well-tested - product way sooner...

/Tonny

Do as you wish. Just realize that you're reporting bugs on pre-beta software that you're not even supposed to know exists. I think that if Garmin had wanted us to be reporting bugs on it, they would have mentioned it in the 3.03 announcement thread themselves.

I feel like a huge jerk for even mentioning the fact that apps seemed to work.

Garmin never announced that App support was available, it was discovered. I think it is unfair, and possibly wasteful, to be posting about bugs in something that doesn't officially exist.

Travis

Why? I'm not complaining. Just stating that I found bugs. I always thought the whole purpose for beta's was so that users can help finding bugs, before the final release.
I could mail the bugs I found using the form in the beta zip. But I've done that before and I never got any response. That's why I post the bugs on the forum, because then at least there's some response.

I'm very happy I'm able to test on the device now.

Do as you wish. Just realize that you're reporting bugs on pre-beta software that you're not even supposed to know exists. I think that if Garmin had wanted us to be reporting bugs on it, they would have mentioned it in the 3.03 announcement thread themselves.

I feel like a huge jerk for even mentioning the fact that apps seemed to work.

I can easily understand your position. After all Garmin decided not to mention that apps and widget are (semi-)supported for a reason - most likely because they know of too many things that doesn't quite work well enough to let the stuff loose in the jungle...

But... it is here and if we can shorten the beta period by "reporting" things that does work as we would expect, I find that to be a good thing.

Another thing is that the current Connect IQ document does leave some areas undocumented and the sooner we can figure out the playing field, the better.

@Brandon, what is your take on this? Would prefer us not the report anything on apps and widgets just yet, or...

Feel free to go ahead and report issues. We are working on cleaning all this stuff up.

TeunMo,

I think all of the input bugs will be fixed in the next release. The Menu key was not mapped properly and has been fixed. The next/previous behaviors were not assigned to the up and down keys as they should have been. You will need to make sure you return true from your input handler to avoid strange native device behaviors from popping up (like the WiFi/lock screen you are seeing). We are still working on cleaning that up.

We fixed a bug with pushView, but it might already be fixed in 3.03. If you can't push a Ui.View, then you will be able to in the next version. Some of the support for view types is missing, which is the other reason you might not be able to push a menu. We are working on fixing those issues as soon as possible.

the Layout centering I am not sure of I will try to make sure it gets reported.

When I have my own watch face and watch is in sleep mode and then when I push any arrow button, it shows popup informing that it's in sleep mode. But it stays there until watch face is not refreshed (1 minute in worst case).

Layout attribute x="center" is not processed properly (processed as x="0")

This is most likely caused by the Dc passed to onLayout() having the wrong dimensions as mentioned here.

When I have my own watch face and watch is in sleep mode and then when I push any arrow button, it shows popup informing that it's in sleep mode. But it stays there until watch face is not refreshed (1 minute in worst case).

I'm pretty sure you're affected by this.