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

Bug 152818

Summary: [Repo View] Repository view tree loses node position when expanding
Product: [Eclipse Project] Platform Reporter: David Williams <david_williams>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 CC: ekuleshov
Version: 3.2Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description David Williams CLA 2006-08-04 00:44:14 EDT
I'm not sure how to explain this, so I'll make a picture. 
In eclipse project repository, one small part  can be represented as follows. 

HEAD
        ...
        org.eclipse.compare.examples.xml (first)
        ...
        platform-compare-examples
                org.eclipse.compare.examples.xml (second)


The "platform-compare-examples" is an "alias", 
but I don't think that really matters. 
Its more the position and/or depth. 

If I double click or try to expand the second, nested instance of 
org.eclipse.compare.examples.xml
then the list and selection jumps around, and the ~first~ occurance in the list is the one expanded. 

From some "local" experiments, I think it really is the position, if I rename
so "a" comes before "o", 

HEAD
        ...
        a-platform-compare-examples
                org.eclipse.compare.examples.xml (first)
        ...
        org.eclipse.compare.examples.xml (second)
        ...

Then its still the first occurance that expands, not the second
(even though its now the deeper one. 

I swear I've seen similar bugs against the project/package navigators, but 
can't find them now. And, I tried a maintenance build and still seems 
broken in Repository Explorer. 

This does have an impact to WTP, since I'd like to define some modules and aliases to better represent our project's features hierarchy, but if the nodes do not expand right and the tree jumps around, then it gets so confusing as to be 
not worse that worthless (that is, confusing). So .. would be nice to fix in 
maintenance release, if possible.
Comment 1 Michael Valenta CLA 2006-08-10 10:51:00 EDT
The repo view does not handle expansion and selection preservation well. To fix it would be a fair amount of work and we do not have the manpower to address it. 
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:13:40 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 3 Eclipse Genie CLA 2021-09-24 15:25:59 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.