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.
