[Alternative method of modifying views] Switched from modifying frame to using an offset #23
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.
Thanks for creating this Nick. I had a use case which required a slight modification that I thought might be useful for others.
Let's say we have this:
Using the current
![before](https://user-images.githubusercontent.com/1586049/99247855-8c485500-27d5-11eb-82d3-8af8ad35a528.gif)
KeyboardObserving
, the result looks like this:You can see it modifies the relative sizes of Blue and Red since Blue is constrained while Red is not.
When I wrote my own keyboard avoiders before SwiftUI, I found messing with the frames sometimes gave hard to debug results so I had always preferred to simply use a transformation on the underlying layer and translate everything up.
This gives the following result:
It may not be what your extension intends but thought it was a nice option to have.