Balderstrom wrote:This wouldn't occur if TC's "temp" backups were named along the lines of FileName.ext.tc.bak or FileName.ext.tc.bk1, etc.
Or if it made a .bk1 for its initial save if an there was a pre-existing .bak
Or backup files will be placed in user-specific temp folder (read my prev post).
Also will be solved a trouble with write-protected folder (if edited files are not write-protected) where TC can't create new .bak-file.
Plz add a feature to keep temporary backup etc files in user-specific folder... It is VERY unconvenient to compare files in write-protected folder. In Vista/7 this is normal to have program folders write-protected, but we need to keep INI etc files write-enabled in such folders. And editing theese files within comparer is impossible because TC can't create backup file and asks where to place modified INI-file.
Any chance for having this resolved? I just overwrote some of my stuff by editing and saving (having previously made a .bak backup). I really don't like TC overwriting files without confirmation. A file manager should never do that! Can we change the extension to .tcb or something like that, bak is far too common! User-specified folder is even better as then you don't pollute the harddisk with garbage files.
gulikoza wrote:Any chance for having this resolved? I just overwrote some of my stuff by editing and saving (having previously made a .bak backup). I really don't like TC overwriting files without confirmation. A file manager should never do that! Can we change the extension to .tcb or something like that, bak is far too common! User-specified folder is even better as then you don't pollute the harddisk with garbage files.
