Could it be that you're deleting something in a source collection, and looking at another collection that's referencing that collection, but there hasn't been a frame tick and so the relevant events haven't been processed yet? It's the only thing I can think of without doing some brute-force stuff and checking for results and throwing an exception on finding the problem as a point to get into some serious single-stepping inside ArrayList / CollectionView....
-Josh On Wed, Jun 18, 2008 at 8:45 AM, richcianci <[EMAIL PROTECTED]> wrote: > --- In [email protected], João Fernandes > <[EMAIL PROTECTED]> wrote: > > > > I'm having this weird issue that never happened before. > > Sometimes, totally randomly, after deleting a managed item in a > > arraycollection, instead of getting the arrayCollection resized by - > 1, > > my arraycollection keeps the same size and I get a null object > where the > > managed item was previously. > > > > This happens using ds.deleteItem() or using > > arrayCollection.removeItemAt( itemIndex ) > > -- > > > > João Fernandes > > > > http://www.onflexwithcf.org > > http://www.riapt.org > > > > I am having the same issue. Did you ever figure it out? > > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
