Thanks, I posted the following with a test case http://bugs.adobe.com/jira/browse/SDK-14892
- Ivo --- In flexcoders@yahoogroups.com, "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Please file a bug with a test case or post a test case in the forum. > > > > ________________________________ > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of ivo > Sent: Wednesday, March 05, 2008 11:47 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] How to maintain a Tree opened/close state after > removed/added to stage? > > > > Hello all, > > There is a behavior that is not apparent when building against Flex 3 > beta 3 but shows up of Flex 3 release. > > I have a Tree that is added/removed from the stage at various times. In > Beta 3 if I remove it from the display list & add it back at a later > time the tree is with the branches opened/closed as they were when it > was removed. > > In the Flex Release the Tree always has all the branches closed once it > is added to the stage. Looking at the Tree properties shows > Tree.openItems does have a correct list of open branches. Iterating over > this list to to open them, or close then open, or saving this list when > removedFromStage and setting it again on addedToStage, or invalidating > the display list does not do anything. My next shot is simulating mouse > clicks on the renderers travelling from the outermost branches inward > but this feels like overkill. > > Any suggestions on how to trigger the display so it matched the internal > open/closed state? > > Thanks, > > - Ivo >
