https://bugs.kde.org/show_bug.cgi?id=466108
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CONFIRMED
CC| |sit...@kde.org
--- Comment #2 from Harald Sitter <sit...@kde.org> ---
This is giving me a headache.
What happens is that we handle onClicked but if you click quickly enough the
second click issues onDoubleClicked. The state confusion then occurs because
clicks directly influence the checked state (though I have to admit I don't
understand how.
More specifically it appears the following happens for single click:
- click
- onCheckedChanged
- onClicked
- checked binding reevaluates
For a double click it is:
- click
- click
- onCheckedChanged
- onClicked
- checked binding reevaluates
- onCheckedChanged (the result of the second click)
- onDoubleClick
What I don't quite get is how the checked state can be directly manipulated
while also being a binding. I'd either expect the binding to break or
onCheckedChanged to not get emitted on clicks (without first running
onClicked).
I think this needs further investigation.
The fix at face value would be to not have checked be a binding and instead of
onclicked react to oncheckedchanged but that also seems a bit weird.
--
You are receiving this mail because:
You are watching all bug changes.
