Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344737

Summary: [client] navigator expansion cache not handling nested expansions
Product: [ECD] Orion Reporter: Susan McCourt <susan>
Component: ClientAssignee: Project Inbox <orion.client-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: jainnayna, pradyutksarma, simon_kaegi
Version: 0.2Keywords: polish
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Susan McCourt CLA 2011-05-04 13:21:51 EDT 
the code that remembers navigator expansions is traversing the expanded nodes in the order they were expanded.  This ensures that we open the parent before we open, say, an expanded child.

The problem, though, is that the expand is asynchronous, so we need to be smarter about expanding the items in the cache.  If the item is nested under the previous item, it needs to be expanded only after the first expansion is complete.

I hadn't noticed this because I tend to link directly into the tree and expand only a couple levels.  but if you are using a deep tree it's immediately apparent.
Comment 1 Susan McCourt CLA 2011-05-04 13:28:10 EDT 
I just realized that the fastest way to handle this would be to analyze the cache list and figure out how much depth is needed.  Then we would only need to do one get.  The challenge then becomes collapsing the nodes that weren't open at that level.
Comment 2 Susan McCourt CLA 2011-06-13 12:34:06 EDT 
*** Bug 349134 has been marked as a duplicate of this bug. ***
Comment 3 John Arthorne CLA 2015-05-05 15:48:07 EDT 
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:


https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
Comment 4 John Arthorne CLA 2015-05-05 16:01:30 EDT 
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:


https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html