To start things off, here is a screenshot of the legacy DolphinWx.exe build shipped with the latest build of Dolphin:
![[Image: jBrCqEC.png]](https://i.imgur.com/jBrCqEC.png)
On the flip side, Windows 10 Sets doesn't detect DolphinQt application windows as seen here:
![[Image: sV3AYGX.png]](https://i.imgur.com/sV3AYGX.png)
What I am guessing is that wxWidgets operates so low-level in Win32 that the application window looks completely ordinary to Windows and thus build 17661 (first Insider Preview outside of Skip Ahead to support Sets) puts it in a tabbed environment, and since my copy of Dolphin was configured to run the game in a separate window Sets created a tab for it.
With Qt, there must be something weird about how the application window is created that prevents Windows from using the Sets feature.
With this all considered, where should I lay the blame on Sets not working? I'm guessing probably Dolphin isn't a major contributor, as it probably uses app windows in a pretty standard way. This leaves Qt due to their window handling or Microsoft for not detecting Qt applications as a normal app window.
If anyone wants to try out Windows 10 Sets feature, at this point you will need to enable Windows Insider Preview in the Fast ring, download build 17661, and make sure that you are opted in to the Sets experiment (to test open Explorer and see if it is in a tabbed window).
P.S. In case it matters, I was using the Vulkan backend for both screenshots.
![[Image: jBrCqEC.png]](https://i.imgur.com/jBrCqEC.png)
On the flip side, Windows 10 Sets doesn't detect DolphinQt application windows as seen here:
![[Image: sV3AYGX.png]](https://i.imgur.com/sV3AYGX.png)
What I am guessing is that wxWidgets operates so low-level in Win32 that the application window looks completely ordinary to Windows and thus build 17661 (first Insider Preview outside of Skip Ahead to support Sets) puts it in a tabbed environment, and since my copy of Dolphin was configured to run the game in a separate window Sets created a tab for it.
With Qt, there must be something weird about how the application window is created that prevents Windows from using the Sets feature.
With this all considered, where should I lay the blame on Sets not working? I'm guessing probably Dolphin isn't a major contributor, as it probably uses app windows in a pretty standard way. This leaves Qt due to their window handling or Microsoft for not detecting Qt applications as a normal app window.
If anyone wants to try out Windows 10 Sets feature, at this point you will need to enable Windows Insider Preview in the Fast ring, download build 17661, and make sure that you are opted in to the Sets experiment (to test open Explorer and see if it is in a tabbed window).
P.S. In case it matters, I was using the Vulkan backend for both screenshots.