spinner component

[Tom Eugelink]

On 2011-12-17 09:34, Daniel Zwolenski wrote:
> Would we lose any features, etc, if we just had the data provider have a
> increment(Value current) and decrement(Value current)
>

I remember that my initial data source idea used that approach, but I ran into troubles. If I remember correctly the problems were with cycling. Is the returned null a valid value or does it denote that there is no next/prev value? So I could throw a NoMoreValuesException, but using exceptions as a return value is considered bad, so that meant the spinner needed to be index aware.

The second issue would be that a value may exists multiple times in the domain. There probably is a usecase that totally warrents that. It would then not be possible to determine the next and prev.

Tom