in GUI Development by
In our implementation of scrollable lists we are using a Core::Outline, a Core::SlideTouchHandler and clickable tiles on top, each with their own Core::SimpleTouchHandler
With the default settings we experienced very slow scroll, so we have improved significantly changing the following 3 properties:
- Core::SlideTouchHandler Friction (reduced)
- Core::SlideTouchHandler ResetDelay (increased)
- (tile) Core::SimpleTouchHandler RetargetOffset (reduced)
Still the experience is more similar to a drag and drop than a proper swipe. You have to pin the tile before you can swipe it away.
A swipe such as we are used to do on the smartphone will not cause any movement.
The question is if there is something else we can play with to further improve this.

1 Answer

0 votes

Hello giuspen,

based on the provided information it is difficult for me to understand the problem. Is it the timing behaviour of the Slide Touch Handler, or time needed to re-draw the screen content?

The timing of the slide touch handler is controlled mainly by Friction and SpeedLimit. However, it will not help when the content to scroll requires much time during the screen update. It means, when the content contains many visual elements which need to be re-drawn each time the content is scrolled.

Also possible, when several touch handler are combined overlapping each other, it is important to understand that a touch interaction is first receipt by the top most lying handler. This handler may be configured to relay the interaction to another handler when particular gesture is performed. May be what you observe is an issue with not correctly configured touch handlers. See also Combine several Touch Handlers together

I would try to reduce the application case and narrow down what causes the delays.

Best regards

Paul Banach

Embedded Wizard Website | Privacy Policy | Imprint