Opened 4 years ago
Last modified 6 weeks ago
#1615 assigned task
touch device support
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 5.0 |
Component: | core | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
Follow up from #1611, see also #173.
Most useful for the HTML5 client (support for precise wheel events added in #1797), which can listen for touch events, suppress the regular clicks and use the new API instead.
We'll probably need to create a uinput touch device, udev rules, etc..
Platform support is going to be "interesting": Understanding touch events as every browser does something slightly different..
Change History (10)
comment:1 Changed 4 years ago by
Description: | modified (diff) |
---|---|
Status: | new → assigned |
comment:3 Changed 3 years ago by
The "Xpra Virtual Touchpad" device is working and enabled as of r18918 (just needed to figure out the magic incantation for uinput)
r18928 allows us to disable the "touchpad" and "pointer" virtual device initialization individually.
We normalize the coordinates using the virtual screen size, maybe this should be using the client's screen size instead? Or some other reliable unit?
New TODO:
- we probably should not be pressing / unpressing with each motion packet (as per above: use separate packets)
comment:4 Changed 3 years ago by
Description: | modified (diff) |
---|
comment:5 Changed 3 years ago by
Milestone: | 2.3 → 3.0 |
---|
This needs more work, so r19051 disables the touchpad emulation by default, for now.
comment:6 Changed 3 years ago by
Description: | modified (diff) |
---|
comment:7 Changed 3 years ago by
See also Input Device Capabilities: This causes problems for developers when supporting both mouse and touch input. It's difficult to know if a mousedown event actually represents new input from a mouse, or is just a compatibility event for a previously-processed touchstart event. - probably doesn't apply to us since we preventDefault()
.
comment:9 Changed 20 months ago by
Milestone: | 3.0 → 5.0 |
---|
comment:10 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1615
Lots of support code and fixes (may backport some) in r18916, see commit message for details.
TODO:
As for browser support, here are some tests: Touch/pointer tests and demos but my tablet isn't seen as a touch device by chrome..