Doh!. I should have looked at that Calculations class more carefully before implementing the same thing!
Yes, my list is single selection.
thanks
matt
Kevin Day wrote:
Cool.
As an FYI, there is already a Calculation implementation that will get you the first element of any list (see Calculations.elementAt() ).
That works great if your list is single selection.
My funky code is useful for providing an intuitive experience in the multi-select case - but, as you say, it does rely on the list selection model. I suppose another (diametrically opposite) option would be to include Calculations.oneElement() in the mix and not show any detail view if multiple items are selected.
- K
