Re: GWT : Activities and Places AND History

The behavior when called from onModuleLoad is unexpected; but calling PlaceController#goTo in onModuleLoad is also unexpected: 99.9% of the cases, you'll want to call PlaceHistoryHandler#handleCurrentHistory, and possibly set new RootPlace("ChartTest") as the default place when initializing the PlaceHistoryHandler.

There are probably legitimate use cases for calling goTo from onModuleLoad, so if you believe you're in this case, feel free to open an issue in the tracker (don't forget to precise the browser(s) it happens in, and the version of GWT being used).

On Friday, August 2, 2013 12:07:47 AM UTC+2, asif...@gmail.com wrote:

Hi,

I have a small ( :) ) confusion about when does history change fire in an Activities and Places scenario.

I have an application with left panel and right panel (called RootPlace) with ActivityMapper for each panel as well as for the main view.

The following call from two different place gives me two different historymapper behaviour.

clientFactory.getPlaceController().goTo(new RootPlace("ChartTest"));

If I call it  from onModuleLoad() the history refreshes the whole page ( essentially onmoduleload is called again).

If I call it from a clickhandler in the rightpanel RootPlace->View, then the history doesn't refresh the whole page.

Why should i have two different behaviour?

What am i missing?

I can upload the code -but it is part of a big app :(  - time to have a jsfiddle for gwt apps.

Regards,
Asif

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.