BUG fixed: Background transfer manager: Abort=Continue

[white]

I created a lot of files of 0 bytes in size (see http://ghisler.ch/board/viewtopic.php?t=2247). I selected to copy these files (F5) and queued the copy operations in the background transfer manager (F2 Queue). While the copying was in progress, I clicked the X to abort. Nothing happened. Then I clicked Pause and the copying paused. While the copying was paused I again clicked the X to abort. And the copying continued.....

BTW. Shouldn't the text on the pause button be pause/continue or stop/start instead of pause/start (or start/pause/continue)?

[ghisler(Author)]

Unfortunately you can't abort or pause if no data is copied at all, sorry.

[white]

I was able to pause, just not able to abort. It's quite confusing when you click the X and the copying is unpaused. When you want to stop you do not want to continue

If I understand correctly an abort flag is set when the X is clicked and the process is unpaused. The process will detect the flag at a convenient time and abort.
Maybe you can also check for abort in between two queued operations?
And if you fix this, maybe you can also change to not unpause the pause button (only the button not the process) in case of an abort. I understand the process needs to continue a bit before it aborts itself, but nobody needs to know do they?

So, Bob the Builder, can we fix it ?


UPDATE:
The bug seems to be fixed in v6.01. No mention of this in the HISTORY.TXT file. Probably this bug was fixed along with other fixes to the background transfer manager.