| Summary: | [Change Sets] Adding a changed file to a changeset collapses part of the Tree | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Benjamin Pasero <bpasero> |
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | CC: | bokowski, dominik.stadler, mlists, shashwat.work |
| Version: | 3.3 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 113675 | ||
| Bug Blocks: | |||
|
Description
Benjamin Pasero
This is in the Team/Synchronize view, showing outgoing changes, with change sets enabled. Expansion preservation is complicated by the fact we are using the Common Navigator framework. We won;t have time to look into this for 3.3. Btw, in my application using a simple TreeViewer I am seeing the same effect (not sure if its related at all though). Could this be a Platform/UI issue then? It could be. I don't know if it applies to this case but, in the past, I've seen similar behavior that was caused by some optimizations in the tree viewer to reuse tree items when there are additions/removals. Depending on where an item was relative to an added/removed item, the tree may lose expansion state. Boris did some work in this area in 3.3 so I've copied him in case he has any insight. Yes, this is caused by TreeViewer - it reuses tree items and only preserves expansion state one level deep. See bug 113675. 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. |