Bug with option "No network browsing on startup"

[slimokanta]

Scenario:

Option "No network browsing on startup" is activated
Tab1 is configured as locked homezone to a local path
Tab2 is browsed to a network share
Software is closed
Software is started
Tab1 is browsed to location of Tab2 (not correct)
Tab2 is browsed to its old location

The homezone in Tab1 is not present and must be configured new.

Without the option it works correct, but then I have long delays on startup when I change the office with my notebook.

[admin]

Cannot reproduce.

This is a totally normal setup. Many users are likely to use it. I would be surprised if there would be a bug here. There must be some other factor.

[slimokanta]

The behaviour is reproducible and depends on a second option ("Open command line start path in new tab") and the last active Tab.

When the Function is activated in the described scenario and Tab1 is active before closing the app:
-> Everything OK

When the Function is activated in the described scenario and Tab2 is active before closing the app:
-> A new (third) Tab is opended after restart with the same path as Tab2 (the homezone in Tab1 is still there, but the third Tab should not open)

When the Function is deactivated in the described scenario and Tab1 is active before closing the app:
-> Everything OK

When the Function is deactivated in the described scenario and Tab2 is active before closing the app:
-> The first Tab is opended after restart with the same path as Tab2 (not correct)

Caution: The first Tab is browsed to a local paht, the second Tab is browsed to a network share in the scenario.

[slimokanta]

Can you reproduce it?

[admin]

No, but every network is different. Can anybody else?

[admin]

Can you reproduce it with a fresh version of XYplorer? (Just run a copy of XYplorer.exe from any temp folder.)

[slimokanta]

yes. xyplorer is then in evaluation mode, but it is exact the same behavior.