It is not a bug per se, but if you set the size>1MB or something small it takes huge amount of time (apparently more than 10mins and does not look like almost ready at all) to check 5 directories all being larger than 1MB (they are in the 100GB range), 3 of them having no smaller files than 1mb and they are deeply recursed.
By my logic it should not take long to check a directory (in the above case at least: size larger than) : if having more added up than the set value it should break and return instead of continuing.
Here is 2 feature suggestions maybe worth implementing, please consider:
1, Check if a specific file or subdirectory exists inside the directory.
To clarify with examples: directory like ".git", file like "*.sln", etc. I know it's called DirSizeCalc but please...
2, Cache and recursion settings could be per rule and not global.
It is not a bug per se, but if you set the size>1MB or something small it takes huge amount of time (apparently more than 10mins and does not look like almost ready at all) to check 5 directories all being larger than 1MB (they are in the 100GB range), 3 of them having no smaller files than 1mb and they are deeply recursed.
By my logic it should not take long to check a directory (in the above case at least: size larger than) : if having more added up than the set value it should break and return instead of continuing.
I'm not sure if I understood this correctly. You can set a calculation limit to a certain number of files not a certain size.
1, Check if a specific file or subdirectory exists inside the directory.
To clarify with examples: directory like ".git", file like "*.sln", etc. I know it's called DirSizeCalc but please...
That's definitely a good idea.
Cache and recursion settings could be per rule and not global.
They are not global. They are field-specific. What do you mean by rule-specific?
It is not a bug per se, but if you set the size>1MB or something small it takes huge amount of time (apparently more than 10mins and does not look like almost ready at all) to check 5 directories all being larger than 1MB (they are in the 100GB range), 3 of them having no smaller files than 1mb and they are deeply recursed.
By my logic it should not take long to check a directory (in the above case at least: size larger than) : if having more added up than the set value it should break and return instead of continuing.
I'm not sure if I understood this correctly. You can set a calculation limit to a certain number of files not a certain size.
I'm sorry for not being clear, English is my second language and sometimes it shows. I'll be more specific:
So TC requests the directory from your plugin, then you get a list and you loop the results, if it is a file you increment a variable like totalsize with the size of the file and increment the filecount(for size calc not needed) variable by 1 or if its a directory then you increment the dircount(for size calc not needed) and recurse into that and so on... until you are done.
Now if the setting is "dirsizecalc size > [somevalue] [someunit]" and size setting is recursive. So every time you should compare: if targetsize<=totalsize then you should "return true" instead of going on. Works the other way around too: size < [somevalue] : return false. (see my original post now for details, imagine the scenario described there.)
Lefteous wrote:2z9000
1, Check if a specific file or subdirectory exists inside the directory.
To clarify with examples: directory like ".git", file like "*.sln", etc. I know it's called DirSizeCalc but please...
That's definitely a good idea.
Thank you.
Lefteous wrote:2z9000
Cache and recursion settings could be per rule and not global.
They are not global. They are field-specific. What do you mean by rule-specific?
I can set one setting for the field "size" so in this sense is global, I cannot set a rule to : size>10gb no recursion OR size<1mb recursion(do you see the advantage now?).
I have read all 29 pages in TC's English forum thread for DirSizeCalc, and your Readme. Unless I missed it, I think I found a problem.
If I use DirSizeCalcSettings.exe to ADD a custom field, I cannot set (or preselect) any other field than SIZE (FieldIndex=0). After adding custom field, DirSizeCalcSettings.ini always shows the new custom field containing FieldIndex=0. I have to go into ini file and manually edit it to the proper value.
BTW, my TC is v9.12 x32; my DSC is v2.22 x32; my OS is Windows 7 SP1 x64
No, you cannot turn them off currently. What is the reason why you don't want them to be displayed? If everything is fine, they are not displayed. If they are not displayed although the calculation is not complete, you could perform unwanted decision on such a folder.
Is there a way to make use of "everything" for calculating space? I like how fast shift+alt+enter is to calculate space using voidtools "everything", but it's a problem to send that command every time i change directory.
but it's a problem to send that command every time i change directory.
You can make a View Mode that has the command *cm_CountDirContent in the "Auto run commands" field, and then add an Auto Switch Mode for that View Mode, then the sizes of directories will be updated automatically.
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14 TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
but it's a problem to send that command every time i change directory.
You can make a View Mode that has the command *cm_CountDirContent in the "Auto run commands" field, and then add an Auto Switch Mode for that View Mode, then the sizes of directories will be updated automatically.