Tab key behavior when the Preview tab is open

[Mesh]

Hitting Tab to switch between the list and tree panes doesn't work when the Info panel is open, because XY starts cycling through the fields in whatever tab is open in the Info panel.

For me, this gets in the way quite a bit, since I'm far more likely to want to navigate the file/folder structure then go into the Info tab fields. If that's what I want, I'll just click there, or use a KB shortcut that I know brings me there (such as Ctrl-F for the find tab).

I would request a configuration option to exclude tabbing to the Info panel from the list/tree panes. Obviously, if the focus is already in the Info panel, then you should still be able to tab through what's there.

If nobody uses the current behavior, then I'm all for making the change unilateral. But if people do, then perhaps a flag in the INI file?

[LittleBiG]

If you press F12, problem is gone.

Why do you keep open the info panel, if you don't want to use it? Anyway, when Properties is open, the TAB focus doesn't stop on info panel (unless you edit a field).

[Mesh]

If you press F12, problem is gone.

Why do you keep open the info panel, if you don't want to use it?

That's very shortsighted.

As an example, if I'm exploring File Info for various files, or using the preview function - but are moving around to different files in different folders. I'd have to open and close the Info panel several dozen times during a short session.

That's why.

[LittleBiG]

That's very shortsighted.

Sorry for that.

Personally in this case I use Shift+TAB to navigate back avoiding info panel. So I use TAB and Shift+TAB intensively.

[admin]

Use F6 = Cycle focus: Address Bar > Tree > List > Catalog.

[Mesh]

Use F6 = Cycle focus: Address Bar > Tree > List > Catalog.

Well, that's helpful - thanks!

I will say that I find the Tab key a lot more natural to use. I can use that by feel instead of hunting for the F6 key.

I'll still say it would be nice if this was configurable. But it's not a big deal.

[admin]

Use F6 = Cycle focus: Address Bar > Tree > List > Catalog.

Well, that's helpful - thanks!

I will say that I find the Tab key a lot more natural to use. I can use that by feel instead of hunting for the F6 key.

I'll still say it would be nice if this was configurable. But it's not a big deal.

Of course it is configurable (find it in CKS under Miscellaneous).

But TAB is not a key that can be assigned to any function.

[Mesh]

Of course it is configurable (find it in CKS under Miscellaneous).

But TAB is not a key that can be assigned to any function.

What I meant was the ability to set XY so that the tab key didn't cycle between the list/tree panes and the Info panel.

[Stefan]

What I meant was the ability to set XY so that the tab key didn't cycle between the list/tree panes and the Info panel.

i use always
Tools > Configuration... > Dual Pane
"Tab between both panes only"

You mean something like
"Tab through everything except Info Pane" ?

IOW Tab through Tree > Catalog > pane1 > pane2 > AB only

[Mesh]

You mean something like
"Tab through everything except Info Pane" ?

IOW Tab through Tree > Catalog > pane1 > pane2 > AB only

Well, Tab through everything except inactive pane and Info Panel. To be honest, at this point, the best way to hande it if it were to be put in the GUI, would be a series of checkboxes. And you would check what you want the tab key to cycle through.

Wouldn't that be great?

[admin]

Harder to do than you'd think.

F6 is good enough IMO, and standard.

[Mesh]

Harder to do than you'd think.

F6 is good enough IMO, and standard.

This isn't a big deal, so not a problem.

But maybe you'll keep it in mind as one of those cool customization options that would be ideally suited to a good case of insomnia?

[TheQwerty]

FWIW: One can achieve much more control over the focus order via scripting.

Using the following one should be able to create shortcut keys to move around XY as they desire. Though as Don stated, they won't be able to change the behavior of the Tab key itself, at least not unless something like AutoHotkey is introduced into the mix.

Code: Select all

get(#CommandID, [ReturnOnTrue = 1], [ReturnOnFalse = 0]);
Here you can retrieve the current state of a couple of toggles that have a command ID, and control what is returned on what state. Currently supported are the following Command IDs:
 #660 = Show Address Bar
 #661 = Show Toolbar
 #662 = Show Tab Bar
 #663 = Show Navigation Panel
 #664 = Show Catalog
 #665 = Show Info Panel
 #668 = Show Tree
 #669 = Show Background Bar
 #670 = Show Status Bar
 #685 = Wide Info Panel
 #800 = Dual Pane
 #801 = Horizontal Panes
For example, this returns "DP" when Dual Pane is enabled, and "SP" when it's not:
 text get("#800", "DP", "SP");
And this returns "1" resp. "0":
 text get("#800");

Code: Select all

get("FocusedControl", [(unused)]);
"A" for AddressBar, "T" for Tree, "C" for Catalog, "L" for List, "X" for other

Code: Select all

focus [control (L|A|T|C|P1|P2|PI)];

control:   The control to focus
 L: [Default] List 
 T: Tree 
 C: Catalog 
 A: Address Bar 
P1: Pane 1 (left/top pane)
P2: Pane 2 (right/bottom pane)
PI:  Inactive Pane

[Mesh]

FWIW: One can achieve much more control over the focus order via scripting.

Using the following one should be able to create shortcut keys to move around XY as they desire. Though as Don stated, they won't be able to change the behavior of the Tab key itself, at least not unless something like AutoHotkey is introduced into the mix.

Hmm... I use AutoHotkey - a lot. So this has promise. Thanks!