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

Bug 337062

Summary: Include Browser and Call Hierarchy Browser should only search project
Product: [Tools] CDT Reporter: Henning Riedel <kesselhaus>
Component: cdt-source-navAssignee: Project Inbox <cdt-source-nav-inbox>
Status: NEW --- QA Contact: Jonah Graham <jonah>
Severity: major    
Priority: P3 CC: cdtdoug, malaperle, yevshif
Version: 7.0.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:
Attachments:
Description Flags
Ghost Projects when using WorkingSets as TopLevel-Elements in ProjectExplorer
none
screenshot mschorn.eclipse: iplog-

Description Henning Riedel CLA 2011-02-13 08:54:21 EST 
The Include Browser and CallHierarchy Browsers should only show search results from the current project, or maybe referenced projects.

Currently, when you use "Show in Include Browser" or "Open Call Hierarchy", the whole workspace is searched. Also, there is no distinction which results is from which project.

foo()
 + bar() - might be from project1
 + bar() - might be from project2

Using a workingset does not really help.
Comment 1 Markus Schorn CLA 2011-02-14 03:54:41 EST 
To distinguish between the results you can select to show the file-names in the view. It be helpful if you can elaborate, why a working-set is not helpful.

I think we could add a search-scope to call-hierarchy, type-hierarchy and include-browser, which would be one of workspace, project, referenced projects or a working-set. The selection of the search-scope should be available through the local menu.

A contribution would be welcome.
Comment 2 Henning Riedel CLA 2011-02-15 17:21:33 EST 
(In reply to comment #1)
> To distinguish between the results you can select to show the file-names in the
> view. It be helpful if you can elaborate, why a working-set is not helpful.

I wanted to say, that I tried a working set, but it did still show all findings from all open projects, even though, the projects are in different workingsets.

I'm usually do not use workingsets, since I have not that much projects in the workspace. Also, using WorkingSets and selecting the "TopLevel-Elements"->"WorkingSet" I get ghost projects of one project.

Though, using the "Show filenames" is a good point for now. (Wonder, why I missed that option.)

> 
> I think we could add a search-scope to call-hierarchy, type-hierarchy and
> include-browser, which would be one of workspace, project, referenced projects
> or a working-set. The selection of the search-scope should be available through
> the local menu.
> 
> A contribution would be welcome.

I'm a C programmer on Embedded Systems solely. My last encounter with Java-code is about 8 years back. ;/
Comment 3 Henning Riedel CLA 2011-02-15 17:54:12 EST 
Created attachment 189056 [details]
Ghost Projects when using WorkingSets as TopLevel-Elements in ProjectExplorer

Created a workingset.
Added one project to the workingset and make workingset active.
In ProjectExplorer-Menu, select TopLevel-Element->WorkingSet.

Change between workingsets or open/close project -> Ghost projects of the one project in this workingset appear, no matter if Eclipse 3.6.1 + CDT 7.0.1 or Eclipse 3.7m5 + CDT 8.0.

Project is a C-Makefile Project, with folders to external directories.
PyDev as nature, because some build related scripts are in Python.
Comment 4 Markus Schorn CLA 2011-02-16 08:05:01 EST 
Created attachment 189090 [details]
screenshot

You need to select the working-set from the local-menu of the call-hierarchy. It then limits the tree to the working-set, see attached screen-shot.