Preserve URI of tabs with "Lock Tab and Address" on secondary/external HDDs

[i2]

Describe the bug The tabs marked with "Lock Tab and Address" preserve their value only when the resource is persistently available (e.g. fixed HDD). If it is a secondary (or external) HDD and you open Explorer++ when that HDD is not inserted, the tab's URI/address is gone (as far as I can tell) and replaced with the default value (which in my case was "This PC"). I describe it in more details below.

To Reproduce Steps to reproduce the behavior:

1. Mark some tabs located on a secondary HDD (e.g. G:\ partition) with "Locked Tab and Address"
2. Shutdown the computer
3. Remove the secondary HDD
4. Turn computer on and open Explorer++

Expected behavior Obviously the tabs content should/would not show up, but I would want the URI to stay intact for next time the URI becomes available (in this case, inserting secondary HDD back), but right now Explorer++ changes all of them to "This PC", and next time you open Explorer++ even if G:\ is available, all Tabs are still showing "This PC".

Version (please complete the following information):

• Explorer++ version: Explorer++ version 1.5.0.2444 dev (64-bit build) Build date: Jul 22 2024 20:36:20
• OS: Windows 11

Additional context I checked registry entries under HKEY_CURRENT_USER\Software\Explorer++\Tabs to see if I can recover my tabs, but no dice as the Directory entries are in hex.

I had a lot of tabs open as locked... I know this was not a good practice and it should have been better if I bookmarked them using "Manage bookmarks", but I thought to bring up this issue.

[derceg]

At the moment, if enumerating a directory fails, Explorer++ will instead navigate to the default folder. Similarly, if you were to remove the drive while Explorer++ was open, any tabs open on that drive would be navigated up.

It might be worth rethinking this. I don't think there's any particular reason why showing a non-existent folder wouldn't work. Obviously, operations in that folder would fail, but the application should continue running normally. I also think it would be more akin to what a web browser does when you visit a page that doesn't exist - it simply shows an error page, it doesn't try to navigate to a page that does exist.

On the other hand, navigating away from a non-existent folder is the behavior that Windows Explorer has and it's arguably useful in some cases. For example, if a folder is deleted, there's not much point keeping a tab in that folder.

So, perhaps the best option would be to make this behavior user-configurable. That is, an option that would prevent Explorer++ from navigating away from a non-existent folder.

[i2]

Sure. Making this user-configurable would be great. Thank you!