![]() ![]() They don't "consume" windows making them unavailable for subsequent rules, as they act on applications. Unhide and hide, if used, should usually go into their own rules (with a windowfilter that allows invisible windowsįor unhide) that come before other rules that deal with actual window placement - unlike the other actions, by placing them out of the way (minimize). relevant to your current workflow) windows first (move, maximize.) and after that deal with less prominent (with more generic windowfilters) last similarly, within a rule, you should have commands for the more "important" You should place higher-priority rules (with highly specialized windowfilters) first, and "fallback" rules for fullscreen and maximize, a screen hint indicating the desired screen if omitted, uses the window's current screen.Indicating the destination rect for the command for move, tile and fit, an hs.geometry rect, or a unit rect plus a screen hint (for hs.screen.find()),.an hs.geometry size (only valid for tile and fit) indicating the desired optimal aspect ratio for the tiled windows.(least recently created), or closest (pick the maxn windows that are closest to the destination rect) if omitted,ĭefaults to closest for move, tile and fit, and newest for everything else It can be one of focused (pick maxn most recently focused windows), frontmost (pick the recent focused window if itsĪpplication is frontmost application, otherwise the command will be skipped), newest (most recently created), oldest a selector, describing the sort order used to pick the first maxn windows from the window pool for this command.Windows are "consumed" and are excluded from the window pool for subsequent commands in this rule, and from subsequent rules If omitted (or if explicitly the string all) all the remaining windows will be processed by this command processed a maxn number, indicating how many windows from this rule's window pool will be affected (at most) by this command.hide, unhide: hides or unhides the window's application (like when using cmd-h).PreserveRelativeArea parameter will be set to true tile, fit: tiles the windows onto a specified rect, using hs.() for fit, the.move: moves the window(s) to a specified onscreen rect (if the action is omitted, move is assumed).Rules within a layout are evaluated in order once a window is acted upon by a rule, subsequent rules will not affect it further.Ī rule needs a windowfilter, producing a dynamic list of windows (the "window pool") to which the rule is applied,Īnd a list of commands, evaluated in order.Ī command acts on one or more of the windows, and is composed of: Windowlayouts work by selecting certain windows via windowfilters and arranging them onscreen according to specific rules.Ī layout is composed of a list of rules and, optionally, a screen arrangement definition. (Should you encounter any issues, please feel free to report them on It can undergo breaking API changes or go away entirely at any point and without notice. This module is for testing purposes only. Hammerspoon docs: hs.window.layout docs » hs.window.layout
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |