Property sheet question [RESOLVED]

[MarkFilipak]

Hello,

This is a question that may lead to a flaw that maybe should be fixed (?)

Step 1: I go to the root of a drive, and
Step 2: I search for *.*, and
Step 3: I 'Feed to listbox', and
Step 4: I highlight all (i.e. Ctrl+A), and
Step 5: I right-click and select 'Properties'.

Is the resulting Property sheet from TC or from Windows?

Regards,
Mark Filipak.

[nsp]

This should be the windows one !
You can do the same in windows explorer with multiple file you see the file on which you R-Clicked as title but inside you see multiple files information like nb of selected file, total size, type, folder ...

[MarkFilipak]

Ah, from Windows. I suspected that. Thanks.

Well, the property sheet is wrong. Perhaps the system call that creates the Property sheet is wrong, or perhaps the Windows internal DLL code is defective. I wouldn't know.

I won't trouble you with details unless you think that would help.

I have a workaround, but it's a bit inconvenient.

[Dalai]

Well, the property sheet is wrong.

What exactly is wrong with it? There's a lot of information in that dialog, so I wouldn't even want to guess. Furthermore, I somehow doubt there's some major issue, because even that part of the shell is used millions of times a day worldwide. However, nothing's impossible, especially when considering the "quality" Microsoft has been producing over the last half a dozen years ...

Regards
Dalai

[MarkFilipak]

Well, the property sheet is wrong.

What exactly is wrong with it? ...

Regards
Dalai

If subdirectories are part of the selection, the Property includes the bytes occupied by files plus (recursively) the bytes in all the files in the listed subdirectories (and their subdirectories etc.), so the total space reported by the Property sheet is way over twice the actual space occupied.
Example:
Search for M:\*.* -- (M: is a 4TB drive), then "Feed to listbox", then select all (Ctrl+A), and right-click and select "Properties".
Result is:
"4,886 Files, 158 Folders"
"Size: 8,037,640,061,675 bytes"
"Size on disk: 7,995,540,881,408 bytes"

Meanwhile, in the TC status bar:
"3,898,612,073,354 b / 3,898,612,073,354 b in 1610 / 1610 file(s), 71 / 71 dir(s)"

The workaround in TC is: In the "Find Files" dialog, click the "_/Advanced\_" tab, select "[X] Attributes", unselect "[_] Directory", and then search for M:\*.*

When TC uses the Windows Property utility, if there's a way to mask out the directories, TC should do that regardless whether directories are in the selection.

[Dalai]

I see, and I can confirm your observations. Well, you told the shell to show the properties of all selected objects, and it does. By the way, pressing Ctrl+L leads to the same result, but is much faster when dealing with a lot of objects (at least in my tests). And I don't consider this a bug either.

Regards
Dalai

[MarkFilipak]

I didn't tell the shell anything. I told TC. The result is misleading. I wonder how many times I made unfortunate decisions based on bogus occupied/available bytes?

I don't consider it a bug either. I consider it a flaw.

[Dalai]

I didn't tell the shell anything. I told TC.

And TC told the shell what you told TC to do. In the end, you told the shell (or whatever part of Windows), directly or indirectly.

The result is misleading.

I agree, kind of. From a technical perspective, the result is correct. But from a usability standpoint, it's kind of a mess. But what else should the shell take into consideration? Keep in mind that there are hard links, symlinks and junctions, at least on NTFS. The more variables are involved, the more complicated it gets.

I don't have a good solution other than the workaround you already use (prevent directories from being part of the search results).

Regards
Dalai

[MarkFilipak]

Thank you for being gracious and not thinking I'm an idiot.

I usually go to the root of a drive and 1: select all (including dirs) and get the properties, or 2: right click on the drive letter bread crumb in the panel and select properties. But 2, above, doesn't work if I'm in a subdir; even right clicking just the drive letter bread crumb (i.e. not the subdir bread crumb) gives me just the properties of the subdir. I guess the bread crumbs are not smart regarding properties, just smart regarding navigation. It does require me to go to the root of the drive. Oh, well. I still adore TC and always have. I use Explorer... oh... maybe once a year.

[sqa_wizard]

If you want to see the properties of a drive, just right click on the dedicated drive button or the entry at the drive list.

[MarkFilipak]

If you want to see the properties of a drive, just right click on the dedicated drive button or the entry at the drive list.

Thank you. I don't use/expose the buttons of which I assume you speak -- I don't use a button bar. I'm unsure what you mean by drive list.

[Dalai]

2MarkFilipak
The drive list(s) can be opened by Alt+F1 and Alt+F2. In TC's settings it's called drive combobox.

Regards
Dalai

[MarkFilipak]

HaHaHa... You'll never believe it. NVIDIA GForceExperience had captured Alt+F1 and Alt+F2 for it's own use. Damn it. ... I just had a really hard time breaking it's grip on them -- including finding & disabling a system service. All is under control, now.

In 25 years of TC, I've only ever used F5, F6, Alt+<, and Alt+>. You're talking about 'cm_SrcOpenDrives', aren't you? It's in my custom menu, though I didn't know there were left-window - right-window versions of it.

Thanks All. Unless you want to comment on what I wrote in this post, I think we're done.

[Dalai]

HaHaHa... You'll never believe it. NVIDIA GForceExperience had captured Alt+F1 and Alt+F2 for it's own use. Damn it. ... I just had a really hard time breaking it's grip on them

Yeah, they also capture Alt+F7 by default which is why a lot of people complain about not being able to open TC's search window... It's really annoying that applications register such hotkeys system-wide. The worst I've seen so far is an application which registers F8 system-wide ... When my brother told me this I just facepalmed really hard.

You're talking about 'cm_SrcOpenDrives', aren't you?

Didn't remember there was a command for it, but yes, this is it.

[...] though I didn't know there were left-window - right-window versions of it.

Well, the left drive list opens if it is the active side/panel when this command is called, and the right one opens when the right panel is active. Active side = source, hence cm_SrcOpenDrives.

Regards
Dalai

[MarkFilipak]

HaHaHa... You'll never believe it. NVIDIA GForceExperience had captured Alt+F1 and Alt+F2 for it's own use. Damn it. ... I just had a really hard time breaking it's grip on them

Yeah, they also capture Alt+F7 by default which is why a lot of people complain about not being able to open TC's search window... It's really annoying that applications register such hotkeys system-wide. The worst I've seen so far is an application which registers F8 system-wide ... When my brother told me this I just facepalmed really hard.

To prevent NVIDIA grabbing keys, open Windows Services and Stop, then Disable the 'NVIDIA LocalSystem Container' service.