[TC8.50b6]Verify after copy not disabled in BTM

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: Hacker, petermad, Stefan2, white

Post Reply
User avatar
white
Power Member
Power Member
Posts: 5815
Joined: 2003-11-19, 08:16 UTC
Location: Netherlands

[TC8.50b6]Verify after copy not disabled in BTM

Post by *white »

* Enable option in configuration: Configuration - Options - Copy/Delete - Verify after copying
* Copy a big file using the BTM (select a file, press F5,F2) and pause the operation (click pause button in BTM window)
* Select another file, press F5, deselect the Verify option, press F2 to add it to the queue
* Assume you picked the wrong file in the previous step, go to the BTM and delete the last two lines which were added in the previous step
* Select another file (the right file), press F5, Verify option is still disabled and marked with an exclamation mark, press F2 to add it to the queue
* Verify after copy is not disabled for the last copy operation.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50541
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Sorry, the flag is only sent to the BTM when there is a change between verify set and not. The foreground thread has no idea what is the state of the BTM. This is impossible because the user can always remove these flags by himself (as you did).
Author of Total Commander
https://www.ghisler.com
User avatar
white
Power Member
Power Member
Posts: 5815
Joined: 2003-11-19, 08:16 UTC
Location: Netherlands

Post by *white »

ghisler(Author) wrote:The foreground thread has no idea what is the state of the BTM.
Exactly my point. That's why you should always send the flag.
User avatar
MVV
Power Member
Power Member
Posts: 8711
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Post by *MVV »

white wrote:That's why you should always send the flag.
Agree. If foreground thread has no idea about BTM state, it has no idea if there is a change between flag states, so it must send flag to ensure that correct state is used.
Post Reply