I've got some scenarios where binding does not fire if I use
ac.addItem or ac.removeItem.
But it will fire if i use ac = new ArrayCollection......
This is hard to reproduce as it only usually happens in large apps.
If i create simple test cases it usually works.
Anybody have any hints why ?
On 01/02/2008, at 5:57 AM, Alex Harui wrote:
You should use Array anywhere you don’t need binding or events that
indicate changes to the array.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of Teddy Setiawan
Sent: Thursday, January 31, 2008 8:39 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Re: Array vs ArrayCollection
I have the same problem regarding slower performance using
arraycollection in some iterating process.
Then I change it to array , but I get another big
problem......memory leak.
I use the array for small iterating process and using
arraycollection for larga data.
To: flexcoders@yahoogroups.com
From: [EMAIL PROTECTED]
Date: Thu, 31 Jan 2008 16:18:46 +0000
Subject: [flexcoders] Re: Array vs ArrayCollection
This is something I too wonder about from time to time. I notice alot
of developers are using the ArrayCollection for data binding but I
can't say with 100% confidence why one would be used in any specific
problem domain opposed to a basic array. I guess if you find you want
to use the functions exposed by the ICollectionView and IList
interfaces the ArrayCollection is your tool.
Anybody have any clear examples?
Nick
--- In flexcoders@yahoogroups.com, "rmarples" <[EMAIL PROTECTED]> wrote:
>
> We have recently made some big performance gains in our product by
replacing the use of
> ArrayCollections with Arrays in some data calculation algorithms. It
appears that even
> iterating through an ArrayCollection is significantly slower than an
Array.
>
> My question to you all is... what have you found to be the best
place to use one of the other
> in your applications?
>
> Ryan
>
Connect and share in new ways with Windows Live. Get it now!
