#5BCEFA at (22,8)

#5BCEFA at (20,8)

#FFFFFF at (19,15)

I think you missed mine from yesterday, #F5A9B8 at (19,11)

#F5A9B8 at (19,11)

Cyan at that spot? D:

#5BCEFA at (19,9)

#5BCEFA at (19,7)

It’s day 152 all over again 😵‍💫

#FFFFFF at (18,18)

#FFFFFF at (18,16)

CAN WE HIT 1 MILLION TOMATOES???

#F5A9B8 at (18,12)

#5BCEFA at (18,10)

The fallout from this truth nuke finally landed on me after 7 years!

#5BCEFA at (18,8)

#FFFFFF at (17,17)

I think you missed my pixel from yesterday >_<

http://tom7.org/harder/ (has links to the paper and also to the video)

#F5A9B8 at (17,13)

I dug even deeper and installed Weston to see how seats are configured. Turns out this is done by attaching a udev property to the device called WL_SEAT, which libinput uses to make logical seats, which Weston uses for seat management. See: https://wayland.freedesktop.org/libinput/doc/latest/device-configuration-via-udev.html

Note: your udev filter (the ones with ==) matters!! I thought I could re-use the filter generated from loginctl (i.e. ENV{ID_FOR_SEAT}=="..."). This led to several confusing hours where I could set ENV{ID_SEAT} but not ENV{WL_SEAT}. Follow the docs above and you’ll be fine.

Once I got it working in Weston, I tried it on Plasma, and got my answer: no, Plasma Wayland does not currently support multi-cursor.

It looks like the best solution in our case will be to use the Plasma X11 session. I was able to reinstall the x11 session on my pc and tested multi-cursor there, and it seemed to work as expected.

If the X11 session is too unstable, I guess Weston is there as a backup.

#F5A9B8 at (17,11)

#5BCEFA at (17,9)

#F5A9B8 at (16,14)