2 small problems and a suggestion

[JohnMirror]

Hi.
Thank you for the new version.
I have only 2 small problems:
1. Sometimes when I check the size of a folder using Spacebar key, the information disappears fast (split second). I have to use Spacebar key again and it's annoying.
I should mention that I changed the refresh settings:
http://www.imagebam.com/image/851615193333441

Maybe some files are changed inside that folder but still TC should "know" that and it should (re)display this information.
2. I need to disable sometimes the "write protect" for the files when I compare them. The problem is that the bultin editor doesn't help me 100% so sometimes during this I have to use another editor. But I can't save changes in the external editor because the compare function doesn't allow it.
A professional approach would be to monitor changes and to ask if it should reload the file, not to forbid the change. It does this sometimes but not in all situations.

And a suggestion: sometimes I uncheck the option "allow only one copy...". The problem is that most of the times I need it to be checked so it wouldn't open another instance (that I have no use for). But when I really need another instance, TC is already busy doing some operation and I have to edit wincmd.ini manually.
How about an option "start a new copy if the current instance is busy"...? Doesn't have to be exactly this name, it's just an example.

[umbra]

Hi, I've got a few answers for you, however you probably won't like them.

Folder sizes:

Maybe some files are changed inside that folder but still TC should "know" that and it should (re)display this information.

TC knows that and that's why it stops showing the folder size - it's not accurate anymore. And why does TC not recalculate it again automatically? Because that's a very resource-hungry operation that might take several seconds (or minutes). It would only slow your computer down.

External changes to compared files:

A professional approach would be to monitor changes and to ask if it should reload the file, not to forbid the change. It does this sometimes but not in all situations.

Try to check, if that only happens with files larger than 1MiB or not. In TC 8 there is a change that disables external changes to compared files, if they are larger than 1MiB. The reason is that in previous versions, TC could corrupt such files in some special cases. Fixing it would be rather hard and probably would require a significant changes in code, so it was disabled for the time being.

Allow only one copy:
Honestly, I don't see a big reason for that option to exist at all. If you don't want to start another instance, then don't start it. Simple. It makes sense in applications, that are associated with file types, but not in TC. Anyway, your proposed option would make things just messy. You would never know, what would your next click do - if opening a new instance or an existing one.
Note: if you want to open a new instance if TC even if you have disabled multiple instances, you can create a shortcut, that will start TC with a command line parameter \N (see section 4a in TC's help).