You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 3 viewControllers for paging. Everything is perfect except one. viewDidAppear() of second viewController called when first viewController is loaded.
Problem is we are presenting a viewController (basically a coach mark) when second view controller is loaded. Hence when first view controller appears, second viewController's presenting viewController (i.e coach mark) is shown.
I have checked internal code of PagingKit. It has something called "isEnabledPreloadContent" property and 'preloadContentIfNeeded' method which is not used anywhere. I believe if isEnabledPreloadContent is set to false, it should not load viewControllers which are yet to present/load.
As a workaround, I am using "menuViewController(viewController: PagingMenuViewController, didSelect page: Int, previousPage: Int) " method to decide whether to present viewController or not. But this is not satisfying!!
The text was updated successfully, but these errors were encountered:
I have 3 viewControllers for paging. Everything is perfect except one.
viewDidAppear() of second viewController called when first viewController is loaded.
Problem is we are presenting a viewController (basically a coach mark) when second view controller is loaded. Hence when first view controller appears, second viewController's presenting viewController (i.e coach mark) is shown.
I have checked internal code of PagingKit. It has something called "isEnabledPreloadContent" property and 'preloadContentIfNeeded' method which is not used anywhere. I believe if isEnabledPreloadContent is set to false, it should not load viewControllers which are yet to present/load.
As a workaround, I am using "menuViewController(viewController: PagingMenuViewController, didSelect page: Int, previousPage: Int) " method to decide whether to present viewController or not. But this is not satisfying!!
The text was updated successfully, but these errors were encountered: