DirSizeCalc 2.22 (content plugin)

[Lefteous]

Current version 2.01
A new version is ready for download. In this version version a few errors have been fixed. In addition an optional calculation limit can be set.
The full list of changes is now also available online.

Plug-in home page: Download, description and documentation
On totalcmd.net
On my web site


2petermad
Please check if "move location" works in 2.01.
I have added a new option so languages files needs to be updated. I will try to make a beta release of the next version so translators can post their updated translations or the next version will just contain more languages and bug fixes.

[petermad]

2Lefteous

The Move location seems to work fine now (now the same function in your Total SQX plugin just has to be fixed the same way )

String 1001 is still missing in the [eng] section of the language file.

Danish translation can be downloaded at: http://madsenworld.dk/tcmd/wdx_dirsizecalc_2.01_danish.zip

[Lefteous]

2petermad

String 1001 is still missing in the [eng] section of the language file.

Thanks. I will add it and until then hope translators wll notice it.

Danish translation can be downloaded

Thank you

[solid]

2Lefteous
Thanks for the new version!

But what about adding custom or user defined size values, discussed earlier in this thread?

[Lefteous]

2solid

what about adding custom or user defined size values

Well as I wrote it's good idea but I haven't had time to work on this feature so far.
My number one priority is currently to get a stable 2.0x release containing a large number of translations.

[solid]

OK.
I was hoping it will be in 2.0 release, but I guess we should wait for 2.5
Keep up the good work

[Flint]

Lefteous
Two typos in the LNG file, line 28:

// Displayed in the size fields if no files have been found or it the directory is completely empty instead of just displaying 0.

The comment should start with ";" instead of "//", and instead of "it" I suppose you meant "if".

Besides, in the pluginst.inf file you missed plural:

DirSizeCalc provides several numeric calculation for directory contents.

and did not add the phrase about background counting that is present in the German description ("Alle Berechnungen werden im Hintergrund durchgeführt.")


Now, the Russian translation is ready, but, I'm afraid, there is one aspect that can cause problems. I weighed all pros and contras and finally decided against the "SI-compliant" units you are using. It was not an easy desision, but I can't apply different standards all over my different works, users will just get confused. So, I left Kb, Mb, Gb for the binary units, exactly as TC does (BTW, that was one of the main reasons), and for decimal ones I use the special units K°b, M°b, G°b. Between "K/M/G" and "b" I put a degree sign looking like a small superscribed circle — something like an indication of a decimal "zero" for decimal units.

I know you are a strong adherent of the "SI" notation and you would hardly like such "innovation" of mine, and I'm sorry for that, but that was my desicion. You may accept or not accept it (in this case I can distribute the language file separately, e.g. via wincmd.ru/totalcmd.net site).

Here is the package with the Russian parts of the LNG and pluginst.inf files:

Code: Select all

MIME-Version: 1.0
Content-Type: application/octet-stream; name="DirSizeCalc2.01_rus.rar"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="DirSizeCalc2.01_rus.rar"

UmFyIRoHAKOccwgADQAAADIGAADXRnSAkDUAzAAAAP4AAAACxI+JYBFoYTkdNRAAIAAAAHBsdWdp
bnN0X3J1cy5pbmYAsBofdacYWxcaZsjoxIhYUoFYvPBCbrhyaYl/ccOMjo7goJW0w+mPDvU1OTPM
hJVJtgGTDrmnokeVxQZVF53wEHypgLM/BZF5S1BRDInXR+Ijix1jvcjl6AWhQAuJmTmbNMcLiPKZ
8LvKo4hoYW5epejcCqkOvIf52bAurgaJMR4EYEsltdPiesj97wv2pDjJCAzmNlSzhDJNG12Yajt6
Varllu0sVuXnfKxEwy5q6LsBdU0IinDLH+4RN4FxGfBJRJI7OGa95AAAv4hn9qn/1G4ZdJCQOADl
BAAAfwsAAAKC7K200mZhOR01EwAgAAAARGlyU2l6ZUNhbGNfcnVzLmxuZwCwqq8Rh14w3oVLQsAW
Qt9TKrJWcINZ2M/olBKZN2FSFCLzKDmTV985ww/ZNOSsjh2VdDjpjkoUKkZh1M0Oplr62wKXnRXv
9jD79TynxaUuXbvcq76GtBi7RXz6HUtVvjW2aYMGeHsxaGE9k5PBWBa6WO5CRzj2xuT1uRjeuBc+
cPVZ37T87/B9ugtAjGOy0ew4K3avy2NoWpmIzQZiu11VQXQRj0y8w0bkiEIsdw9HFh0sc6D/Zajk
QY1n+rmT9NZKMLbGESF3JQeTdhmZ8LibcM3fQptxpfAZ+pK5TxovSCElZPL2fe/3BjX87AHSnUi+
0JeZb0OXcbB83seKnqbQC/uaCJelSddCaczsFItNbRzUGTHK7Ic1sTuLrijaMenvuREHbKKVhXW/
D2rMlPzmjqLXc/nsczdgirkxzDOlniweI7b9yevGdKXGKH2CqcC0tmi9tQDAb3ou5TV1gRJRYnVH
YyxairdqvMlcgUj35GXQn0xMZY63sH03GXRHfiHIBab3OhOLcoGkGUoFY2gyhSILYZ86Qt9AtrN4
3m3GCPJJeIzQyTmA1m2SkXemJWyAgebKwAU6UxkGcuPzKGn/c2f+VJgD7w/ZFOREl9bYQMLXj8NH
tO7CRp3YT7Wnq4b3Q+0U2QyhlAjP8mEeTn2N+F9mO14IyxsniPabhQJWU2lQ5gJkoUUwJ8lxJZ+l
ZjsmaTi3g8nYqRSl1MgBqQls3UTikbKZhf988K1KpJRYXOP0DOFtYdDNXDN4DyKGpel7c8I51Zgl
LfrN8qQ77ujOd9yeUEycxVf4lC7LyuJUXReQwNWo3O8Li2tzOH6wZxFkTkQ1+afkwV0/fo3MADqJ
s3lYQeKFb5P82f9KoD7AryLhaEtWAO+Comj2ZgUyfVDh8+HYxycrS5iTWon/3ar6v38f+xMgRARx
Ma7f3prGaRrTMeNQCIQomy13DORPUXJvhpQhtUDUydHYpt/sCFtvzKEIRRa3BgV0ohxsb0vHeec9
XUFId/L38b29qNXEooLzycFke6l+DwHveyepiR69Yi/XwIvUJzWaGvuT6AzUxuhck/naJo2sULQx
Kn/C9imifaFirb4dmrltGEkFS+A3ZHVQlg+GcwUaLPGEV5yLeFpjvSzE4V6G0wQbiZwRPbueRRAy
yDdY9XzaAsd20/xHkxXgGaa87TVNxowXua7Ql8rGJogktPT1/SkC3dZyhgbQQq/67NXbZ+icOrJY
bisYOyHGVMXcWbzcDtCkOnda1rIgi7Z6jIMwfJfq4eQV7LyoGoJYbmDqBESize4LFbBu4bqq/NIS
0frxymuTkh7RijkPQPcxi7niTk/ES4I5veXnV+s7zC31fO7FRlIilr19rqa07e0wXq6un4vMCNiP
PJyzh1fsgz+ztU9Kw9kW7FyaGcnm3Sj/TLKAdwKuRiS0iQXY2bjmCTY/+qltTCCq+DLgbFuYJbwr
J5SvRmTpLlqjkZNY6t1LP+mzjGj4qRkmS9DL+kBwwtY173H/k3vg6vJjIbE341cWL+E8e8ED/WyY
PilfBlUkNpXPNKj86Scz8kbs5Evzxg8yJNL6y0qV+O7V2feKUHDP0rsw9cSCpSevrtCztP15f24O
PamIN8xzLjeyFvcgFlSGzylcvRkXMWjgw9gAt6jXAg+BIMekvnJMAL+IZ/ap/9SzxHoAwPMAAAAA
AAAAAAACAAAAAOFpYTkdMAIAAAAAAEFWFwBEaXJTaXplQ2FsYzIuMDFfcnVzLnJhcgAAEQBLb25z
dGFudGluIFZsYXNvdgAAPWDz/4mV9CVLKyTR4QKmL6KnkhQ+/16/v/3e4spAaSxiTlyj67Jktq7i
SW7ZrZhxd61k/8w9ir7Jg0JaGhogXqVh0kAsqkJOCELRzkCFzDh7yenzyK81qJQ52oKOuRw9YBuy
8lAwWgBI3X0epo4KKxfgIPQHzo5YxFHA7riWfwgQxAIUKBM2H6s1uYfJq5tqHxdqGccA6JvWCwhx
vuFpYTnEPXsAQAcA

[Lefteous]

2Flint
Thanks for the hints on typos and errors in the language file.

the Russian translation is ready

Thank you for for translating my plug-in into Russian

ecided against the "SI-compliant"

Well I can of course not accept such "creative" translations. I could add a FAQ entry on how to change the language file to adapt prefixes. I can also provide to add your translation of this string as an outcommented template in the language file. What do you think?

[Flint]

I can also provide to add your translation of this string as an outcommented template in the language file. What do you think?

I'm sorry, but unfortunately I cannot accept such a variant. The binary units annoy me too much (like scratching a blackboard with one's nails; or cutting foam plastic with a knife). So I would better put the translation as a separate project on wincmd.ru (and, maybe, on my web-page) with explanations of the reasons.

Anyway, thank you for trying to find a compromise (and for the plugin, of course).

[Lefteous]

2Flint
What I don't understand is why you don't want to provide a translation which I can include in the official setup file. You could still provide an alternative language file on your homepage or somewhere else.

[Flint]

Lefteous
It's not so easy to explain; reasons important to me may look strange/unimportant/ridiculous for someone else. I don't want to create anything using the binary prefixes, it's just my position in this question. I can understand that some people like these prefixes and switch to them, but I don't want to join these people. And if I write anything with a binary prefix, it would mean that I joined this team anyway; maybe not permanently, maybe not completely, but joined. That's not what I want.

Besides, I don't want people who use my programs/translations hesitate which prefixes are used in each particular program/translation. I just want that all my works shared between them as many ideas as possible.

[white]

I used filemon to see what happens when you use the "Empty" field.

Code: Select all

12:38:25	Totalcmd:FFF13365	FindOpen	F:\PROJECT\TC\FILES\*.*	SUCCESS	.
12:38:25	Totalcmd:FFF13365	FindNext	F:\PROJECT\TC\FILES\*.*	SUCCESS	..
12:38:25	Totalcmd:FFF13365	FindNext	F:\PROJECT\TC\FILES\*.*	SUCCESS	File1
12:38:25	Totalcmd:FFF13365	FindNext	F:\PROJECT\TC\FILES\*.*	SUCCESS	File2
12:38:25	Totalcmd:FFF13365	FindClose	F:\PROJECT\TC\FILES\*.*	SUCCESS

After the first file (File1) is found another FindNext call follows to find the next file. Then then second file (File2) is found and a FindClose call follows.

It seems like only after the second file is found, DirSizeCalc knows the folder is not empty and closes the search. Why does it not stop after the first file is found?

[Lefteous]

2white
Thanks for the hint. This call isn't necessary. It doesn't break the functionality though. I will remove it.

I wonder why you are looking so deeply into this...

[white]

I wonder why you are looking so deeply into this...

Because of a question by someone in the dutch forum. He uses your plugin for coloring empty folders but this slows down his VPN connection to a remote server. For that reason he is searching for a way to create an on/off button to enable/disable your plugin. Do you know a solution for him?

[Lefteous]

The problem here is that TC performs this functions always in background even when a field supports background operation.

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.