• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode's Find in Project
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode's Find in Project


  • Subject: Re: Xcode's Find in Project
  • From: Jim Wintermyre <email@hidden>
  • Date: Mon, 19 Feb 2007 13:10:54 -0800

 > I think your complaints are more nits than serious shortcomings. Does
 > the Find in Project feature actually get in your way every day? And is
there no acceptable workaround?
When using projects containing multiple sub-projects the find function
is absolutely unusable. It insists on opening a new window containing
each sub-project. Xcode's support for sub-projects in general is
woeful.  Try doing a command click to find a symbol that's defined in a
sub-project. You'll be lucky if it ever finds it.

Totally agreed. I filed a bug report for the symbol-in-subproject issue (radar 4916555). I set up my XCode projects to mirror the CW setup, which used a lot of subprojects, and now I'm kicking myself because of the lost productivity time due to subproject issues. If indexing across sub-projects is working for some people, then it must depend on the type of project, because it's totally broken for me.


Whether they are called "cross-project references" or subprojects, XCode should either *fully* support them like CW did, or the limitations should be clearly documented. I can't think of a technical reason why it couldn't fully support subprojects a la CW. All the indexing info is there and I would think the IDE *could* be changed to use it.

I still have CW versions of all my projects. Thank God. Whenever I need to do actual work, I'm working in CW. Then I go build and debug in XCode. These little "nits" that everyone is bringing up add up to serious productivity killers in XCode for me.

However, my main beef with the Xcode find is the lack of a "Find All" in a single file, as well as the inability to have each multi-find file search result in a separate window.

Yeah. How could that be omitted? Maybe they figured "well you can just do a find all in the project, and then just look at the results for the one file you actually wanted"?? Pretty much whenever I need to do some serious searching, I open up CW.


Xcode supports closing all if you Option- click the close button, but alas the menus don't support the standard Save All and Close All commands (go figure -- another useful standard Mac behavior not seen in Xcode).

Thanks, I've been wondering why the hell that wasn't implemented! Wonder what other potentially helpful features I'm missing because they're buried... :)


Jim

_______________________________________________
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


  • Follow-Ups:
    • Re: Xcode's Find in Project
      • From: Lawrence Gold <email@hidden>
  • Prev by Date: Re: Dependency analysis failing - FIX (Re: What are your top desired improvements in Xcode ?)
  • Next by Date: Re: Cross-project references (was Re: Xcode's Find in Project)
  • Previous by thread: examining values of each element of an array in debugger
  • Next by thread: Re: Xcode's Find in Project
  • Index(es):
    • Date
    • Thread