-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for SafeArea #24
Comments
please can provide me all code kindly |
@1mohmmad4 Maybe you can use safe area layout to fix this problem.
|
Ive tried using Safe Area Layout but for some reason it is still cut off. |
Hello, @tuyen-vuduc could you add the above code snippet, safe area is too much important nowadays. Thank you |
Hello, @alexmartinezm . Your above approach treat only safe area for the top, but for the bottom also needs to be considered. Thanks |
@danpadua |
Hello,
I have seen that there is no support for SafeArea, required by iPhone X, Xs, and so on. To achieve this, I have set the top SafeAreaInsets like this:
var marginTop = UIApplication.SharedApplication.Windows[0].SafeAreaInsets.Top;
Then, maringTop should be applied in the first VisualFormat constraint, specifically on TopTabbedRenderer.
The constraint would look like this:
View.AddConstraints(NSLayoutConstraint.FromVisualFormat($"V:|-{marginTop}-[tabbar]-0-[content]-0-|", 0, null, views));
I hope that you can include this on the next release.
Regards,
Àlex MM.
The text was updated successfully, but these errors were encountered: