mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Server stats:

5.4K
active users

There's something very wrong with the way mouse cursors are handled on Linux. If you have a low DPI display, the Adwaita cursor is ugly and pixelated. The same cursor image in the KDE theme preview is smooth and nice.

This is a common problem in GNOME, KDE, and wlroots. Probably because they all use the same library to load the cursor and... nobody noticed?

Oh, and of course I have to take photos of the screen, because screenshots do not include the actual cursor image that is displayed.

@wolfpld maybe broken subpixel rendering? I don't know if Linux does it for fonts/cursors

@BartWronski It supposedly just uploads an RGBA image to be used as a cursor. The common complaint about Wayland is that it doesn't support hardware cursors. But the code I've seen says otherwise.

It works fine at high DPI, but there are subtle differences in behavior between KDE and GNOME. KDE uses the appropriately scaled cursor image depending on the DPI of the screen. GNOME seems to just load the high resolution cursor and scale it down on a low resolution screen, where it looks fine.

Bartosz Taudul

@BartWronski The particularly trollish thing about Wayland is that it requires every single program to provide the cursor image. The protocol has no way of specifying what theme or size the program should load. So it's especially fun when several hacky solutions are involved.

Even if you are able to fix this on the compositor side, the programs will still be using the broken library and will still provide the ugly cursors.

@BartWronski Good news though! After 15 years of Wayland being a thing, the committee has finally fixed this one little problem!

gitlab.freedesktop.org/wayland

It just requires that all programs adapt to the new solution! They seriously think that updating all existing client applications is the way to go.

I believe I have an alternative solution, which is a big hack, but it will make all these problems go away.

GitLabcursor-shape-v1: new protocol (!194) · Merge requests · wayland / wayland-protocols · GitLabThis is based on the Chromium protocol 1. Closes: