Closed qarmin closed 8 months ago
This is documented in the documentation: https://slint.dev/snapshots/master/docs/slint/src/language/builtins/elements#toucharea
double-clicked()
: Invoked when double-clicked. The mouse is pressed and released twice on this element in a short period of time. Assigning this callback will cause theclicked
callback to get delayed, so that Slint can detect whether the first click was a click or the first half of a double click.
We discussed this and thought this was the best course of action because we didn't want the clicked
callback to be emitted if the user double clicked.
Perhaps we should also emit the clicked
directly if the mouse is moved though. @hunger: thought?
If you really want to react to clicks as well, then using the pointer-event might be the way.
not works in web, because it is version 1.3.2, but double-clicked is available in newer version
@tronical and I had a discussion internally , and we came to the conclusion that preventing the clicked
to be fired was probably a bad idea.
Se we're going to change the behavior so that clicked is always emited (twice) on double click.
(So we'd have clicked
, clicked
, double-clicked
). This seems to align with what other framework are doing.
This should be fixed now. Thank you for your patience.
Slint nightly
Enabling
double-clicked
callback slows downclicked
callback which is called a lot of later than alonehttps://github.com/slint-ui/slint/assets/41945903/089a0cb0-6cac-4742-a18c-64c489768a03
CODE - not works in web, because it is version 1.3.2, but double-clicked is available in newer version