https://bugs.winehq.org/show_bug.cgi?id=51230
--- Comment #7 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
I'm not saying that it is a change at all. I never knew that it worked like that, so, to me, it has always been global settings. I'm interested to see how that feature is implemented in the code and how it plays out in actual use.
While the feature makes sense from a technical perspective, now I wonder what realistic scenario would depend on mixing WM managed windows with multiple virtual desktops of various sizes, or mixing DPI/capture mouse settings within the same prefix.
I usually put each application in its own prefix and never met an application that had a dependency on another that had incompatible requirements in the settings.
Do any of you happen to have such dependent applications with incompatible requirements? Otherwise, could you each explain your actual need for that feature?
The problem is that the devs won't put effort into fixing this feature if there isn't a reasonable need for it. The fact that the feature existed at some point and is now broken won't be sufficient. They may even decide that it's too much effort to maintain and make the settings global.
Regards.