Pollok Shields
Active Member
- Joined
- Feb 3, 2015
- Messages
- 107
- Lightroom Experience
- Advanced
- Lightroom Version
LR comes with a bunch of develop presets I'm never going to use. I want rid of them. Any clues?
Welcome! Login here or Register for exclusive content.
LR apparently does not allow "Untitled Folder" to be used as a valid Folder name. This is probably to insure that the default value (Untitled Folder) has been replaced by a Valid Folder name value. A valid folder name needs to conform to the naming convention of your FileSystem AND not duplicate any other sub folder where created.
I can also put spaces into an 'Import' sub-folder; same caveat that there are no spaces at the end.
With everyone running Sierra, I can only conclude that there is some LR Preferences setting. In the File Handling tab of Preferences, there is a File Handling section. that controls file naming. ( folders are a part of the file name)Well, all I can conclude is that Lightroom does not behave the same on our systems. You saw the screenshot, complete with the error message. That error message even has the Lightroom icon on it, so it does come from the application.
With everyone running Sierra, I can only conclude that there is some LR Preferences setting. In the File Handling tab of Preferences, there is a File Handling section. that controls file naming. ( folders are a part of the file name)
Paul & I can create everything in Presets folders as long as there is no trailing space. In the Folder panel, I can add a new folder "San Francisco" without it converting to "San_Francisco" So I ask those of you that can't match the results that Paul & I get to compare your File Name Generation section with mine below:
Actually they are a part the path which is a part of the file name and are treated by the OS a zero length files. No bug here. But I agree that Adobe could make this section clearer to encompass folders and are always a part of the file name.Folders are not files!
Actually they are a part the path which is a part of the file name and are treated by the OS a zero length files. No bug here.
It depends how you define a bug. A bug does not necessarily mean broken. A bug or to use a more precise term 'defect', might be when an application does not confirm to requirements. If I were testing the application and I couldn't create a preset folder because some where in the file handling Preferences setting it said don't allow spaces in the file name (which as an application user are two completely unrelated things), then unless that was specifically defined in the user requirement I'd raise a defect.No bug here.