1341: Everything -rename, is broken

[therube]

1341:

Everything.exe -rename

Is simply, broken.

[NotNull]

Can you be more specific? What is broken?
Everything64.exe -rename starts the rename window
Everything64.exe -rename file1 file2 starts the rename window with those 2 files in the Old filenames box.

At least here ..

[therube]

Everything -rename 0B*

Code: Select all

0B2FE61FA3A64A65F99BECF6A9ED327D17C95965
0B69C2C175A052802565AB37949BDD66483F3149
0B6FBFEDC7BC1876AE492F33B74C617BC91963F1
0BBF2115A9F4CE1599F3F6D5B06EE1A262C145C1
0BC6858B354E6DAC26F1C8EE3E97CEB37D80F643

Old format: 0B%1
New format: 0B%1

Change to..

Old format: b
New format: -testing123-

1340:

Code: Select all

0-testing123-2FE61FA3A64A65F99-testing123-ECF6A9ED327D17C95965
0-testing123-69C2C175A052802565A-testing123-37949-testing123-DD66483F3149
0-testing123-6F-testing123-FEDC7-testing123-C1876AE492F33-testing123-74C617-testing123-C91963F1
0-testing123--testing123-F2115A9F4CE1599F3F6D5-testing123-06EE1A262C145C1
0-testing123-C6858-testing123-354E6DAC26F1C8EE3E97CE-testing123-37D80F643

1341: <unchanged>
.

Everything 1341 -rename is broken.png (16.74 KiB) Viewed 3605 times

[NotNull]

Yep, that is broken ...

it does not change the New Filenames list. However, when starting the rename anyway, the files will be renamed according to the new filename pattern.

[void]

Thank you for the issue report therube,

1341 is adding a small delay before updating the new filenames.
I added this delay because the performance of updating the new filenames for several hundred files when making a change to the format edits was poor.

Unfortunately, when using -rename, the event for this delay never triggers.

I'll have this fixed in the next alpha update.

[void]

Everything 1.5.0.1342a fixes an issue with -rename not updating the new filenames.