Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support bottom content inset for container view #257

Merged
merged 3 commits into from
Aug 31, 2019

Conversation

nderkach
Copy link
Contributor

@nderkach nderkach commented Aug 27, 2019

Fixes #256

1

I've removed containerViewTopInsetConstraint and containerViewHeightConstraint in favor of using a bottom constraint.

It's not quite clear what's the purpose of topInteractionBuffer and bottomInteractionBuffer exactly, but I tried to keep the logic intact.

Copy link
Owner

@scenee scenee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your PR. I added some change requests. Could you please take care of them?

Framework/Sources/FloatingPanelSurfaceView.swift Outdated Show resolved Hide resolved
Framework/Sources/FloatingPanelSurfaceView.swift Outdated Show resolved Hide resolved
@nderkach nderkach force-pushed the nikolay/fix-bottom-contentinsets branch from dcbd7ba to 76f8c97 Compare August 29, 2019 16:56
@scenee scenee merged commit f8b8176 into scenee:master Aug 31, 2019
scenee pushed a commit that referenced this pull request Aug 31, 2019
and also fix height of a content view resized by the inset
Fix #256
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Setting contentInsets top value offset the whole container to the bottom
2 participants