auto-optimize tree does not work

[rndbit]

For some reason expanded nodes are not collapsed in tree when auto-optimize is selected.
Would be great if it worked

[admin]

Hi and welcome,

Help: "Auto-optimize sets in when you expand the current tree node." It seems to work.

Regards,
Don

[rndbit]

weird, i can browse around folders as much as i want and manually expand tree nodes as much as i want - no node is ever collapsed. could it be im confusing something?

[admin]

"Auto-optimize sets in when you expand the current tree node."

Have you noted the "current"?

[Borut]

rndbit, maybe the tweak

Code: Select all

AutoOptimizeTreeRadical=1

is for you.

[Regmos]

rndbit, maybe the tweak... is for you.

Brilliant. Thanks a lot

[rndbit]

rndbit, maybe the tweak

Code: Select all

AutoOptimizeTreeRadical=1

is for you.

Many thanks! Thats exactly what i expected!

I totally missed "current" in explanation, and info in tooltip is not quite intuitive. It made me think it should work as AutoOptimizeTreeRadical=1. Thanks for help people

[Borut]

Nice that it helps you (both). I could not live without it - I guess that the need for it comes natural for the heavy tabs users (and I am one of those).

Don, after the next big thing is once out, maybe it would be a good idea to promote this tweak into GUI.

[admin]

I don't use AutoOptimize myself, so I have no personal opinion.

So I ask you AutoOptimizers: what about doing AutoOptimizeTreeRadical=1 by factory default?

[Borut]

There is an older thread on this subject around here.

I seem to recall that this might be unexpected for those working with lesser number of open tabs concurrently (meaning about one tab per pane). I think that these people might find that surprising, irritating and an obstacle to their usual work flow. Besides, it is not how MS WE is operating (at least not on my XP).

Radical activated suits - I can imagine - more those users that liked to use more than one MS WE instance concurrently, in their pre-XYplorer period (and are using XYplorer tabs extensively).

This is at least an extrapolation of my own experience.

So, in short: I wouldn't object, but for me it is irrelevant and I suspect that many would object.

[admin]

Thanks for the reply! I think I will leave things as they are for now. The config dialog is full enough...

[binocular222]

I found it! It's due to an ini entry:

Code: Select all

LockTree=1

Anyone know what this entry does? Where's in the Config dialog?

[TheQwerty]

That's command #488 View | Lock Tree.

Lock Tree

Ever since, the Tree shows basically the same path as the Window Title, the Address Bar and the List: If you change the current path by any of the numerous ways available in XYplorer, the Tree is automatically adjusted to the new location. Even, if you don't really need that service... "Lock Tree" allows you to turn off that automatic syncing of the Tree.

With Lock Tree on, "Refresh Tree" (F4) will re-sync the Tree without changing the mode. Also turning Lock Tree off again, will instantly re-sync the Tree. The setting is remembered between sessions. When you startup with Lock Tree on, the tree will be initialized to a default state with only the top nodes shown.

Here are some possible reasons for turning Lock Tree on once in a while:

(1) It offers a uniform maximum browsing speed that's totally independent of the nesting depth of the target locations. For example, if you quickly need to check size and version of a particular system file, it is totally pointless to expand the tree down to system32, because all you need is a quick glance at that file in the file list. Or, if you have a script that needs to visit some location -- why should the tree get busy here?

(2) It keeps the Tree in a stable state and position while browsing. For example, this can be valuable when collecting stuff from various locations via drag+drop into a couple of target folders -- no need to scroll the tree anymore: the Tree just sits there and waits.

(3) It makes consequent use of XYplorer's many ways of going to a new place: Address Bar, Tabs, Catalog, Favorites, History, Hotlist, Breadcrumb, GoTo, UDCs, Scripts, etc. ... they all work flawlessly without the Tree, and if you just need to go somewhere to work with certain items, you may well be completely uninterested in their position in the file system -- no need for a Tree to show you.

While the Tree is an ingenious interface element one must admit that it almost always shows much more information that you need to have at any given time. So, for the sake of informational economy, you now get a "stand-by" button with it.

[soldier9599]

I have been having a problem with this feature ever since I started using XYplorer. It does not work at all. I have auto-optimize tree enabled, however every path I ever open will remain open in the tree until I close it manually. This results in a horribly cluttered tree in which I have dozens of paths being displayed even though I only have one tab open in each pane. I tried using the "AutoOptimizeTreeRadical=1" flag and it worked but it is not the behavior I am looking for. I started using the mini-tree to combat this problem, but even that gets cluttered after a while.

[autocart]

I have been having a problem with this feature ever since I started using XYplorer. It does not work at all. I have auto-optimize tree enabled, however every path I ever open will remain open in the tree until I close it manually. This results in a horribly cluttered tree in which I have dozens of paths being displayed even though I only have one tab open in each pane. I tried using the "AutoOptimizeTreeRadical=1" flag and it worked but it is not the behavior I am looking for. I started using the mini-tree to combat this problem, but even that gets cluttered after a while.

Hi soldier9599,
not sure if it helps you but I am working on an ahk-script for XYplorer for this or a similar purpose: http://www.xyplorer.com/xyfc/viewtopic.php?f=7&t=12234
it's still under (slow) development but already usable. maybe it can help you. plus any feedback is welcome too.
Regards, Stephan