diff options
author | Laszlo Papp <lpapp@kde.org> | 2022-05-07 09:55:31 +0100 |
---|---|---|
committer | Laszlo Papp <laszlo.papp@foundry.com> | 2022-05-11 15:56:55 +0100 |
commit | d9be9fedfb15c3eca69adedf9e2e95c0df9643e7 (patch) | |
tree | 388c98182ffe9a18461ae6ce9caa3e7ab75bf7b5 /mkspecs | |
parent | 4872392925b5d4df3e307b71a9a575b7d26e4c7e (diff) |
Add a clear action to QKeySequenceEdit
This can be really helpful for deleting shortcuts that one may never
intend to use so that they do not accidentally get in the way while
interacting with the user interface.
The workaround is to try to find the QLineEdit child of the
QKeySequenceEdit widget, but it is suboptimal. Some first-class citizen
API for this would be a more stable and cleaner solution as opposed to
poking implementation details as a user of the QKeySequenceEdit API.
The clear action would be configurable and opt-in as not everyone may
potentially want this to be turned on. Or at least, not by default
anyway. Also, not to suddenly change existing QKeySequenceEdit uses with
surprising UI changes after a Qt upgrade, this needs to be opt-in.
Moreover, some customers may have already used findChild<QLineEdit *>()
to add actions to QKeySequenceEdit in this way on the client side. So,
if it was enabled by default, they would suddenly get multiple actions
potentially for the same clear action. This would be certainly
undesirable.
The new clear property is based on the corresponding QLineEdit API for
consistency.
[ChangeLog][QtWidgets][QKeySequenceEdit] Added a clear action to
QKeySequenceEdit to be able to remove existing hotkey configurations.
Change-Id: I3a90bfacd49bff10c1284abb155d7edd4f537900
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
Diffstat (limited to 'mkspecs')
0 files changed, 0 insertions, 0 deletions