Timer and globals

Hi all,

I get this strange result, I surely miss something but don't understand what...

Here is the code, actionLoaded is a global

function loadActions() {
	// Load next X action(s)
	var X = 5;
	
	for (var it = 0; (it < X) && (actionsLoaded < TOTAL_ACTIONS); it++) {
        //Some code to load an action number "actionLoaded+1"
		actionsLoaded++;
		WatchUi.requestUpdate();
	}
	
	if (actionsLoaded < TOTAL_ACTIONS) { // If all settings not loaded, recall after return to VM
		var myTimer = new Timer.Timer();
		myTimer.start(new Lang.Method($, :loadActions), 50, false);
	}
}

In the onUpdate(dc) of my View, I put a

System.println("I load " + actionsLoaded);

I guess to have :

I load 1
I load 2
I load 3
...
I load 35

but I get :

I load 5
I load 5
I load 5
I load 5
I load 5
I load 10
I load 10
I load 10
I load 10
I load 10
I load 15
I load 15
I load 15
I load 15
...

It seems that the requestUpdate() is launched 5x times at the end of the timer's callback function but why ?

Regards.

jim_m_58 over 5 years ago

With x=5, what's happening is since you don't return to the VM after each requestUpdate, it's not acting on that until you do That's why you see multiple 5's, 10's 15's. CIQ is single threaded.

jim_m_58 over 5 years ago in reply to jim_m_58

It's working just the way it should.

RodolpheDumesnil over 5 years ago in reply to jim_m_58

OK, thanks.
So the thing I misunderstand is the VM... I thought that the VM was "all the world outside the app"... In other words, when the app is "idle", here, because I ask an update of the View, I was thinking these actions were inside the app... but apparently not. Can you point me a documentation to well understand this point ?

Regards.

jim_m_58 over 5 years ago in reply to RodolpheDumesnil

The thing here is that you you don't leave your code until the loop has been performed 5 times and the Ui.requestUpdate doesn't do anything until you exit your code.

RodolpheDumesnil over 5 years ago in reply to jim_m_58

Yes, that's it, requestUpdate is in fact done in the VM, I was thiking it was in the app scope ...

Not totally related, but do you know if the min timer is the same for all watches ? I test some, it seems that is 50 for all ... If not, where can I find this info (not in the simulator.json) or better, how to get it directly into the code ?

jim_m_58 over 5 years ago in reply to RodolpheDumesnil

I wouldn't go any lower than 50ms, as you don't want the code you're executing running longer than how often the timer fires.

RodolpheDumesnil over 5 years ago in reply to jim_m_58

Yep, I totally agree, the goal is rather to adapt the timer to a potientially higher minimum value on oldest watches (and avoid a potentiel message that tell that the timer has been autocomatically adapted ;o) )