4 ms·
I'm left wondering -- isn't this a toolkit/library issue? I am a bit afraid of seeing gestures handled differently in multiple programs, like inertial scrollin
by MayeulC 5y ago
I'm left wondering -- isn't this a toolkit/library issue?
I am a bit afraid of seeing gestures handled differently in multiple programs, like inertial scrolling, or pinch-to-zoom speed. At least gestures are always detected by libinput AFAIK, so there's that.
But instead of implementing this in every application, wouldn't it be nicer to implement the common part in a library and link that library to all app that require/want touch handling? This would provide homogeneous behavior, and would allow sharing configuration files.
- p12tic 5y agoMost applications will use either Gtk or Qt widget libraries, so a lot of similarity of how applications behave already exists. I don't think it's possible to make Gtk and Qt themselves behave identically at this point. For example Qt is a commercial project and an effort that would break backwards compatibility is not worth it. Gtk on the other hand has strong opinions about how things should work, so it would be hard to change that too.
- jhasse 5y agoThere was a Gtk backend for Qt which would have solved this: https://github.com/CrimsonAS/gtkplatform https://github.com/CrimsonAS/gtkplatform
- MayeulC 5y ago> Qt is a commercial project and an effort that would break backwards compatibility Not sure how that would break backwards compatibility. Moreover, Qt has always tried to plug into native libraries and integrate as well as possible with the host platform. You have a fair point about GTK. Any implementation should at least cater exactly to their need or they will make their own.