Closed abekert closed 4 years ago
Hi @abekert, first of all massive thanks for taking the time to report this and document it very clearly. This is very appreciated. This is a limitation indeed, I had not thought of this but this is a perfectly valid use case. As you noted in your PR, to support this we need the distinct layout guides. The PR looks very good. I'm going to review it right now
PS: please excuse the late reply 🙏
This is a very handy framework!
Currently
keyboardLayoutGuide
automatically pins tosafeAreaLayoutGuide.bottom
. There is a way to disable it getting a pointer tokeyboardLayoutGuide
and setting itsusesSafeArea
property tousesSafeArea
.Issue
There are two cases:
1) Currently you can't pin two existing views to the
keyboardLayoutGuide
, one takingsafeArea
into account, the second doesn't —keyboardLayoutGuide
is a single instance property. 2) It's not very comfy. You should write something like:Solution
I prefer one from the following:
1) having a separate property for
keyboardLayoutGuide
withusesSafeArea = false
2) having a computed property returning
KeyboardLayoutGuide
withusesSafeArea
turned offAchievable via extension like: