Yes, I am aware that if I don't include the tokenizer in the mapping, it works fine. The problem with that is that it's an all or nothing solution, whereas I'm looking for a programatic way of choosing when the navigation should add a new history item and when it should not. It seems to be a very simple thing to do - a flag in the PlaceChangeEvent (support for this seems to exist in various other gwt projects - GWTP for instance). I'll also try to give more detail on my use case: I'm navigating to a new Place/Activity with the url looking like this: ....abc:null. This page has a list of items, which can be selected, and this selection changes the URL as well, adding the id at the end - abc:1, abc:2. This happens automatically and so what I'm getting is two events added to the history - first abc:null and then, automatically abc:1. That messes with the history completely - back now clearly won't work (will go to abc:null). So, what I'd like to do is make the first navigation (to abc:null) not add it's event to history (because I know that selection will add a history entry anyways). If I could do that, then a single entry would end up in history and the world will be right again :). Thanks for the help. Eugen.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/XIQgK-kZ86YJ. 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.
