One "Enter" to much after wrong URL with ThreadFin

[ricobautsch]

TC automatically starts the File, which is currently under the cursor, or changes to the directory, which is currently under the cursor.
This only happens, if "ThreadFindFirst" is activated, and if i enter in the address-bar above the File-list an URL that does not exist.

This behavior is already confirmed, see here.

The steps to reproduce in detail:

1.
Change to Edit-mode in the adress-bar above the file-list (click with the mouse to the path in this field)

2.
Enter the following in the edit-box: \\doesnotexist\c$
and confirm with pressing the enter key.

3.
From now, i don't touch the keyboard or the mouse. The following happens:
- some seconds Hourglass-cursor
- after that a longer time the dialog "Connect" with the cancel button
- after that, the dialog "Connect" hides and TC starts whatever is currently under the cursor

TC 7 rc1

[Flint]

Confirm too.

[ghisler(Author)]

Thanks, I could reproduce it now.

[Flint]

Hm... In RC2 TC just does not react to the pressing of Enter. Nothing happens, the title remains editable...

[karlchen]

Hm... In RC2 TC just does not react to the pressing of Enter. Nothing happens, the title remains editable...

As far as I can tell this only happens if you enter an invalid UNC path:

(1) Typed in a valid \\machine\D$\, pressed the enter key => immediately switched to the machine and D:\

(2) Typed in an invalid \\notthere\C$\, pressed enter key => heard "plong", editbox stayed in edit mode.

(T.C 7rc2 on WinXp Prof)

I assume this is the intended behaviour now.

Karl

[ghisler(Author)]

Yes, it should happen exactly like this when Windows reports quickly enough that the path is invalid! However, when it takes more than 3 seconds to respond, you will get the ThreadFindFirst error dialog.

[karlchen]

However, when it takes more than 3 seconds to respond, you will get the ThreadFindFirst error dialog.

Right, this happened after half a dozen tries. - Our network is simply too fast (as a rule). - But somehow I was lucky, found 1 slow connection and got the Abort-Dialogue for a few seconds.

So ThreadFindFirst=1 still does its job in cases where establishing a connection takes more than 3 seconds.

Karl

[ricobautsch]

TC does NOT start the file under cursor automatically anymore.
So i can confirm this bug as fixed.

[ghisler(Author)]

Thanks for checking!