Its still there in 2.0.1 and has more or less been confirmed as a bug by Adobe. There is a workaround though. Put
myCollection.filterFunction = null; just before updating your value, no call to refresh() necessary. That will prevent the erratic behavior and for now seems to be the easiest way to avoid it. Adobe is in fact researching the issue though. HTH, Ben --- In [email protected], Daniel Wabyick <[EMAIL PROTECTED]> wrote: > > Hi Ben, > > I had similar problems using filters on ArrayCollections and lists. Some > really weird rendering issues happened, and I basically manually > implemented filters (e.g myCollection.removeAll(), > myCollection.addItem( item1 ), myCollection,addItem( item 2)). This > played nicely with binding. > > I believe I filed bugs against this in 2.0, but I can't fully recall. > Did this change at all in 2.0.1 ? > > Cheers, > -D > > > > > ben.clinkinbeard wrote: > > > > Hi Dimitrios, > > > > Thanks for the reply. I am not sure exactly when/where you were > > suggesting I apply the sort, but even if that fixed the issue I don't > > know how usable a solution it would be. Since the collection is being > > displayed in a DataGrid, it may have already been sorted in various > > ways and I need to preserve the existing order. > > > > Thanks, > > Ben > > > > --- In [email protected] > > <mailto:flexcoders%40yahoogroups.com>, "Dimitrios Gianninas" > > <dimitrios.gianninas@> wrote: > > > > > > Try applying a sort function to the ArrayCollection, maybe that will > > solve your problem. > > > > > > Dimitrios Gianninas > > > RIA Developer > > > Optimal Payments Inc. > > > > > > > > > ________________________________ > > > > > > From: [email protected] > > <mailto:flexcoders%40yahoogroups.com> > > [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com>] > > On Behalf Of ben.clinkinbeard > > > Sent: Wednesday, January 03, 2007 5:05 PM > > > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > > > Subject: [flexcoders] Erratic behavior when modifying an item of > > filtered ArrayCollection > > > > > > > > > > > > Hello, I have a DataGrid displaying an ArrayCollection, and one column > > > using a CheckBox as the itemRenderer. I am properly overriding the > > > data method in the renderer and updating an underlying property of the > > > item that is clicked. > > > > > > The problem is that when there is a filterFunction applied to the > > > ArrayCollection, updating that underlying property causes erratic > > > behavior in the DataGrid, such as the reordering of rows. If there is > > > no filter applied or I comment out the line that actually updates the > > > row's value there are no issues, so its definitely related to the > > > updating of the data. > > > > > > Even stranger is the fact that not every row seems to trigger the > > > reordering. Clicking on the CheckBox in the first or last row in the > > > DataGrid always causes the problem, but with rows in the middle the > > > problem isn't as consistent. > > > > > > Anyone have any idea what is going on or how to avoid this? > > > > > > Thanks, > > > Ben > > > > > > > > > > > > > > > > > > -- > > > WARNING > > > ------- > > > This electronic message and its attachments may contain > > confidential, proprietary or legally privileged information, which is > > solely for the use of the intended recipient. No privilege or other > > rights are waived by any unintended transmission or unauthorized > > retransmission of this message. If you are not the intended recipient > > of this message, or if you have received it in error, you should > > immediately stop reading this message and delete it and all > > attachments from your system. The reading, distribution, copying or > > other use of this message or its attachments by unintended recipients > > is unauthorized and may be unlawful. If you have received this e-mail > > in error, please notify the sender. > > > > > > AVIS IMPORTANT > > > -------------- > > > Ce message électronique et ses pièces jointes peuvent contenir des > > renseignements confidentiels, exclusifs ou légalement privilégiés > > destinés au seul usage du destinataire visé. L'expéditeur original ne > > renonce à aucun privilège ou à aucun autre droit si le présent message > > a été transmis involontairement ou s'il est retransmis sans son > > autorisation. Si vous n'êtes pas le destinataire visé du présent > > message ou si vous l'avez reçu par erreur, veuillez cesser > > immédiatement de le lire et le supprimer, ainsi que toutes ses pièces > > jointes, de votre système. La lecture, la distribution, la copie ou > > tout autre usage du présent message ou de ses pièces jointes par des > > personnes autres que le destinataire visé ne sont pas autorisés et > > pourraient être illégaux. Si vous avez reçu ce courrier électronique > > par erreur, veuillez en aviser l'expéditeur. > > > > > > > >
