-
-
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
Two questions: Only one child view controller & asynchronous menu fetching #399
Comments
Update: |
Hey @ivanmih ! Where you able to find a workaround for this issue ? |
Hey @santiagofm. It's something like this. Also, interesting thing is that the first dummy child viewcontroller is completely white although i've changed it's color. |
Just stumbled upon another problem of a previous approach. |
Any resolution on this? I think this is the source of my problem as well. Getting a crash on Still haven't been able to diagnose / reliably reproduce it, but it does happen when loading them asynchronously |
Probably this library isn't built for these specific purposes, but it might be good to cover these edge cases anyway.
I am asking these questions here and not on stack overflow because they are causing crashes in my app.
First of all, in my situation, number of child view controllers with their names and relevant data comes from the server. Since 'viewControllers(for pagerTabStripController: PagerTabStripViewController) -> [UIViewController]' method needs to return viewcontrollers as soon parent view loads, i've blocked the main thread until networking returns data from the server.
Is it possible to somehow populate child view controllers after async networking call have retrieved data?
I've been trying to make a workaround and return a dummy view controller and reloadPagerTabStripView after networking. This causes my app to go into some kind of a deadlock, blocking the app and creating some kind of memory and processor usage outrage. Processor is going to 200% and memory rockets by gigabytes (simulator).
Current workaround consists of returning two dummy view controllers, solution which i quite dislike.
Thanks!
The text was updated successfully, but these errors were encountered: