Re: Jump to Definition problem
Re: Jump to Definition problem
- Subject: Re: Jump to Definition problem
- From: João Varela <email@hidden>
- Date: Tue, 8 May 2007 19:41:42 +0100
There's been a lot of discussion of the inadequacy of Jump to
Definition,
but I have a problem I haven't seen discussed here. I'm wondering
if I've
run into a feature that I don't understand, or if it's a bug.
I am working on two projects that are very similar because one is
a branch
of the other. That means they share lots of symbols.
When I control-click on a symbol (usually the name of a function) and
select Jump to Definition, I get (at least) three choices in the
resulting
menu. Two are from the older branch and one is from the newer
branch. This
is in spite of the fact that the two branches are in totally separate
projects, separate source file trees, etc. It happens when I have
only one
of the projects open. It happens in both projects- the old one and
the new
one.
Does anyone know if this is a feature or a bug? If it's a feature,
can I
disable it? If it's a bug, does anyone know of a work-around?
This happens to me as well. It's particularly dangerous when you
don't notice and end up editing the wrong file. Jump to Definition
is potentially really useful but half of the time it takes you to
the wrong file, half the time it does nothing at all and the other
half it gives you an enormous menu containing prefix matches for
the symbol you clicked on which invariably doesn't include the
symbol. I'd love to see this working properly in a future version....
Jerry
Did you file a bug containing a project example where this happens? I
do not have the problem you describe. Invariably when I hit "Jump to
definition" Xcode finds what I want, even in different multi-target
projects with shared code.
Joao
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden