I've added a resources directory as a folder reference to the app bundle according to this question. I'd like to exclude some of underlying files, since I don't need them in my app.
The "Delete" context menu item is disabled on every file below the root folder. If I add the files with "Create Groups", they are added flat, without any hierarchy.
Is it possible to remove specific files under a folder reference? Is there another way to add files and keep the hierarchy?
You could create a symbolic link to the folder, add a group that points to the link, and then remove references to any files unwanted in the group.
As the name implies, it's a reference to the folder, not to the files. The folder gets included in your bundle. If you don't want some of the files in the bundle, you'll have to remove them from the folder.
Related
is there a way to move this folder with Issue Templates to .git ?
i have more diverse stuff to fill this file list with, this one just takes space for no use . and i don't want to extend editors with file hiding functions .
If you have no use for the .github directory, one solution is to simply delete it. You can have a look at this answer to see what it contains. Many of its contents can simply be moved to the project root (or deleted, if you don't need them).
You could theoretically put them in the .git folder, but you would not be able to actually git add them (you'd basically be making the .git folder track itself), so you're losing all the benefits of using git in the first place.
I would like to know if it is somehow possible to only edit the path to the Shapes folder from the default Tableau Repo.
I know the path to the entire repo can be edited within the software but I am only interested in the Shapes folder.
I would like to have it stored in a shared drive, and eventually doing the same thing with the Preferences.tps file. I don't want to place the entire repo on the shared folder mainly because the datasources folder has some customizations that can't be shared.
Best,
Max
have you tried using a symlink on a mac, or a shortcut on Windows for the Shape folder?
Thank you Alex...
I need to checkout files from StarTeam 12.0 into my local folders.
The folder tree on starteam is like :
folder_top
folder_level_1a
subfolder_level_2
subfolder_level_3
folder_level_1b
folder_level_2
folder_level_3
But, after checking out all files in my specified local folder, all files (of folder_top) are located in one folder. All subfolders and their files are not checked out.
Any help would be appreciated.
Selecting your top folder, then selecting Check Out All from the File menu will check out all the files in that folder and descendant folders.
Also, note that clicking the All Descendants button will show all files in descendant folders as well as the selected folder.
Sounds like you might have checked out to a specific location. There is (or at least used to be) an option in the check-out dialog to override the location of the checkout, and in this case all of the files would be placed in that specific location. What you need to do in StarTeam is set your Alternate (not Default) Working Folder for the View, and then all of the files you check out will be put in the relative location based on the folder name. Do not override the working folders at the folder level, because this will cause your folder structure not to be mirrored. If you keep it simple and always set the Alternate Working Folder at the View and nowhere else, all your checkouts should go to the expected location. Don't override in the checkout dialog. Keep in mind, however, that even if you don't override the default working folders at the folder level, someone else on your team might. In those cases you can override their overrides by setting your alternate working folder to the folder name. This is one of the most painful and poorly designed aspects of StarTeam and always has been. Despite years and years of proposed enhancements to fix this, they have done nothing to address these issues. Be vigilant!
Over the last few months, I've been doing some maintenance on a project with many source files. I was recently informed that there is an issue with one of my bug-fixes and I was asked to fix my bug-fix.
However, since there are so many files and folders within the project, I can't remember which one I modified.
Therefore, I would like to be able to search within the root directory of the project for changesets that have affected files within the folder. I'm sure that I could determine which changeset caused the problem by the comments I put on them.
How can I find all TFS changesets that affect at least one file within a specific folder?
If you're interested in viewing the history for a single folder, navigate to that folder in Source Control Explorer, right-click on it and select "View History".
This will show you all the changesets that have affected this folder.
i just realized that all my groups in Xcode are ignored and all files i added to my project are copied into the Documents folder directly.
As i have several different types of files i want to keep them organized from the beginning.
So is there a way to predefine a folder hierarchy in the Documents folder of my app and place my files in the corresponding folders or do i have to move them manually on my first app launch?
regards and thanks for any help in advance!
Max
Nothing in your app automatically goes into the Documents folder when an app is installed. Your app must specifically copy or create files in the Documents folder. You are free to create any subfolder layout you want in the Documents folder. This must all be done at runtime.
If your goal is really to package your app so certain resource files are organized into a fixed folder structure in the app's resource bundle, then that is a different issue. This can be done but it requires that when you create the folders in your project, you don't simply make a group, you must create an actual folder reference. Folder references appear as blue folder icons in Xcode, not yellow like all other group folders. When you add files to your resources, the dialog that appears for the file chooser, be sure to select "Create Folder References for any added folders" instead of the "Create groups for any added folders".