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

Most of transitions do not respect non translucent navigation bar leading to glitches and wrong frames. #305

Open
3 of 5 tasks
mikhailmulyar opened this issue Sep 7, 2016 · 10 comments · Fixed by #441
Open
3 of 5 tasks

Comments

@mikhailmulyar
Copy link

mikhailmulyar commented Sep 7, 2016

When using some transition animations with push, if the Navigation bar set to translucent=false. The following transitions are not working properly:

  • Flip
  • Explode
  • Card
  • Turn
  • Fold

There are no problems for present transition or if Navigation bar set to translucent=true.

----- Original message ------
Hi. When navigation controller uses opaque navigation bar, translucent=false most of the transitions end up with the wrong frame for destination view, not respecting navigation bar height and UIViewControllerContextTransitioning finalFrameForViewController method.
In most cases like in Fade animation, final frame for view just wrong.
In several cases like in Flip animation it leads to UI jumps and glitches.
In rare cases like Turn left and right animation(not top and bottom, those also have glitches) it works as expected.

@JakeLin
Copy link
Member

JakeLin commented Sep 7, 2016

@mikhailmulyar thanks for reporting this issue, how do you use these animators? We recommend you use them in Apple's way like #242 when you use them in code.

@mikhailmulyar
Copy link
Author

I use them in code, but this issues happens in all cases.This issue is reproduces in your Example project, if you go to playground part, to Transitions.storyboard and set navigation bar to non translucent.

@JakeLin
Copy link
Member

JakeLin commented Sep 8, 2016

@mikhailmulyar thanks for your reply, we are busy on swift3 branch at that moment. Please let me know if you have any initial idea how to fix them. I haven't done a deep look, hopefully, it's as simple as calling initialFrameForViewController:fromVC and finalFrameForViewController and set the Rect of the views. A PR will be appreciated 😉

@JakeLin
Copy link
Member

JakeLin commented Sep 8, 2016

@mikhailmulyar I have a look at Flip, it is not that simple. There is some issue with createSnapshots to calculate the frame. But I haven't found a solution yet.

@mikhailmulyar
Copy link
Author

mikhailmulyar commented Sep 10, 2016

I have checked all transitions, more than half of them are easy to fix, like all system. But other will require some time to fix, like Flip and Fold

@JakeLin
Copy link
Member

JakeLin commented Sep 10, 2016

@mikhailmulyar thanks for looking at this issue, if you would like to help me out with this, don't need to fix them in one PR. You can PR them bit by bit. We are about to merge swift3 into master, would you like to work on swift3 (future master) or current master (will be swift2.3), it is up to you? Please let me know if you have any questions.

@mikhailmulyar
Copy link
Author

Added PR #309 for Card, Fade, NatGeo, Slide and all System animations

@tbaranes tbaranes mentioned this issue Sep 17, 2016
4 tasks
@tbaranes
Copy link
Member

tbaranes commented Sep 17, 2016

I catch up the discussion you started in #309. I search a bit about why the transitions are broken. I have no explanation, but the transitions are working as expected on the iPhone 6 simulator but broken on the iPhone 7. Any idea what's difference could be have between both?

Also, it's definitely the resizableSnapshotView which is broken, but not sure how we could replace it.

@tbaranes
Copy link
Member

Should we really close this? There's still a few bugs related 🙃

@JakeLin JakeLin reopened this Apr 20, 2017
@JakeLin
Copy link
Member

JakeLin commented Apr 20, 2017

@tbaranes I don't think we should close this issue. I closed it when I merged the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants