Actually implement a resize API #616
Merged
Conversation
This file contains 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
43 tasks
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.
#566 claimed to handle resizes. Unfortunately I had not hooked up the module graph correctly, and it turns out that code wasn't even being compiled. Whoops!
This adds the ResizeStrategy API, which allows you to generate Transforms to handle resizing of the window. Unlike in Quicksilver 0.3, where this code was all magic-behind-the-scenes, this is actually all in 'userspace.' It uses only public APIs from other Quicksilver modules.
Resolves #594
Resolves #602
At default size:
Scaled up:
Checks
CHANGES.md, with [BREAKING] next to all breaking changessrc/lib.rsandREADME.mdwere updated