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

Jump while dragged up or down #154

Closed
1 of 3 tasks
vovkaprigarin opened this issue Mar 7, 2019 · 16 comments
Closed
1 of 3 tasks

Jump while dragged up or down #154

vovkaprigarin opened this issue Mar 7, 2019 · 16 comments

Comments

@vovkaprigarin
Copy link

vovkaprigarin commented Mar 7, 2019

Short description

Up from .tip to .half and from .half to .tip position is incorrect while dragging.
This behavior was appeared on library version 1.4.0, previous version work perfectly.

Expected behavior

library version 1.3.5 and correct behavior:
ezgif-1-76694c1667d7

Actual behavior

library version 1.4.0 and incorrect behavior:
ezgif-1-22e3941c8930

Environment

Simulator iPhone 5s iOS 12.1

Library version
1.4.0

Installation method

  • CocoaPods
  • Carthage
  • Git submodules

iOS version(s)
12.1

Xcode version
10.1

@scenee
Copy link
Owner

scenee commented Mar 19, 2019

I will investigate the issue. Thanks for your report!

@scenee
Copy link
Owner

scenee commented Mar 19, 2019

I tested this issue with the Samples app on v1.4.0, but unfortunately it isn't able to reproduce this issue. Could you please attach a sample code to reproduce this?

@scenee
Copy link
Owner

scenee commented Mar 21, 2019

I could watch the issue once! But I’ve not be able to find a concrete repo way...

@vovkaprigarin
Copy link
Author

vovkaprigarin commented Mar 21, 2019

@scenee I will create sample and post in this issue, but later, ok?

@scenee
Copy link
Owner

scenee commented Mar 21, 2019

Of course, @vovkaprigarin! I appreciate your contribution 👍

@scenee
Copy link
Owner

scenee commented Mar 21, 2019

@vovkaprigarin
I could fix this issue on fix-safeareainsets branch!
I found a safe area inset issue related to top/bottom dragging of a panel with a large title navigation bar. The branch resolves the issue. I'm not sure it's same, but it's possible this issue is also related to a safe area inset. So could you try the branch?

@pakko972
Copy link

Hi all, I had the exact same issue and branch fix-safeareainsets fixed it.

@scenee
Copy link
Owner

scenee commented Mar 22, 2019

Thanks, all! I created PR #168. It will be released in v1.4.1 soon.

@vovkaprigarin
Copy link
Author

vovkaprigarin commented Mar 22, 2019

@scenee fix-safeareainsets fixed this issue partially :) Now panel not jumping, but still moving to top. fix-top-dragging-boundary (for 167 issue) fixes it completely!

How check both fixes fix-top-dragging-boundary and fix-safeareainsets ?

@scenee
Copy link
Owner

scenee commented Mar 25, 2019

I'm going to rebase fix-top-dragging-boundary soon by the master branch already merged fix-safeareainsets. I'll let you know it in this issue when I did. I'm pleased that you will check the new fix-top-dragging-boundary branch(both of fix-top-dragging-boundary and fix-safeareainsets)!

@scenee
Copy link
Owner

scenee commented Mar 26, 2019

@vovkaprigarin
I prepared the new fix-top-dragging-boundary branch. I polish the previous one. I'm pleased that you check it.

@Lukaz32
Copy link

Lukaz32 commented Mar 26, 2019

Should the problem be solved in the fix-top-dragging-boundary branch?
I still get the weird behaviour on it.
I've set my full position at -44, and also fpc.additionalSafeAreaInsets = UIEdgeInsets(top: -44, left: 0, bottom: 0, right: 0)
but after scrolling around it never returns to the correct position.

giphy

@scenee
Copy link
Owner

scenee commented Mar 27, 2019

@Lukaz32
No, the branch intends to solve #167. But the problem should be fixed. This library hasn't taken care of a use case using it with fpc.additionalSafeAreaInsets. So could you please file a new issue and let me know source code of your modified Maps app?

@Lukaz32
Copy link

Lukaz32 commented Mar 27, 2019

Oh, my bad, I thought it was related to this issue. Sure thing, I'll file a new issue on this matter. Thanks

@vovkaprigarin
Copy link
Author

@scenee All is well. Works perfectly, Thank you!

@scenee
Copy link
Owner

scenee commented Mar 27, 2019

@Lukaz32
Thanks! I will be sure to fix it.

@vovkaprigarin
Thank you, too! I could fix the fundamental issues by your contribution. I really appreciate it.

@scenee scenee closed this as completed Mar 27, 2019
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

No branches or pull requests

4 participants