https://bugs.kde.org/show_bug.cgi?id=371877
Darin Miller <darinsmil...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |darinsmil...@gmail.com
--- Comment #16 from Darin Miller <darinsmil...@gmail.com> ---
Adding a note from a remmina perspective:
Meta keys are used frequently when remoting into a Windows box:
<meta> by itself on windows provides same functionality as Kicker (user text
search for applications and files)
<meta>+D minimizes all windows
<meta>+e file manager (Explorer)
<meta>+<arrow> splits window half screen in corresponding arrow direction.
<mete>+<pause/break> windows settings
etc.
Options:
1. Disable kicker meta shortcut entirely
2. Disable meta key with script when launching key capturing applications,
re-enable when application is closed. This is a pseudo solution, as kicker
would not work while app is running. I switch to local desktop frequently when
remoted to a windows box. Though I use krunner to launch most of apps, I would
have used the meta key long ago if it worked. Thus, new users will expect it
to work if switching from windows.
3. Provide a list of apps in a config file or possibly a "window rules" setting
that will disable the kicker meta key when they have focus. However, this
requires the user to maintain the key grab setting in the app and in the config
file.
4. Honor the key capture state of the application that has focus. Can the key
capture state of an app be determined when the app obtains focus? If so, auto
disable meta-kicker relationship when respective apps are set to capture the
keyboard and re-enable when non-key capturing apps or local desktop has focus.
Option 4 is preferred as it requires the least amount of configuration.
Options 1, 2 and 3 keep KDE in the tinkerer's realm and discourages users who
do not like to fiddle with their system.
--
You are receiving this mail because:
You are watching all bug changes.
