No icons visible in tree

[Daniel0312]

Hi
On a Vmware virtual machine I have a problem when upgrading from 26.80.0100 to 26.80.0200.
The icons in the tree are not visible anymore (funny how we are used to them...)

20250123_091425.png

I seems the problem starts with 26.80.0101.

No problem on a "regular" PC

[admin]

Run this through the address bar: sysicons;

[Daniel0312]

All icons are fine and show when hovering the absent ones.

20250123_095903.png

Another problem I noticed, again between 0100 and 0101, again on a virtual machine.

20250123_095549.png

[admin]

Does is make a difference if you untick this: Configuration | General | Safety Belts, Network | Network | Assume that mapped network drives are available

[Daniel0312]

I was just going to add this : unchecking

Code: Select all

Configuration | General | Safety Belts, Network | Network | Assume that mapped network drives are available

solves the problem !

[admin]

Solves both problems?

[Daniel0312]

YES !

[admin]

Should be fixed in next beta.

[Daniel0312]

Ok, report

The icons are back where they belong
So I guess the initial reason I posted is solved.

However, here what I noticed :
with "Assume that mapped network drives are available" unticked
on XY start all is fine

1-20250123_152020.png

pressing F4

2-20250123_152126.png

pressing Ctrl+Shift+F4 shows the first snapshot

with "Assume that mapped network drives are available" ticked
on XY start

3-20250123_152503.png

pressing F4

4-20250123_152632.png

pressing Ctrl+Shift+F4 shows back the previous snapshot

[admin]

The \\DANIEL-PC stuff should be there. The rest should not. But I can't really reproduce it here. Anyway, I'll try something in the next beta.

[Daniel0312]

26.801.0203 » everything seems ok

Code: Select all

The \\DANIEL-PC stuff should be there

You mean that when "Assume that mapped network drives are available" is ticked, the UNC name should be displayed ?

[admin]

Yes, as in File Explorer.

[Daniel0312]

I renamed it to remove the server name

20250123_174534.png

Windows Explorer capture...

I was mainly pointing this out in case it was the visible part of some deeper problem.
I can live with the way it is now and, come to think of it, save a few nanoseconds.

[admin]

Yep, you got it. It's part of the deal that you'll lose your custom name if "Configuration | General | Safety Belts, Network | Network | Assume mapped network drives are available" is checked. I wasn't aware of this consequence before (thanks!), but it's unavoidable.

The cause of all this fuss is that Windows seems to have no way of quickly checking the availability of network drives. It insists on taking 20 seconds to do this. This has been driving me mad for years.

[Raf]

Some programs like Mountain duck (Cyberduck CLI) have a separate independent interface for fast work with network drives that they connect when working with cloud services.

It was a big surprise to me that XYplorer works with network drives very quickly and files appear on Google drive with minimal delay... Explorer built different.