Not applicable
15-10-2007
04:47 PDT
- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
There aren't really any errors, it's just not updating the
Collection like it should. I have an object that has a unique ID
(once assigned, never changes) and an dateUpdated timestamp,
between the 2 fields, flex can tell when an object has been
updated. The Collection should have 10 items, and shows a length of
10, but only the first element contains the object, the rest are
nulls. I think it's just using the timestamp and since they all
have the same timestamp each overwrites the previous resulting in 1
object and 9 nulls.
Thanks,
Steve
Collection like it should. I have an object that has a unique ID
(once assigned, never changes) and an dateUpdated timestamp,
between the 2 fields, flex can tell when an object has been
updated. The Collection should have 10 items, and shows a length of
10, but only the first element contains the object, the rest are
nulls. I think it's just using the timestamp and since they all
have the same timestamp each overwrites the previous resulting in 1
object and 9 nulls.
Thanks,
Steve
Views
Replies
0 Likes
Total Likes