[8.0ß18x32] No context menu on [..] and long network path

[CodeMajster]

The context menu is not displayed on first list item (directory level drop [..]) when selected path is a network path containing more than 260 characters.

It makes it difficult to work around the “Search path not found!” problem because you cannot easily launch path in the windows explorer.

This context menu worked on version 7.55a. It does not work on all versions 7.56a and up.

[ghisler(Author)]

NOT confirmed, the context menu appears just fine (Windows 7 x64).

[CodeMajster]

Sorry, I didn't realize it initially, but to trigger this issue, you need to perform the following steps:
1. Open TC and make sure it is set to return to last viewed directory on launch
2. Browse to the long network path (from server root directory)
3. Try to open the context menu – this time it will work as expected
4. Close and reopen TC
5. Try to open the context menu on the remembered network path again - it doesn’t appear on my system (also Win7 x64)

Note: if you re-browse from server root directory, problem goes away until you restart TC again.

Version 7.55a has this problem too. Apparently, I never restarted its instance when I tested this.

Edit:
I just reproduced the missing context menu behavior on local NTFS drive by creating 20 nested directories, all with the following name: 12345678.123
When showing the context of the last directory, menu does not show up. It does not matter whether folder was just browsed to or remembered on TC restart. However, explorer is not even able to open 20th folder. In this case disabling context menu seems appropriate.

Thanks

[Flint]

I confirm that for long paths (>260 chars) no context menu appears on the [..] item. Besides, even for files and dirs located at such long paths the context menu is opened but does not contain most of the items usual files/dirs have.

[ghisler(Author)]

Currently I don't have any plans to make this work, because it's unreliable with such long paths.