Emulator Issues #11833
Qt: Windows taskbar hover displays closed config window as still open
What's the problem? Describe what went wrong.
While emulation is running, opening and then closing a configuration window (e.g. graphics settings) causes the window to appear as still open when hovering over the Dolphin application in the Windows 10 taskbar with the mouse.
The issue appears to have been introduced with the Qt UI. I do not know if other versions of Windows are affected.
What steps will reproduce the problem?
- Start any game.
- Open a config window.
- Close the config window.
- Hover over the main Dolphin window (not the game window) in the taskbar.
- Observe that the window preview ("mouse peek") shows the closed config window on top of the game list, as if it were still open.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Is the issue present in the latest stable version?
No (only affects Qt UI)
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
Likely when Qt was introduced (Verified broken after 5.0-6901 and before 5.0-7100. If anyone knows the exact first Qt build I can verify)
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel Core i5-8400, GeForce GTX 1070, Windows 10 Home (ver 1903)
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
#2 Updated by Cadex over 1 year ago
This sounds like the same issue: https://bugreports.qt.io/browse/QTBUG-48855. Comments suggest it is a Qt issue with dialogs not being cleaned up properly when allocated on the heap instead of the stack?
Also, the Qt documentation (https://doc.qt.io/qt-5/qdialog.html#exec) appears to suggest creating dialogs with show/open instead of exec to prevent unspecified bugs, but I don't know what other implications that change could have. Just a guess, as I have zero Qt programming experience.