"Merge actions", because there can be multiple files which after the first rename step can be the same name and there for can't be renamed. The second step will try to change al file names but some of them are leaved unchanged after first step.
Example:
say we have a two file names:
file1.bak
file2.bak
both file names have the same creation date and time (2006-01-22 12:00:00), BUT we have to rename the file names:
at first according creation date/time value:
file1.bak -> 2006-01-22_120000.bak
file2.bak -> 2006-01-22_120000.bak will be leaved as file2.bak because the new file name already exist.
the second step will add an numeric value at the end of file name
(file1.bak) 2006-01-22_120000.bak -> 2006-01-22_120000_01.bak
(file2.bak) file2.bak -> file2_02.bak
but by merging the bouth steps we can get a result:
file1.bak -> 2006-01-22_120000_01.bak
file2.bak -> 2006-01-22_120000_02.bak
merging means new file name calcualtion according all together merged actions AND only after them take real reaname action.
I see what you mean... Yes, this could be a nice idea actually. I have to think how to integrate that in the user interface, and what implications it has in the program.
I'll put it in my to-do list, but I do not know when I'll do that
