| Summary: | generic actions: condition list | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Oswald Buddenhagen <ossi> |
| Component: | kcm_khotkeys | Assignee: | Lubos Lunak <l.lunak> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.20.3 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. As announced in https://pointieststick.com/2023/07/26/what-we-plan-to-remove-in-plasma-6/ and https://community.kde.org/Plasma/Plasma_6#Removals, I'm afraid KHotKeys has reached end-of-life in Plasma 6. Accordingly, all bug reports and feature requests for it must be closed now. Most of what KHotKeys could do can already be done with the newer KGlobalAccel system in Plasma 6. A few features such as mouse gestures and triggering conditions based on changes to window states are not yet implemented in the new system. These will be added in the future if and when resources materialize for them, and/or when a kind soul submits patches to implement them! :) Meanwhile, the 3rd-party "Mouse Actions" app (https://github.com/jersou/mouse-actions) may be usable for implementing your own mouse gestures again. Thanks for your understanding, everyone. |
the problem lies in the word list ... it should be actually a strict tree, where only operator nodes and the root node are allowed to have children (i think it's the case already), and only combining operator nodes (AND, OR) are allowed to have multiple children - the root node must not allow it (how would they be combined?). the rest are related wish-list items ...: as soon as a non-root node exists some node will be selected, and as the root node is busy then, the annoying "group selected, do you want ..." question can go. impossible items should be visibly disabled. keybingdings are needed, prolly <ins> for new, <del> for delete, and <f3> for modify. some advanced editing actions should be implemented: - two "new" menus are required - to insert a child (only for "non-terminal" nodes, obviously), and to insert a parent ("terminal" nodes have only this option) - complementary to inserting a parent, it should be possible to delete non-leaf nodes with only one child. possibly this should ask, whether only the selected node or the entire subtree should be deleted - but i'd prefer a separate action for this (ctrl-<del> for entire subtree; complementary to <ctrl>-ins for insert parent). - ideally, it would be possible to drag and drop items within the tree. oh, well.