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.