I'd create a util class listens to CollectionChangeEvents from your collection and keeps a list of what's added, a list of what's dirty, and a list of what's removed. It'd probably take 2 hours to write and be a pretty useful util class.
-Josh On Fri, Jul 18, 2008 at 10:26 AM, Gordon Smith <[EMAIL PROTECTED]> wrote: > Please note that you can implement toString() on the item class to do > anything you want. But that doesn't imply it's a good way to compare two > collections. > > > > Perhaps you should reconsider whether you really need two collections that > may or may not be exactly the same. Or consider keeping a 'dirty' flag that > you set to true when you add, remove, or edit an item. > > > > Gordon Smith > > Adobe Flex SDK Team > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
