XYplorer Beta Club

Is that a Mini Tree, and if yes, does it allow zombies?

admin wrote: ↑02 Feb 2025 11:26 Confirmed. I fixed all the things you mentioned (next beta).

Thanks!

I don't want to be a party pooper ... but ... my custom configuration still shows the tree bug
After countless back and forth between a fresh installation and my installation, I managed to boil it down to two settings: CustomDnDMenu and NetworkDrivesAssumeAvailable.

The combination of CustomDnDMenu=0 and NetworkDrivesAssumeAvailable=1 will make the tree behave weirdly on network drives again.

Copying a folder in the tree view works, but copying a folder in the list view will not update the tree (and refreshing the tree does nothing).
Deleting a folder in the list view will remove that folder from the tree, but deleting a folder in the tree view will not update the tree (and refreshing the tree does nothing).

Confirmed, again. No problem, fixing bugs IS the party.

Confirmed fixed, thanks! I just realised it's Sunday evening. Amazing that you fix bugs on a weekend

daniel_m wrote: ↑02 Feb 2025 17:40 I just realised it's Sunday evening. Amazing that you fix bugs on a weekend

Not across the pond. It's only 11:45 am EST.

admin wrote: ↑02 Feb 2025 14:46Is that a Mini Tree, and if yes, does it allow zombies?

Just in case you are asking me: No, it is not a mini tree. The following (perhaps relevant) tree options are checked at my place: Auto-optimize tree, Check existence of subfolders in tree (but NOT In network locations as well), AutoOptimizeTreeRadical=1.

@Borut: Yes, that's strange indeed, but ATM I cannot explain it. Windows caches some of the mapped stuff for different times. There is (of course) absolutely no documentation about this, but from observation I'd say some things are cached for 5 seconds, some for 20 seconds, some for 60 seconds. But this is experience in Win 8.1. It may be different in Win 10/11. You mentioned a "2 seconds" delay with your unavailable drives, you're in luck. Here on Win 8.1 it would cost me at least 20 seconds (not checked on Win 11).

Thanks Don! BTW, maybe I am in luck with these few seconds because my network is very small. I remember some occasions from my former business environment, when I would be opening a predefined tabset under the (very seldom) circumstances of one location of it being temporarily off, it would last for ages. (I oft had to disconnect the unavailable logical drive to be able to continue to use the rest in XY.)

Yep. I don't understand why there is no way to tell Windows: check if this drive is available, but give up after 500ms.

admin wrote: ↑28 Jan 2025 20:15

DeeLight wrote: ↑27 Jan 2025 18:31 P.S. You also mentioned:

any custom names (which you don't seem to have) will be replaced by the generic names

Is there a reason for this? As all the names should be available even for offline drives in the registry under

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\##SERVER#Mount#Point

as:

_LabelFromReg

Exactly what I did in v26.80.0206.

In .0401 release, with my settings, for offline mapped drives I still get the generic "Drive X:" labels, did you decide to revert getting the drive names via registry so they would be visible under all settings constellations?

You mean with "Assume that mapped network drives are available" enabled?

Well yes, but I really meant, regardless of the settings, isn't it possible to always have the drive label shown via the above method, without incurring any slowness, so at no times Drive X: (without a label) is shown?

Definitely. But I can no longer reproduce a "Drive X:" occurrence with any setting. Not for mapped drives, I mean.

I am seeing Drive V:, which is a offline drive that isn't manually mounted yet for the session.

Is it shown in this list: Tools | Tools Special | Disconnect Mapped Network Drive... ?