slint-ui/slint

Distinguish between touch and mouse to pan the Flickable

Open

#4,352 opened on Jan 16, 2024

View on GitHub
 (3 comments) (2 reactions) (0 assignees)Rust (22,596 stars) (881 forks)batch import
a:flickablegood first issue

Description

Currently, Flickable::interactive means that you can pan it with the mouse press and drag. It is always possible to pan it with the mouse wheel. We should in fact make sure that you can always pan it with touch event even when interactive is false.

perhaps interactive property should be deprecated and renamed something like pan-with-mouse. Alternative is an interaction mode enum that can be None, Normal, WithMouse.

(Relates a bit to https://github.com/slint-ui/slint/issues/2260)

Contributor guide

Tech stack
rust
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
RustGUI programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the current Flickable::interactive property and how panning is handled for mouse and touch events. Review the linked issue #2260 for context. Consider implementing an interaction mode enum (None, Normal, WithMouse) or deprecating interactive. The changes will likely be in the core Slint library, possibly in the flickable component implementation.