-
Notifications
You must be signed in to change notification settings - Fork 32
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
in the Global-Actions-Manager-window: checkbox: double-click versus one click #190
Comments
by the way, I think the button "Swap" on the right side of the list of shortcuts does not work (or maybe I missed something); |
Two things should be fixed IMO:
For the latter better an separate issue. |
@stefonarch "For the latter better an separate issue." I opened a new issue: #191 |
there is also an other issue in Lubuntu 21.04 in LXQt 0.16.0: |
in the Global-Actions-Manager-window:
at the moment shortcuts can be deactivated in the list of shortcuts by double-click on the checkbox;
the checkbox is exactly the same checkbox like in the properties of the shortcut;
but in the properties only one click on the checkbox is enough to deactivate the shortcut;
that is a contradiction: 2 different behavior for a checkbox;
checkbox should have exactly the same behavior
Expected Behavior
in the Global-Actions-Manager-window:
one click to activate/deactivate the checkbox (like the checkbox in the properties of the shortcut, what can be reached for example by double-click on the description of one shortcut)
Current Behavior
in the Global-Actions-Manager-window:
double-click is necessary to activate/deactivate the checkbox
Possible Solution
I think it is necessary to add a column on the right side of the checkbox;
in this column there should be only the id-number
the reason:
in other words:
instead of 1 cell with checkbox and id-number, there should be
2 cells, so one cell only for the checkbox, and one cell only for the id-number,
because of 2 different behavior
Steps to Reproduce (for bugs)
Context
checkbox should have exactly the same behavior
System Information
The text was updated successfully, but these errors were encountered: