maintaining group hierarchy
maintaining group hierarchy
- Subject: maintaining group hierarchy
- From: David Harper <email@hidden>
- Date: Tue, 29 May 2007 11:47:53 -0400 (EDT)
Hi,
I'm working on a (technically small) project with many nested groups. That is, there's an include group with several subgroups for all the header files, a source group with several subgroups, and a release group with a subgroup for each build target.
I'm having trouble maintaining the group hierarchy when adding classes to the project. I choose (add -> New file...) and it allows me to select a directory for the filles, but it creates both the header and .m file in the same directory, where I'd prefer the header to go in /include/group/subgroup and .m in /source/group/subgroup.
I move the files, and xcode claims they have disappeared and i have to delete and reset the references. Is there a better way to manage the hierarchy than to separately create the header and source files? Is there a way to make xcode move the actual /files/ when I move the references in the groups and files view?
Thanks in advance - still
warming up to Xcode.
-Dave H.
_______________________________________________
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