2008/9/12 Folke <[EMAIL PROTECTED]>
>
> On Sep 12, 5:57 pm, "Ian Bambury" <[EMAIL PROTECTED]> wrote:
> > What exactly is wrong with my design?
>
> Go ahead, use History.onHistoryChanged() and mark the calling method
> with @SuppressWarnings("deprecation"). But there are much better and
> cleaner ways to set your application to a new state, in fact, the
> history listener(s) should use these methods, too.
>
My question was 'Why depracate it?'
I am aware that I can still use it.
So, since you know of better and cleaner ways to set my application to a new
state, would you be kind enough to tell me what one of them is, so I may use
it?
Thanks,
Ian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
