For some perspective on why we, as developers, are frustrated with Wayland:
Have a read of this latest mess: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/247
It’s not the first time such a proposal has been put forward. Something that developers need for their applications to work properly on WL (particularly multi-window applications), and it gets vetoed. Every other OS manages this fine. But apparently we’re in the wrong for not conforming to some warped view of how applications should be, despite our applications working fine on every other platform. Especially the GNOME folks, not everyone wants to use the rubbish that they call GTK.
And don’t give me the “but I don’t use GNOME, I use wlroots/kwin/whatever, it works fine”, that’s good for you, then build from source, or use the flatpak+flatseal. Unfortunately, a good chunk, if not a majority of Linux users end up with GNOME, and they get the crap experience, and we can’t really say “if GNOME, disable WL”, since Qt makes that decision, not us.
Have a look through the PCSX2 source for references to Wayland. Here’s some:
$ grep -ri “wayland” pcsx2-qt/
pcsx2-qt/MainWindow.cpp:// Qt Wayland is broken. Any sort of stacked widget usage fails to update,
pcsx2-qt/MainWindow.cpp: // .. except on Wayland, where everything tends to break if you don’t recreate.
pcsx2-qt/MainWindow.cpp: // make sure we’re visible before trying to add ourselves. Otherwise Wayland breaks.
pcsx2-qt/MainWindow.cpp: // Don’t risk doing this on Wayland, it really doesn’t like window state changes,
pcsx2-qt/MainWindow.cpp: // Wayland’s a pain as usual, we need to recreate the window, which means there’ll be a brief
pcsx2-qt/DisplayWidget.h: // Wayland is broken in lots of ways, so we need to check for it.
pcsx2-qt/DisplayWidget.cpp: // We only need this on Wayland because of client-side decorations…
And you wonder why we just throw our hands in the air and say “bugger this”. As an OS developer, you need to have applications, or it’s kinda pointless. By pushing developers away from your platform, because they’re tired of dealing with complaining users, about things that are 100% out of their control, you have nobody to blame but yourself.
>>> Read full article>>>
Copyright for syndicated content belongs to the linked Source : Hacker News – https://github.com/PCSX2/pcsx2/pull/10179