readme.htm 37 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  2. <html>
  3. <head>
  4. <meta http-equiv="Content-Type" content="text/html;
  5. charset=windows-1252">
  6. <title>DirSizeCalc</title>
  7. <link href="./styles/layout.css" rel="stylesheet" type="text/css">
  8. </head>
  9. <body>
  10. <div id="content">
  11. <h1>DirSizeCalc</h1>
  12. <p>Version 2.22</p>
  13. <p>&nbsp;</p>
  14. <p>DirSizeCalc is a content plug-in for the file manager Total
  15. Commander. It provides several numeric calculation for directory
  16. contents. The calculations can be started automatically while
  17. entering a directory or explicitly by the user.</p>
  18. <h2>Contents</h2>
  19. <ol>
  20. <li><a href="#field_descriptions">Field descriptions </a></li>
  21. <li><a href="#requirements">System requirements </a></li>
  22. <li><a href="#use">Use</a>
  23. <ol>
  24. <li><a href="#use_cases">Use cases </a>
  25. <ol>
  26. <li><a href="#use_cases_automatic_calculation">Display
  27. directory and file sizes automatically </a></li>
  28. <li><a href="#use_cases_delete_empty_folder_trees">Delete
  29. empty directory trees </a></li>
  30. <li><a href="#use_cases_check_if_comression_makes_sense">Find
  31. out if compression makes sense </a></li>
  32. <li><a href="#use_cases_files_count">Find out how many
  33. directory are contained in a directory </a></li>
  34. <li><a href="#use_cases_contains_subdirectories">Find
  35. out if a directory contains subdirectories</a></li>
  36. <li><a href="#use_cases_load_fields_on_demand">Load the
  37. directory size for all selected or all fields by
  38. pressing a keystroke</a></li>
  39. </ol>
  40. </li>
  41. <li><a href="#additional_information">Additional information
  42. for displayed values </a></li>
  43. <li><a href="#empty_directory_display">Size display for
  44. (almost) empty directories </a></li>
  45. <li><a href="#placeholders">Placeholders</a></li>
  46. </ol>
  47. </li>
  48. <li><a href="#settings">Settings</a>
  49. <ol>
  50. <li><a href="#field_settings">Field settings </a>
  51. <ol>
  52. <li><a href="#field_settings_name">Name</a></li>
  53. <li><a href="#field_settings_field_selection">Field
  54. selection </a></li>
  55. <li><a href="#field_settings_loading_behavior">Loading
  56. behavior </a></li>
  57. <li><a href="#field_settings_reparse_point_behavior">Reparse
  58. point behavior </a></li>
  59. <li><a href="#field_settings_recursive">Recursive</a></li>
  60. <li><a href="#field_settings_cache_values">Cache values
  61. </a></li>
  62. <li><a href="#field_settings_limit">Calculation limit</a></li>
  63. </ol>
  64. </li>
  65. <li><a href="#unit_settings">Unit settings </a>
  66. <ol>
  67. <li><a href="#unit_settings_name">Name</a></li>
  68. <li><a href="#unit_settings_prefixes_units">Prefixes and
  69. units </a></li>
  70. <li><a href="#unit_settings_formatting">Formatting</a></li>
  71. <li><a href="#unit_settings_preview">Preview</a></li>
  72. </ol>
  73. </li>
  74. <li><a href="#settings_file_location">Change settings file
  75. location </a></li>
  76. </ol>
  77. </li>
  78. <li><a href="#faq">Frequently asked questions </a></li>
  79. <li><a href="#contact">Author contact </a></li>
  80. <li><a href="#license">License</a></li>
  81. </ol>
  82. <h2>1. Field descriptions <a name="field_descriptions"></a></h2>
  83. <table>
  84. <tbody>
  85. <tr>
  86. <td width="234"> Size</td>
  87. <td width="552">File- or directory size </td>
  88. </tr>
  89. <tr>
  90. <td>Compressed Size </td>
  91. <td>
  92. <p>File- or directory size with set compressed attribute.
  93. This field is only available on Windows NT based
  94. operating systems.</p>
  95. </td>
  96. </tr>
  97. <tr>
  98. <td>Compression Ratio </td>
  99. <td>Calculates the ratio between Size and Compressed Size. </td>
  100. </tr>
  101. <tr>
  102. <td>Subdirectory Count </td>
  103. <td>Count of all subdirectories in a directory </td>
  104. </tr>
  105. <tr>
  106. <td>File Count </td>
  107. <td> Count of all files in a directory. </td>
  108. </tr>
  109. <tr>
  110. <td>Empty</td>
  111. <td>Finds out if a directory is empty </td>
  112. </tr>
  113. <tr>
  114. <td>Contains Files </td>
  115. <td>Finds out of a directory contains files. </td>
  116. </tr>
  117. <tr>
  118. <td>Contains subdirectories </td>
  119. <td>Finds out of a directory contains subdirectories. </td>
  120. </tr>
  121. </tbody>
  122. </table>
  123. <h2>2. System requirements <a name="requirements"></a></h2>
  124. <p>Total Commander 6.50 is required for this plug-in. Total
  125. Commander 7.03 is recommended for this plug-in. </p>
  126. <h2>3. Use <a name="use"></a></h2>
  127. <p>Before DirSizeCalc's fields can be used they must be added to
  128. the part of Total Commander where they are intended to be used.
  129. Basically all content plug-ins can be used in the same way. The
  130. following program parts of Total Commander support content
  131. plug-ins. </p>
  132. <ul>
  133. <li>Custom columns views </li>
  134. <li>Tooltips</li>
  135. <li>Thumbnal view </li>
  136. <li>Find files</li>
  137. <li>Colors by file type </li>
  138. <li>Overwrite dialog </li>
  139. <li>Multi rename tool</li>
  140. </ul>
  141. <h3>3.1 Use cases <a name="use_cases"></a></h3>
  142. <h4>3.1.1. Display size of files and directories automatically<a
  143. name="use_cases_automatic_calculation"></a></h4>
  144. <h5>Custom columns view</h5>
  145. <p>Total Commander provides to calculate the size of directories
  146. by executing the command cm_CountDirContent (Hotkey
  147. Shift+Alt+Enter). An automatic calculation each time a directory
  148. is entered isn't possible though. By using the field "Size" the
  149. directory sizes are displayed as fast as possible. In the
  150. following explains step by step who this can be setup.</p>
  151. <ol>
  152. <li>Open the configuration dialog by clicking
  153. Configuration/Options in the main menu. </li>
  154. <li>Navigate to the page "Custom columns".</li>
  155. <li>Click the "New" button to create a new custom columns view.
  156. </li>
  157. <li> You can setup the number of columns and its contents n this
  158. dialog. Click the "Add column" button. A new row with
  159. properties is displayed. This row represents the new column's
  160. attributes. </li>
  161. <li>The next step is to define the new column's contents. Click
  162. the + button to assign a field to the column. Select
  163. dirsizecalc/Size/&lt;default&gt; in the menu. The property
  164. "Field contents" now displays [dirsizecalc.Size]. You can
  165. select another unit instead of &lt;default&gt;. Fore more
  166. details on this see the "Units" chapter. The property "Title"
  167. displays the text which will be displayed in the column
  168. header. The title can be changed at will. </li>
  169. <li>Click OK to close the dialog "Custom columns". </li>
  170. <li>Click OK to close the configuration dialog.</li>
  171. </ol>
  172. <h4>3.1.2. Delete empty directory trees <a
  173. name="use_cases_delete_empty_folder_trees"></a></h4>
  174. <h5>Find files</h5>
  175. <p>A large amount of directories containing no files may make it
  176. difficult to maintain orientation in the file system. It's a
  177. good idea to clean up from time to time. Values provided by
  178. content plug-ins such as DirSizeCalc can be used to narrow down
  179. the number of found files. So the find files function of Total
  180. Commander is used together with with the DirSizeCalc plug-in to
  181. find directories containing no files. </p>
  182. <ol>
  183. <li>Click "Search" in the Commands menu. </li>
  184. <li>Navigate to the "Plugins" tab. </li>
  185. <li>In this tab rules can be defined. For each file and
  186. directory in the search scope the defined rules will be
  187. checked. Only if the rule applies the file or directory will
  188. be added to the list of found files. In this case the rule is
  189. Plugin: dirsizecalc, Field: Contains Files, Operator: = and
  190. Value: No. In Furthermore the short form is used. In this case
  191. this would be dirsizecalc.Contains Files=No. The rule ensures
  192. that only directories will be found that contain no files. If
  193. a directory contains files or a problem occurred during
  194. retrieving the contents the directory won't be found during
  195. the search. </li>
  196. <li>Click on the button "Start search". Wait until the search
  197. has finished. </li>
  198. <li>Click on the "Feed to Listbox" button to display the search
  199. results in a Total Commander file list panel.</li>
  200. <li>Select all directories listed in the search results panel.</li>
  201. <li>Apply the delete operation to the selected files. During the
  202. process a prompt might be displayed informing you that a
  203. directory isn't empty. The statement is true but this is just
  204. a directory containing other empty directories. The prompt can
  205. be answered by clicking on the "All" button.</li>
  206. </ol>
  207. <p>Alternatively the rule dirsizecalc.Empty=Yes can be used. In
  208. this case the directories will be deleted without warnings as
  209. they don't even contain empty subdirectories. The disadvantage
  210. is that after deleting new empty subdirectories emerge until no
  211. empty directories are found.</p>
  212. <p>&nbsp;</p>
  213. <p>It's a good idea to search the search parameters to be able to
  214. repeat the search later. </p>
  215. <h4>3.1.3. Find out if compression makes sense <a
  216. name="use_cases_check_if_comression_makes_sense"></a></h4>
  217. <h5>Custom columns view </h5>
  218. <h5>Find files</h5>
  219. <p>The Windows file system NTFS allows you to set the "compressed"
  220. attribute to each file. The file is compressed but in contrast
  221. to archives you can continue working as if the file were
  222. uncompressed. Why are not all files compressed automatically?
  223. Reading and writing of compressed files takes longer compared to
  224. uncompressed files. For this reason only files should be
  225. compressed where write operation are performed infrequently.
  226. Many files are archives or files with a high information
  227. content. The cannot be further compressed by using NTFS
  228. compression. This is where "Compressed Size" and "Compression
  229. Rate" come into play. They can be setup the same way as
  230. described in the use case "Display size of files and directories
  231. automatically" but an additional column "Compressed Size" has to
  232. be added. Alternatively you can search for files which couldn't
  233. be compressed very good. The search is setup in the same way as
  234. described in "Delete empty directory trees" but the rule defined
  235. in the "Plugins" tab differs. It could be for example some like
  236. this:</p>
  237. <ul>
  238. <li>tc.Compressed = yes </li>
  239. <li>tc.Directory = no</li>
  240. <li>dirsizecalc.Compressed Size &gt; 80</li>
  241. </ul>
  242. <h4>3.1.4. Find out how many files are contained in a directory <a
  243. name="use_cases_files_count"></a></h4>
  244. <h5>Thumbnail view </h5>
  245. <ol>
  246. <li>Open the configuration dialog by clicking
  247. Configuration/Options in the main menu. </li>
  248. <li>Navigate to the page "Thumbnail view".</li>
  249. <li>Make sure "Show custom fields below thumbnails" is checked.
  250. </li>
  251. <li>Enter "Size: " (without quotes) in the fields below. </li>
  252. <li>Click on the "Add" button right to the edit field. </li>
  253. <li>Select "dirsizecalc/File Count" in the menu. </li>
  254. <li>Click OK to close the configuration dialog.</li>
  255. </ol>
  256. <h4>3.1.5. Find out if a directory contains subdirectories <a
  257. name="use_cases_contains_subdirectories"></a></h4>
  258. <h5>Tooltip</h5>
  259. <ol>
  260. <li>Open the configuration dialog by clicking
  261. Configuration/Options in the main menu. </li>
  262. <li>Navigate to the page "Display".</li>
  263. <li>Make sure that the options " Show filename in file list as
  264. tooltip if truncated" and are activated. </li>
  265. <li>Make sure the options "Show file name in file list as
  266. tooltip if truncated " and "Win32-style tips with file
  267. comments"are activated.</li>
  268. <li>Click on the "+" button to create a user-defined tooltip.</li>
  269. <li>The dialog "User-defined fields by file type" is displayed.
  270. Click on the "Add" button to create a new file type.</li>
  271. <li>The dialog "Enter file type" is displayed. Enter *.* to
  272. include all directories.</li>
  273. <li>Click OK to close the dialog "Enter file type".</li>
  274. <li>Now a dialog is displayed which is also labeled
  275. "User-defined fields by filetype". First enter "Contains
  276. subdirectories: " (without quotes).</li>
  277. <li>Clock on the the + button. </li>
  278. <li>Select dirsizecalc/Contains subdirectories. In the text
  279. fields the following text should be displayed: "Contains
  280. subdirectories: [=dirsizecalc.Contains Subdirectories]"
  281. (without quotes).</li>
  282. <li>Click OK to close the dialog "User-defined fields by file
  283. type".</li>
  284. <li>Click OK to close the dialog "User-defined fields by file
  285. type".</li>
  286. <li>Click OK to close the configuration dialog.</li>
  287. </ol>
  288. <p>The described approach can be used in a slightly modified way
  289. to color directories containing subdirectories using the "Colors
  290. by file type" function. In this case Total Commander uses
  291. DirSizeCalc to process the operation in foreground. For this
  292. reason Total Commander until the operation is completed. </p>
  293. <h4>3.1.6. Load the directory size for all selected or all fields
  294. by pressing a keystroke<a name="use_cases_load_fields_on_demand"></a></h4>
  295. <p>Many users don't want that all sizes are calculated
  296. automatically. They rather want to know the sizes of all
  297. selected or of all displayed directories. Total Commander makes
  298. it possible. Here is an example how this can be achieved by
  299. pressing a keystroke.</p>
  300. <ol>
  301. <li>Start the included setting tool (DirSizeCalcSetting.exe).</li>
  302. <li>Select the "Load on demand" option for the already selected
  303. field "Size" in the dialog "Edit field settings".</li>
  304. <li>Click OK.</li>
  305. <li>Restart Total Commander.</li>
  306. <li>Create a new custom column view as described in chapter
  307. 3.1.1 .</li>
  308. <li>Open the configuration dialog by clicking
  309. Configuration/Options in the main menu.</li>
  310. <li>Select the page "Misc.".</li>
  311. <li>Select the desired hotkey (e.g. Alt+Shift+Enter).</li>
  312. <li>Click on the button with the magnifier.</li>
  313. <li>Select the "Custom column view" category in the displayed
  314. "Choose command" dialog.</li>
  315. <li>Select cm_LoadSelOnDemandFields, to calculate the size of
  316. all selected directories or cm_LoadAllOnDemandFields to
  317. calculate the size of all directories. </li>
  318. <li>Click OK to apply the selected command. </li>
  319. <li>Click on the button with the checkmark to apply the chosen
  320. command.</li>
  321. <li>Click OK to close the configuration dialog . </li>
  322. <li>Now select the directories to calculate.</li>
  323. <li>Press the chosen hotkey . </li>
  324. </ol>
  325. <p>Once configured you just have to set the created custom column
  326. view and the steps 15 and 16. Although the new commands can be
  327. found in the "Custom column view" category they also work great
  328. in thumbnail view. </p>
  329. <h3>3.2 Additional values for displayed values <a
  330. name="additional_information"></a></h3>
  331. <p>DirSizeCalc shows some tokens in front of the calculation
  332. result, if the complete directory content couldn't be retrieved.
  333. This can be the case for several reasons: </p>
  334. <ul>
  335. <li>AD = Access denied. This error is displayed if the current
  336. user has no sufficient access permissions for opening the
  337. directory. </li>
  338. <li>U = Unreadable Unicode name. This error occurs if file name
  339. contains characters which don't match the currently set
  340. Windows code page and you have deactivated storing of short
  341. file names.</li>
  342. <li>E = Unknown error. Unknown error should not be displayed at
  343. all. When it's displayed please report it to me.</li>
  344. <li>NF = Not followed reparse point. The user has set the option
  345. to now follow reparse points which results in not including
  346. these these files in the calculation.</li>
  347. </ul>
  348. <h3>3.3. Size display of (almost) empty directories <a
  349. name="empty_directory_display"></a></h3>
  350. <p>There can be multiple reasons for a directory size of 0 bytes.
  351. So far the fields "Leer" and "Contains Files" had to be used to
  352. distinguish them but now this information is displayed directly
  353. in the "Size" field. The following cases are distinguished: </p>
  354. <ul>
  355. <li>The directory contains only files of size 0. In this case
  356. DirSizeCalc displays 0 as size.</li>
  357. <li>The directory contains only empty subdirectories but no
  358. files. In this case "No files" is being displayed.</li>
  359. <li>The directory is really empty In this case "Empty is being
  360. displayed. </li>
  361. </ul>
  362. <h3>3.4 Placeholders<a name="placeholders"></a></h3>
  363. <p>Calculation of directory can take a long time. For this reason
  364. DirSizeCalc displays "Dir." until the actual value has been
  365. calculated. If DirSizeCalc detects that the directory is
  366. actually a reparse point "Junc. Pt." is displayed for junction
  367. points and "Mnt. Pt." is displayed for mount points. </p>
  368. <h2>4. Settings <a name="settings"></a></h2>
  369. <p>The bundled settings tool (DirSizeCalcSettings.exe) can be used
  370. to personalize DirSizeCalc. Closing the setting tool will save
  371. the settings but Total Commander has to be restarted to apply
  372. the changed settings.</p>
  373. <h3>4.1. Field settings <a name="field_settings"></a></h3>
  374. <p>Field settings can be used to personalize the field's behavior.
  375. Initially just predefined fields are available on the "Fields"
  376. tab. By clicking on "Add" you can add you own fields. This can
  377. be helpful if you want to use a certain field with different
  378. behaviors. By clicking "Delete" custom fields can be deleted.</p>
  379. <p>A single click in the list will open a dialog which includes
  380. all settings available for the selected field. Please note that
  381. not all settings are available to all fields.</p>
  382. <h4>4.1.1 Name<a name="field_settings_name"></a></h4>
  383. <p>This is the field's name for all built-in fields. For custom
  384. fields a name set by the user.</p>
  385. <h4>4.1.2. Field selection <a
  386. name="field_settings_field_selection"></a></h4>
  387. <p>Here you can pick one of DirSizeCalc's fields .</p>
  388. <h4>4.1.3. Loading behavior <a
  389. name="field_settings_loading_behavior"></a></h4>
  390. <p>This setting only applies to fields used in custom column views
  391. and in thumbnail view. By default the values are calculated
  392. automatically when opening a directory (setting automatically).
  393. If you change this to "on demand" here than you will have to
  394. press the space key to load the values of all configured fields
  395. for the directory under the cursor.</p>
  396. <h4>4.1.4. Reparse point behavior <a
  397. name="field_settings_reparse_point_behavior"></a></h4>
  398. <p>Reparse points look like normal directories but they point to a
  399. disk volume (mount points) or another directory (junction
  400. points). By default DirSizeCalc treats reparse points just like
  401. normal directories which means the target's directory contents
  402. is calculated. This may lead to wrong assumptions on the
  403. directory's size and take a long time. </p>
  404. <p>DirSizeCalc provides separated options for mount- and junction
  405. points. By unchecking "Follow mount points" respectively "Follow
  406. junction points" calculation can be completely deactivated. In
  407. addition the option "but not in subdirectories" can be used to
  408. treat reparse points like directories in the visible directory
  409. level but don't calculate values for reparse points in
  410. subdirectories.</p>
  411. <h4>4.1.5. Recursive<a name="field_settings_recursive"></a></h4>
  412. <p>By default a directory is processed recursively. This means the
  413. complete directory including all subdirectories and the
  414. directory content of this subdirectories and so on is considered
  415. in the calculation. By disabling "Recursive" only the directory
  416. content is considered.</p>
  417. <h4>4.1.6. Cache values <a name="field_settings_cache_values"></a></h4>
  418. <p>DirSizeCalc stores the retrieved values in a cache to speed up
  419. displaying directory sizes. The cache's disadvantage is that the
  420. displayed values are not always up to date. If you want to get
  421. the actual directory sizes you can force a reload by executing
  422. "Reread source" from the View menu (hotkey: Ctrl+R).</p>
  423. <h4>4.1.7. Calculation limit<a name="field_settings_limit"></a></h4>
  424. <p>If you just need approximate values and calculation time is
  425. critical you enable a calculation limit. Here you can enter the
  426. number of files which should be retrieved for a directory. </p>
  427. <p>When the limit has been reached the calculation the calculation
  428. will be aborted and "&gt;=" will by displayed in front of the
  429. value. This indicates the the actual value might by much bigger.</p>
  430. <h3>4.2. Unit settings <a name="unit_settings"></a></h3>
  431. <p>The built-in units differ in unit and prefix. Unit defines if
  432. and how the size in bytes is converted to another unit. Prefix
  433. defines the base on which the calculation is performed.</p>
  434. <p>The so called binary prefixes are based on power of two. The
  435. size dimensions are 2^10 =1.024 (= 1 KiB), 2^20 = 1.048.576 (= 1
  436. MiB) and 2^30= 1.073.741.824 (=1 GiB).</p>
  437. <p>The SI prefixes are based on power of ten. The size dimensions
  438. differ by a factor of 1000. 1.000 bytes (= 1 kB), 1.000.000 (1
  439. MB) and 1.000.000.000 (= 1 GB).</p>
  440. <p>Many programs - such as Total Commander - calculate based on
  441. power of two but use SI prefixes. This presentation is wrong and
  442. isn't used by Total Commander for this reason.</p>
  443. <p>Below you'll find a table containing example conversions.
  444. Please note that actual presentation depends on the chosen
  445. formatting options. </p>
  446. <p>&nbsp;</p>
  447. <table frame="VOID" cols="7" rules="NONE" border="0"
  448. cellspacing="0">
  449. <colgroup> <col width="98"> <col width="120"> <col width="86">
  450. <col width="86"> <col width="120"> <col width="86"> <col
  451. width="86"> </colgroup> <thead> <tr>
  452. <th>
  453. <div align="right">bytes</div>
  454. </th>
  455. <th>
  456. <div align="right">KiB</div>
  457. </th>
  458. <th>
  459. <div align="right">MiB</div>
  460. </th>
  461. <th>
  462. <div align="right">GiB</div>
  463. </th>
  464. <th>
  465. <div align="right">kB</div>
  466. </th>
  467. <th>
  468. <div align="right">MB</div>
  469. </th>
  470. <th>
  471. <div align="right">GB</div>
  472. </th>
  473. </tr>
  474. </thead> <tbody>
  475. <tr>
  476. <td sdval="0" sdnum="1031;0;#.##0" width="98" align="RIGHT"
  477. height="17">0</td>
  478. <td sdval="0" sdnum="1031;0;#.##0,0" width="120"
  479. align="RIGHT">0,0</td>
  480. <td sdval="0" sdnum="1031;0;#.##0,0" width="86"
  481. align="RIGHT">0,0</td>
  482. <td sdval="0" sdnum="1031;0;#.##0,0" width="86"
  483. align="RIGHT">0,0</td>
  484. <td sdval="0" sdnum="1031;0;#.##0,0" width="120"
  485. align="RIGHT">0,0</td>
  486. <td sdval="0" sdnum="1031;0;#.##0,0" width="86"
  487. align="RIGHT">0,0</td>
  488. <td sdval="0" sdnum="1031;0;#.##0,0" width="86"
  489. align="RIGHT">0,0</td>
  490. </tr>
  491. <tr>
  492. <td sdval="587" sdnum="1031;0;#.##0" align="RIGHT"
  493. height="17">587</td>
  494. <td sdval="0,5732421875" sdnum="1031;0;#.##0,0"
  495. align="RIGHT">0,6</td>
  496. <td sdval="0,000559806823730469" sdnum="1031;0;#.##0,0"
  497. align="RIGHT">0,0</td>
  498. <td sdval="0,000000546686351299286" sdnum="1031;0;#.##0,0"
  499. align="RIGHT">0,0</td>
  500. <td sdval="0,587" sdnum="1031;0;#.##0,0" align="RIGHT">0,6</td>
  501. <td sdval="0,000587" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  502. <td sdval="0,000000587" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  503. </tr>
  504. <tr>
  505. <td sdval="1000" sdnum="1031;0;#.##0" align="RIGHT"
  506. height="17">1.000</td>
  507. <td sdval="0,9765625" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  508. <td sdval="0,00095367431640625" sdnum="1031;0;#.##0,0"
  509. align="RIGHT">0,0</td>
  510. <td sdval="0,000000931322574615479" sdnum="1031;0;#.##0,0"
  511. align="RIGHT">0,0</td>
  512. <td sdval="1" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  513. <td sdval="0,001" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  514. <td sdval="0,000001" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  515. </tr>
  516. <tr>
  517. <td sdval="1024" sdnum="1031;0;#.##0" align="RIGHT"
  518. height="17">1.024</td>
  519. <td sdval="1" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  520. <td sdval="0,0009765625" sdnum="1031;0;#.##0,0"
  521. align="RIGHT">0,0</td>
  522. <td sdval="0,00000095367431640625" sdnum="1031;0;#.##0,0"
  523. align="RIGHT">0,0</td>
  524. <td sdval="1,024" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  525. <td sdval="0,001024" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  526. <td sdval="0,000001024" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  527. </tr>
  528. <tr>
  529. <td sdval="81981" sdnum="1031;0;#.##0" align="RIGHT"
  530. height="17">81.981</td>
  531. <td sdval="80,0595703125" sdnum="1031;0;#.##0,0"
  532. align="RIGHT">80,1</td>
  533. <td sdval="0,0781831741333008" sdnum="1031;0;#.##0,0"
  534. align="RIGHT">0,1</td>
  535. <td sdval="0,0000763507559895515" sdnum="1031;0;#.##0,0"
  536. align="RIGHT">0,0</td>
  537. <td sdval="81,981" sdnum="1031;0;#.##0,0" align="RIGHT">82,0</td>
  538. <td sdval="0,081981" sdnum="1031;0;#.##0,0" align="RIGHT">0,1</td>
  539. <td sdval="0,000081981" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  540. </tr>
  541. <tr>
  542. <td sdval="101654" sdnum="1031;0;#.##0" align="RIGHT"
  543. height="17">101.654</td>
  544. <td sdval="99,271484375" sdnum="1031;0;#.##0,0"
  545. align="RIGHT">99,3</td>
  546. <td sdval="0,0969448089599609" sdnum="1031;0;#.##0,0"
  547. align="RIGHT">0,1</td>
  548. <td sdval="0,0000946726649999619" sdnum="1031;0;#.##0,0"
  549. align="RIGHT">0,0</td>
  550. <td sdval="101,654" sdnum="1031;0;#.##0,0" align="RIGHT">101,7</td>
  551. <td sdval="0,101654" sdnum="1031;0;#.##0,0" align="RIGHT">0,1</td>
  552. <td sdval="0,000101654" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  553. </tr>
  554. <tr>
  555. <td sdval="1000000" sdnum="1031;0;#.##0" align="RIGHT"
  556. height="17">1.000.000</td>
  557. <td sdval="976,5625" sdnum="1031;0;#.##0,0" align="RIGHT">976,6</td>
  558. <td sdval="0,95367431640625" sdnum="1031;0;#.##0,0"
  559. align="RIGHT">1,0</td>
  560. <td sdval="0,000931322574615479" sdnum="1031;0;#.##0,0"
  561. align="RIGHT">0,0</td>
  562. <td sdval="1000" sdnum="1031;0;#.##0,0" align="RIGHT">1.000,0</td>
  563. <td sdval="1" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  564. <td sdval="0,001" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  565. </tr>
  566. <tr>
  567. <td sdval="1048576" sdnum="1031;0;#.##0" align="RIGHT"
  568. height="17">1.048.576</td>
  569. <td sdval="1024" sdnum="1031;0;#.##0,0" align="RIGHT">1.024,0</td>
  570. <td sdval="1" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  571. <td sdval="0,0009765625" sdnum="1031;0;#.##0,0"
  572. align="RIGHT">0,0</td>
  573. <td sdval="1048,576" sdnum="1031;0;#.##0,0" align="RIGHT">1.048,6</td>
  574. <td sdval="1,048576" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  575. <td sdval="0,001048576" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  576. </tr>
  577. <tr>
  578. <td sdval="5400000" sdnum="1031;0;#.##0" align="RIGHT"
  579. height="17">5.400.000</td>
  580. <td sdval="5273,4375" sdnum="1031;0;#.##0,0" align="RIGHT">5.273,4</td>
  581. <td sdval="5,14984130859375" sdnum="1031;0;#.##0,0"
  582. align="RIGHT">5,1</td>
  583. <td sdval="0,00502914190292358" sdnum="1031;0;#.##0,0"
  584. align="RIGHT">0,0</td>
  585. <td sdval="5400" sdnum="1031;0;#.##0,0" align="RIGHT">5.400,0</td>
  586. <td sdval="5,4" sdnum="1031;0;#.##0,0" align="RIGHT">5,4</td>
  587. <td sdval="0,0054" sdnum="1031;0;#.##0,0" align="RIGHT">0,0</td>
  588. </tr>
  589. <tr>
  590. <td sdval="70000000" sdnum="1031;0;#.##0" align="RIGHT"
  591. height="17">70.000.000</td>
  592. <td sdval="68359,375" sdnum="1031;0;#.##0,0" align="RIGHT">68.359,4</td>
  593. <td sdval="66,7572021484375" sdnum="1031;0;#.##0,0"
  594. align="RIGHT">66,8</td>
  595. <td sdval="0,0651925802230835" sdnum="1031;0;#.##0,0"
  596. align="RIGHT">0,1</td>
  597. <td sdval="70000" sdnum="1031;0;#.##0,0" align="RIGHT">70.000,0</td>
  598. <td sdval="70" sdnum="1031;0;#.##0,0" align="RIGHT">70,0</td>
  599. <td sdval="0,07" sdnum="1031;0;#.##0,0" align="RIGHT">0,1</td>
  600. </tr>
  601. <tr>
  602. <td sdval="1000000000" sdnum="1031;0;#.##0" align="RIGHT"
  603. height="17">1.000.000.000</td>
  604. <td sdval="976562,5" sdnum="1031;0;#.##0,0" align="RIGHT">976.562,5</td>
  605. <td sdval="953,67431640625" sdnum="1031;0;#.##0,0"
  606. align="RIGHT">953,7</td>
  607. <td sdval="0,931322574615479" sdnum="1031;0;#.##0,0"
  608. align="RIGHT">0,9</td>
  609. <td sdval="1000000" sdnum="1031;0;#.##0,0" align="RIGHT">1.000.000,0</td>
  610. <td sdval="1000" sdnum="1031;0;#.##0,0" align="RIGHT">1.000,0</td>
  611. <td sdval="1" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  612. </tr>
  613. <tr>
  614. <td sdval="1073741824" sdnum="1031;0;#.##0" align="RIGHT"
  615. height="17">1.073.741.824</td>
  616. <td sdval="1048576" sdnum="1031;0;#.##0,0" align="RIGHT">1.048.576,0</td>
  617. <td sdval="1024" sdnum="1031;0;#.##0,0" align="RIGHT">1.024,0</td>
  618. <td sdval="1" sdnum="1031;0;#.##0,0" align="RIGHT">1,0</td>
  619. <td sdval="1073741,824" sdnum="1031;0;#.##0,0" align="RIGHT">1.073.741,8</td>
  620. <td sdval="1073,741824" sdnum="1031;0;#.##0,0" align="RIGHT">1.073,7</td>
  621. <td sdval="1,073741824" sdnum="1031;0;#.##0,0" align="RIGHT">1,1</td>
  622. </tr>
  623. <tr>
  624. <td sdval="6250000000" sdnum="1031;0;#.##0" align="RIGHT"
  625. height="17">6.250.000.000</td>
  626. <td sdval="6103515,625" sdnum="1031;0;#.##0,0" align="RIGHT">6.103.515,6</td>
  627. <td sdval="5960,46447753906" sdnum="1031;0;#.##0,0"
  628. align="RIGHT">5.960,5</td>
  629. <td sdval="5,82076609134674" sdnum="1031;0;#.##0,0"
  630. align="RIGHT">5,8</td>
  631. <td sdval="6250000" sdnum="1031;0;#.##0,0" align="RIGHT">6.250.000,0</td>
  632. <td sdval="6250" sdnum="1031;0;#.##0,0" align="RIGHT">6.250,0</td>
  633. <td sdval="6,25" sdnum="1031;0;#.##0,0" align="RIGHT">6,3</td>
  634. </tr>
  635. </tbody>
  636. </table>
  637. <p>&nbsp;</p>
  638. <h4>4.2.1. Name<a name="unit_settings_name"></a></h4>
  639. <p>For built-in units this is the default unit abbreviation. For
  640. custom units this is a name defined by the user.</p>
  641. <h4>4.2.2. Prefixes and units <a
  642. name="unit_settings_prefixes_units"></a></h4>
  643. <p>DirSizeCalc allows the user to define which unit is used for a
  644. certain range of file- and directory sizes. By default bytes is
  645. used. First check all other units which you want to use. Than
  646. enter the minimum value in bytes where this unit should be used.
  647. </p>
  648. <p>If you want to use KiB as the smallest unit you have to enter 0
  649. in the KiB size field.</p>
  650. <h4>4.2.3. Formatting<a name="unit_settings_formatting"></a></h4>
  651. <p>There are a bunch of options to customize the formatting of
  652. file- and directory sizes. This includes the number of digits,
  653. decimal- and thousand separators and some more.</p>
  654. <h4>4.2.4. Preview <a name="unit_settings_preview"></a></h4>
  655. <p>This preview displays how directory sizes will be displayed
  656. later in Total Commander.</p>
  657. <h3>4.3 Change the settings location <a
  658. name="settings_file_location"></a></h3>
  659. <p>By default DirSizeCalc stores its settings in the same
  660. directory where Wincmd.ini - Total Commander's main settings
  661. file - is located. In this dialog you can choose between several
  662. locations.</p>
  663. <p>&nbsp;</p>
  664. <ul>
  665. <li>Same directory as "Wincmd.ini"</li>
  666. <li>Directory "DirSizeCalc" in "Wincmd.ini" directory.</li>
  667. <li>Plug-in directory</li>
  668. <li>Total Commander root directory</li>
  669. </ul>
  670. <p>&nbsp;</p>
  671. <p>To choose a new location please select the desired location
  672. from the combo box. </p>
  673. <p>In addition the current path and if this path is writable is
  674. displayed. </p>
  675. <h2>5. Frequently asked questions <a name="faq"></a></h2>
  676. <p><strong>Can I use DirSizeCalc to calculate values for all
  677. selected or all directories?</strong></p>
  678. <p>Yes this is possible starting from Total Commander 7.50. There
  679. is a <a href="#use_cases_load_fields_on_demand">use case</a>
  680. which describes how it works. </p>
  681. <p>&nbsp;</p>
  682. <p><strong>I changed to a directory containing many files.
  683. Previously I sorted by a column which contained a DirSizeCalc
  684. field. Total Commander seems to hang. Is there anything I can
  685. do? </strong></p>
  686. <p>Total Commander waits for the calculation to finish and blocks
  687. program's use. Trying to abort the calculation (e.g. by hitting
  688. Escape) is not handled by Total Commander and for this reason
  689. not forwarded to the plug-in. I asked the author of Total
  690. Commander to add adda way to abort the calculation as soon as
  691. possible. </p>
  692. <p>In the meantime you can use "Calculation limit" option which
  693. only calculates a fraction of the directory contents and
  694. therefore shortens the waiting time.</p>
  695. <p>&nbsp;</p>
  696. <p><strong>Instead of displaying the size of directories in
  697. archives just 0 is displayed. Why it doesn't work?</strong></p>
  698. <p>In this case DirSizeCalc would have to get the values from
  699. Total Commander. Unfortunately this isn't possible in the
  700. current Total Commander version. I asked the author of Total
  701. Commander to add this feature as soon as possible.</p>
  702. <p>&nbsp;</p>
  703. <p><strong>In earlier versions there have been fields called "in
  704. background" and "on demand". Where have they gone?</strong></p>
  705. <p>The default setting is now "in background". If you want to load
  706. the values "on demand" you are free to do so. Please start the
  707. bundled configuration utility (DirSizeCalcSettings.exe). This
  708. tool allows you to set "on demand" loading for each single field
  709. or you can even create your own custom field with loading
  710. behavior set to "on demand". The reasons for changing the field
  711. names have been reducing the field count and shortening of field
  712. names. If you added custom columns you had to change the title
  713. manually resulted in losing the information anyway. </p>
  714. <h2>6. Contact<a name="contact"></a></h2>
  715. <p>There is a <a
  716. href="http://www.ghisler.ch/board/viewtopic.php?t=18021">thread</a>
  717. in the <a href="http://www.ghisler.ch/">Total Commander forum</a>
  718. which can be used to discuss problems, bug and suggestions.</p>
  719. <h2>7. License and liability <a name="license"></a></h2>
  720. <p> Any liability for damage of any sort is hereby denied.<br>
  721. All rights reserved. This Total Commander plug-in is copyrighted
  722. free ware.</p>
  723. </div>
  724. </body>
  725. </html>