TDEMenu shortcuts: Additional checks/fixes #232

Merged
blu.256 merged 1 commits from fix/kmenu-shortcut-checks into master 3 years ago
Collaborator

Please test:

  • Setting Escape as a shortcut
  • Setting Escape as one out of two shortcuts
  • Not setting a shorcut at all (then the search line can only be activated by clicking on it).

If all's okay, then I can squash the commits and merge the PR.

Please test: * Setting Escape as a shortcut * Setting Escape as one out of two shortcuts * Not setting a shorcut at all (then the search line can only be activated by clicking on it). If all's okay, then I can squash the commits and merge the PR.
blu.256 added the PR/rfc label 3 years ago
blu.256 added this to the R14.0.11 release milestone 3 years ago
SlavekB requested changes 3 years ago
SlavekB left a comment
Owner

It seems there is a change in the code that was intended differently.
See comment below.

It seems there is a change in the code that was intended differently. See comment below.
c->setGroup("KMenu");
m_searchShortcut->setShortcut(TDEShortcut(c->readEntry("SearchShortcut", "/")));
m_searchShortcut->setShortcut(TDEShortcut(c->readEntry("SearchShortcut", "/"))), false;
Owner

At first glance, this does not look like the intended result. I assume that false was supposed to be as an argument for setShortcut – so before parenthesis?

At first glance, this does not look like the intended result. I assume that `false` was supposed to be as an argument for `setShortcut` – so before parenthesis?
Poster
Collaborator

Strange that it didn't break the build for me. Yes, it should have been before the last parens as an argument for setShortcut. Fixing this.

Strange that it didn't break the build for me. Yes, it should have been before the last parens as an argument for `setShortcut`. Fixing this.
Owner

Yes, it does not cause FTBFS because there was this false basically completely ignored == false there had no effect or meaning, but did not cause an error in syntax.

Thank you, I assumed it exactly and therefore I built it with such a modification for performing the tests.

Yes, it does not cause FTBFS because there was this `false` basically completely ignored == `false` there had no effect or meaning, but did not cause an error in syntax. Thank you, I assumed it exactly and therefore I built it with such a modification for performing the tests.
blu.256 marked this conversation as resolved
blu.256 force-pushed fix/kmenu-shortcut-checks from cdb0710583 to d26e5f7c17 3 years ago
blu.256 force-pushed fix/kmenu-shortcut-checks from d26e5f7c17 to 89449e1960 3 years ago
SlavekB approved these changes 3 years ago
SlavekB left a comment
Owner

I did tests and it seems, everything works as intended.

I did tests and it seems, everything works as intended.
Poster
Collaborator

Okay, then I'm merging this.
Thanks for testing, Slávek.

Okay, then I'm merging this. Thanks for testing, Slávek.
blu.256 force-pushed fix/kmenu-shortcut-checks from 89449e1960 to 10cddab2e3 3 years ago
blu.256 merged commit 10cddab2e3 into master 3 years ago
SlavekB deleted branch fix/kmenu-shortcut-checks 3 years ago
SlavekB removed the PR/rfc label 3 years ago
Owner

Thanks Philippe, it works fine. May I suggest a minor rewording?

From: Cannot set Escape as menu search shortcut.

To: Escape cannot be used as a shortcut for the menu search field.

Thanks Philippe, it works fine. May I suggest a minor rewording? From: Cannot set Escape as menu search shortcut. To: Escape cannot be used as a shortcut for the menu search field.

Reviewers

SlavekB approved these changes 3 years ago
The pull request has been merged as 10cddab2e3.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/tdebase#232
Loading…
There is no content yet.