Add multi-window arrangers (grid / cascade) over the layout planner#344
Merged
Conversation
Not up to standards ⛔
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Lay out a whole set of windows in one call —
snap_windowmoves one window and the v133 layout planner only computes rectangles; these close the loop.arrange_grid(AC_arrange_grid): tile a list of window titles into an R×C grid (defaults to a near-square auto-shape for the window count), with an optionalgap. Windows beyond the grid capacity are left untouched.arrange_cascade(AC_arrange_cascade): stagger the titles diagonally, eachoffsetpx down-right of the previous, sized to 60% of the work area.snap_window's injectablemover/screen_sizeseams, so the arrangement logic is fully headless-testable (the tests inject a recording mover); both return the count moved. Default mover is Win32 today, other platforms no-op until their backend lands.