> On Aug. 21, 2016, 7:08 vorm., Martin Gräßlin wrote: > > As the maintainer of both klipper and kglobalaccel I'm strictly against > > ading this shortcut by default! This was already stated by me in the bug > > report by setting it to wontfix. > > > > At the moment this would result in a hidden default shortcut no user knows > > about. This is bad, we should not add unexepected and unknown shortcuts. > > And we should not needlessly steal shortcuts from applications. In doubt > > don't set a shortcut by default. At the current time this would only result > > in a degrated user experience: either an in-application shortcut, which we > > don't know that it existed, started to break, or the user presses the > > shortcut and gets hit by surprise what happens. It's totally unexpected > > behavior to open this menu. > > > > Before we start to add new shortcuts, we need to rethink and implement > > better ways of global shortcut handling: > > 1. educating users about shortcuts > > 2. ensuring that we don't steal shortcuts (e.g. by setting up a policy > > about which modifier belongs to the DE) > > > > As long as these problems are not solved, I'm strictly against adding > > shortcuts for hidden functionality. No matter how much we personally think > > they are sensible. > > Andreas Kainz wrote: > In General you are right and we work on aa shortcut strategy, but it need > time and in the end everybody will say. Dont Change my shortcut workflow. > > Why There are two global shortcuts available in klipper. Arent They > hidden functionality? > > What Is your user scenario for klipper? > > Martin Gräßlin wrote: > > Why There are two global shortcuts available in klipper > > No idea. Legacy. Probably should be removed. > > > Arent They hidden functionality? > > Yes they are. But they still are if we expose the shortcut and nobody > knows about it. > > > What Is your user scenario for klipper? > > If I'm totally honest I would love to kill most functionality of klipper. > Because it's unmaintained and as you say hidden functionality. I don't know > why there are things like the "Invoke action". Also the menu is something I'm > not totally happy with as it requires a completely differnt code path. If I'm > totally honest I don't want these features to be exposed to more users as I > don't think they are in a good shape and we don't have developers working on > klipper (haven't had for years, I only took over maintainership because it > needs significant adjustment for Wayland).
Its aAA default widget and it is aa usefull one in my workflow, but with the new shortcut it would improve the widget to a great feature. aa - Andreas ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/128726/#review98523 ----------------------------------------------------------- On Aug. 21, 2016, 12:47 vorm., Andreas Kainz wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/128726/ > ----------------------------------------------------------- > > (Updated Aug. 21, 2016, 12:47 vorm.) > > > Review request for Plasma and KDE Usability. > > > Repository: plasma-workspace > > > Description > ------- > > add a default shortcut for open clipboard at mouse point (ctrl+alt+c) > > BUG 366690 > > > Diffs > ----- > > klipper/klipper.cpp 525ef87 > > Diff: https://git.reviewboard.kde.org/r/128726/diff/ > > > Testing > ------- > > > Thanks, > > Andreas Kainz > >
