On Sep 20, 2011, at 22:41 , Gerriet M. Denkmann wrote: Just did. But then a Panel comes up, asking me:
Do you want to save this project in a new workspace?
You can only combine content with this project in a workspace.
Cancel Save
Well, I do NOT want a new workspace (don't even know what a workspace is). So I have to click Cancel, and everything is as bad as before.
Yeah, it's screwed up. I just did the same thing to one of my projects by creating a new group containing the project.
You can actually go ahead and let it create the workspace (which is just a container for one or more projects) and fix the grouping in the workspace, but that doesn't seem to fix it in the project itself (if you re-open the project outside the scope of a workspace).
However, that's the clue to the workaround. Part of Xcode 4's weirdness is that it *always* opens a project in a workspace. If you didn't create the workspace yourself, it puts a default one inside the project package itself. Any navigator structure to which the project belongs is in the workspace, not the project.
So, close the project in Xcode. Then, in the Finder, do a Show Package Contents on the project's .xcodeproj package. Inside it you should see the (default) workspace that it uses when the project isn't used in the scope of a workspace you created yourself. Drag that workspace out of the package to the Trash.
When I did that and re-opened the project in Xcode, the outer group was gone and things were back to normal.
Sounds like a candidate for a bug report, too.
|