Clancey / FlyoutNavigation

Other
95 stars 87 forks source link

Navigation menu overlaps with Carrier name on iOS 7 #47

Closed slavb closed 10 years ago

slavb commented 10 years ago

I have got the latest source code.

If I drag menu up in Sample project it overlaps the Carrier name.

What is wrong?

Thanks Slava

Clancey commented 10 years ago

The menu itself should be fine, but the sample content may not be doing proper view containment for iOS 7. That is not something this library takes care of.

slavb commented 10 years ago

Thanks for a quick response.

I guess you are right, this is not a library issue. ;-)

I am very happy with the library so far.

In regards to the menu formatting - I tried to fix this issue myself, but did not get far unfortunately.

Would it be possible for you to have a look into the sample project - maybe it is something simple to fix?

Kind regards Slava

Clancey commented 10 years ago

Check out some of the stack overflow questions on this topic. http://stackoverflow.com/questions/18900428/ios-7-uitableview-shows-under-status-bar

http://blog.jaredsinclair.com/post/61507315630/wrestling-with-status-bars-and-navigation-bars-on-ios-7

slavb commented 10 years ago

The links helped - I managed to make my menu look OK.

Another issue - for all the child view controllers I invoke from the menu navigation controller's toolbar appears outside of the bounds (Y is more than screen height) and is not visible. Also I cannot seem to click on anything on the bottom of the screen - probably again some strange iOS 7 issue.

Would you know what is wrong? I could not find anything in Google.

Thanks

On Fri, Feb 14, 2014 at 9:20 AM, James Clancey notifications@github.comwrote:

Check out some of the stack overflow questions on this topic.

http://stackoverflow.com/questions/18900428/ios-7-uitableview-shows-under-status-bar

http://blog.jaredsinclair.com/post/61507315630/wrestling-with-status-bars-and-navigation-bars-on-ios-7

Reply to this email directly or view it on GitHubhttps://github.com/Clancey/FlyoutNavigation/issues/47#issuecomment-35033456 .

Clancey commented 10 years ago

I have no idea what you are doing that is causing that. I suggest you create a small sample reproducing the problem. Once you get that, post it in the Xamarin forums.

slavb commented 10 years ago

Another sleepless night and I have figured it out.

My AppDelegate was missing a line

window = new UIWindow (UIScreen.MainScreen.Bounds);

Not sure why this happened.

All is good - thanks for a great component! I need to find one for Android now.

On Mon, Feb 17, 2014 at 5:41 AM, James Clancey notifications@github.comwrote:

I have no idea what you are doing that is causing that. I suggest you create a small sample reproducing the problem. Once you get that, post it in the Xamarin forums.

Reply to this email directly or view it on GitHubhttps://github.com/Clancey/FlyoutNavigation/issues/47#issuecomment-35206346 .

Clancey commented 10 years ago

https://github.com/garuma/FlyOutMenu ;)

slavb commented 10 years ago

Fantastic!

Will give it a go

Thanks

On Tue, Feb 18, 2014 at 3:48 PM, James Clancey notifications@github.comwrote:

https://github.com/garuma/FlyOutMenu ;)

Reply to this email directly or view it on GitHubhttps://github.com/Clancey/FlyoutNavigation/issues/47#issuecomment-35352359 .