Does Not Remember Tree Configuration Upon Startup

[arielberschad]

I am running the latest version of XYPlorer 64 bit (28.10.0300). Upon startup, I can't get XYPlorer to display the directory, in the left hand pane, the same way each time. Instead, it always reverts to expanding the C (Local Disk) instead of the actual directory that I want it to expand. In Tools/Configuration/Startup, I've selected the Permanent Startup Path, but to no avail. I've also selected the Startup Pane to be the "Last Pane", also without success. Lastly, I've selected "Save Settings on Exit" without success. ARE THERE ANY OTHER CONFIGURATION SETTINGS THAT I NEED TO SELECT IN ORDER FOR XYPLORER TO DISPLAY THE SAME DIRECTORY STRUCTURE EACH TIME UPON STARTUP?

[jupe]

Configuration | General | Startup & Exit | Expand in tree

[arielberschad]

Thanks, but I already had that selected, so that does not resolve the problem.

[jupe]

Are you loading it via a shortcut lnk or similar? you may be loading it pointing to the C: in the shortcut.
Or you may have locked the tree ?

Tools | Customize Tree | Lock Tree

Or you may have Mini Tree enabled ?

View | Mini Tree

there are a lot of variables, a screenshot might help, you may want disable this, if you just mean you want C: saved collapsed:

Configuration | General | Tree and List | Tree | Remember state of tree

[arielberschad]

Thank you for all the ideas. The only one that finally worked was "Remember State of Tree." I appreciate your advice.

After this experience, I have the impression that the software configuration selections in this software are overlapping and potentially conflict with each other, and that the number of choices has become bloated, leading to the inability to quickly adjust basic settings to a desired state.

[admin]

"Remember state of tree" is enabled by default. You actively changed that setting. It's not really surprising that the state of the tree is no longer remembered.

[arielberschad]

I didn't change that setting. It worked fine for me for several years until I upgraded to the 64-bit version...then the problem started occurring.