I don't know why you say there's a lot of stuff happening. It's just using
binding (in the form of a binding function) to set an initial selection.
Seems completely legitimate to me. The fact that it's a function rather than
a direct reference is because of the well-known ComboBox limitations with
--- In flexcoders@yahoogroups.com, "Tracy Spratt" wrote:
>
> You have a lot of stuff happening in there. Did you debug it to see
why
> it was not working? Particularly the "computeSelectedDateRangeIndex()"
> function? Was it being called when you expected?
I agree with Tracy. I would expect
The code snippet worked fine for me if the intervals property is an
array of strings. Is it possible you are initializing intervals from a
web service call? If so, you have a timing problem in that the
selected index was set long before the data arrived (actually it
thought it had zero rows o
3 matches
Mail list logo
