User Interface Setup
Twitter Slide Out Menu
Let's begin this mini series with a little bit of UI work that will lay the foundation of our Slide Out Menu. First we'll construct our main UINavigationController that will hold the home screen's ViewController components. Next we'll set up the necessary navigation button, called a UIBarButtonItem, that triggers the menu reveal.

Comments (8)
daishengliang@gmail.com
4 years ago
oh! I am the first?
duypham
4 years ago
I'm second :) Thanks Brian for this course
Steven Verheyen
4 years ago
Looking forward to this course! Thanks you for all your helpful tutorials!
pawelcichonski
4 years ago
I like your consistency in all of your projects. Properties at the top (usually as closures), viewdidload and then methods at the bottom. I've already created separate SlideController+UITableView for table methods. It's so much different to the code I encounter elsewhere like having just properties declared at the top and then they are defined and scattered in either viewDidLoad or functions.
Tube
4 years ago
Is this tableView going underneath the home Button? How can you restrict the table to the safe area?
Pakawat Srimahaprom
4 years ago
Hi Brian, do you know how to fix this error it's just annoying me when I'm run the code in a simulator objc[29833]: Class AXAccessQueue is implemented in both /Applications.... . . . One of the two will be used. Which one is undefined. 2018-10-21 11:25:56.579046+0700 SlideOutMenuLBTA[29833:3683035] [AXMediaCommon] Unable to look up screen scale 2018-10-21 11:25:56.579361+0700 SlideOutMenuLBTA[29833:3683035] [AXMediaCommon] Unexpected physical screen orientation 2018-10-21 11:25:56.641853+0700 SlideOutMenuLBTA[29833:3683035] [AXMediaCommon] Unable to look up screen scale 2018-10-21 11:25:56.646064+0700 SlideOutMenuLBTA[29833:3683035] [AXMediaCommon] Unable to look up screen scale 2018-10-21 11:25:56.646156+0700 SlideOutMenuLBTA[29833:3683035] [AXMediaCommon] Unexpected physical screen orientation
mike.pujol
4 years ago
I got the same issue check out the link below. It doesn't explain the source but it will stop it from popping up. https://stackoverflow.com/questions/52410471/unable-to-look-up-screen-scale-and-unexpected-physical-screen-orientation-in-xco
Pakawat Srimahaprom
4 years ago
Thank you Mike, at least it solved my problem.
Tokyojogo
4 years ago
Hi Brian, I wanted to ask a question before I purchase this. Will this work if my tableview cells have a swipe function (left and right swipe) that opens up options inside the cell? Thank you.
jwaples
4 years ago
Hi Brian, What is the difference between these two lines of code under the cellForRowAt ...? let cell = tableView.dequeueReusableCell(withIdentifier: cellid, for: indexPath) let cell = UITableViewCell(style: .default, reuseIdentifier: cellid)
jwaples
4 years ago
I guess you would use dequeueReusableCell if you wanted to find the right indexPath for different classes, like if you set up class Book { let title: String let author: String ... } and also set up a function to call books from an initializer, like let book1 = Book{title: "Book1 Title", author: "Book 1 Author") but if you don't do any of this work, there's no need to dequeue, just use = UITableViewCell ?
henrybear
4 years ago
It's more about reusing resources :)
HELP & SUPPORT