romangg added a comment.
In D15443#324889 <https://phabricator.kde.org/D15443#324889>, @davidedmundson wrote: > I don't understand removing this. If I have an app that doesn't understand touch doesn't it make sense to synthesise a pointer? I didn't read the code correctly. Thought it is meant for compositors not supporting touch, but indeed it's meant for clients not supporting it. Hmm, I imagine since most Wayland clients use some sort of GUI library there are not many Wayland native clients not supporting touch. And Xwayland translates touch events. So maybe it would still make sense to remove the code. But I'll add it back for now. This way the change also becomes more narrow. REPOSITORY R127 KWayland REVISION DETAIL https://phabricator.kde.org/D15443 To: romangg, #kwin, #frameworks Cc: davidedmundson, kde-frameworks-devel, michaelh, ngraham, bruns