On Fri Feb 2 06:05:41 2024 +0000, Rémi Bernon wrote:
Well, just to make it clear I only gave my view of how this should be going, it's always possible that someone else feels differently and feels like reviewing this and approve as it is. Alexandre will in the end also decides what he feels would be best. Then my opinion is based on the time I spent moving virtualized display modes *out* of winex11, in the hope that other drivers could build upon it, and as it's been merged I can only assume Alexandre thought the same. Adding back virtualized modes in a different driver simply feels like going backwards that's all.
I mean, if XWayland can't do it, I don't see why Wine's driver has to, considering it's even less integrated and just a "normal" app to the compositor unlike XWayland.
Ultimately, whether we do this in the DWM (wine's "compositor") layer or driver layer still means we have to basically implement compositing ourselves since we can't rely on *the actual compositor* to do it. Fun.
Maybe if we have generic impl upstream we can finally drop the fullscreen hack from Proton and have one less thing to worry about, considering it's been a source of rebase bugs. If we allow VDs to scale, that is. Unless I'm misunderstanding how it's supposed to work…?