PCSX2 Emulator Disables Wayland Support By Default

[hf_139]

Yeah, and if the GNOME platform wants to implement an incomplete subset of the Linux+Wayland platform that's missing the extension for server-side window decorations, that's their problem and I will direct users of my creations to them for support.

Same here.
I don't have time to care about their special snowflake implementations. I did in the past, but random GNOME updates would break random things again. I am not going to follow them around.

If things don't work on GNOME, but work everwhere else, the users should go to them and complain to them. Or at the best case, they should just stop using GNOME. The Red Hat devs at GNOME of course blame the application developers... but not a single other DE needs that much special attention, others just work.

[fitzie]

Same here.
I don't have time to care about their special snowflake implementations. I did in the past, but random GNOME updates would break random things again. I am not going to follow them around.

If things don't work on GNOME, but work everwhere else, the users should go to them and complain to them. Or at the best case, they should just stop using GNOME. The Red Hat devs at GNOME of course blame the application developers... but not a single other DE needs that much special attention, others just work.

the issue is that gnome currently has the most polish so there's a ton of users there. I'm hoping cosmic delivers. they seem to not have bitten off too much, where projects like kde and xfce seem to be way more code then their developers can maintain.

[hf_139]

the issue is that gnome currently has the most polish so there's a ton of users there. I'm hoping cosmic delivers. they seem to not have bitten off too much, where projects like kde and xfce seem to be way more code then their developers can maintain.

GNOME is so "polished" that they had a massive security vulnerability just recently and if you look into the Fedora 39 Discourse, you see a flood of reports of GNOME 45 permanently crashing.

In a few months, it will be a good moment to kill GNOME off and to suggest people to switch. Gnomes Wayland implementation is years behind kwin or wlroots. Plasma 6 will be the first DE with full fractional scaling (both Compositor and Applications). And both Budgie and Cosmic look promising for the people who simply don't want KDE. Hyprland is also waiting to collect a specific subset of users.

[guglovich]

The island of adequacy in the world of Open Source

[mSparks]

waylandmeme.jpg

you can argue all day long that it's not a wayland issue but a compositor issue ( or a gnome issue or a systemd issue or a dbus issue), but that's missing the forest for the trees. it's a desktop issue, and developers should be able to write apps that just work on the desktop.

A lot of them are compositor issues afaict.

The key problem is, gnome and KDE arent compositors, so its their fault for not being a compositor.

This is also why KDE wayland is down to one showstopper wayland bug, even though KDE wayland is useless for desktop, and KDE X11 is a great DE.

But lets not let nvidia off the hook so easily here. If they hadnt been so focused making billions of dollars selling AI solutions on Linux X11 and had given IBM all their IP for free then wayland stuff would be in a much better position than it is now.

[patrick1946]

Glad we agree. I write applications for Linux+Wayland, not GNOME. Until they come into compliance with the Linux+Wayland standard that KDE, wlroots, etc. implement and honor requests via the decoration protocol, I consider GNOME to be an unsupported out-of-spec platform I'm not trying to target which just happens to implement enough of the API to run my creations badly.

Server side decoration have drawbacks which are only fixableby an complicated API and you can add use simply a shared library to paint client side decoration consistently.

The current problem is not technical but social.

[mSparks]

Server side decoration have drawbacks which are only fixableby an complicated API and you can add use simply a shared library to paint client side decoration consistently.

The current problem is not technical but social.

A lot of confusion arises here because in display server land client and server roles are reversed to what you would expect.

The server is in front of the user, and the client is the application that wants to give the user stuff they can see and interact with.

There is no "client side decoration", the client is a software application that can only see and send zeros and ones to and from different sources.

[patrick1946]

A lot of confusion arises here because in display server land client and server roles are reversed to what you would expect.

The server is in front of the user, and the client is the application that wants to give the user stuff they can see and interact with.

There is no "client side decoration", the client is a software application that can only see and send zeros and ones to and from different sources.

Do you program GUI applications? I do. Docorations are simply areas where you paint to and handle events. There is nothing special about them.

[mSparks]

Do you program GUI applications? I do. Docorations are simply areas where you paint to and handle events. There is nothing special about them.

you're writing gui applications using DRM?

[ssokolow]

Server side decoration have drawbacks which are only fixableby an complicated API and you can add use simply a shared library to paint client side decoration consistently.

The current problem is not technical but social.

The source doesn't matter. The point is, on Windows (the PCSX2 developer's OS of choice), the CSD library is guaranteed to be there. On Linux, if you're using anything but GNOME, you have to explicitly choose to use libdecor and it won't necessarily be installed by default on users' machines.

As for drawbacks, CSDs have drawbacks which are only fixable by complicating your compositor with support for letting the user manually specify a crop rectangle to hide the flipping Headerbars in a hamburger menu and restore consistency and access to a compositor/WM control interface that obeys their configuration settings... as the developer of Arcan made a proof of concept of.

Though it fizzled out, KDE proposed the sane idea which preserves user choice, as usual, while GNOME just tried to gaslight everyone into believing that the limitations imposed by bad architectural decisions in Mutter were actually universal truths.