State of multi-player Wayland
21–30 of 115 posts
Re: State of multi-player Wayland
#22Re: State of multi-player Wayland
#23I'm building a compositor now, and I've been thinking about multi-seat from the beginning, but I know there are lots of places that assume a single seat, and so this sort of thing won't work for me. It's actually a lot more work than you'd think to support this...
Like: how would one support multiple keyboards? Is there an experimental or logical model for that?
Re: State of multi-player Wayland
#24Re: State of multi-player Wayland
#25Earlier quoted context omitted.
Which desktop are you running where you can't figure out how to take a screenshot? Maybe some of the more tech-savvy folks here at HN can help you figure it out.
Yes. Show me how to make zoom screen sharing work without pipewire and prayer.
Re: State of multi-player Wayland
#26Earlier quoted context omitted.
Which desktop are you running where you can't figure out how to take a screenshot? Maybe some of the more tech-savvy folks here at HN can help you figure it out.
screen sharing is not a static screencap that you would need to email or something
Re: State of multi-player Wayland
#27Earlier quoted context omitted.
That's not what this article is about. You still only have one mouse cursor in that case, but two things (the touchscreen and touchpad) drive it. This is about actually having multiple, independent mouse cursors on the screen at once, with different input devices controlling different cursors.
Sometimes that's true, but sometimes (imo the superior approach) the touchscreen is independent from the cursor. I think touchscreen Chromebooks are like that, for example.
Re: State of multi-player Wayland
#28Re: State of multi-player Wayland
#29Re: State of multi-player Wayland
#30cant read the entire article on ios because the left part is just somehow cut off :(