https://bugs.kde.org/show_bug.cgi?id=496861
--- Comment #10 from John Kizer <john.ki...@proton.me> --- I'm no personal expert, but for me reading through the blog explaining cursor size challenges (and the subsequent blogs linked from there) helped it click for me of why KWin simply taking a cursor bitmap and multiplying it by a scaling factor doesn't work in a clear/simple way in a system using the Wayland protocol (tl;dr it's the apps that are handling the cursor, so the approach has to be able to be implemented across app toolkits) There's quite a bit of developer discussion ongoing on this, FWIW: see https://invent.kde.org/plasma/kwin/-/issues/247 https://invent.kde.org/plasma/kwin/-/issues/241 https://invent.kde.org/plasma/kwin/-/issues/187 I think perhaps where we're both getting stuck here, so to speak, is that this bug is originally stating that the cursor size from one configuration, with one scaling factor, should match the cursor size in another configuration with a different scaling factor (in the original report, screenshots 1 and 2 are in a pretty different system scaling factor than 3 and 4), and all were with a cursor theme set that doesn't seem to be set up for scaling to HiDPI screens. Are you observing that, on your Plasma 6.2.4 device, the Breeze cursor theme is not using a larger size when you change the system scaling? If it's not, that feels like a tangible bug that could be actionable and could have clear progress made? Otherwise, my guess is this probably doesn't have a solution outside of the broader "re-thinking about how cursors work in the modern Wayland/FreeDesktop world" work and what KWin might need to do that was mentioned in https://bugs.kde.org/show_bug.cgi?id=451158 -- You are receiving this mail because: You are watching all bug changes.
