Thanks for your input.
Regarding History object and the firing of ValueChangeEvents... I've
confirmed that the events are not being fired with this:
History.addValueChangeHandler(new ValueChangeHandler<String>() {
@Override
public void onValueChange(ValueChangeEvent<String> event) {
Window.alert("history changed");
}
});
I am wondering if the use of Places and the MVP framework has something to
do with this... The way navigation works in my app is via
"clientFactory.getPlaceController().goTo(place);" and if the user stays
within the same "Place" (ie same token prefix) no event is fired. However,
I am able to detect the user navigation via:
eventBus.addHandler(PlaceChangeRequestEvent.TYPE, new
PlaceChangeRequestEvent.Handler() {
@Override
public void onPlaceChangeRequest(PlaceChangeRequestEvent event) {
Window.alert("new place requested");
}
});
And since what I'm really after is the user navigation not the tokens
themselves, this is sufficient for me... Why I'm not getting the
ValueChangeEvents from the History object is a mystery to me...
On Monday, February 27, 2012 5:38:31 PM UTC-5, Jens wrote:
>
> I like the idea, but I'm finding that the value change event only fires
>> when prefix portion of the token changes.
>>
>> Thanks for your reply... By the way, am I right that the value change
>> event only fires this way?
>>
>
> History.addValueChangeHandler() always fires a ValueChangeEvent if the
> history stack changes. Otherwise it wouldn't be possible to switch between
> places of the same type but with different internal state (e.g.
> #DetailsPlace:1 and #DetailsPlace:2).
>
> Honestly I wouldn't skip any history tokens when a user hits the back
> button. When the user edits 3 documents in a row then he maybe wants to
> switch between them back and forth for some reason. I found it more natural
> if I would have to hit 3 times the back button to be back at the INDEX
> place if I have navigated to three different documents. Thats what you
> would expect from normal web navigation.
> In addition your app can provide a link like "back to index view" so that
> the user can directly jump back to the INDEX place if I really wants to.
>
> -- J.
>
--
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/-/bjfngPbG2HIJ.
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.
