5 ms·
I was saying that the inertia scrolling should be implemented in the toolkit level, instead of emitting bogus mouse events for ‘inertia’. Which means that GTKSc
by pcr910303 7y ago
I was saying that the inertia scrolling should be implemented in the toolkit level, instead of emitting bogus mouse events for ‘inertia’. Which means that GTKScrolledWindow (or whatever is NSScrollView’s eqivalent is) should implement it’s functionality, not in libinput.
I considered it as fragmented b.c. the reason it was implemented this way (instead of implementing in the toolkit) was mostly because one can’t coordinate big changes in at least three big libraries (vendor drivers + libinput + Qt/GTK) to achieve something relatively small (inertia scrolling) when Apple can just decide to ‘fix everything related’ if one decides to adopt a new feature.
Not that fragmentation is a necessarily bad thing, but it’s not great in these cases.
- diffeomorphism 7y agoSo in qt or gtk on macos it is implemented at the toolkit level?
- pcr910303 7y agoI’m not quite understanding the question (probably due to my lack of English skills) but if you’re asking if it’s implemented in the macOS equivalent of Qt/GTK(which probably means AppKit), yes AFAIK it’s true.
- tssva 7y agoSome apps on macOS are not written using AppKit but are cross platform apps which use either the QT or GTK toolkits even on macOS. The question is asking how inertia scrolling is handled on macOS for applications which use these toolkits instead of AppKit.
- yc-kraln 7y agoBadly, which is why cross-platform applications stand out like a sore thumb on MacOS
- pcr910303 7y agoWell, I'm not sure (as I always erase GTK/Qt apps as soon as they become useless), but what I remember is that they do handle window changes (b.c. event propagation is handled in AppKit), but the inertia doesn't feel right. I think there are apps that do implement inertia, and there are also apps that don't implement inertia. Both feels wrong.
- diffeomorphism 7y ago> Both feels wrong. That was my question. So macOS has one blessed toolkit working nicely and everything else feeling "wrong". So this has nothing at all to do with being "fragmented" but simply says "apple has one good toolkit and lots of bad ones".
- pcr910303 7y agoWell, I won’t call GTK/Qt as a macOS toolkit... but in Linux world, both are used similarly. I think that’s the difference.
- WesolyKubeczek 7y agoIt’s not handled there at all. Qt likely uses NSScrolledView underneath, but Java/Swing and GTK feel foreign even if they look the same (which they don’t, with different levels of unsubtlety).