Nokia’s Qt ports are best classified as work in progress – Symbian-based Qt apps can’t be released, and don’t even get me started on Maemo-based ones.
The fast “patching sequence” should thus be unsurprising. The latest patch for Maemo brings us up to 4.6.2+; and mainly bothers with kinetic scrolling:
Up until now, kinetic scrolling was limited to 20 fps. This is a good default, since 20 fps look smooth, don’t drain too much battery and leave some CPU for background processes/threads (isn’t it nice to have multi-tasking?). However, for demo purposes, you might want to have 60 fps for that really, really smooth look, so we introduced the QAbstractKineticScroller::scrollsPerSecond property. Unfortunately, our camera cannot grab 60 fps, so no youtube video today
The second interesting feature is QAbstractKineticScroller::axisLockThreshold. Imagine that a user scrolls downwards in a QScrollArea. Now, unless he’s an android, he won’t manage to scroll down in a perfect line, usually it’s something like 100 pixels downwards and 5 pixels to the left. The axisLockThreshold property allows to lock the scrolling to the nearest X or Y axis. In our example, the 5 pixels to the left are ignored, and the view just moves 100 pixels down.
Finally, QAbstractKineticScroller::OvershootPolicy allows to set the overshooting behavior when scrolling. The default is to just do overshooting when a view is able to scroll in a particular direction. In addition to the default behavior, overshooting can now be completely disabled, or always forced on
Further information via the URL below: