You are not logged in.
The "Fix conflicting new names" option is not meant for one-time use: A typical user would like it to be invoked whenever he renames files.
But currently it is a manual option: The user has to press CTRL+F after he sees the alert message.
It would be far easier for the user if this option is included in the Settings>Preview.
Offline
I share your view on this, but not fully. I think current option is not persistent enough, while such option in the general settings is too permanent.
Maybe putting it as an option in the CleanUp rule will be better? What do you think?
Offline
Maybe putting it as an option in the CleanUp rule will be better? What do you think?
That sounds fine to me .
If this software has helped you, consider getting your pro version. :)
Offline
Sorry, i wanted to think about this and report earlier, but forgotten it.
I think, the idea to make "Fix conflicting new names" option more prominent is an good idea.
I share your view on this, but not fully.
I think current option is not persistent enough, while such option in the general settings is too permanent.Maybe putting it as an option in the CleanUp rule will be better? What do you think?
i think, putting it into the CleanUp rule is an worst thing.
An user will
- first not easily find this option, and
- second always have to add an extra CleanUp rule
And i mean it IS "persistent enough" to have it in the Settings dialog.
So I vote for putting "Fix conflicting new names" into the [Rename] tab.
Read the *WIKI* for HELP + MANUAL + Tips&Tricks.
If ReNamer had helped you, please *DONATE* to Denis or buy a PRO license. (Read *Lite vs Pro*)
Offline
I agree. It should be in the "Rename" tab.
Offline
In fact, I found the perfect place for this check box:
The Rename tab has a check box called "Overwrite files with New Names".
Well, our "Resolve conflicting filenames" is the exact opposite alternative for that option!
These closely related options MUST be placed in the same place, so that the user can choose between them easily.
Convert both into radio buttons (reason: They are mutually exclusive: User cannot select them both simultaneously).
In fact, a third option is also needed: "skip renaming".
In other words, when names conflict, the ReNamer can behave in one of the three preset ways:
(a) new file overwrites the older one
(Suboption check box: Wait for user-confirmation), OR
(b) new file gets a suffix, or
(c) renaming is skipped.
a,b, and c are radio buttons. Suboption in (a) is a check box.
Last edited by narayan (2012-08-31 03:00)
Offline
In other words, when names conflict, the ReNamer can behave in one of the three preset ways:
(a) new file overwrites the older one
(Suboption check box: Wait for user-confirmation), OR
(b) new file gets a suffix, or
(c) renaming is skipped.
In case that it would be done I think that presented somehow like this would be more clear:
In case of conflicting names:
(a) Don't do anything. (Default)
(b) Add serialized suffix.
(c) Overwrite older file.
[ ] Always ask before overwriting.
Where (a) is the same behavior as it has now.
Last edited by SafetyCar (2012-08-31 13:43)
If this software has helped you, consider getting your pro version. :)
Offline
Well, if the options are sorted in the order of their use, then I guess the most used case would be to add a suffix.
Also, I prefer "Skip renaming" to "Don't do anything".
BTW I forgot add the main subject at the top.
So, the reworked group should be like this:
In case of potential name-conflicts:
(a) Add serialized suffix
(b) Skip renaming of the file
(c) Overwrite older file
[ ] Always ask before overwriting
Last edited by narayan (2012-08-31 14:57)
Offline
Well, if the options are sorted in the order of their use, then I guess the most used case would be to add a suffix.
My intention was to order it into what does more or less change.
Also, I prefer "Skip renaming" to "Don't do anything".
I don't like "skip renaming" because to me it feels like it's going to do something strange, different from what it does now... What about "Don't check for conflicts"?
Last edited by SafetyCar (2012-08-31 17:31)
If this software has helped you, consider getting your pro version. :)
Offline
My intention was to order it into what does more or less change.
No the GUI must always present the most-used option at the top AND also make it the default option.
That way, the user does not have to adjust the GUI too much.
(In most cases, all he has to do is to click on the OK button.)
What about "Don't check for conflicts"?
IMHO "Skip renaming the file" is the most appropriate expression, because-
(a) It speaks in terms of each potential name-conflict that may arise.
In fact, the label of this whole section poses a question, and each of the options actually completes the sentence.
For example, In case of potential name-conflicts> Skip renaming of the file.
(b) Skipping is in reference to the usual practice of loading multiple files in ReNamer at a time.
Only a few files will have the name-conflict.
In that context, "skipping" means moving on to the next file. Any user will understand that easily.
(c) It speaks about what exactly to expect from ReNamer.
On the other hand, we can NOT offer a choice titled "Don't check for conflicts":
ReNamer MUST check for name-conflict, simply because Windows will throw exception otherwise.
ReNamer has to handle that one way or the other.
Last edited by narayan (2012-08-31 18:02)
Offline