Actually it's not necessarily a bad thing. At least for what I do. I am more concerned about the minimum CIQ api level that a certain device can have than with the maximum, because I am generating code/excludeAnnotations based on that to minimize code…

	//! Handle the partial update event
	//! @param dc Device context
	public function onPartialUpdate(dc as Dc) as Void {
		_partially += 1;
	}

I hope not, I'm not using onPartialUpdate except as a counter so it has at least one line of executable…

That's not the launcher icon. Here, in the LIST I do see the launcher icon:

But my problem is when you click on one item:

Here we're supposed to see a bigger (128x128 I guess) logo. You see the black square, it's huge. And in that place I see the…

This is a really stupid question, but are you sure onStart() is being called? I assume your code snippet is supposed to be from your class which is derived from AppBase, but if it isn't, then onStart() is not going to be called (unless you are calling…

flocsy said:

Ok, this really can work because it has both the font and the y position

Yeah but like I showed above, what's shown in the sim isn't exactly the same as what's on the device, at least for my device and the one layout I tried.…

While this issue is VERY repeatable on my quickie custom WF, and one I had gotten off the Connect IQ store (which is why I started researching this)... the Garmin watch faces do not exhibit this same problem.  Using a Garmin WF, the backlight goes into…

The "exit code: 100" thing is, as you have discovered, not very helpful because it essentially just says "could not compile for some reason"...

But...

If you scroll up in the terminal, you will see all of the good information about…

hi Peter,

it's indeed recommended to disable auto-lap (or to set at least auto lap size the same as the internal lap size)

the data field will not autopause, it will even continue guiding you even when you have passed your goal distance (based on…

There's overhead associated with a dictionary and with each array (8 bytes per array, IIRC).

Also, the 235 is pretty old -- newer devices have at least twice the memory for data fields.

If you really want to dig into it, you'd have to run your app…