Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 14959 - Synchronize View's tree is messing up expansion state
Summary: Synchronize View's tree is messing up expansion state
Status: RESOLVED DUPLICATE of bug 5771
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: James Moody CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-30 16:20 EDT by Randy Hudson CLA
Modified: 2002-05-16 14:36 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Randy Hudson CLA 2002-04-30 16:20:38 EDT 
If I have 4 folders with changes under them, and folder 1&3 are expanded, and 
folder 2&4 collapsed, like this:
+
-
+
-

And I select the first folder and commit the changes, folders 2,3, and 4 seem 
to slide up and reuse the TreeItems that were there.  As a result, the User's 
expansion state is completely screwed up.  In the above example, folder 3 gets 
collapsed, and 2 and 4 are expanded, completely inverting the prior state.
Comment 1 James Moody CLA 2002-05-08 13:31:29 EDT 
Investigating. This has annoyed me as well.

Our code simply calls refresh() on the TreeViewer. It's the tree viewer's
refresh code that "maintains" the expansion state, if I can use that word. It
appears that there is a bug in their refresh() code because it seems to remember
expanded state based solely on the item's index, rather than based on which
Object is underneath.

I will log a UI bug describing this.
Comment 2 James Moody CLA 2002-05-16 14:36:31 EDT 
This is actually a duplicate of 5771, no action required by the Team team. When
5771 is fixed the sync view will function as expected. Thanks for the bug report.

*** This bug has been marked as a duplicate of 5771 ***