Bug 419846 - PlasmaComponents3.ToolButton is not triggerable during the animation to change its icon
Summary: PlasmaComponents3.ToolButton is not triggerable during the animation to chang...
Status: CONFIRMED
Alias: None
Product: libplasma
Classification: Frameworks and Libraries
Component: components (show other bugs)
Version: 5.85.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords: usability
: 443665 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-04-08 16:04 UTC by Matej Mrenica
Modified: 2021-10-15 14:00 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Matej Mrenica 2020-04-08 16:04:16 UTC 
SUMMARY
So, if you double-click (or click quickly after another click) on the play/pause button, only the first click is registered.


SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.68
Qt Version: 5.15.0 Beta
Comment 1 Nate Graham 2020-04-15 03:07:15 UTC 
Fixed in the 5.19 visual refresh!
Comment 2 Matej Mrenica 2020-06-11 09:10:26 UTC 
This still happens exactly as described, it's not fixed.
Comment 3 Nate Graham 2021-08-29 23:56:46 UTC 
The button is not doing anything nonstandard, so the issue must be in PlasmaComponents.ToolButton itself.
Comment 4 Nate Graham 2021-10-14 23:36:05 UTC 
*** Bug 443665 has been marked as a duplicate of this bug. ***
Comment 5 Jose 2021-10-15 07:35:41 UTC 
I did a simple test and I changed onClicked event to onReleased event and was launched properly.

Also I reviewed the source code for PlasmaComponents.ToolButton and it seems fine.

So, I think that this bug would involved to the original Qt object. Would be just a different behaviour for the onClicked events when a double click arrives?
Comment 6 Nate Graham 2021-10-15 14:00:26 UTC 
It's quite possible this is an upstream bug in how double-click events are handled. However this control doesn't have an onDoubleClicked: handler, so that would be inappropriate behavior to invoke.

Would you be interested in taking a look upstream in Qt?