Description handling

Jan 14, 2011
4
0
I'm trying to figure out how description handling works with file manipulation in the folder & list views.

When I copy or move a file by dragging it from its appearance in List View into a directory under Folders, I'd expect (and desire) that the description be copied/moved with it. That generally doesn't seem to be the case.

I have "Enable Descriptions" checked under both "Configure Take Command" and "Configure TCC". I'd prefer not to use NTFS descriptions since not all my disks are NTFS, but I've tried with it both enabled and disabled.

Results seem completely inconsistent. Sometimes the description is copied, but most of the time it isn't. Sometimes, besides failing to copy the description it wipes out descriptions in the target directory entirely. The command line works consistently with non-NTFS, but gets almost as flaky as the GUI when I enable NTFS descriptions.

I suspect that the explorer-like file operations are actually farmed out to Windows so that non-NTFS description handling is impossible. True?

I also suspect that NTFS descriptions don't actually work very well, period.

I'm trying to decide whether to upgrade from command line only to full folder/list view, but I have thousands of files with descript.ion descriptions on both NTFS and non-NTFS disks. If the folder/list view can't manipulate descriptions there'd be no benefit to the upgrade - should I stick to the command line?
 

rconn

Administrator
Staff member
May 14, 2008
12,365
150
I'm trying to figure out how description handling works with file manipulation in the folder & list views.

When I copy or move a file by dragging it from its appearance in List View into a directory under Folders, I'd expect (and desire) that the description be copied/moved with it. That generally doesn't seem to be the case.

It is *never* the case if you're using DESCRIPT.ION -- the description files are not updated with drag & drop operations.

I also suspect that NTFS descriptions don't actually work very well, period.

That would require a fairly catastrophic bug in the Windows NTFS code, as NTFS descriptions are just streams attached to the file, so all description handling is done by Windows. Do you have an example that is failing?
 
May 30, 2008
235
2
It is *never* the case if you're using DESCRIPT.ION -- the description files are not updated with drag & drop operations.

Maybe they should be? That would be something the TCMD interface would have over just using Windows Explorer directly.

That would require a fairly catastrophic bug in the Windows NTFS code, as NTFS descriptions are just streams attached to the file, so all description handling is done by Windows. Do you have an example that is failing?

He did say he have non-NTFS disks as well, so perhaps he copied the files with NTFS descriptions back and forth between those. That would probably wipe out the descriptions right? (Unless TCC can do some magic)
 
Jan 14, 2011
4
0
That would require a fairly catastrophic bug in the Windows NTFS code, as NTFS descriptions are just streams attached to the file, so all description handling is done by Windows. Do you have an example that is failing?
I did originally, but I can't reproduce it now. I believe I understand what was happening, though.

The issue is the transition from one type of description to another. If I have file foo1.txt with description "bar1" in DESCRIPT.ION, and file foo2.txt with description "bar2" in NTFS, then when viewing the directory in TC or TCC I can only see one of the descriptions. That's not entirely surprising, but it is disappointing.

As I mentioned I have thousands of files with DESCRIPT.ION descriptions, so it sounds like the TC file explorer will never be of much use to me:

If I switch to NTFS those descriptions will become invisible - and over time be lost, as file operations will leave the descriptions behind. Also of course this won't work on non-NTFS drives like my NAS. So I guess I can't switch.

If I don't switch, I'll be unable to do any file operations using TC, since again the descriptions will get lost. So I guess I can't use TC.

I was hoping I'd finally found a file manager that would work with the descriptions I've spent years and years building up in 4Dos and Take Command. Total Commander handles descriptions seamlessly, but its UI is extremely non-intuitive to me. Any chance the file manager aspects of TC will be enhanced to handle DESCRIPT.ION?
 
Similar threads
Thread starter Title Forum Replies Date
Joe Caverly Populate DESCRIBE dialog with existing description Support 7
C show file description? with dir? Support 8
WavSlave Fixed Unable to sort files by description in TCC v19 Support 2
fpefpe How to? Description not copied Support 2
C Problem with /R description-range Support 5
Jay Sage TCMD11: Maximum Description Length Support 1
vefatica WAD TCC: inconsistent character handling Support 11
M Handling of %~I problem Support 4
J File explorer handling from command line? Support 2
forbin Strange handling of [nonbright] magenta background (v22) Support 2
T WAD Difference between TCC and CMD in handling multi-command lines Support 6
thorntonpg Handling files with embedded spaces Support 1
J junction copy/move handling Support 6
C How to? MOVE and handling out of space Support 2
The Wizard WAD Possible Incorrect COMSPEC handling Support 2
BobK How to? Handling filenames with blanks at command line Support 3
Frank WAD handling variables with $-prefix Support 14
A Discrepancy in handling of "can't copy or move file to itself" Support 4
M How to? A question about error-handling... Support 25
B Strange handling of a .BAT file Support 5
C handling percent signs in filenames Support 2
C handling percent signs in filenames Support 1
S Ctrl-C handling while piping Support 0
vefatica Icon handling in b153 Support 7
U An annoying bug with TCC's icon handling in the taskbar Support 25
p.f.moore Bug in plugin break handling? Support 0
p.f.moore Error handling in plugins Support 2

Similar threads