4 ms·
Sway is basically i3 on Wayland. You pretty much keep your config file (with a few modifications), there really isn’t much friction. That’s not a reason to do
by badgersnake 7mo ago
Sway is basically i3 on Wayland. You pretty much keep your config file (with a few modifications), there really isn’t much friction.
That’s not a reason to do it of course, for me the driver was support for multiple monitors with different scaling requirements.
- bandrami 7mo agoSort of. If your software wants to do something like "know where the pointer is" it won't work on sway.
- Gigachad 7mo agoWhy would I want software to know where my pointer is other than when the pointer is over the software's window?
- bandrami 7mo agoWell, 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
- badgersnake 7mo agoSure, but that is pretty niche. My point was it’s pretty low friction for most people and certainly to try it. But obviously be pragmatic, if it doesn’t work for you because you have a particular requirement, or even if it doesn’t offer any improvement over what you have then don’t use it.
- mega-tux 7mo agoI do not know exactly what all that means but does it needs to be desktop wide or just inside a specific app window?
- bandrami 7mo agoNeither 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.
- user142 7mo agoSurely 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.
- bandrami 7mo agoHover is done by the client telling the compositor it would like the cursor to change its shape if it is over a certain area the client is drawing. But the client does not know where the cursor is or where on the screen the client is (or even if the client is visible at all).
- blue_pants 7mo agoI don't think this is true. As per wayland protocol docs (https://wayland-book.com/seat/pointer.html https://wayland-book.com/seat/pointer.html): > Using the wl_seat.get_pointer request, clients may obtain a wl_pointer object. The server will send events to it whenever the user moves their pointer, presses mouse buttons, uses the scroll wheel, etc — whenever the pointer is over one of your surfaces. [...] The server sends this event when the pointer moves over one of our surfaces, and specifies both the surface that was "entered", as well as the surface-local coordinates (from the top-left corner) that the pointer is positioned over. So the program should know the pointer's local coordinates.