Actually, this is a non-issue. The visual activity isn't as bad as I thought if I just set the filterfunction to null while I'm doing my editing of the value object.
--- In flexcoders@yahoogroups.com, "steveb805" <quantumcheese...@...> wrote: > > > I have a filter function for a List that hides the item if the duedate is > larger than a particular number. > > In a function I call, to change a value object field, as soon as I hit this > line below, the filter goes into effect (which is expected since duedate is > the field specified in the filter) > > projectListAC[projectList.selectedIndex].duedate = tempDateNumber; > > and hides the item, and the selectedIndex goes to -1. > > (projectListAC is the dp) > > If I temporarily set filterFunction to null, and then change the duedate, and > then set it back to the filter, you get a visual flash of all a sudden a lot > of items becoming visible, and then back again. > > Not really the effect I want. > > Shouldn't the List only change after calling refresh() on the dataprovider? > As soon as i change the List's value object field, the filtering takes place > > Steve >
