Generic error when changing timestamps of locked files

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

Moderators: Hacker, Stefan2, white

Post Reply
ChristianGruen
Junior Member
Junior Member
Posts: 16
Joined: 2008-09-14, 15:45 UTC

Generic error when changing timestamps of locked files

Post by *ChristianGruen »

When trying to modify the timestamp of a locked file to the current date/time, I get
Fehler beim Setzen des folgenden Attributs:
Zeitstempel (Datum+Zeit) (1x)
It was some time later when I noticed that the file was locked. Maybe some more information could be given on why the operation fails.

It may well be that this behavior is not specific to the latest version (I didn’t check older ones).
User avatar
white
Power Member
Power Member
Posts: 2659
Joined: 2003-11-19, 08:16 UTC
Location: Netherlands

Re: Generic error when changing timestamps of locked files

Post by *white »

ChristianGruen wrote: 2022-05-10, 12:42 UTC Maybe some more information could be given on why the operation fails.
Sounds very much like a suggestion. Why did you post this in the bug reports forum?
ChristianGruen
Junior Member
Junior Member
Posts: 16
Joined: 2008-09-14, 15:45 UTC

Re: Generic error when changing timestamps of locked files

Post by *ChristianGruen »

Mostly due to missing knowledge on specifics of the implementation: If the current behavior is expected, it would indeed be a suggestion.

Sorry for the confusion. Feel free to close it or move it somewhere else.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 43207
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: Generic error when changing timestamps of locked files

Post by *ghisler(Author) »

Total Commander currently only shows a summary at the end of the operation. It only records the number of failures, not the reasons. With the current error handling, the error dialog would become very complicated when there were multiple errors with different reasons. Currently it's not planned to show an error for each affected file, because normally the user can't do anything when such an error occurs, e.g. because the files are on a read only network share etc.
Author of Total Commander
https://www.ghisler.com
ChristianGruen
Junior Member
Junior Member
Posts: 16
Joined: 2008-09-14, 15:45 UTC

Re: Generic error when changing timestamps of locked files

Post by *ChristianGruen »

Thanks for the assessment and explanation.
Good to know it's expected behavior.
User avatar
AntonDudarenko
Senior Member
Senior Member
Posts: 296
Joined: 2006-11-04, 15:30 UTC
Location: Russian Federation

Re: Generic error when changing timestamps of locked files

Post by *AntonDudarenko »

ghisler(Author) wrote: 2022-05-11, 06:23 UTC Currently it's not planned to show an error for each affected file, because normally the user can't do anything when such an error occurs, e.g. because the files are on a read only network share etc.
Thus this topic could be moved to "TC Behaviour which will not be changed" subforum?
Although I do have one suggestion in this case.
Why not keep a LOG of files that have had some problems? Not an operation log in general, but an error log of an operation to copy/move/substitute one file for another. And ONLY for this log and these files write out more precise definitions of errors and circumstances that led to this situation?
#146217 personal license
Post Reply