XYplorer Beta Club

Don,
does "General > Controls and More > Miscellaneous > Allow zombies in the Mini Tree" work as it should?

• When I have it unchecked [ ] (-> not allowing zombies) and I add a non-existent zombie drive letter to the MT with loadtree, it still shows.
• When I have it checked [x] (-> allow zombies) and I add non-existent zombie paths with the C: drive as a base, they still do not show.

1) Hmm, cannot confirm.
2) I don't think anything changed here recently, or do you? You can add Zombie paths only of the drive is a Zombie as well. I'm a bit surprised about this myself, but I won't open this box now.

1) Ok, I realized one more detail about it: The zombie drive letter must have already been showing with the "Allow Zombies" setting ON. When it is switched off thereafter, all those drive letters visible before will: (a) not be removed immediately (b) if they are removed manually, can still be added again. The gif shows it.
2) I don't think anything changed recently. Like at a thread some days ago, I just want confirmation that this is supposed to be so and will not change in the near future - or else be fixed before I get used to a wrong implementation. It is more a bug question that an bug report.

Is there a problem?

unexpected / inconsitent behaviour if one has the "allow zombies" on and then turns it off vs. having it off to begin with

I won't touch this now. The behavior is a bit complex. It's a result of many years of community usage.

ok, no big thing.

Would it be complicated to expose the setting "Allow zombies in the Mini Tree" via/for scripting?
Then I could write my own work around by checking that setting and making sure on my own that the zombie drives are not included in loadtree when that setting is off.

EDIT: Being able to read that setting would be enough.

Actually, it would even be helpful already if a message popped upon unticking the "Allow zombies in the Mini Tree" setting.
It should say that a restart of XY is required for this (un-)setting to take full effect.
That would also solve any potential confusion and frustration on the user's side.

EDIT: That message seems not needed when ticking the setting.

It's fine the way it is. Time has proven it.

Ok, Don, to keep it short, I have understanding for smart arguments, but this isn't one of those. Still, so be it. I must accept ... or must I? We'll see.