Problem with <Read error!>

[MarcinW]

Steps to reproduce:

1) create "C:\test" directory
2) go into it
3) close TC
4) delete "C:\test" directory by using Explorer
5) launch TC again - you will be in a non-existent "C:\test" directory, with <Read error!> pseudofile visible

Regards

[DrShark]

23.04.18 Added: If we cannot access a directory when TC starts, show <Read error!> even if IgnoreDirErrors=1 isn't set (32/64)

[MarcinW]

Well, I apparently overlooked this.

But it is strange... Do I must see <Read error!> message even, when my configuration tells, that I don't want to see it?

As for me, there is no advantage of such behavior - I just must then perform some additional steps to go elsewhere, when - for example - memory card or flash drive has been removed, and this was TC's last location. With the previous behavior, where TC goes to the root system drive, there was at least a chance, that it's a good starting location for a work.

Regards

[ghisler(Author)]

I was asked to do it this way so everyone can benefit from the new option, not only the 2-3 users who read the docs and set the option manually...

[MarcinW]

But this is inconsistent, because it ignores the INI setting... And those users, that don't read the documentation, may think, that it's some strange error, not a feature...

Maybe TC could just use the new functionality by default, if not disabled by setting IgnoreDirErrors to 0? This way everybody will see the new feature, and TC will behave in a consistent way.

Regards

[ghisler(Author)]

No, but I could make 3 options, with the current one the default, and IgnoreDirErrors=-1 turning everything off?

[MarcinW]

I could live with such a solution

[deus-ex]

I was asked to do it this way so everyone can benefit from the new option, not only the 2-3 users who read the docs and set the option manually...

That's hilarious. I wonder who the other 1-2 users might be?

[ghisler(Author)]

I made 2 changes in beta 3:
1. I show <Read error!> only for locked tabs now (either with or without directory changes allowed) with IgnoreDirErrors=0 or IgnoreDirErrors=1

2. I have added IgnoreDirErrors=-1 which turns it off even for locked tabs.

Please test!

[MarcinW]

Partially fixed. Try this (with IgnoreDirErrors=0):

1) create c:\test directory
2) open TWO tabs with c:\test
3) lock SECOND of them, and make SECOND of them currently active
4) close TC, delete c:\test, start TC again
5) BOTH tabs are opened with <Read error!> message - but first should go to the root c: directory instead

If you make FIRST of them currently active in step 3, everything works properly.

Regards

[ghisler(Author)]

This happens because after the first <Read error!>, this directory is marked as problematic. So when you change tabs, TC doesn't try to re-read it.

If you use two different directories in the two tabs and delete them both, then you shouldn't get this problem.