If I use the function dc.drawArc in a View which is working in the simulator, I get an exclamation mark when I upload it to my Fenix 3. Is this function not supported in SW version 4.70?
Well, I just installed the latest SW version 4.90, but this does not help. The View works without drawArc, but with the call of the function, I get the exclamation mark.
I'm fairly certain that drawArc() was added with the 1.2.0 SDK (the docs indicate is was with 1.0.0, but I'm certain that is wrong). Unless you have firmware on your fenix3 that supports the ConnectIQ 1.2.0 SDK, you can expect it to crash your device.
Thanks for your help, now I see how to handle this issue.
I updated the firmware in my Fenix to Softwareversion 4.90 and I am using connectiq-sdk-win-1.2.0. With this setup, drawArc is not working, but my Fenix is not crashing, it's just the exclamation mark given. The rest of the watch works as usual.
In the mean time, I continued with the developpment of the View I would like to publish. But now there is another problem with the behaviour of the Fenix (without using drawArc). In the simulator it works nicely. When I enable the view in my watch, it starts up and is usable, but when I do not touch any key for approx. 2 minutes, the view switches back automatically to the default view.
Any ideas, how to stay on the view, is there a function to disable the automatic roll-back (like in the screensavers)?
KR,
Christof
P.S: When will it be possible to publish Views from the SDK 1.2?
@OE8BCK What Connect IQ app type do you mean when you refer to a 'View'? Some app types have timeouts, such as the Widgets (though the widget timeout is much less than 2 minutes--it's more like 10 to 15 seconds).
@OE8BCK What Connect IQ app type do you mean when you refer to a 'View'? Some app types have timeouts, such as the Widgets (though the widget timeout is much less than 2 minutes--it's more like 10 to 15 seconds).
At the risk of hijacking this thread, I wanted to comment on the widget timeout. I have heard that the timeout is short on the VA, but on my Fenix the widget timeout is exactly 2 minutes. Have to say I would be very unhappy if it were as short as 10 to 15 seconds since this is not long enough to digest information from some widgets I use.
If this is a timeout of 2 minutes, and the watch is a Fenix then it would sound to me exactly like the widget timeout which cannot be prevented.
[edit] I noticed that you mention this is on a Fenix, and if you start from the watch screen using the arrow buttons, then this is a widget. Therefore, by design it will timeout after 2 minutes. If you want it to stay there indefinitely, you need to use an app rather than a widget which would be accessed using the start/stop button from the watch screen.
gasteropod is correct--if your project type is set to 'Widget' in the project properties, then this timeout is by design. For your app to stay active, you'll need to change the project type to 'Watch App'. Here's how to do it in Eclipse:
Right click on the project in the Project Explorer
Choose Properties
Click on Connect IQ in the left pane of the Properties window
Click the pull-down menu under Choose the Project Type
So I changed from Widget to App as suggested, now there is no time-out any more. I also added the suggested "if" to drawArc, but as I have updated to the latest Beta, I now see the arc at my watch.
But - as usual - I got another problem. If I enter the setting menu I added, there is another question mark. It is coming immediately, when I press enter, the mark appears. This time the watch needs reset to be usable again. The code I use is
---
class MyMenuDelegate extends Ui.MenuInputDelegate {
function onMenuItem(item) {
Sys.println(item);
if ( item == :menu_starttime )
{
//Sys.println("Settings");
var np = new Ui.NumberPicker( Ui.NUMBER_PICKER_TIME_MIN_SEC , counter_start*60 );
Ui.pushView( np, new NPDf(), Ui.SLIDE_IMMEDIATE );
}
}
}
class NPDf extends Ui.NumberPickerDelegate {
function onNumberPicked(value) {
counter_start = value.value();
}
}
---
