D15443: [server] Allow multiple touch interfaces per client and remove fallback code

David Edmundson noreply at phabricator.kde.org
Wed Sep 12 22:14:25 BST 2018


davidedmundson added a comment.


  Oh, I see what you're saying, I misread, sorry. That does indeed make sense.
  
  > Some undocumented fallback code has been removed as well. Platforms not supporting touch are just considered not capable instead.
  
  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?

INLINE COMMENTS

> seat_interface_p.h:147
>              SurfaceInterface *surface = nullptr;
> -            TouchInterface *touch = nullptr;
> +            QVector<TouchInterface*> touchs;
>              QMetaObject::Connection destroyConnection;

touchs -> touches

REPOSITORY
  R127 KWayland

REVISION DETAIL
  https://phabricator.kde.org/D15443

To: romangg, #kwin, #frameworks
Cc: davidedmundson, kde-frameworks-devel, michaelh, ngraham, bruns
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180912/5f77b482/attachment.html>


More information about the Kde-frameworks-devel mailing list