You need to design your app for this. * You need to assign something as a history listener (or handler in 1.6)
* When the listener/handler gets a call, it sets the site up with the correct page (or a default if the token is blank or invalid) * When you want to display a 'page', you create a history record and this fires the history listener/handler which displays the 'page' for you. * When onModuleLoad happens, (depending on the GWT version) you 'refresh' the history token with something like History.fireCurrentHistoryState(); and this fires the history listener/handler which displays the 'page' for you. If you do it this way, only the history listener/handler ever displays a page - the onModuleLoad calls it with the current history token and it displays whatever that indicates, and you can use Hyperlinks to fire History to display other pages. I don't actually like Hyperlinks, so I use something else, but it still fires the history change. And of course, the user using forward/back will also fire the history listener/handler. Ian http://examples.roughian.com 2009/3/5 mrfreeze81 <[email protected]> > > Thanks Ian, > I have actually coded with the History() class, I think I must > have done something wrong, because, every time I refresh the page it > still take me back to the first page that it loads onModuleLoad. I > guess my history is getting set back to the first token. > > Freeze > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
