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 had a layout issue caused by the following steps:
Modal presentation over the content view controller
Rotate the device
Dismiss the modally presented view
Now the content view is not sized properly
I traced these steps to viewWillTransition and specifically the following line: self.contentContainerView.frame = self.contentFrame(visibility: self.isMenuRevealed). For me, view.frame is not correct and instead should use the size argument to viewWillTransition in SideMenuController.swift. I changed the line to the following: self.contentContainerView.frame = CGRect(origin: .zero, size: size). This is probably a hack, but thought I'd bring it up in case you see the proper fix.
Best,
Chris
The text was updated successfully, but these errors were encountered:
First a viewController is pushed to the navigation and that rotates the screen horizontally
Then when that viewController is popped up the rotation is going back to vertical (portrait)
And then you can see the black portion in the screen shot which is part of SideMenuController because it has clear color.
I Could not manage to solve the problem. Hope you can emulate the problem and fix.
Because of this I will not be able to use this project.
Nevertheless I really liked it.
Best.
First off, great project! Simple and easy to use.
I had a layout issue caused by the following steps:
I traced these steps to
viewWillTransition
and specifically the following line:self.contentContainerView.frame = self.contentFrame(visibility: self.isMenuRevealed)
. For me,view.frame
is not correct and instead should use thesize
argument toviewWillTransition
inSideMenuController.swift
. I changed the line to the following:self.contentContainerView.frame = CGRect(origin: .zero, size: size)
. This is probably a hack, but thought I'd bring it up in case you see the proper fix.Best,
Chris
The text was updated successfully, but these errors were encountered: