-
Notifications
You must be signed in to change notification settings - Fork 11
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
interface rotations doesn't work #1
Comments
…sly. Requires view controller to forward rotation callbacks to the paging view (as shown in the demo). Each rotation is a reload of the paging view, causing its view to be recycled and cause weird animation on rotation. Will try to solve it sometimes in the future.
Hi there, Thanks for the kind words. I'm sorry the project wasn't very well designed. I have a quick fix that would requires you to forwards the view controller rotation callback methods to the paging view, like this:
This should fix the rotation layout problem. The currently implementation requires a reload for every rotation which cause the views to be recycled, so you might face some animation issue. I'm not sure when I will have time to come back to fix the remaining issue, but if the remaining issue still bug you, let me know, so that I can find some time to fix it. Thanks for the head up. |
Hi! THANKS so much for the quick turnaround! I've tried your code and it works :) As you say sometimes the animations are not perfect because of the recycling of the views, but it's good enough for now :) Again, thanks so much for the support! |
Great! I'm currently rushing projects at my day work. But will hopefully provides a better fix in near future. finger cross :) |
Hi, thanks for your awesome project!
I have been having heavy problems with interface rotation. I can't make it to work, the views always get completely garbled :( I've tried calling layoutSubviews on -(void)willAnimateRotationToInterfaceOrientation:(UIInterfaceOrientation)toInterfaceOrientation but it still doesn't work.
Any hint on this? Thanks!
The text was updated successfully, but these errors were encountered: