-
-
Notifications
You must be signed in to change notification settings - Fork 717
fix: check if double click action associated #2695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2695 +/- ##
=======================================
Coverage 13.58% 13.58%
=======================================
Files 152 152
Lines 11339 11336 -3
=======================================
Hits 1540 1540
+ Misses 9799 9796 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice! Thanks for your help 😃
Please also add this bugfix to the changelog.
When a module is clicked, only wait for the double click interval if a double click action is associated with that module. Otherwise trigger the click right away. Fixes: polybar#2663
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
What type of PR is this? (check all applicable)
Description
When a module is clicked, only wait for the double click interval if a double click action is associated with that module. Otherwise trigger the click right away.
The check is button specific, so if the user performs a right click on an area that has an action for a double left click, the right click is triggered immediately.
Related Issues & Documents
Fixes: #2663
Documentation (check all applicable)