Re: searching in headers
Re: searching in headers
- Subject: Re: searching in headers
- From: Matt Neuburg <email@hidden>
- Date: Sun, 01 Aug 2004 19:13:19 -0700
On Wed, 28 Jul 2004 22:30:57 -0700, Chris Espinosa <email@hidden> said:
>On Jul 28, 2004, at 8:39 PM, Heath Raftery wrote:
>
>> On 29/07/2004, at 1:17 PM, Prachi Gauriar wrote:
>>
>>> On Jul 28, 2004, at 9:18 PM, Matt Neuburg wrote:
>>>
>>>> What happened to the cool feature where command-double-clicking a
>>>> word would
>>>> take you to the header where that word was defined? Thx - m.
>>>
>>> It's still there.
>>
>> And still here in V1.2. What version are you using, Matt? Perhaps you
>> need to rebuild your project index, so XCode can find the symbols.
>
>I think you suffer from the misconception that the project index is
>generated at build time. In 1.2 and later, it is not; it's done by a
>separate indexing task.
>
>To reindex your project, select the Project icon in the Groups and
>Files outline view, choose Get Info, and click the Code Sense tab in
>the Inspector. Make sure that Code Sense is on; you can then click the
>Rebuild Index button to rebuild the index.
>
>Indexing takes some time depending on the number of source files in the
>project (more so by the number of system frameworks you include, as
>those have to be indexed, too).
>
>Only when your project is indexed will features like code completion,
>symbolic navigation, the Class Browser, the Project Symbols smartgroup,
>etc. work.
I do not know what it means to "make sure Code Sense is on"; but indexing is
enabled. Some code completions do work, although others cause an error in
Xcode: "Uncaught Exception: *** -[NSCFArray objectAtIndex:]: index (0)
beyond bounds (0)". I do not know what symbolic navigation is, so I can't
speak to that. Project Symbols works. The Class Browser does not - it
doesn't see outside the project. When I rebuild the index it happens very
fast, and it is apparent that the project itself is being indexed but Cocoa
header files on which it depends are not.
Other projects do not behave this way (and command-double-click works!). I
cannot find a relevant difference in settings between this project and the
others.
Throwing away the build folder and opening the project again makes no
difference.
What could it be about this project that is causing this special
(mis)behavior? It's a small, ordinary Cocoa project. The built app works
fine. :) Thx - m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide
<http://www.amazon.com/exec/obidos/ASIN/0596005571/somethingsbymatt>
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.