[947] cancel copy-action quirky

[alf5000]

this behavior started with [946] and is still here in [947]
Ctrl+C / Ctrl+V invokes the Windows copy action (not FCXE copy dialogue) on my machine.

1) select a large file/folder
2) press Ctrl+C
3) press Ctrl+V
4) press Esc to cancel the copy-action
5) Win copy dialogue disappears for a second or two, BUT then it appears again and copying continues

the third Esc finally terminates the copy-action

[Marek]

Have you the same with default settings too?
Could you send me your freecommander.ini?

[alf5000]

yes, pristine FCXE portable (both versions 946&947) also shows this behavior.
it is always pressing Esc exactly three times.
MS file explorer works correctly.

after further investigation I see that the issue started in earlier versions of FCXE (I didn't notice it earlier).

[Marek]

That doesn't happen to me. The operation is aborted immediately after the first ESC.

[alf5000]

i'll try another machine tomorrow - seems there is something fishy with my Win10

[Dreamer]

It looks like a regression, I could reproduce it in older version, but I just can't reproduce it now in 947, Windows 10.

Please try to provide more info and steps to reproduce, so we could try to reproduce it.

[alf5000]

I tried it on a different Win10 machine with pristine portable FCXE.
the problem exists, but I cannot tell which version started the issues.
deeper reseach shows, that the problem occurs only when the copy action deals with a lot of different files.

I have a Vivaldi Standalone folder, for example (3,16GB with 16500 files in 2700 folders)

1) select folder
2) press Ctrl+C
3) press Ctrl+V
4) the copy process doesn't immediatly start, but Win10 does some work first (presumable "prepare the copy-action" or "collecting data" as I'd call it)
5) press Esc WHILE this "prepare the copy-action" in progress
6) Win copy dialogue disappears for a second or two, BUT then it appears again and copying continues

mind: if the "real" copying has started, then the first Esc will reliably terminate the process.

[Marek]

deeper reseach shows, that the problem occurs only when the copy action deals with a lot of different files.

That's it.
I can reproduce it now, fixed for the next release.

[alf5000]

, glad you found the problem