On 12 sep, 17:57, "Ian Bambury" <[EMAIL PROTECTED]> wrote:
> 2008/9/12 Thomas Broyer <[EMAIL PROTECTED]>
>
> > String currentToken = History.getToken();
> > History.newItem("SomeToken");
> > History.newItem(currentToken, false);
>
> > It works because history change events are now fired synchronously.
>
> But that writes out *two* history tokens. onHistoryChanged("SomeToken")
> doesn't write out any.
>
> But I'd rather say that you shouldn't do such things and try to find
>
> > an alternate, better *design* for your app.
>
> What exactly is wrong with my design?
May I ask you the rationale for dispatching a history change with a
token different from the current one? (so we could try to find a
better application design; if any...)
FYI, the rationale for deprecating onHistoryChange is mentioned in
this thread:
http://groups.google.fr/group/Google-Web-Toolkit-Contributors/t/8cd798858b3db823
and in this one, where you were the one who asked:
http://groups.google.com/group/Google-Web-Toolkit/t/ea6474bd2b6c6fee/#9352cc3f4c47438a
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
