XYplorer Beta Club

In the 32-bit versions, launching XY sets focus to the list item view. In 64-bit versions, the focus on launch is the address bar. I couldn't find any options to change this behaviour.

For me, the focus is restored where it was on the last stop.
As I never leave XY with focus on the address bar
it starts in the left list window (2 pane layout)

Hmm... In further testing I'm finding the behaviour to be unpredictable... I tested by launching a fresh instance of XY directly out of the noinstall zip, 100% default configuration. The focus went to the address bar. Now I just tried a new noinstall extraction, and like you said it did seem to focus on whatever was focused previously... But then launching from the original zip again the focus is always on the folder tree... It's even having an effect on my completely separate 32-bit install, which for some reason is now launching with address bar focus when it has never done so before. My main install (also portable) has Save settings on exit [Startup & Exit - Save Settings] disabled. How does any instance of XY determind where to set focus on startup? It must not be saved in the local ini, otherwise a standalone portable version should not have affected my main portable configuration. I don't understand what's happening...

No matter what I do, the 64-bit version will not start with focus set to the file list using my ini configuration. A separate copy from the noinstall zip does launch with focus wherever it was when last closed. It looks like it's supposed to use [General]LastFocus ini value. Mine is set to L, and it still starts up with address bar focus.

why not just use exe flag : /script="::focus 'L'"

bossi wrote: ↑24 Oct 2025 17:22 why not just use exe flag : /script="::focus 'L'"

I just tested that, it still focused the address bar.

Confirmed when the main menu bar is hidden. Tricky situation. Unfortunately the various tB-bug-workarounds now come in conflict with each other. At the moment there is nothing I can do.

Found a dirty hack that fixes it. Next beta.

Fix confirmed in v28.00.0502. Thanks!