On Mon, Jan 12, 2009 at 2:13 PM, Kelly Norton knor...@google.com wrote:
We actually have it, it's called DeferredCommand. Unfortunately, we let its
implementation get too gangled up with another feature called
IncrementalCommand and use of DeferredCommand now generates way too much
code. Many
DeferredCommand really is, and always has been, meant to be exactly the same
thing as invokeLater(). I do agree with Kelly that the implementation
became heavyweight by being intertwined with IncrementalCommand, and that we
should undo it. (It seemed like a good idea at the time...)
@Lex: Do you
Lex said Every place in GWT that installs a global event handler should
also call runInvokeLaterCommands. In addition, there could be a
periodic timer that calls runInvokeLaterCommands, to catch any cases
that were missed
I'd be careful with this. It sounds like you want a GWT-maintained
event
Heh, I think I always have an opinion on Timers :-)
I think Timers should allow 0ms delays and I think we should also have a
mechanism for what is commonly called invokeLater. Here's why:
Timers should accept 0ms
I do think allowing 0ms is kind of wrong because browsers clamp at 10ms-15ms
and
