1.8.2: copy/move hangs with assigned, but disconnected network drive(s)

[Marsu42]

XnView: MP 1.8.2 - 64 bit
OS: Windows 64bit

If a network drive is assigned with a drive name like n: XnViewMP takes a long time before each copy/move operation ON OTHER DRIVES if the source of the network drive (or the network) is disconnected. Again, the source/move op doesn't have to do ANYTHING with the assigned network (drive).

Effect: Program hangs for some time before performing copy/move

To reproduce:
1. assign a network drive with something like use n: \\192.168.1.10\c
2. disconnect the network or the source of the network drive = letter keeps being assigned
3. do a copy/move operation (alt-c/alt-m) like c:\folder1\image.jpg to c:\folder2
Actual behaviour (bug): XnViewMP hangs for some time before performing copy/move

Expected behaviour: XnView performs copy/move immediately like w/o assigned (but connected) network drive or connected network drive

You can verify that the assigned network drive is the problem by reconnecting the drive/network or unassigning with 'net use /d n:' and doing the same copy/move op again.

[xnview]

I think that the delay is when creating the folders tree, this can be slow if a network drive doesn't respond

[Marsu42]

I think that the delay is when creating the folders tree, this can be slow if a network drive doesn't respond

Well, it's very slow to the point of being nearly unusable unless the disconnected network drives are unmounted. I've never seen such a behavior in any other app.

Maybe it's possible to
- speed up creating the folders tree with a shorter timeout if some network drive doesn't respond or
- not to create a folder tree for network drives if the "Network" node is collapsed or
- to ignore network drives with a hidden setting viewtopic.php?t=48925