List of changes (version 8.52 - 8.52a)
Jump to navigation
Jump to search
List of changes (version 8.52 - 8.52a) is a list of changes to Total Commander since version 8.52 until the release of version 8.52a. The list starts at the latest change and goes back in time.
| This page is transcluded into other pages. Editors must be aware of this and use "noinclude", "onlyinclude" and "includeonly" markup. |
List of changes (version 8.52 - 8.52a)
(17.09.15) Release Total Commander 8.52a final (branch with just bugfixes) (32/64)
- (17.09.15) Fixed: Compare by content was hanging on Linux/Wine when file was changed outside of the compare tool (32/64)
- (16.09.15) Fixed: TC switched from network drive to c:\ when launching, and the user couldn't access the root of that drive (32/64)
- (15.09.15) Fixed: Handle crash in FindFirstFile function, could lead to hanging directory read function (32/64)
- (09.09.15) Fixed: "Connecting" dialog not removed when: Testing big RAR (Alt+Shift+F9), Background, switch to currently inaccessible drive (e.g. network), RAR test ends after "Connecting" dialog appears (32/64)
- (08.09.15) Fixed: Didn't use abs() when calculating timeouts from GetTickCount() in some places, might cause problems after 25 days of uptime (32/64)
- (07.09.15) Fixed: Installer: Close running Total Commander also when we cannot determine its path (32)
- (04.09.15) Fixed: Button bar: put parameter %P%N in double quotes not only when the name contains a space, but also for '&' (needed for cmd.exe) (32/64)
- (04.09.15) Fixed: cm_FocusCmdLine didn't show the command line if it was hidden via settings (64)
- (04.09.15) Fixed: 32-bit uninstaller was shown as "Remove TC 64-bit" (German only) (32)
- (04.09.15) Fixed: Handle invalid ZIP files where the attribute flags are set to 255, so all files appear as folders (32/64)
- (02.09.15) Fixed: Crash unpacking ZIPs packed with LZMA compression (wrong tcmdlzma.dll included) (32)
- (01.09.15) Fixed: Crash when entering more than ~300 characters in Files - Change attributes - "time" field, may be a possible security hole (32/64)