-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
User interaction is disabled calling moveToViewController two times #284
Comments
1 |
Maqix
added a commit
to Maqix/XLPagerTabStrip
that referenced
this issue
Dec 9, 2016
Merged
1 |
mtnbarreto
pushed a commit
that referenced
this issue
Jan 23, 2017
I think your fix didn't worked for me. When I call that method, the app stays frozen with no errors. |
Using XLPagerTabStrip 7.0.0 and I am also getting the UI freeze. Anybody knows what is going on? |
Had to override moveToViewController to solve this issue
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I call
moveToViewController(at: Int, animated: Bool)
ormoveTo(viewController: UIViewController, animated: Bool)
two consecutive times on the same index/ViewController the User interaction is disabled and the user is forced to close and reopen the app.So I have to check each time that the index is not the same as the one currently displayed.
I suggest to edit
moveToViewController(at: Int, animated: Bool)
insidePagerTabStripViewController.swift
addingcurrentIndex != index
in the guard this way:The text was updated successfully, but these errors were encountered: