It’s the default keybinding for that function in many tiling window managers, so why reinvent the wheel. For the most part I’m sticking with commonly used bindings for example, SUPER + RETURN to open a terminal seems reasonable. I may add more to this list, because there may be other basic functions that most, if not all, tiling window managers have and if so, then I want to be sure the keybindings for those functions are consistent. This is just an initial attempt at standardizing keybindings. Rotates the windows in the stack, the opposite direction of j Rotates the windows in the stack, the opposite direction of k Switches focus between windows in stack, the opposite direction of j Switches focus between windows in stack, the opposite direction of k Here are the some of the basic functions that almost every tiling window manager has builtin, and here are my standardized keybindings: So I’m working hard to rectify this problem and standardize on keybindings. The command to switch monitor focus was not the same in all of my configs. The command to open dmenu was not the same in all of my configs. I think that this is important because it will make transitioning from one window manager to another easier, since many of the keybindings will be the same. One of the things I want to do is provide consistent keybindings among the various window manager configs on my GitLab. When the user clicks 'Pin to Start', you should immediately call the API from the UI thread to pin the secondary tile. I know many people grab my configs from my GitLab, and I want to make sure that those people have a nice, consistent experience when trying out various window managers. Consider the following recommendations when enabling secondary tiles in your app: When the content in focus is pinnable, the app bar should contain a 'Pin to Start' button to create a secondary tile for the user. One of the things that I have been working on recently is cleaning up all of my tiling window manager configuration files.
0 kommentar(er)
