could you please specify Swift version for each lesson you sale, that way we are up to date with the version of Swift.

i just purchased $20.00 course and the version of Swift is 3. witch is outdated.

Having only four menu items, I wouldn't make the tableView in the menu scrollable at all, though. Twitter probably did this because they support landscape mode, which gives the menu a lot less space to show its selectable items. It totally depends on the design of your application of course :)

The intrinsic size thing sure comes in handy sometimes, BUT... We are setting exact sizes in points! This goes against auto layout, size classes, etc. Doesn't seem like good practice?

I think SpacerView also is a hack. UIStackView has a method 'open func setCustomSpacing(_ spacing: CGFloat, after arrangedSubview: UIView)'.

Everything is very clear to this point. I am just trying to understand one thing if I may. In the logic for velocity: //so before our 'main logic' of opening and closing the menu, we are checking the following if isMenuOpened { //if menu is OPENED and we want to slide it to the left to hide it if abs(velocity.x) > velocityThreshold { If the value of velocity is less than 500 = close the menu closeMenu() return } //next logic if abs(translation.x) < menuWidth / 2 { // ????????????? QUESTION BELOW ??????????????? openMenu() } else { closeMenu() } } else { //If the menu is CLOSED and we want to slide it to the right to open it if abs(velocity.x) > velocityThreshold { //if greater than value of 500 then we are going to open the menu openMenu() return } //'main logic' if translation.x < menuWidth / 2 { //if it's less than half open (to the right) then close it back to the left closeMenu() //from 0 to 150 = close } else { //if it's more than half open (to the right) then open it completely openMenu() // } } "if abs(translation.x) < menuWidth / 2" - HAVE NO IDEA WHAT THIS LOGIC IS FOR. WHY DO WE CHECK FOR THE ABSOLUTE VALUE OF TRANSLATION.X ??? IT IS SIMILAR TO THE LOGIC of translation.x < menuWidth / 2 BUT THE RESULTS ARE SWAPED (open menu or else close).

You're just brilliant with StackViews

I have no idea why my menu don't want to load the header ~_~

Hi Brian, I tweaked the handleEnded function just a tad for some better (I think) calculations. Currently, I found a bug that if you open the menu and then pan really fast towards the right the menu closes even though it should be open. And when the menu is closed and you pan really fast towards the left the menu should stay close but instead opens. I thought this was because of the absolute value calculation with the velocity and originally didn't think it would matter but after making a tweak with lines 69 and 79 I found it fixed the bug. I didn't want to change that math but instead wanted to check for the translation direction to allow the velocity to only work when panning in the right translation.x direction. So with my way the menu only opens when the speed is greater than the threshold and the translation is positive. It will respectively only close when the translation is negative. if isMenuOpened { if abs(velocity.x) > velocityOpenThreshold && translation.x < 0 { closeMenu() return } if abs(translation.x) < menuWidth / 2 { openMenu() } else { if translation.x > 0 { openMenu() } else { closeMenu() } } } else { if abs(velocity.x) > velocityOpenThreshold && translation.x > 0 { openMenu() return } if translation.x < menuWidth / 2 { closeMenu() } else { openMenu() } }

nice videos