Quote:
Originally Posted by cbk1994
I did a bit of testing on an iPhone 4.
I commented out, in turn, either the trigger for timeOut or the trigger for scheduleEventTest.
PHP Code:
//#CLIENTSIDE
function onCreated() {
this.loopCount = 0;
this.trigger("scheduleEventTest");
// this.trigger("timeOut");
}
function onScheduleEventTest() {
this.loopCount ++;
player.chat = this.loopCount;
this.scheduleEvent(0.05, "scheduleEventTest");
}
function onTimeOut() {
this.loopCount ++;
player.chat = this.loopCount;
this.setTimer(0.05);
}
Results from clientstats after running for about 4 minutes (until the loop counter hit 5k):
scheduleEvent:
setTimer:
I closed and re-opened Graal before each test on the iPhone.
|
That is quite interesting. Thanks for the statistics, I would (+ rep 1) if possible.
So basically there is no nice way of doing it. Well, at least I'm fully aware of the constraints on that part.