Additional attributes in Change Attributes dialog
Moderators: Hacker, petermad, Stefan2, white
Additional attributes in Change Attributes dialog
In File -> Change Attributes dialog, TC handles many file attributes:
- some directly in "Change attributes" group,
- date/time can be changed below,
- and below is a "tc" plugin with many extended attributes - in conjunction with two previous options, it handles all the file attributes described in SetFileAttributes function, like "compressed" or "encrypted" - but except:
a) FILE_ATTRIBUTE_NOT_CONTENT_INDEXED,
b) FILE_ATTRIBUTE_OFFLINE,
c) FILE_ATTRIBUTE_TEMPORARY.
So I'd like to ask to add these attributes to "tc" plugin. Especially FILE_ATTRIBUTE_NOT_CONTENT_INDEXED is useful, because it can exclude some files from indexing.
Regards
- some directly in "Change attributes" group,
- date/time can be changed below,
- and below is a "tc" plugin with many extended attributes - in conjunction with two previous options, it handles all the file attributes described in SetFileAttributes function, like "compressed" or "encrypted" - but except:
a) FILE_ATTRIBUTE_NOT_CONTENT_INDEXED,
b) FILE_ATTRIBUTE_OFFLINE,
c) FILE_ATTRIBUTE_TEMPORARY.
So I'd like to ask to add these attributes to "tc" plugin. Especially FILE_ATTRIBUTE_NOT_CONTENT_INDEXED is useful, because it can exclude some files from indexing.
Regards
- ghisler(Author)
- Site Admin
- Posts: 50873
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
This makes no sense, it's used for files which are created temporarily - Windows will delete files with this attribute when they are closed.FILE_ATTRIBUTE_TEMPORARY
I didn't know this one, seems to be something new.FILE_ATTRIBUTE_NOT_CONTENT_INDEXED
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
To be precise, FILE_ATTRIBUTE_TEMPORARY directs the operating system not to delete the file after close, but to cache file contents in memory when possible - because disk operations are slow and this is a temporary file that application is going to delete after close.
Having this attribute in TC could be useful in particular to clear this attribute when debugging problems with some applications - to enforce writing all data to file, to be able to view file contents.
Having this attribute in TC could be useful in particular to clear this attribute when debugging problems with some applications - to enforce writing all data to file, to be able to view file contents.
You are of course right. I can use a custom plugin, I can also write a 5-lines program that will clear the file attribute. I can also launch some problematic application under the debugger and clear the attribute flag when creating a file. But using TC would be the most straightforward way, wouldn't it? 
