Hm, Thanks for the quick reply. I think I will just have to check and reload the activity when I setPlace from PlaceHistoryMapper.
Which means, when the activity is not currently showing, it will go ahead and start process the new place before the start() is ever called. I don't think this will be an issue Thanks very much! On May 18, 11:39 am, Thomas Broyer <[email protected]> wrote: > If your ActivityMapper returns the exact same instance as the current > activity, the activity won't be stopped/restarted, and won't be notified > either (it'd have to listen to PlaceChangeEvent, or your ActivityMapper > would have to "notify" it; in the Expenses sample for instance, it "sets the > place" on the activity as mean to "notify" it). > > I for one highly prefer the "disposable activity" approach, where the > ActivityMapper creates a new activity instance each time it's called (unless > it would be "the same" as the previous one, but that's better handled with a > CachingActivityMapper). -- 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.
