Run app as administrator from the Taskbar. Open another instance of an app from the Taskbar. Reveals typed password in Sign-in screen. Switch between open apps while pressing Tab multiple times. Runs command for the underlined letter in apps. Select multiple items on desktop or File Explorer. On Windows 10, you can use these keyboard shortcuts to open, close, navigate, and perform tasks more quickly throughout the desktop experience, including the Start menu, Taskbar, Settings, and more. Windows key + Period (.) or Semicolon ( )Ĭapture a full screenshot in the "Screenshots" folder.Ĭapture part of the screen with Snip & Sketch. Take a screenshot and stores it in the clipboard. (If no active window is present, a shutdown box appears.)ĭelete the selected item permanently, skipping Recycle Bin. after all, all I am trying to do is close a window with a shortcut rather than having to use the mouse and click that X in the window title bar.Undo an action, including undelete files (limited).Ĭreate new folder on desktop or File Explorer.Ĭlose active window. then isn't it true that by binding Ctrl+Q to XDestroyWindow only has the disadvantage that any client's Ctrl+Q key mappings are not being triggered? I mean. Is it correct then, that the XDestroyWindow event is actually the same as clicking the X in the window title bar? If so. So this just confirms that the idea of the whatsapp-desktop developers was to keep whatsapp running in the background, so that you can receive messages even if the window is closed. I realized today that whatsapp-desktop actually stays open if you close the window via its "X" from the window, as in the X icon of the window bar. So if I want to stick with 'Q', I should probably configure mod4+Q to close windows. As a matter of fact, I have set up most of the Enlightenment keybindings with the mod4 key. Using the mod4 key (usually the "Windows" key if I understand correctly) for WM key bindings is certainly the way to go. ![]() You could bind Ctrl-Q in your WM to XKillClient rather than XDestroyWindow and it should then do what you want for Whatsapp, but this still doesn't seem like a good idea to me. But if you do, you really can't expect all programs to behave nicely with it. So, in short, you certianly may use a non-convential key binding scheme for your WM. You are running into one of those problems now. This is not - as far as I know - formalized anywhere in any binding protocol, but going against such widely used convention is bound to cause problems. There certainly are exceptions, but it is generally expected that Mod4 key combinations are for WMs and Ctrl key combinations are for clients (as are most Alt/Shift combinations unless they are paired with Mod4). applications) generally do not bind Mod4 key combinations. This is why it is a bad idea for a window manager to bind that key as it will result in clients never detecting the key press.įor very similar reasons, clients (i.e. If you write a Qt program, you certainly can chose not to use Ctrl-Q for "quit", you could use Ctrl-H if you wanted, or Ctrl-Shift-Space-F3-Y if you want to appeal to emacs users But Ctrl-Q is a de-facto standard client / application bound key. ![]() Qt) using it as a default for many applications. This is both reflected by and reinforced by some toolkits (e.g. `Ctrl-Q` is a common key for quitting a program.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |