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
{{ message }}
This repository has been archived by the owner on Sep 11, 2022. It is now read-only.
I'm curious and I developed some iPhone Apps a few years ago. Currently I plan to work on a new project and need something like the PKRevealController. But one question I came up with is: What are the benefits of using PKRevealController instead of the UISplitViewController, which can nowadays also be used on IPhones?
This is more of question than a real issue, I am sorry for that, but I didnt find a proper place to ask. On StackOverflow there does not seem to be a real discussion about this and it might be useful if the PKRevealController documentation might state the difference to UISplitViewController.
The text was updated successfully, but these errors were encountered:
The quick answer is that they do different things. One shows the shelf with an arbitrary view controller. The UISplitViewController is designed around a master-detail data refinement process. Yes, you can use it like PKRevealController. But it is different and may not be what you want from a UI.
Anon,
Andrew
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm curious and I developed some iPhone Apps a few years ago. Currently I plan to work on a new project and need something like the PKRevealController. But one question I came up with is: What are the benefits of using PKRevealController instead of the UISplitViewController, which can nowadays also be used on IPhones?
This is more of question than a real issue, I am sorry for that, but I didnt find a proper place to ask. On StackOverflow there does not seem to be a real discussion about this and it might be useful if the PKRevealController documentation might state the difference to UISplitViewController.
The text was updated successfully, but these errors were encountered: