XYplorer Beta Club

Tom wrote:I'm saying that if the tab's node is not expanded, and I click the tab, the node does not expand automatically.How do you post a screenshot?

"Expand Destination Node in Tree" is checked.

It would expand to your current node, but won't expand the node that you're in.

Tom wrote:How do you post a screenshot?

Upload it as an attachment and insert it in your reply.

It would expand to your current node, but won't expand the node that you're in.

I'm in Node #1

I click a tab that references Node #2

Node #2 becomes highlighted in the tree, but does not expand.

Tom wrote:I'm in Node #1

I click a tab that references Node #2

Node #2 becomes highlighted in the tree, but does not expand.

So node 2 is a child of node 1, correct? and node 2 is a parent to at least another one child, right? so you were expecting for node 2 to expand and show its child(ren) when you selected its tab? it doesn't work that way, node 2 wouldn't expand.

Node #2 is not a child of node #1.

Both nodes are root directories:

C:\node1\

C:\node2\

Tom wrote:Node #2 is not a child of node #1.

Both nodes are root directories:

C:\node1\

C:\node2\

Ah, but in either case node 2 wouldn't expand if you're going via tabs. it would expand up to node 2, but not node 2 itself.

OK, but isn't that what this, "Expand Destination Node in Tree", is for?

Or is just because tab navigation is different?

Tom wrote:OK, but isn't that what this, "Expand Destination Node in Tree", is for?

Or is just because tab navigation is different?

It would expand to the destination node, but wouldn't expand the node itself. There may be some confusion as to how one interprets it.

OK, thanks zer0!

Instead of opening a new thread I decided to comment on this one:

zer0 wrote:

Tom wrote:OK, but isn't that what this, "Expand Destination Node in Tree", is for?

Or is just because tab navigation is different?

It would expand to the destination node, but wouldn't expand the node itself. There may be some confusion as to how one interprets it.

Confusion of interpretation? -> obviously
multiple possible correct interpretations? -> Not really
The way XY works currently it "shows" the destination node in tree, it does NOT "expand" it. This is a difference. If Don wants to listen to me, I would suggest to either change the wording in the configuration or change the behavior of XY to actually expand the node. I would vote for the latter. Thx for your attention.

EDIT:
This is becoming a plea, now. I just discovered the tweak "AutoOptimizeTreeRadical". I really like this tweak, but for it being active to make any sense (to me ) I would need to destination node to really, actually expand, PLEASE, Don. *beg, beg, please* You could implement it as tweak as well, call it "ExpandDestNodeInTreeRadical" and put it right underneath "AutoOptimizeTreeRadical" .

EDIT2: Since I did write a script meanwhile, which does this, it's not nessecary anymore at the moment. I am also currently testing the work flows to see what is best.