I am new to Dopus. I switched to it because I could not stand the way Win Explorer shows the navigation pane for the USB flash drive in the C: drive window that's already up, even though the file pane is showing the contents of a folder on the C: drive. Dopus clearly understood this problem and fixed it.
However, Win Explorer does one thing I like that I don't know how to do in Dopus. When you eject and remove a USB flash drive in Win Explorer, the window closes; is there a way to make this happen in Dopus? I have searched your forum and have not found this addressed.
You could do it using the OnBeforeFolderChange event from a script. If Opus detects the current drive has gone away, it will parent up a level (normally to This PC), and a script could see that happening, check the old path was no longer there, and close the tab*.
(*Or close the window, but I doubt you'd really want that if you had other tabs open.)
That topic is also interesting for me. And I would guess also for others, but most users seems to not complain about it.
Can you think about adding this as setting in a future build? So that the user can define if Opus shall close a tab of a disconnected device or parent up a level (current behavior).
But what is the idea behind parent up a level? I cannot see the sense behind or the use case. After removing the device I do not longer need this tab and all the more I do not need a tab with "this PC" (which is in my case already existing as locked tab)
Because the window has to display some folder and going up a level is what it does in general when the current directory is removed (where, when a folder is removed, you often want to then move to the next directory beside it).
Because windows closing by themselves is often extremely confusing and annoying.
Even with a USB stick, you might insert another stick afterwards to do something with it. Or you might want to go to another folder. If the window closed automatically then you'd have to open a new one in those situations, and may be wondering where your Opus window even is if it closed in the background when you were looking at something else.
I don't mind if some people want something different as an option, but the reasoning behind the current design shouldn't really need explanation.
When I insert another stick a new tab is automatically opened due to autorun setting for media from windows. Cross reference: It is not possible to define there Opus for MTP devices, only explorer.
When I want to go to another folder I use a link/button for that which is opened in a new tab (with middle mouse button). So, no additional clicks necessary between tab is still open or closed.
So for me the current design needed an explanation, because it does not fit to my way of working.
I can imagine the use case behind parenting up one level when the current folder is deleted.
But when I unplug an USB device I want that the tab is closed by 100 %, because I do not need this tab any longer.
For sure not the whole lister should closed automatically, only the tab of the USB device.
Also sure that some poeple like to keep the tab, but then a setting for that (close tab or keep it after a removable device is disconnected) would be nice.
Then you can also simply use the close button from the tab or lister, right?
Or what would be the benefit of an additional button? Ok, if you want to use a safely eject function...
You should always use the safely eject function unless you like corrupting your USB drives.
Using a button which closes the tab and safely ejects the folder gives you everything you want in one click.
(If you want something that also looks for other tabs/windows showing the same folder, or anything below it, I have a script for that which I use myself when unmounting encrypted drives which won't dismount unless all windows pointing at the drive are already closed; sort of the opposite problem.)
That article is kinda nonsense, and they had to add a clarification to the end of it which basically admits that.
You have no way to know for sure if anything has decided to start writing to the drive, or if an operation is still going on which you forgot about or thought had finished. It may usually be safe to yank it out a few seconds after you're done, but it won't always be safe.
Ejecting the drive properly can be done in a single click or hotkey. There's no real reason not to do things the safe way when it means avoiding data corruption.
There is only on issue:
If you have a tab open with "This PC" and you eject a drive with this button the device is shown as folder with a drive letter in the group "unspecified" afterwards and you have to refresh the tab to "remove "this entry.
This issue does not occur if you use the eject function via windows taskbar button. The Opus tab is automatically updated.
When you simply remove the device via unplug it is lot listed anywhere any longer in the tab "This PC". The Opus tab is automatically updated.
@Leo Can you reproduce this issue? Is this a "mistake" in the button command or how can this be fixed?
Thank you.
I think I would have to use "Go REFRESH=ALL", because the tab with "this pc" is not always the active&source tab afterwards.
What I forgot to write: Somehow the tab "this pc" is refreshed automatically - the usb device is moved from the removable device area to unspecific....
But when the refresh command works it would help against the symptom and not the cause. I think it would be better to find a solution for the cause, right?
I think Go REFRESH=ALL only refreshes the active left/right file displays and folder trees in the window it's run from. It won't affect other windows. You'd need to use a script for that.
But it was the same window (same lister). The refresh is also executed, but the entry under unspecific is created after this refresh.
Its more a move. You can see that with the eject command the ubs-device is changing the icon from drive to folder and is then moved to "unspecific".
But the main topic is: Why is this entry created in Opus when ejecting with an Opus command - can this not be avoided?
And I would guess also for others, but most users seems to not complain about it.