Re: Setting up searches in Xcode (Re: [ANN] Xcode + Leopard at WWDC this year)
Re: Setting up searches in Xcode (Re: [ANN] Xcode + Leopard at WWDC this year)
- Subject: Re: Setting up searches in Xcode (Re: [ANN] Xcode + Leopard at WWDC this year)
- From: Rua Haszard Morris <email@hidden>
- Date: Wed, 26 Jul 2006 14:31:26 +1200
One last whack for Xcode's find: it doesn't take into account the
search paths.
I think this is the main gold that I'm missing from CW - it would
know from what was #included (in combination with what the search
paths were) what headers to search.
Any combination of criteria to effectively hard-code this list of
files is a complete nightmare compared to CW's notion of "the headers
being used to build this target" - if you change the user header
search paths, you have to change the search criteria regexp for
"search headers".
I guess I should file a radar for it...
On 20/07/2006, at 9:49 PM, Laurence Harris wrote:
On Jul 19, 2006, at 1:57 PM, glenn andreas wrote:
The responses I'm getting seem to be making my point. So far I've
gotten three replies to my question and each time someone points
me to the Options window*, but no one has told me how to
configure a search of the headers. I'm sure it can be done, but
IMO, it would be obvious how to do so if Xcode's Find system were
designed better, and it says something that no one has actually
explained how to do it.
Let's take a quick stab at it - bring up the options window. We
want to make a new "Find Set", so click "Add..." and type in "In
Project Headers".
Click the radio button that says "Filter files using regex
patterns:". Click in the first column next to the pattern "\.(h|H|
hxx|hpp|i)$" so that the value is "=".
Close window. Done.
Now just select "In Project Headers" in the popup when you want to
only search in the project headers.
Thank you. :-)
Now, while this does work, it is far less than ideal because:
- Amazingly enough, not everyone is comfortable with regexp.
Something this basic shouldn't require regexp (or the use of a
second window) IMO. This is one of the things I intensely dislike
about Xcode: it just isn't user friendly. You can do what you need
to do, but even simple things tend to be buried in some not-very-
Mac-like interface that offers a lot of power and flexibility --
assuming you can figure out how to use it.
- An option that requires a visit to the Options window is an
option that can't easily be added to another search. For example,
suppose I have three find sets defined, and I use them when
searching the headers sometimes and source files at other times. It
sounds like Xcode is going to make me set up six find sets instead
of just letting me set up three and turn a check box on and off in
the main Find window.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40adinstruments.com
This email sent to email@hidden
_______________________________________________
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