Multi Rename feature executed on "This PC" reveals peculiar behavior attempt [FIXED]
Posted: 18.09.2021, 15:31
How to experience this:
1] Have multiple [letter] drives assigned in your Windows 10
2] Navigate all the way up to This PC [i.e. the most main / root virtual "folder"]
3] Select all items
4] Open the Multi-Rename window for them [with CTRL + M]
What do you see? I see that the default Pattern in form of
for the File Name want-ing to change drives' letters into multiplied versions of them from already multiplied letters [unsuccessfully I presume - as I have not really even tried to execute this option on them. plus theirs New Name data is all written in red thus indicating errors]
So for example the first of my drive which is C is about to be changed from
So is this actually some telltale of a bug that can lead to discovery of other bugs related to the inner-workings of this renaming feature - or just a funny glitch without any meaning whatsoever for the reliability if FreeCommander?
1] Have multiple [letter] drives assigned in your Windows 10
2] Navigate all the way up to This PC [i.e. the most main / root virtual "folder"]
3] Select all items
4] Open the Multi-Rename window for them [with CTRL + M]
What do you see? I see that the default Pattern in form of
Code: Select all
[n]So for example the first of my drive which is C is about to be changed from
intoC: C: C: C: C: System-W10
while the fourthC: C: C: C: C: System-W10
is supposed to be changed toF: F: Photos
F: F: Photos
So is this actually some telltale of a bug that can lead to discovery of other bugs related to the inner-workings of this renaming feature - or just a funny glitch without any meaning whatsoever for the reliability if FreeCommander?