Using the {dlab} code in the status bar is giving me unexpected results for mapped network drives.
In the tree and on drive buttons mapped network drives are labelled SHARE (\SERVER) the same as in Windows File Explorer. These labels can be renamed by the user locally.
But the {dlab} code returns something like the label of the share's parent volume on the server? Meaning multiple mapped drives residing on the same server volume have the same label, and this can't be changed unless you have access to the server.
I am wondering what is the thinking behind this behaviour and can it be changed?
It displays the label of the drive the current folder is on, so what it's doing is certainly correct... but maybe a little too correct.
Drive labels on network folders are usually hidden from view and I can see the argument for displaying the UNC \server\share path instead of the label, even if what it does now is technically correct.
I haven't looked at the code yet to see if there would be any complications, but I'll add this to our ideas list for a future version.
