3 ms·

One can run an XWayland container transparently. Broadcasting keypresses is forbidden due to security reasons, nobody forbids patching it in as an extension. Se

One can run an XWayland container transparently. Broadcasting keypresses is forbidden due to security reasons, nobody forbids patching it in as an extension. Setting keyboard layout dynamically is as easy as calling swaymsg with the required parameters, if a particular window is required instead, there's a protocol for that in hyprland. It all depends whether a particular window manager does it or not. Finally, I get that accessibility isn't best with Wayland, but it was not ideal with X11 either.

yjftsjthsd-h 2y ago
> One can run an XWayland container transparently. That still only helps for applications (unless you mean just run a whole nested X session, in which case sure but that's not really using wayland). > Broadcasting keypresses is forbidden due to security reasons, nobody forbids patching it in as an extension. Nobody's writing that extension, either; as a user, X does what I want and Wayland doesn't and I'm not in a position to change that. > Setting keyboard layout dynamically is as easy as calling swaymsg with the required parameters, That appears to be just for sway? Or at least (from testing I just did) not all wlroots compositors support it. > if a particular window is required instead, there's a protocol for that in hyprland. It all depends whether a particular window manager does it or not. Exactly. In X, I could use whatever wm I wanted and all the same tools just kept working. In wayland, if I want to do anything interesting I appear to be stuck with sway or maybe hyprland. > Finally, I get that accessibility isn't best with Wayland, but it was not ideal with X11 either. Oh sure; X is a huge pile of hacks and ugly code, but it's a working pile of hacks and ugly code, and quite flexible at that, which is better than Wayland's elegant, well designed brokenness.

3 ms·

One can run an XWayland container transparently. Broadcasting keypresses is forbidden due to security reasons, nobody forbids patching it in as an extension. Se

by ac130kz 2y ago

yjftsjthsd-h 2y ago
> One can run an XWayland container transparently. That still only helps for applications (unless you mean just run a whole nested X session, in which case sure but that's not really using wayland). > Broadcasting keypresses is forbidden due to security reasons, nobody forbids patching it in as an extension. Nobody's writing that extension, either; as a user, X does what I want and Wayland doesn't and I'm not in a position to change that. > Setting keyboard layout dynamically is as easy as calling swaymsg with the required parameters, That appears to be just for sway? Or at least (from testing I just did) not all wlroots compositors support it. > if a particular window is required instead, there's a protocol for that in hyprland. It all depends whether a particular window manager does it or not. Exactly. In X, I could use whatever wm I wanted and all the same tools just kept working. In wayland, if I want to do anything interesting I appear to be stuck with sway or maybe hyprland. > Finally, I get that accessibility isn't best with Wayland, but it was not ideal with X11 either. Oh sure; X is a huge pile of hacks and ugly code, but it's a working pile of hacks and ugly code, and quite flexible at that, which is better than Wayland's elegant, well designed brokenness.