Collapse tree node without changing folder

[grindax]

I've always thought it quite strange that in XY when you collapse a node in the tree, XY changes to the folder at the root of that node.

For example, say your S: is expanded in the tree, and in the list you're currently in S:\Download. If you try to collapse the S: node in the tree, XY changes location to S:\

I think that clicking the minus sign on the node should not change where you are currently in the filesystem in the list.

[admin]

If the current node disappears by the collapsing then change of location is necessary.

[grindax]

Why?

That doesn't even happen in Windows/File Explorer.

And remember: In XY I'm using locked maxi tree. It's quite normal for my current location to not always be visible in the tree.

[admin]

I know -- one of the many reasons why WE/FE is so bad and people like me can make a living of making something better.

Locked Tree... well, in that case one might think about it.

[grindax]

Please don't forget about this

I like to have very precise control over the tree, concerning what is expanded and what is not. I often purposefully collapse a node, only to be unceremoniously whisked to a different location.

[admin]

Next beta...

[grindax]

Thanks Don. But in v16.20.0005 when you collapse such a node and then expand it, Tree Path Tracing doesn't update.

EDIT: by the way, with TPT for a collapsed node that you are currently inside, it would be useful (more visible) if the tracing/highlight also included the little '+' / '-' box.

[admin]

Thanks Don. But in v16.20.0005 when you collapse such a node and then expand it, Tree Path Tracing doesn't update.

EDIT: by the way, with TPT for a collapsed node that you are currently inside, it would be useful (more visible) if the tracing/highlight also included the little '+' / '-' box.

1. That (minor) bug is even older than this thread. Might go at it when I find the time...
2. That's done on purpose to show that the tree is out of synch.

[grindax]

1. That (minor) bug is even older than this thread. Might go at it when I find the time...

How can it be? Previously when it was necessary to re-expand the node and go back manually to where you were beforehand, the TPT would update as you did so. Now if I collapse and then expand, TPT doesn't tell me where I am at all.

2. That's done on purpose to show that the tree is out of synch.

But when I am inside a node that is collapsed, surely a highlight on the actual '+' will more clearly indicate: you are inside here. Click this plus to see where. When expanding the node, if you are then at the root of that node, then it makes sense to remove the highlight from the '+'.

[admin]

Tested with 16.20.0000. Try it.

has been like this for years, won#t change it now.

[grindax]

I think we are talking past each other. I suspect this is because you don't use locked tree, and don't fully understand how it's used.

Can you rather revert the recent change then. I can't stand seeing TPT giving me inaccurate and misleading information.

[admin]

No problem, was not too happy with it anyway.

Is there anybody using Locked Tree apart from you?

[grindax]

You should probably just remove locked tree completely. Every bit of development you do to XY breaks it anyway. It's something you've never cared for.

[TheQwerty]

Is there anybody using Locked Tree apart from you?

I did at one point as a way to keep my MiniTree from getting polluted.

I don't think I've bothered configuring the tree to my liking since I started with a fresh config yet.
Instead I've reverted back to my old ways of pretty much entirely ignoring the tree.

[highend]

You should probably just remove locked tree completely

Seriously?

I f**** love my locked tree. Can't live without it. Populated by one of my scripts whenever I switch my work environment....