Bug 216578 - Project Explorer doesn't update focus to show where the currently selected source file is located
Summary: Project Explorer doesn't update focus to show where the currently selected so...
Status: RESOLVED INVALID
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 5.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-25 08:14 EST by Chris Grey CLA
Modified: 2008-01-25 11:19 EST (History)
2 users (show)

See Also:


Attachments
Screencap of Project Explorer not updating focus (129.22 KB, image/jpeg)
2008-01-25 08:52 EST, Chris Grey CLA
no flags Details
Screencap of Project Explorer not updating focus (129.22 KB, image/jpeg)
2008-01-25 08:53 EST, Chris Grey CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Grey CLA 2008-01-25 08:14:13 EST
Build ID: M20071023-1652

Steps To Reproduce:
1. Open a few *.c or *.h source files from Project Explorer. Choose files that are in different folders. 
2. Click between the various files that are open. Project Explorer doesn't update to show where the currently selected file is in the file hierarchy. 



More information:
This is an annoying problem when you F3 (Go to Declaration) and the IDE opens a *.h file that you aren't familiar with and don't know where it is in the project without doing a windows file search. The location would be obvious if the Project Explorer would update focus to whatever file is selected.
Comment 1 Anton Leherbauer CLA 2008-01-25 08:35:01 EST
This works for me in general. Can you give more details in which case this does not work for you?
Comment 2 Chris Grey CLA 2008-01-25 08:52:53 EST
Created attachment 87860 [details]
Screencap of Project Explorer not updating focus
Comment 3 Chris Grey CLA 2008-01-25 08:53:17 EST
Created attachment 87861 [details]
Screencap of Project Explorer not updating focus
Comment 4 Chris Grey CLA 2008-01-25 08:56:20 EST
One of those 2 attachment posts can be deleted. It's a duplicate post. And in both posts, my comments didn't make it to the board so here they are:

I'm working with the bundled CDT installation release which is based on Eclipse v3.3 because the v3.4 is not working well for me. This version, while deplete of some of the nicer features that have been implemented in v3.4 is more stable for me. 

Included is a screencapture showing the Project Explorer not updating. 
Comment 5 Anton Leherbauer CLA 2008-01-25 09:08:46 EST
You need to enable the "Link with editor" feature.
Comment 6 Chris Grey CLA 2008-01-25 09:19:12 EST
That took care of it! Until I knew to look for that feature, I didn't know it existed. 

I guess technically this bug can be closed, but the real bug is that this feature isn't on by default. Is there a good argument for keeping it disabled by default? I can't think of one. 
Comment 7 Mike Kucera CLA 2008-01-25 10:35:59 EST
(In reply to comment #6)
> I can't think of one. 

Well... because some people find it annoying. I don't like how it causes the project tree to keep expanding and expanding as you navigate.

Comment 8 Chris Grey CLA 2008-01-25 10:48:48 EST
At my company, we have a tree-structure in our User Interface that's much the same and we got the same complaints from customers that they would get "lost" in the tree. So what we did was automatically relocate focus like normal. But auto-collapse all other folders so there's only one folder/path completely expanded at a time. This solved both problems of getting lost in the tree and not knowing where you are when you jump to other locations. 

Given this dialoge, it seems logical that the same thing could be implemented here as a feature request, not as a bug.

Thoughts?
Comment 9 Mike Kucera CLA 2008-01-25 10:53:36 EST
(In reply to comment #8)

Sounds like a decent feature to me, you could open a feature request if you like.

Also, I think the Mylyn CDT bridge effort is trying to address issues like these, see bug 162558.

Comment 10 Chris Grey CLA 2008-01-25 11:04:51 EST
Many of the things I've been writing up as bugs are more correctly called feature requests OR usability issues/concerns. At my company, we treat usability issues pretty much the same as a bug, but I can also understand the need to handle them as feature requests.

So Where do I submit feature requests for things that are truly feature requests? I'd like to get the ideas somewhere where they can be kicked around and considered. 
Comment 11 Chris Recoskie CLA 2008-01-25 11:10:39 EST
Just to set some expectations...  this is very non-standard behaviour.  You might get the Platform team to implement it as an optional feature, but I doubt it would ever become the default.  Most of us would find it annoying because it's not the typical way an IDE works.

And to reiterate, the Platform team handles the project explorer's behaviour.  You'd have to take this up with them.
Comment 12 Chris Grey CLA 2008-01-25 11:15:42 EST
That makes sense. 

But to reiterate, is there a single repository for accepting/handling feature requests?
Comment 13 Mike Kucera CLA 2008-01-25 11:19:32 EST
(In reply to comment #12)

Bugzilla is used for feature requests, sorry I guess I confused you. I meant that you could open another bug asking for it as a new feature since this bug has been closed.