Difference between revisions of "ReNamer:Renaming folders"

From den4b Wiki
Jump to navigation Jump to search
m (markup cleanup)
(→‎Conflicting order: Refactored an example of conflicting renaming operation)
Line 19: Line 19:
 
If a parent folder is renamed first, the actual path for its contents changes instantly, with its new name. However, the subfolders and files contained in that folder are still listed in ReNamer with their old path. As a result, ReNamer is unable to find those items at the specified location, and therefore it cannot rename them.
 
If a parent folder is renamed first, the actual path for its contents changes instantly, with its new name. However, the subfolders and files contained in that folder are still listed in ReNamer with their old path. As a result, ReNamer is unable to find those items at the specified location, and therefore it cannot rename them.
  
For example, assume you have a folder named "C:\Folder" and a file named  "C:\Folder\File" in it.
+
=== Example ===
Assume also that you have listed '''Folder''' above '''File''' in ReNamer.
+
 
As soon as first '''Folder''' is renamed to '''New_Folder''', the path for '''File''' changes to '''C:\New_Folder\'''. However, the File is still listed in ReNAmer at its original location (with the '''C:\Folder\''' path). Thus ReNamer is unable to find '''File'''.  
+
Let's imagine that you have a folder <code>C:\Folder</code> which contains a file <code>C:\Folder\Document.txt</code>. You would like to rename both the folder and the contained file at the same time. You have listed the '''Folder''' before the '''Document.txt''' in ReNamer. As soon as the '''Folder''' is renamed to '''NewFolder''', the path for '''Document.txt''' changes to <code>C:\NewFolder\Document.txt</code> in the file system. However, the '''Document.txt''' is still listed in ReNamer at its original location <code>C:\Folder\Document.txt</code>. Thus ReNamer is unable to find '''Document.txt''' when it attempts to rename it.  
  
 
In other words, while the contained folder is renamed, the contents are not.
 
In other words, while the contained folder is renamed, the contents are not.

Revision as of 10:24, 21 June 2017

ReNamer has several filter options which configure how added items (files and folders) are treated.

By default, folders are not added to the renaming list as items, instead, their contents are added to the renaming list. To rename the folders themselves, open filter settings and enable option "Add folders as files".

Extensions in folders

Note that Skip extension option also affects folders. (If there are any periods in the name of a folder, the portion on the right side of the last period is treated as extension.

A typical example is folders that contain tutorials: 01. Introduction, 02. Basics, etc.) Here, the words "01" and "02" are treated as names, and "introduction" and "Basics" are treated as extensions.

Conflicting order

Renaming a folder also affects all of its content. Therefore renaming of folders requires a little more care.

A problem can occur if you try to rename folders and their content in a single run. Items in the renaming list are processed from top to bottom. The order of items in this case is extremely important for successful renaming.

Important: Parent folders must always appear below their contained items. This can be easily achieved by sorting items in descending order by the Folder or Path column.

If a parent folder is renamed first, the actual path for its contents changes instantly, with its new name. However, the subfolders and files contained in that folder are still listed in ReNamer with their old path. As a result, ReNamer is unable to find those items at the specified location, and therefore it cannot rename them.

Example

Let's imagine that you have a folder C:\Folder which contains a file C:\Folder\Document.txt. You would like to rename both the folder and the contained file at the same time. You have listed the Folder before the Document.txt in ReNamer. As soon as the Folder is renamed to NewFolder, the path for Document.txt changes to C:\NewFolder\Document.txt in the file system. However, the Document.txt is still listed in ReNamer at its original location C:\Folder\Document.txt. Thus ReNamer is unable to find Document.txt when it attempts to rename it.

In other words, while the contained folder is renamed, the contents are not.

Problem occurred

Preview Rename
ReNamer Folder Rename Bad Before.png ReNamer Folder Rename Bad After.png

Items as they appear after they were added, no sorting.

Problem solved

Preview Rename
ReNamer Folder Rename Good Before.png ReNamer Folder Rename Good After.png

Items after they were sorted in descending order by Folder column.