DirSizeCalc 2.22 (content plugin)

[white]

A possible solution could be to exclude those VNC paths as first matching criteria and dirsizecalc.Field as the second. So when TC checks the custom file type it will immediately abort and never call the plugin on such paths.

I already did suggest something like that. I also suggested to start (a second) TC with a different ini file. He said he was going to try the latter suggestion.

[DrShark]

Lefteous, can you add "follow Vista's symlinks" feature to your plugin? Currently neither TC nor Windows Explorer can show size of symlink's target

[Lefteous]

2DrShark
Unfortunately I don't have Vista and not a programming environment ready for this operating system.

[m^2]

Lefteous, could you make it WOW64 aware? In case of this plugin you get own thread for quite a while and you can safely switch it on and back off.

ADDED: Readme typo: 4.2.2. Prefixes ans units

[Lefteous]

Sorry I don't have a 64 bit machine.

[Lefteous]

Current version 2.10
A new version is ready for download. I decided to release the new version of my plugin a few days before the public beta test of Total Commander 7.5 starts. An error in older DirSizeCalc versions prevents using them in Total Commander 7.5. For this reason updating to the new plugin version is recommended for all DirSizeCalc users even if you don't need Unicode support.

The new commands in Total Commander 7.5 which can be used to load the values of all or just the selected "On demand" fields are another reason to update. You'll find more on this in help file.
The command improve working with content plugins a lot. A plugin like DirSizeCalc with has quite long value loading times benefits more than others.

Most important change: Unicode-Support (requires Total Commander 7.5)

The complete list of changes can be viewed online.

Plugin page: Download, description und documentation
totalcmd.net
My website

[Peter]

Hello Lefteous

the link to the "list of changes" is broken.

Peter

[Lefteous]

2Peter
Thanks. That was just a capitalization problem.

[Hacker]

[mod]2 OT posts moved to Preliminary information about Unicode support (TC7.5).

Hacker (Moderator)[/mod]

[DrShark]

2Lefteous
A question about installition your new unicode plugins (DirSizeCalc and ShellDetails) under TC 7.5.
Should I install it using autoinstall (it installs DirSizeCalc.wdx) or I should register DirSizeCalc.uwdx by hand (for example by changing line with DirSizeCalc.wdx to DirSizeCalc.uwdx in wincmd.ini)?

[Lefteous]

2DrShark
Just use the auto installer. TC automatically detects a corresponding uwdx plugin and uses it instead. The wdx plugin still appears in the ini file.

[ghisler(Author)]

Indeed you always need to install the wdx/wcx etc, not the uwdx version. Total Commander will look automatically whether there is a u* version on Unicode-based Windows versions.

[petermad]

Indeed you always need to install the wdx/wcx etc, not the uwdx version

Can I also rename the .uwdx to .wdx and get rid of the .uwdx file - or will that not work?

And if I do so, then wich configuration program should I use - DirSizeCalcSettings.exe, DirSizeCalcSettingsU.exe or DirSizeCalcSettingsU.exe renamed to DirSizeCalcSettings.exe - or does it not matter - the two .exe's only differ by one byte.

[Lefteous]

an I also rename the .uwdx to .wdx and get rid of the .uwdx file - or will that not work?

Won't work.

[ghisler(Author)]

No, it will not work, because TC will then expect an ANSI- only, or combined Ansi/Unicode plugin.

If you want to create a Unicode-only plugin, create a dummy .wdx plugin which does nothing except for exporting the basic functions and returning an error, and an .uwdx with the actual Unicode functions.