Re: Multiple search windows?
Re: Multiple search windows?
- Subject: Re: Multiple search windows?
- From: Steve Mills <email@hidden>
- Date: Tue, 9 Oct 2007 13:33:11 -0500
On Oct 9, 2007, at 13:16:43, kwiley <email@hidden> wrote:
Good suggestion. Thank you. I see how that works. It isn't nearly
as versatile as CodeWarrior of course, which would preserve the
selected block of code in its own window, and could display countless
searches simultaneously, but it should help.
Especially if you don't use that project window layout (all in one or
whatever it's called). I use the one where the project window is its
own window, like CW. It's much easier to get things done and it
doesn't take up so much space.
<sigh> There are so many things I miss about CodeWarrior. It's
syntax coloring is so much more diverse, the cursor was actually
visible against a black background, the global search window enabled
not only project search but also directory search and accepted
regular expressions, and now this lack of multiple search windows
issue...so many nuances are missing from XCode. It's a mature
product now, it's several years old. Shouldn't these kinds of
"extra" features be in XCode by now?
Am I only the only person who thinks this? Do other Mac programmers
think XCode is the greatest thing every created and that anyone who
complains about it is being unfair? If so, I apologize.
Some things Xcode does very well, much better than CW. But in most
cases, like the day-to-day code organization, editing, and such, CW
is still miles ahead of Xcode. The multifile Find window being just
one great case where CW kicks tush. It's really annoying to have to
remember the 2 or 3 search terms that found you the results you were
looking for and have to continually perform those searches again
(using the previous searches popup makes it a *little* easier, but
that stops working (no longer shows the search results instantly
without having to do the search again) once code has been edited or
something). Plus Xcode's multifile Find window doesn't hard-map the
return key to the Find button, so you have to reactivate the Find
field before you can hit return (like if you've moved on to the
Replace field). And once the source code pane has been activated,
there's no way to get back to the Find field via the keyboard except
by hitting command-option-f again, which is not nearly as simple as
hitting tab or option-tab.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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