https://bugs.kde.org/show_bug.cgi?id=455444
osh...@eliyahu.co.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |osh...@eliyahu.co.uk
Status|RESOLVED |REOPENED
Resolution|INTENTIONAL |---
--- Comment #10 from osh...@eliyahu.co.uk ---
Respectfully, I don't think this is the right decision.
I was using this feature to add custom bindings between keyboard combinations
and commands, and it worked perfectly reliably - and still does. Today I found
that when I wanted to add a new shortcut, the feature had disappeared - yet it
did and still does work perfectly well.
Creating a new script file for every single shortcut is hugely impractical and
a massive waste of time - not to mention the fact that for some users less
familar with creating scripts, they may not properly understand how to do so.
(To be honest, until I read this thread, I didn't realise I could bind a custom
script with 'browse' and thought this was limited to desktop files for
launching more conventional "apps".)
Also, since the feature still works well, I am much more inclined to go editing
~/.config/khotkeysrc to add my new shortcut than creating files that clutter
up my disk. Yet this is now much more of a pain than the GUI was, and I am
immediately nervous that I'll break something when I open up the file and see
UUIDs...
On top of that, this creates an actual driving force towards X - why would you
ever switch to Wayland if as soon as you do, you lose features? This actively
hurts Wayland adoption, which seeing as Wayland is supposed to be the future,
doesn't make any sense.
I understand that the motivation for this was to remove a "broken" feature -
some of the options didn't work on Wayland, and providing a feature that won't
work for a while doesn't make sense. But some of the options - very very useful
options - work perfectly right now.
Would it not make more sense to remove only the option to create new
shortcuts/actions that are known to not work? Or perhaps just leave them in
with a warning that they won't work on Wayland for now?
(You may say this is unpolished, but arguably so is removing a feature like
this - just removing it is confusing when users go looking for something
they've been using before.)
--
You are receiving this mail because:
You are watching all bug changes.
