Skip to main content

UIViewController view is overlapped with the Navigation and Status bar

Background:

Since iOS7 release status bar is part of your  the view. It is the common problem faced in application that navigation and status bar overlapped with your view content when you use nib or xib files.


                XIB                                          Actual result

I have seen in some application that to fix this problem view content is start from 64 pixel down. But it can raise other problem in the applications. So question is:

How To Fix This ?

Solution 1:

In View did load you can add the following line:

[self setEdgesForExtendedLayout:UIRectEdgeNone];

Example:

- (void)viewDidLoad {
    [super viewDidLoad];
    // Do any additional setup after loading the view, typically from a nib.
    [self setEdgesForExtendedLayout:UIRectEdgeNone];
}

edgesForExtendedLayout
This property tells which sides of your view can be extended to cover the whole screen. If you push a UIViewController into a UINavigationController, when the view of that view controller is laid out, it will start where the navigation bar ends, but this property will set which sides of the view (top, left, bottom, right) can be extended to fill the whole screen.
DefaultValue: UIRectEdgeAll (That is the reason your view is overlapping to Navigation bar and status bar. Because it try to cover whole screen).
UIRectEdgeNone: By this property we are specifying do not extend to any side. So it is fit.
Reference : Stackoverflow

Solution 2:

Set the translucent property of navigation bar of UINavigationController to No. By default it is "yes".

UINavigationController* navController = [[UINavigationController alloc] initWithRootViewController:viewController];
navController.navigationBar.translucent = NO; 





Comments

Post a Comment

Popular posts from this blog

Best Practices in iOS with Objective - C

In this post i am making collection of points which i read from some other post or some documentation. Today we will learn what are good or bad habits while doing programming in objective - c. 1) Instance Type and id I noticed one day that in iOS SDK init method of class has  instancetype  as a return value. I am curious to know about this thing and why this type not id. So what i found is following: Example: - ( instancetype )initWithProximityUUID:( NSUUID *)proximityUUID identifier:( NSString *)identifier What is instancetype? Suppose you are writing a method for object initialisation and according to objective c coding convention you need to return the object of same class from the method. So you can use instance type as a return type of method. Instance Type -  It represents the instance of the class or subclass of the class in which you are writing the method with return type instancetype. Confusing ? Let suppose i have declare a class empl...
Post a Comment
Read more

Constant Weds Literals Venue Objective C

Arrangement: While working on a application you may have used some predefined values. The visibility of these values can be application level, feature level or class level. For the  convenience  we give name to these values and then use in the application. In this case the name given by you only representing the single value and it never change to represent some other value thats why it is called Constant. On the other hand variables are like us doing jobs in IT World and can switch from one organization( value ) to other. Like while choosing a partner for marriage you may choose best for you by seeing multiple persons and still after sometime you feel stuck. Same may happen you choose a best option to declare a constant and after sometime this constant can create a issue for you in code due to its scope or any other reason. On the other hand you may have a fixed mind that you always declare a constant in a same way in any situation like a love ma...
Post a Comment
Read more

What does enable bitcode do in Xcode

Background: Now days compilation process for any language is divided into two parts and same is applicable for objective c. Frontend Compiler (Clang) Backend Compiler (LLVM) Frontend Compiler (Clang):  Responsibility of front-end compiler is to take a source code and convert into intermediate representation (IR).  In case of clang it is LLVM IR.  Backend Compiler(LLVM):  Responsibility of backend compiler is to take a IR as input and convert into object code. LLVM input is bitstream of LLVM IR (Bitcode) and output is sequence of machine instruction(Object code). Each  cpu or processor has different set of  M achine   instruction, So  LLVM output is CPU dependent or it can be executed on specific CPU only.   There may be question in your mind that  1) What is the need to divide into these phases? 2) What is LLVM IR? Can we see the LLVM IR as Output? What is the need to divid...
Post a Comment
Read more