Total Commander

It it a known issue, that TC does not apply a color filter automatically, when a file is updated. Say, according to my my color scheme all files with modification time (age) less than 10 minutes ago is shown in red.

But TC does not apply this filter automatically to files in the currently opened folder, when a file was just changed and its modification time was updated by some external application, including TC plugins). I need to update the files list manually to see the changes. This behavior is very inconvenient for me, furthermore, it is misleading, so I've already lost some files and data due to this issue.

Well, I guess some reasons to avoid applying color schemes automatically, if a color scheme is heavy (say, it needs to read files internal data via multimedia plugins) and/or the machine is old. But why we can not get automatic applying of colors optionally, leaving if to a user to decide? Especially in the event, that color scheme does not rely on any plugin and machine's CPU is fast enough?

Many thanks in advance!

Of course this wont help if you leave the file panel for more than 10 minutes untouched, because only the system time but not the file system attributes are changed.

Regards
Holger

2HolgerK

Configuration -> Options... -> Refresh: Auto-Refresh when the file system changes

Thank you, but I don't sure, which of the six options of this section do you mean. I suggest, that it should be the second option: [Also when size, date or attributes change], am I right?
If I am, this option is already enabled at my system, but when a file in the current folder updates, the color does not apply automatically, but I need to refresh the list manually.

Does it actually work for you?

Of course this wont help if you leave the file panel for more than 10 minutes untouched, because only the system time but not the file system attributes are changed.

Sorry, but I don't understand what you speak about Why 10 minutes? Why attributes? Could you please explain your thought a bit more detailed?
Many thanks in advance!

oshizelly wrote:If I am, this option is already enabled at my system, but when a file in the current folder updates, the color does not apply automatically, but I need to refresh the list manually.

Does it actually work for you?

Uups, sorry. This seems to be a bug.
- Existing file "abc.txt" (older than one day)
- Color filter "not older than 1 day"
- running the following batch in background:- The file time and size gets an update but the color filter not.
- The color filter is only updated after <Ctrl+R> or changing the focus to another application and back to TC.

Sorry, but I don't understand what you speak about Why 10 minutes? Why attributes? Could you please explain your thought a bit more detailed?

according to my my color scheme all files with modification time (age) less than 10 minutes ago is shown in red

If you wait 10 minutes a file becomes older without changing the last modification time stamp. There will always be the possibility that a trigger for a color filter is independent from a file system attribute change.
E.g. something like this: Regards
Holger

2HolgerK

Uups, sorry. This seems to be a bug.

I'm not sure, that it is a bug. I admit, that it is made intentionally by the author (as I've already noticed in the 1st post on this topic).
That's why it would be fine to get Christian's short comment for this subject.

If you wait 10 minutes a file becomes older without changing the last modification time stamp.

Now I see, what you meant, thank you. However it is not the point of our discussion.

Colors are cached, it could cause a horrible slowdown if they were updated on each file change.

2ghisler(Author)

Colors are cached, it could cause a horrible slowdown if they were updated on each file change.

Yes, I suggested something as this. That's why I accented the word "optionally".

I mean, that if a user has a machine with quite power CPU and if colors updating in real time is very important due to his work tasks, he could anyway use this option, at least temporarily for some tasks, in spite of horrible slowdown. There are a lot of cases, when a user will be glad to "buy" a bit more usability, paying for it with dramatically lower speed of operations.