Beginning with Xcode 9, Xcode can automatically create a filesystem folder when you create a group in your project. If you rename a group, and that group has a corresponding folder with the same name, Xcode 9 also renames the folder. In Xcode 9, if you drag a file from one group to another, and the groups have different folders, Xcode 9 moves the file to the new group's folder, regardless of whether the new group's folder has the same name as the group. If you do not want this behavior in Xcode 9, you can set an undocumented setting from the command line:.
Basically, Xcode tries to guess whether your new group should have its own folder based on whether its future siblings have their own folders.
You can create a new group, with its own folder, directly in Xcode, but it's not at all obvious. This doesn't save you much if you need to move existing files into the new group, because Xcode still won't do that. For those who are too lazy to synchronize the folders, there is a nice tool on GitHub. Synx is a command-line tool that reorganizes your Xcode project folder to match your Xcode groups.
It does not store any personal data. Functional Functional. Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features. Performance Performance. Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors. Analytics Analytics. Analytical cookies are used to understand how visitors interact with the website.
These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing.
The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form. Advertisement Advertisement. Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns.
These cookies track visitors across websites and collect information to provide customized ads. Cookie Duration Description IDE 1 year 24 days Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
The purpose of the cookie is to determine if the user's browser supports cookies. Used to track the information of the embedded YouTube videos on a website. Others Others. Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet. Powered by. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
If this is intended behavior that "Grouping" concept in Xcode is no more? Xcode should atleast be able to update its reference to the path on disk, instead of move the file, and then sayig it doesn't know where it is. What's weird is that in a new project if you choose "New Group" it creates an actual directory breaking with Xcode's previous behavior as already mentioned.
But I noticed if you create a new project and before creating any "Group" you choose "New Group without Folder" then the "New Group" menu item creates groups without folders the old way. So the meaning of the context menu item "New Group" changes based on whichever grouping style you choose first. Seems pretty convoluted to me.
Even still, silently changing the meaning of "New Group" based on the initial action in a project seems weird. Does the HIG say anything about that? Would make more sense to make it a preference in Settings I'd think, than potentially having "New Group" behave differently from project to project. But what do I know?
You mean the release notes? I don't think the HIGs speak to the mechanics of Xcode, so much. Getting file management in XCode closer to Finder's may be a good thing. But forcing to manually update seems awful. XCode is doing so many more complex tghings, it could keep track, at least propose in a dialog to do it. Claude31 Yea, I'm not at all opposed to it, though I don't think using the same menu item title for two different actions "New Group" depending on a previous action silently, is a good user experience.
It certainly makes sense to have the behavior of "New Group without Folder" the old way and "New Group with Folder" but IMHO the "New Group" menu item should only be one or the other, not both, and shouldn't change from project to project based on a subtle action. I should be able to make my choice in preferences and be done with it. Now that I know how it works, I guess I'm over it, but I still don't think it is good to have an action title be somewhat ambiguous.
Of course the HIG doesn't specifically speak to Xcode functionality. I did just take a quick look at the menu section, and it doesn't seem to mention anything about consistency of menu item actions so I guess it may be okay, but then again they may have thought that that is so obvious that it wasn't necessary to explicitly state. And HIG rules are very clear that the consequence of a user choice must be predictable. Which is not totally the case here to say the least.
In addition, when XCode is able to detect a problem notably for build that would be great to help user make the required modifications notably when it resolves to simply cleaning a folder select the group, and then open the File inspector and click on the on the Clear path button X.
I noticed the same lack of help when dealing with build problems due to. I got a cryptic message, but no help to solve. Perhaps - that would be consistent with their easter egg habit where users are expected to explore and find certain features on their own. The problem with your complaint is that it's not clear that it's accurate.
I tried creating a new project, and followed these steps:. I selected the project item in the navigator, and chose "New Group without Folder" from the context menu. It created a new group with no folder association, and selected the group. Leaving the just-created group selected, I chose "New Group" from the context menu. It created a nested group with no folder association. I selected the project item, and chose "New Group".
It created a new group with folder association, as well as the folder itself. Thus, the behavior of "New Group" seems to depend on the parent group, not "based on the initial action in a project" as you claimed.
0コメント