| Summary: | allow passing of certain, otherwise blocked keystrokes to a window (by the window controls) | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Hauke Laging <hauke> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
Version: (using KDE KDE 3.4.0) Installed from: SuSE RPMs Certain keystrokes are intercepted by - I assume - the window manager. <Ctrl>-<Tab> e.g. I use VNC and have the problem that I cannot use these key combinations on the remote PC. This may be useful for applications with hotkeys (I experienced this with OpenOffice) which cannot be used because the window manager(?) uses them itself. It is probably not (easily) possible to offer a "pass the next key stroke" function so I think of a ("half") virtual keyboard. It would probably be enough to tell the window controls to treat the next keystroke as if the key would keep pressed. I don't think that the window manager uses single keys for special purposes. As problems probably arise with the special keys (Ctrl, Alt, AltGr, Esc, Shift, Windows) it might be enough to offer a menu of these in the window controls which allows you to click them. As long as they are activated the window manager would "add" these keys to those which are actually pressed. An example: I need <Alt>-<Tab>. I open the window menu and mark <Alt> as pressed and then press <Tab>. Two additions were nice: An additional button in the frame controls which appears when this feature is used so that the special keys can be disabled by one click (omitting the menu). And a history would be cool, of course, as you probably use the same special keys again. These could be chosen from this new frame control button if the user wants to see it permanently.