AHK-script for MiniTree - automatic expanding and collapsing

[autocart]

new version 0.008:
http://www.xyplorer.com/xyfc/viewtopic. ... 27#p109427
multi instances: for now I only implemented that the script takes effect only in the first XY-instance it finds (regardless of the exe-path). when that instance closes then the script also terminates.
more details in first post

[SkyFrontier]

Scheduled to test it this weekend, Stephan. Very, very, very busy lately.
I'm planning to kill two rabbits with a single rock - checking the AV vs AHK issue, too.
Will report soon!
Thanks much.

[SkyFrontier]

Hello, Stephan!

Finally I got the time to test this update. Sorry for such late reply.
It's making an awesome job, here.
It's less distractive to work with MIniTree, now.

The exe restriction now seems to work as expected, thanks much!

Is is possible to achieve the per-tab MiniTree for visited folders?

All the best!

SF.

[autocart]

thx, SF, for the encouraging words,
unfortunately again I do not know what you mean by per tab MT for visited folders.
Do you mean the "history"-functionality directly in the tree, as I described it some time before?

One thing, though, i want to point out - again - is that this script does NOT (at the moment) provide "per tab" MT, even if it may feel like it most of the time - maybe "per folder" but not even that 100%.

[SkyFrontier]

History: all locations visited on/from that tab.
Original, start point: pane 1, Tab1 - c:\temp.

If I go to to d:\video, currently the AHK displays only that, forgetting c:\temp.

If I go to pane 1, Tab2, there will be another location there, say d:\blah.

When back to pane 1, Tab1, I'd like to have c:\temp + d:\video on MiniTree (d:\blah must not be there as it belongs to Tab2); currently, I only get the last visited location (d:\video, in case).

Back again to Tab2, I'll have just d:\blah MiniTree'ed, only.

[autocart]

For that I would have to actually make it tab based, since at the moment it is not.
And this is would mean quite a bit of work.

Honestly I do not feel up to it at the moment.
If one or two other users would find a real tab based mini-tree more beneficial as well, then I might have more motivation again to try it, but as of now, I don't think I will do it (anytime soon).

Regards, Stephan

[autocart]

I just found out:
This script is not compatible with mouse down blowup. MDB will simply not work.
I can not think of any way how to work around it. Just wanted to let everybody know.

[autocart]

new version 0.009:
http://www.xyplorer.com/xyfc/viewtopic. ... 27#p109427
Since yesterday I found 2 things:
1) more sleep
2) a work around for the mouse down blowup problem. it's so simple that it must be related to point 1
anyway, mdbu works again with this script.
(I also updated the simple version: XYplorer_MiniTreeExpandDestination)

[autocart]

new version 0.010:
http://www.xyplorer.com/xyfc/viewtopic. ... 27#p109427
improved the handling of differentiating between navigating "upwards" in path and collapsing a super-node of the current path (which also results in an "upward"-navigation but in which case the node obviously is not desired to be reopened immediately)

[autocart]

new simple version 0.003 (XYplorer_MiniTreeExpandDestination):
http://www.xyplorer.com/xyfc/viewtopic. ... 27#p109427
Now, also on the simple version I improved the handling of differentiating btw. navigating "upwards" in path and collapsing a super-node of the current path (which also results in an "upward"-navigation but in which case the node obviously is not desired to be reopened immediately).

[autocart]

new version 0.011:
added ignorance for paper folders (before paper folder caused a problem, since they are not visible in the tree)
http://www.xyplorer.com/xyfc/viewtopic. ... 27#p109427

[autocart]

new version 0.012:
http://www.xyplorer.com/xyfc/viewtopic. ... 27#p109427
1) new ini-file

2) added a switch in the ini-file to toggle the termination behaviour of the script:
In general: The script only takes effect in the first XY-instance it finds. If this one is closed then the script terminates also.
Now: If findNextXYinstanceIfAssociatedXYCloses is turned on then it does not terminate but takes effect in the next XY-instance it finds.
If there is none then it waits in the background for XY to be started and takes effect then.
For a change of this value to take effect either a path change in XY or a restart of the script is required!
0 or blank means off. Everything else means on.

Default is 1 (on).
SkyFrontier, you might probably want to set it to 0 (off), I assume.

3) changed the meaning of the value of showDirectSubfolders slightly (in order to be more logical)
now: 0 or blank means no. Everything else means yes.

4) BIG NEW CHANGE:
introduced path groups (in the ini-file):
You can now define groups of paths in the ini-file that should stay expanded (not get collapsed by this script), incl. any expanded sub-paths, when browsing (sub-)paths of that group.
As soon as you are browsing a path that is not in (or a sub of) the group then the group's paths are treated in the usual way again.

EXAMPLE: You have 2 or more paths that do NOT have a sibling or parent-child relation (e.g. "C:\ab\1" and "C:\xy\2").
Now, with this script, all these paths besides the current one would likely get collapsed as soon as you browse any one of them.
(Browsing "C:\ab\1" would likely collapse "C:\xy\2" and vice versa.)
If you put them in a group then they and any sub-paths stay expanded (if they already are) while you browse any path in that group (or their sub-paths).
(Browsing "C:\xy\2" or "C:\xy\2\sub" would leave "C:\ab\1" and its subs expanded if it already is and vice versa.)
As soon as you browse a path outside of the group then all the group's paths are treated in the usual way (likely collapsed again).

The key "pathGroups" (in the ini-file) contains all the group identifiers. They may not consist of the char "|" and must be unique in the whole ini-file, obviously.
Other than that I assume any "normal" chars should work. The group identifiers are seperated by "|".
For each group identifier a seperat key must be added below (with the same name as the identifier) containing the paths for this group.
The paths are seperated by "|".
Note: Paths in a group should NOT have a parent-sub-path relationship. E.g. if "C:\ab\1" is in the group then the group should not contain any subs theirof.

I am not 100% sure if pathGroups are already bug-free (if that could ever be possible). So please test it (at your own risk, as always) with care and if you find any buggy behavious, please let me know. Thanks to all of you.

[autocart]

new version 0.013:
http://www.xyplorer.com/xyfc/viewtopic. ... 27#p109427
added ignorance for search results (sometimes it could have come to interferences)
added a version check; XY must be at least "14.50.0107" (needed for ignoring search results)