Details
-
Suggestion
-
Resolution: Done
-
P2: Important
-
5.11
-
None
-
583b7b0324a03337b8f21b5c2eacb6657c16ade7
Description
Currently the docs suggest using onValueChanged to react to value changes resulting from user interaction, which can cause issues (e.g. binding loops).
See also QTBUG-57203.
If grouped properties can have signals, they could look like this:
first.onMoved: settings.foo = first.value second.onMoved: settings.bar = second.value
Otherwise they could look like this:
onFirstMoved: settings.foo = first.value onSecondMoved: settings.bar = second.value
Attachments
Issue Links
- is duplicated by
-
QTBUG-67732 Include moved signal in RangeSlider Control first, second
- Closed
- relates to
-
QTBUG-57203 Add signals for interaction with controls
- Closed
-
QTBUG-67317 RangeSlider lacks a valueAt() function
- Closed