[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Call Hierarchy, Include Browser ... search behaviour
|
Well, I tried it with a WorkingSet, but it stil uses all projects within
the workspace.
E.g. in call hierarchy i get some mixture of calls within 2 or 3 projects.
These projects are either different MKS Variant Sandboxes of the same
project, or another project which shares some codebase but also has some
major differences to our project. Since the call hierarchy does not
state which call is from which project, that is useless until you close
all other projects and restart the search again.
Am 03/12/2010 12:00, schrieb Schorn, Markus:
You can use a working-set to limit the call-hierarchy to a single project.
The same applies to the include browser (I think).
Markus.
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of kesselhaus
Sent: Freitag, 03. Dezember 2010 01:15
To: CDT General developers list.
Subject: [cdt-dev] Call Hierarchy, Include Browser ... search
behaviour
Importance: Low
Hi folks,
I'm not sure if that is already addressed here, but I have
that rather
annoying behaviour of the Call Hierarchy Browser or the
Include Browser,
References ...
They all show the findings of all occurences in the whole
workspace and
not just the project I'm in. I have to close first all other projects
and reexecute the search in order to only get occurences in that
particular project.
I guess it is somehow related to the indexes, since they are saved in
the workspace and not the project?
Is there any option i missed to set?
Another thing I have problems with is, setting in a Makefile project
under Paths&Symbols the include paths to<> includes, seems like they
are only used for "" includes.
Regards,
Henning
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
