Hi!
This was bugging me always. When I move a folder or file within the same drive its usually instantaneous. But sometimes something is locking the file. TC realizes this and starts copying the file, and THEN warns me that it can't move the file. Even if I skip or abourt I end up with a copy of the file. Which doesn't make sense. I don't want to copy the file. I think it would be best if TC warned me when it accesses the locked file, that way I could close the other program (maybe even TC could show which process is locking the file), and retry, or skip it.
Notify when something is locked when moving.
Moderators: Hacker, petermad, Stefan2, white
-
sqa_wizard
- Power Member
- Posts: 3893
- Joined: 2003-02-06, 11:41 UTC
- Location: Germany
+1
would it be possible to pre-establish all files that will be a problem for a move file process during the sizing phase? Then present all of the operation stoppers at the front end so we can turn hid/sys checking back on, for those of us that have had to turn it off due to it constantly boning up a monster move processes.
or again, -IF- a move is a true copy-compare-delete original, can we dispense with the warning of deletion of hid/system on all move operations?
would it be possible to pre-establish all files that will be a problem for a move file process during the sizing phase? Then present all of the operation stoppers at the front end so we can turn hid/sys checking back on, for those of us that have had to turn it off due to it constantly boning up a monster move processes.
or again, -IF- a move is a true copy-compare-delete original, can we dispense with the warning of deletion of hid/system on all move operations?
carpe` cervesi
knf (35402)
knf (35402)