Maybe call invalidateList() when the filter changes? Just a guess.
--- In flexcoders@yahoogroups.com, "Rick Root" <[EMAIL PROTECTED]> wrote: > > So I'm building an application which contains lists of items that I > want users to be able to filter, select some items, filter again, > select some more items, etc. > > However, when a selected item is filtered out, when the filter is > removed, the item is no longer selected. > > Take the following example: > > http://www.it.dev.duke.edu/public/CheckBoxListTest/CheckBoxListTest.html > > select "Item 1" then filter for "Item 2"... don't select anything. > Remove the filter now. > > Item 1 is no longer selected. But the label still says it is > selected.. the label is bound to the > {cboRatings.selectedIndices.length} property. > > In my test application I can't get it to work the way I want it to at > all. In my real application, it works sometimes but not others. > > I thought maybe it was the CheckBoxList component that someone had > written for me... or the CheckBoxListItemRenderer that was part of > that component, but i'm finding the same problem in the above test > application which only uses a simple, standard list component. > > If it makes any different, I'm compiling the application with Flex > Builder 3 (beta 2). I've compiled it with the Flex 2.0.1 HF3 SDK and > the latest Flex 3 beta SDK. > > Why doesn't the list remember what's selected? Doesn't the filter > simply prevent an item from displaying? > > -- > Rick Root > Check out CFMBB, BlogCFM, ImageCFC, ImapCFC, CFFM, and more at > www.opensourcecf.com >
