How to view the complete expanded DGML generated from Architecure - CodeMap menu , till fields/methods.
For each level currently we are required to select and click on expand in Group menu and it expands one level.
How to drill down to all levels at once.
You can't do that, you have to expand level by level. The reason we didn't put something like this in the product was that as you drill down more and more graph elements are created on the screen and it becomes unmanageable / unusable fast.
Alternatively, there are a few code queries you can use, if you right click on a class etc. you see options such as "Show all classes derived from this" etc.
In the project view in Intellij IDEA, there is an option to "hide empty middle packages".
Is there an equivalent for folders? I don't want a sole "src/main/java" to take up 3 lines...
No, there isn't.
But if your folders are getting so long, you can always scroll the project pane to the right :)
It's also possible to use a different view (e.g. Packages) or define bookmarks and favourites to navigate around quickly, plus enable Auto-scroll from source.
Is there any way to Collapse all folder on the Directories Tab in SmartSVN Foundation 8.0.1?
I Accidentally pressed Ctrl+A (Select All) and ALL THE FOLDERS COLLAPSED!
Now if i want to add a specific folder i need to collapse some or all... or most, but there's no easy way to do it, right now i'm doing it one by one, but the vendor folder (all composer packages) is enormous.
Any ideas?
Seems odd. I've tried to replicate this and have been unable (I'm assuming you're on Windows?) even if I select all and then click the collapse icon on one folder it just collapses that folder.
More than happy to raise a feature request for you if you could give me a bit more detail about what you're after? For example, adding a 'collapse/expand all' and/or a 'collapse/expand selected' option to the View menu that you could set a custom shortcut for in the Edit -> Customize -> Accelerators options?
I use intellIJ. Sometimes I have two packages, A and B, that are nested such that A contains B and nothing else. When this happens then the folder structure on the left displays them like this:
I don't like how it groups A.B together into a single tree node. Is there a setting to prevent IntelliJ from doing this?
(I've googled around a bit and dug through the settings menu and I'm not seeing anything but may'be I've missed it.)
Click on the gear icon on top of the project panel and look for "Compact empty middle packages"
I have an Xcode 4 objective-C project which contains about 150 .m and .h files in it.
The code underlying the project does not always correspond in underlying disk structure to the folders shown in the Xcode project. I get that part.
What I don't get is why Xcode won't tell me anything about why I can create new project groups and move items to them, with no problems, but certain existing project folders will cause the project to become broken, and the code will no longer build once I move certain .m files or .h files into a different group. When its broken it just shows the file in red. This is frustrating and confusing.
In the screenshot below, the left side of image before shows state before, when all is good, right side shows red (missing) file after moving into a group. Given that groups don't represent a folder on disk, I would not expect moving from one group to another to break things. Sometimes it does, and sometimes it does not. This particular XCode issue upsets me a lot.
In the good old days of Friendly Mac User-Interfaces, you could hit ⌘+I and get some information about the properties of objects, or right click and get to the properties of something via its context menu. Groups (folder icons) in XCode projects have no properties item in their context (right click menu) and yet these groups all clearly NOT all alike. What's up with these identical looking groups?
Secondly, how does a person learn how to reorganize both the on-disk-folder-organization and the visual group organization, in a way that does not leave you bloodied and beaten? (XCode 4 is the most difficult IDE version I have ever used, for this, I'm sure I've missed some important documentation on dealing with folders and files and so on.)
Update: The File Inspector (Identity Inspector in Utilities menu) is the key to this mystery, but exactly how a new user is to discover this (other than by painful experience) is still unknown to me. I also don't really understand what all this is about, with various choices available in the Path drop-down, and the blank or non blank value that has no description or help, just a cryptic icon and either a name of some real on-disk-folder or else a gray text field saying None:
This sort of thing doesn't just happen out of the blue. In this case, what has happened is that a user has opened an .xcodeproj and is unaware of the difference between the various relative or absolute Path options that a Group can be a part of. A Group in XCode is always shown with exactly the same manilla color folder-icon inside your XCode project, no matter what modes or properties it has defined inside of it.
By default the simplest case is that you create a new folder Group object in XCode and it's purely a cosmetic organizational tool that has no disk location information stored in it.
This is not the ONLY thing that these groups do, and not the only "mode" that these groups can be used in. These groups can also be used to point at some folder and say "things that are in this virtual folder are really somewhere else, either underneath this project's main folder in a subdirectory, or even up somewhere else on your hard-drive, either stored in relative path, or absolute path format". When used like this, these things remind me of a Windows "Shortcut" object on the desktop, or a Mac "Alias" object in the finder.
Dragging a file from one group to another does not move it to a different folder on the disk. It simply moves a reference to a file with a certain name, to another group, which might mean that after you drag a file, you haven't really moved it, or copied, or relocated it in any way, you've just moved an alias from a place where it could resolve properly to a real file, to a place where it can't. Thus XCode helpfully turns it red for you, without any helpful error message about what happened.
How do you fix it? In this case, go to the Identity inspector pane in the Utilities menu, and either decide to clear out the bogus value in the place where I have shown in the picture in the original question where I had "Classes". Clearing out a value that is invalid is not exactly easy to do because XCode requires that you basically find the root folder of your project and select that, and that will 'clear" the relative or absolute path property on your folder-group.
Alternatively, you can leave the folder alone, and just don't drag files from group A to group B without first checking what relative or absolute path they reference.
What still seems horrible to me is that XCode tutorials tell you to "use XCode to manage your project's contents, don't just drag files around in the finder inside an XCode project directory", and that's good advice, but it leads me to assume that XCode provides full and intuitive physical (and virtual) group-folder organization tools. It does not. As an example, imagine you inherit a project that has .m and .h files scattered through four physical folders underneath the main XCode project folder and you want to move those files around. You have to do a combination of tricky things inside XCode, and either in Terminal or in the Finder, in order to reorganize your folder. With the complications involved in moving items around in your version control tool of choice added upon the top of that, and XCode's very limited support for only Git and Subversion, you have a really tricky mess.