Hi Thomas/Chris -

Thanks for the responses. I was missing the part about the build-in check
for Place equality. Any idea how the equality check is implemented?

For example, if my Place has 2 fields - an integer and a string, is it
implicitly true that 2 places are equal if those values are the same in
both, or do I need to explicitly define an equals() method?


On Thu, Mar 1, 2012 at 10:28 AM, Thomas Broyer <[email protected]> wrote:

>
> On Thursday, March 1, 2012 3:23:01 PM UTC+1, Shaun Tarves wrote:
>>
>> @Thomas - In the example you pointed me to, what prevents this from
>> essentially creating an infinite loop? OnSelectionChange fires a new
>> history event. The history handler responds, gets info and changes the
>> selection, which would in turn fire a new history event. No?
>>
>>
> If the value to be selected is the same as the already-selected one, then
> no SelectionChangeEvent is fired.
> If the place to go to is the same as the current place, then this is a
> no-op too.
>
> So there's no infinite loop.
>
> --
> 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/-/EMJeu1Io5yEJ.
>
> 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.
>

-- 
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.

Reply via email to