mahkoh
mahkoh
> I'm personally worried that the use of CoffeeScript is limiting potential contributors. If I may say so: One obstacle is the size of the repository. At over 400MB it...
Thanks for working on this. I'm not familiar with how other compositors implement touch input, but here are some thoughts regarding how I would imagine it: There are two touch...
Alternatively, each touch id could have its own touch owner. This seems to be how it works on android.
>I've implemented your first suggestion, what do you think? LGTM. Have you checked how other compositors handle multi-touch? >Also, I was trying to hide the cursor with seat.set_app_cursor(None), but then...
>KWin, Sway and Windows all hide the cursor on touch. I find it can be distracting when you're not using it. Maybe it's best to simply not render the cursor...
I'm currently working on adding tablet support. I'll continue the review once that is done.
The tablet PR #190 has significant overlap with this MR: - It adds a mechanism to map input devices to outputs. - It adds a CursorUserGroup type with a deactivate...
Sounds good.
#190 has been merged.
Sorry I'm busy with work at the moment. If you could finish it that would be great.