Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

State of multi-player Wayland

blinry.org

Post reply on HN
Print view View original

81–90 of 115 posts

Re: State of multi-player Wayland

#81

Post by solarkraft »

gorgoiler wrote: post #52

I wish libinput gave the option for pointer inertia, where the pointer glides to a gradual rather than a hard halt after you stop moving it. I’m limited to a trackpad these days and it’s a really nice feature on my Steamdeck that I’d love to have on my Thinkpad. Come to think of it, Steamdeck is Wayland? How do they implement it?

I highly agree. The synaptics driver on an Asus Eee PC I had had this feature and I really liked it. It just makes sense: It is a thing you touch and flick around. Having it immediately stop is like the list you’re scrolling immediately coming to a hard stop once you release the finger.

Re: State of multi-player Wayland

#82

Post by solarkraft »

rcxdude wrote: post #55
gorgoiler wrote: post #52

I wish libinput gave the option for pointer inertia, where the pointer glides to a gradual rather than a hard halt after you stop moving it. I’m limited to a trackpad these days and it’s a really nice feature on my Steamdeck that I’d love to have on my Thinkpad. Come to think of it, Steamdeck is Wayland? How do they implement it?

>I wish libinput gave the option for pointer inertia, where the pointer glides to a gradual rather than a hard halt after you stop moving it Why? That seems like it would make it a lot harder to move the cursor precisely. (in fact the main implementation of it on linux I know of was a joke in IOCC)

The opposite applies to my use. Humans are generally great at predicting where moving things will land - we evolved for that. It feels great flicking the cursor around and stopping it at the right point. It’s just like scrolling a list on your phone, I for one get great precision doing that. It’s especially great on small touchpads.

Re: State of multi-player Wayland

#83

Post by chrismorgan »

chmod775 wrote: post #24

The more "typical" use for a feature like this is drawing tablets and touch screens. You don't necessarily want a touch/drawing tablet input to move your actual "main" mouse cursor.

That’s unrelated. The typical device will only ever have one seat. From Wayland core, that seat may have a pointer, keyboard and touch; and from tablet-v2 https://wayland.app/protocols/tablet-v2>, you can add tablets and their tools and such, all still in the one seat.

Re: State of multi-player Wayland

#84

Post by chrismorgan »

jauntywundrkind wrote: post #13

On the web, PointerEvents and touch events both support multiple different cursors. https://developer.mozilla.org/en-US/docs/Web/API/Touch_event... https://developer.mozilla.org/en-US/docs/Web/API/PointerEven...

You’ve been led astray by the altered title on this submission. The web does not support the concept described in this article (seats) at all. It supports tracking multiple pointers, but it’s all still single-player, in the terminology of this article: you’re still limited to single focus, single typing, single pointer.

Re: State of multi-player Wayland

#85

Post by MayeulC »

OsrsNeedsf2P wrote: post #49

This is actually something I've always wanted, but people told me it's dumb. I want two cursors and two keyboards, with two "focused window" panes. If Mouse A clicks Pane1, keyboard A presses should go into Pane1. I think this would be so fun for multiplayer games on the same computer for example (think two Minecraft instances running).

It's possible with wayland seats, if the compositor supports it. I've used sway this way. Assign M+K A to seat A and M+K B to seat B. I only wish I could change the focused window decoration depending on the seat (say: one blue seat and one yellow seat).

Re: State of multi-player Wayland

#86

Post by nvme0n1p1 »

arxari wrote: post #57
nvme0n1p1 wrote: post #39

Earlier quoted context omitted.

Here's a post from 2023 where the majority of people say it just works, except for one guy who tweaked his env and broke it. https://www.reddit.com/r/kde/comments/18gfffw/is_zoom_still_... The fact you're griping about implementation details like pipewire makes me think you also tried micromanaging your env and broke something. If you use a fresh install and leave everything default, I'm sure it would work for you li…

> micromanaging your env All the "micromanaging" you need to do to not have screensharing is one of the following; 1. Don't have a started dbus session 2. Don't have portals installed and setup 3. Don't have pipewire installed and setup Meanwhile on X what you need is: 1. Have X So no, it wouldn't work, the reason why it works for those people in the Reddit post is because they use distros and sessions that do all th…

Are you using a distro that is missing some of those core OS services? If so, which distro does this not work out of the box in 2023? (let alone 2026?)

Or, did you remove some core OS services, and now you're complaining when various things started to break?

Re: State of multi-player Wayland

#87

Post by nvme0n1p1 »

Lammy wrote: post #64
nvme0n1p1 wrote: post #39

Earlier quoted context omitted.

Here's a post from 2023 where the majority of people say it just works, except for one guy who tweaked his env and broke it. https://www.reddit.com/r/kde/comments/18gfffw/is_zoom_still_... The fact you're griping about implementation details like pipewire makes me think you also tried micromanaging your env and broke something. If you use a fresh install and leave everything default, I'm sure it would work for you li…

>micromanaging your env PERSONAL Computer

That means you're free to use or break it however you want and nobody will stop you. If you put a nail through your water pipes, you'll also flood your PERSONAL house, but the end result is still nobody's fault but your own.

Re: State of multi-player Wayland

#88

Post by wimiso »

chmod775 wrote: post #24

The more "typical" use for a feature like this is drawing tablets and touch screens. You don't necessarily want a touch/drawing tablet input to move your actual "main" mouse cursor.

Interestingly, for me this usecase isn't typical at all. Ever since I switched from X11 to Wayland (on GNOME) I've had the bug that when I'm drawing with my Wacom tablet, there's two mouse cursors and the tablet doesn't influence the main cursor anymore.

I thought this is a bug in the Wayland implementation: I find it utterly unintuitive to work like this. (I just have no idea with whom to file a bug report, which is why I haven't.)

Are you implying that this is intentional behavior?

Re: State of multi-player Wayland

#89

Post by MayeulC »

kelnos wrote: post #8

I'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...

One very nice use case that I haven't seen anyone else talk about is touchscreens.

I have assigned my touchscreen to be in a separate seat. This allows me to interact with apps without moving my cursor or changing my window focus.

For instance: web browser on the left, with a document. Text editor on the right. I am writing some notes with my keyboard, scrolling the document with my touchscreen. The editor stays focused, no back-and-forth with the mouse. It feels very natural this way, instead of having your cursor jump where you touched the screen and change your M/K focus.

Post reply on HN