https://bugs.winehq.org/show_bug.cgi?id=51230
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #4 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
I see possible issue with per application virtual desktop setting.
Case A (multiple application using virtual desktop):
1) Create a new prefix with an affected Wine version. 2) Launch winecfg. 3) Add a per-application override for winecfg and change it to use a virtual desktop. 4) Add a per-application override for notepad and change it to use a virtual desktop. 5) Apply the change, close winecfg and restart it. 6) Open another terminal and start notepad from same prefix.
Case B (application spawning child application):
1) Create a new prefix with an affected Wine version. 2) Launch winecfg. 3) Add a per-application override for Steam (or a file manager) and change it to use a virtual desktop. 4) Apply the change, close winecfg and start Steam (or a file manager). 5) Launch a game from steam (or any other application, from the file manager).
What do you expect from those scenario? A: One virtual desktop with both notepad and winecfg, or two independent virtual desktops? B: The main application in a virtual desktop and the other application managed by the WM, or both the main app and the child app in the same virtual desktop?
My opinion is that having per application virtual desktop will cause more trouble/confusion for users than a simple all-or-nothing global virtual desktop setting.
For DPI, i think that it doesn't matter if child/concurrent apps have different settings than the main app, so it makes sense to be a per-application setting like window decorations are.
Regards.