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.
