Well, in my case, because the VCF on my synth sets its cutoff frequency based on the pointer's Y position and its resonance based on the pointer's X position
I do not know exactly what all that means but does it needs to be desktop wide or just inside a specific app window?
Neither way works in Wayland. A program can know where it was clicked but not where the pointer was immediately before that. For that matter Wayland doesn't have a concept of "the" pointer; there may be multiple pointers.
First they said we couldn’t have screenshots because they were insecure. Then they added them back in. Next, it was accessibility APIs and I guess copy paste is still flaky. Now, it’s window managers. What’s next, Remote Desktop? The whole reason given for wayland’s replacement of x11 was that those things are all fundamentally bad ideas. It’s been 15 years. Linux desktops are more fragmented than ever, and they’re s…
> like HDR And variable refresh rate, better fractional scaling (and per-monitor scaling), atomic updates, native touch & gestures. And the isolation/sandboxing is important. The problem is Wayland didn't have portals in the beginning (hence the screenshot issue). Wayland isn't the problem. The pace at which distros (and GNOME, lets be real who is behind the push here) started stripping out X11 was too fast, and too…
> better fractional scaling
X11 was resolution-agnostic from the start, but the ‘desktop Linux’ crowd were so focused on imitating Windows that they ignored Unix lessons and made fixed-resolution toolkits like Windows'.
I don't get the frustration with wayland (the protocol) in the comments. This project shows that having a separate window manager was always possible. First we got wlroots as a library that did most of the heavy lifting, and now we got river as an even higher level abstraction. Sure I agree that wayland (the project) could have provided these abstractions much earlier. But anyone else could have done it, too. We get…
> I don't get the frustration with wayland (the protocol) in the comments. They took a firm principled stance against screenshots to start with, which set them up for the COVID WFH wave. Then we've got this questionable design that seems hard to make accessible since accessibility is a security risk and we're heading right into Agentic AI which will be interesting. I've been avoiding the Wayland ecosystem for as long…
> Then we've got this questionable design that seems hard to make accessible
I'm not a fan of ADA ambulance chasers on principle, but I wouldn't shed a tear see them be able to go after the bigcos that made this mess (e.g. IBM).
> I don't get the frustration with wayland (the protocol) in the comments. They took a firm principled stance against screenshots to start with, which set them up for the COVID WFH wave. Then we've got this questionable design that seems hard to make accessible since accessibility is a security risk and we're heading right into Agentic AI which will be interesting. I've been avoiding the Wayland ecosystem for as long…
> Then we've got this questionable design that seems hard to make accessible I'm not a fan of ADA ambulance chasers on principle, but I wouldn't shed a tear see them be able to go after the bigcos that made this mess (e.g. IBM).
ADA seems like bullshit until something happens that costs you sight, hearing, manual dexterity, etc. Then it is significantly less funny overall, I assure you.
Yeah, it took me a while to discover that it was removed from KWin. (I eventually ended up reading the sources). It didn't help that KWin also does 3D effects, so all of my Web searches for "shading" were returning results for "shader" :-(
Oh, gone from KWin as well? Yet another reason to stick to XFCE I guess.
It is gone from kwin because it is really hard to do in Wayland apparently.
The setting is still there (or was there until really recently).
I do not know exactly what all that means but does it needs to be desktop wide or just inside a specific app window?
Neither way works in Wayland. A program can know where it was clicked but not where the pointer was immediately before that. For that matter Wayland doesn't have a concept of "the" pointer; there may be multiple pointers.
Surely programs can know where the pointer is as long as it is over a window that belongs to the program. Otherwise hover wouldn't work.
Well, it only took 15 years to someone to fix one of many Wayland design flaws and start to make it feel usable. Now it will take another 15 years for people to settle down in a set of common protocols instead of writing their own extension protocols and others 15 years for window managers to mature at the same level of the X11 window managers. Then, people who think they know better than everyone else will throw Way…
It's a shame because Wayland has made complicated what most contributed to the growth of Linux in the last few years: gaming. I still can't run most of my library on Wayland without the added latency of XWayland. It's great if it's one step back to take a big leap, but this feels like two steps back one step forward without much of a plan for parity. As the sibling comment said, with WSL becoming better and better, i…
Except if you need WSLg, because then you can add RDP issue to all your Wayland issues, and, not infrequently, also xwayland issues! You can have all the fun!