https://bugs.freedesktop.org/show_bug.cgi?id=85879
--- Comment #3 from Jonas Ådahl <[email protected]> --- Moving both conversations (this and Bug 87134) here: To use wl_touch we'd have to be able to wl_seat.get_touch in order to get such a device, so you mean that the hand writing client would ask for this feature some how and at that time the touchpad would stop being a touchpad and instead advertise itself as a wl_touch device? Should it only do that to that given client then, and what happens when the touch mode is disabled? It sounds a bit complex to do it that way. Can't we do it similar wl_relative_pointer and with wl_locked_pointer, and always advertise a wl_touchpad when there is a touchpad connected? Meaning when the hand writing client wants to do hand writing, it locks the pointer, gets the wl_touchpad (in the similar way as it'd get wl_relative_pointer). With a wl_touchpad we avoid making regular touch enabled clients to get confused by an extra wl_touch device, and we don't need to ignore the interface specification of the wl_touch device when making the touchpad communicate via it. We'd also avoid any touchpad mode changing and simply rely on the pointer lock to have the client not loose pointer focus. We'd also make it possible for other clients to potentially make use of the touchpad touch points for whatever it may want to use it for, without confusing it with a regular touch device. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
