I'm assuming you meant: sm.setSelected(foo, !sm.isSelected(foo)); sm.setSelected(foo, !sm.isSelected(foo));
To do this I need some temp storage to be able to compare the final state when the event is about to be fired to the previous state at the same point in the code. Is this situation common enough to justify the extra effort? On 2010/08/03 18:27:00, Ray Ryan wrote:
If I do this:
sm.setSelected(!foo, sm.isSelected()); sm.setSelected(!foo, sm.isSelected());
I'll still see an event. Given your nifty event coalescing, I wouldn't
have to.
Should you do it there instead?
Also, I wonder if NoSelectionModel is the exception to the "no bounces
please"
rule.
Agreed. http://gwt-code-reviews.appspot.com/722802/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
