I regularly leave a lister sitting on a network path like "\server1\test\1010\export\data" while I'm waiting for a file to appear.
If I leave that lister for a while, then hit F5 to refresh, the lister doesn't refresh the directory, and instead returns me to the "Network" root folder.
If I hit backspace, it will then return me to the Desktop, instead of the folder.
If I click the back button, it will however return me to the folder.
It doesn't happen all the time, but it happens most times. It's as if the lister's refresh makes it forget it's location.
Windows itself may view it as 'disconnected' though, if it hasn't been accessed in a while, possibly only changing its mind after the first attempt to access it.
You wouldn't normally need to push F5 to see changes such as new files, unless Opus is configured to disable change notification on network drives. i.e. Assuming Preferences / File Operations / Options / Detect external file changes on network drives is turned on, if you have to push F5 to see new files appear on a path shared by a Windows server then it indicates something is wrong and both things are probably related. Is that the case?
Okay, odd. Is there any way to have it not go back to the root? Perhaps it could retry itself and see if it's there? Or have a button in the middle of the file area saying retry.
I don't have to push F5, it's just a tick from way back when if something isn't showing in a timely manner.
Yes, maybe in some way it is for disc/k drives right now. There's that banner on top of the lister, with a retry option in case any medium is unavailable. There might be room for a "parent" button as well ?! I find it confusing from time to time too, when lister location changes automatically.