3.) Choose any element in the popup and use the right mouse button to spawn the context menu here:
4.) Trigger any function with the left mouse button in the context menu. The function will be executed properly and the context menu will close, the Dopus popup menu from the breadcrumbs field does not close:
I'm not seeing the same thing here, for what it's worth.
While the menu item is still on the screen, if you use File > Exit Directory Opus to full exit the program, does it remain there, or does that instantly clear it?
It's still fully functional. If I click with the right mouse button on an item, a proper context menu appears again and with a left click, the folder is being re-activated, which brings Dopus back to the front, even if it was somehwere in the back.
Some more hints that may help you track down this:
1.) This only happens on pop downs that appear when a breadcrumb arrow is clicked. I couldn't reproduce it with breadcrumb folders. (Probably because the context menu directly opens and there is no need for a pop up.)
2.) I think the problem occurs directly after the right click, because the pop stays open. Not sure if you have the same behaviour, but that's at least what happens on my machine. If the pop up would close before the context menu opens, this probably couldn't happen. (Although I want to mention that from a users view it's very convenient, that the pop up remains open.)
As soon as a function in the context menu was triggered that force dopus to change the current tab or folder, the breadcrumb arrow button is gettig deactivated, but the attached menu is not.
3.) As described, by clicking an arrow with the LMB and then selecting an item and use RMB the popup remains open. I can repeat this multiple times which brings more and more 'zombie' popups on the screen. Here you see an example with two 'zombies':
The 'On impulse' folder is the only one who is still properly attached. The other two on the background are already 'zombies'. All 'zombie' popups are still functional and will close if Dopus is closed.
It could be connected to a shell extension that is adding items to the menu, potentially, but turning on "Hide Windows items..." would normally exclude that, so I am at a loss.
There have been cases where video drivers left parts of menus (often just the shadows/borders) around due to bugs in the drivers, but when that happens they are usually only cosmetic and mouse clicks go right through them, so it doesn't seem like that either.
Thanks for your feedback. Could you please try adding a "Open in new folder tab" function by customizing your context menu? After more testing I realized, that this is the one that causes the most trouble. Most other functions of the context menu work well and doesn't cause this effect.
I've added this entry by customizing the file types, "All folders" entry -> 'go newtab fromsel'
Please let me know if you can reproduce it that way.
Well, if it's just my machine, it's probably best just to ignore this. I'm out of additional ideas for more hints of how to reproduce this thing. I could probably make a video, but not sure if this would help at all.
Plus, it's not a breaker in any way. There is no crash or data loss at all. It's just a bit 'ugly', that's all:)
