Sure, file a bug or comment on LiveDocs.
In practice, I don't think REPLACE will have more than one item at a time. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Wednesday, June 04, 2008 6:35 PM To: [email protected] Subject: [flexcoders] CollectionEvent(Kind) - the docs are no good, what's really going to happen? Guys, The docs for CollectionEvent and CollectionEvent aren't so good, leaving me with questions :) CollectionEventKind.REPLACE : The documentation for CollectionEventKind says ONE item is replaced at event.location. The documentation for CollectionEvent says items contains a list of PropertyChangeEvents, and the source to CollectionView seems to be expecting a list of many but sequential beginning at event.location, with oldValue and newValue being for the individual list item objects. Is the source allowing for something that never comes up, or is the documentation for CollectionEventKind incorrect? CollectionEventKind.UPDATE : The docs for CollectionEventKind say X objects are updated, and event.items contains N Items or "ObjectChangeEvents", which I hope is a typo :) The documentation for PropertyChangeEvent say X objects updated, with N PropertyChangeEvents in event.items, and CollectionView seems to expect only PropertyChangeEvents, but more detailed, one for each modified field of a list item, and said Item can be anywhere in the list. I'm going ahead assuming the code in CollectionView is expecting things that actually likely to happen, just wanted to a) flag that the docs are incosistent, an b) give the list a chance to correct my interpretation of things :) Should I file a bug regarding the docs for CollectionEventKind? -J -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
