Re: How to "refresh" Find In Project info in Xcode 3.1.3?
Re: How to "refresh" Find In Project info in Xcode 3.1.3?
- Subject: Re: How to "refresh" Find In Project info in Xcode 3.1.3?
- From: Joar Wingfors <email@hidden>
- Date: Thu, 17 Dec 2009 18:49:16 -0800
On 17 dec 2009, at 09.40, Howard Moon wrote:
> How do I force Xcode to refresh all its Find In Project information in a C++ project? When I'm making a lot of edits, the Find In Project and Find Selected Text In Project features quickly get out of synch with the actual code. They still find the text I'm looking for, but double-clicking on them doesn't take me to the right place.
Xcode has special provisions for tracking ranges of text across edits, and is in general able to locate a find result even if you edit the file after having performed the batch find operation. As far as I know, this works fine. I am surprised to hear that this is not working for you in Xcode 3.1.x.
If you can reproduce this in a sample project, and in particular if you can reproduce it using Xcode 3.2, I'd suggest that you attach that sample project to a new bug report where you describe the issue:
<http://developer.apple.com/bugreporter/>
On 17 dec 2009, at 12.33, Howard Moon wrote:
> On a probably related note: when doing a project-wide Replace, sometimes it doesn't replace anything at all! It even confirms that I want to replace all 22 instances, and still nothing gets replaced. I've tried making sure nothing is highlighted before hitting Replace, but still it's as if it can't find the results of the Find In Project that it just generated.
This makes sense, and is a result of the original problem with finding the correct place for the find result. Xcode will not perform the replace unless it can first verify that the text that it is asked to replace is the same text as it found earlier.
> I wonder if Xcode is just running (way) behind in analyzing the code?
Open "Window > Activity Viewer" to see if Xcode is still indexing or not. I'm suspecting that this is a red herring though. Xcode only use the source index to search if you use a "Definitions" batch find operation. Even if you are using "Definitions", I think that Xcode waits until indexing is complete before searching (and so should never have incomplete or outdated information). That the problem persisted after you having forced the creation of a new index also makes this less likely. What type of search are you using? If you're not using "Textual", perhaps you could try to switch to that and see if you can still reproduce.
On 17 dec 2009, at 13.48, Ken Thomases wrote:
> Do your source files have consistent line endings? Files with inconsistent line endings (Unix LF vs. Mac CR vs. Window CRLF) give editors fits.
An inconsistent set of line endings in the file might perhaps result in something like what's described here. That's at least something to look for.
j o a r
_______________________________________________
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