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
[x] I have updated CHANGES.md, with [BREAKING] next to all breaking changes
[x] I have updated the documentation if necessary
[x] If 01_square example was changed, src/lib.rs and README.md were updated
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