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

Bug 341166

Summary:	[CommonNavigator] Collapse tree state when file closed under Link with Editor
Product:	[Eclipse Project] Platform	Reporter:	Miles Parker <milesparker>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert, prakash, remy.suen
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Miles Parker

2011-03-28 16:30:40 EDT

Currently the "Link with Editor" functionality has one major annoyance that really reduces its usefulness. It doesn't take very long for the tree to become expanded in so many different places that the explorer becomes unusable, requiring the user to manually "Collapse All". Would it be a workable solution to simply collapse the tree when the last file member in a hierarchy is closed? For extra credit, it might be nice to keep track of expansions that the user has done manually and leave those open.

Comment 1 Miles Parker

2011-03-28 16:37:10 EDT

[Moving to IDE]

Comment 2 Dani Megert

2011-03-29 04:18:56 EDT

Many views offer 'Link with Editor'. If we want to add this new behavior then we need to make sure that the most prominent views adopt this. Also, I would only accept the version that contains the "credit" ;-).

Comment 3 Miles Parker

2011-03-29 14:23:32 EDT

;-D I'm afraid the credit would be of the mostly imaginary kind though I would buy you a beer at next EclipseCon. But yes, it would probably violate principal of least surprise to close folders that the user had manually opened. One possibility is to provide an (internal?) API and I'd be happy to hassle other projects about adopting it. I had a thought that this is an issue that Mylyn might have partially solved - though their general solution is too heavy weight there might be a snippet or two in there.

Comment 4 Lars Vogel

2019-11-08 04:40:18 EST

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.

If the bug is still relevant please remove the stalebug whiteboard tag.