Ok. That is sorta helpful. Where does that leave us?
Should GWT implement Timer differently for each browser?
On Mar 31, 12:21 pm, Thomas Broyer wrote:
> On 31 mar, 17:06,SalmanHemani wrote:
>
> > From what I understand, is that that elapsed time is computed by
> > capturing the intial time an
On 31 mar, 17:06, Salman Hemani wrote:
> From what I understand, is that that elapsed time is computed by
> capturing the intial time and polling the system clock for elapsed
> time. So when the system clock changes, the elapsed time increases. IE
> implements this by having its own timer and t
>From what I understand, is that that elapsed time is computed by
capturing the intial time and polling the system clock for elapsed
time. So when the system clock changes, the elapsed time increases. IE
implements this by having its own timer and thus changing system time
does not affect the elap
On 23 mar, 17:14, Salman Hemani wrote:
> I am seeing a strange behaviour so I'd appreciate if someone can
> explain the workings of the Timer class to me.
The Timer class uses setTimeout or setInterval behind the scene
(depending whether you call schedule() or scheduleRepeating() method),
whic
I am seeing a strange behaviour so I'd appreciate if someone can
explain the workings of the Timer class to me.
I have a piece of code that executes in the run() method when a
disconnection from the server is detected. More specifically, the user
is prompted a message for disconnection if the ser
