iOS development · Macros and methods related to iPhone X adaptation

After a long time, today I finally have time to summarize the pitfalls related to adapting to iPhone X. Generally speaking, there are two kinds of pitfalls. One is that the height of the navigation bar + status bar has changed, and the other is that some UITableViews that do not implement proxy methods such as -tableView: viewForHeaderInSection: and -tableView: viewForFooterInSection: will be misplaced.

1. Determine whether it is an iPhone X: Return YES or NO

1.1 Judgment: Macro

(1) Based on screen resolution

Trinocular algorithm

 //Is it iPhoneX YES: iPhoneX screen NO : Traditional screen
 #define kIs_iPhoneX ([UIScreen instancesRespondToSelector:@selector(currentMode)] ? CGSizeEqualToSize(CGSizeMake(1125, 2436), [[UIScreen mainScreen] currentMode]. size ) : NO )

Multi-line logical judgment

 //Whether it is iPhoneX 1: iPhoneX screen 0: Traditional screen
 #define kIs_iPhoneX_test ({\
 int tmp = 0;\
 if ([UIScreen instancesRespondToSelector:@selector(currentMode)]) {\
    if (CGSizeEqualToSize(CGSizeMake(1125, 2436), [[UIScreen mainScreen] currentMode]. size )) {\
 tmp = 1;\
 } else {\
 tmp = 0;\
 }\
 } else {\
 tmp = 0;\
 }\
 tmp;\
 })

Among them, the backslash \ is not a comment or other useless symbol, but a necessary symbol for multi-line macro line breaks.

***The sentence tmp;\ is also necessary, because the tmp obtained through logical judgment is used as the return value of the macro.

(2) Based on screen size

 #define kIs_iPhoneX (kSCREEN_WIDTH == 375.f && kSCREEN_HEIGHT == 812.f)
 #define kSCREEN_WIDTH ([UIScreen mainScreen].bounds. size .width)
 #define kSCREEN_HEIGHT ([UIScreen mainScreen].bounds. size .height)

1.2 Judgment: Method

Method: According to the device model

 +(BOOL)getIs_iPhoneX{
    struct utsname systemInfo;
 uname(&systemInfo);
    NSString *platform = [NSString stringWithCString: systemInfo.machine encoding:NSASCIIStringEncoding]; 
      
    if([platform isEqualToString:@ "iPhone10,3" ]||[platform isEqualToString:@ "iPhone10,6" ]) {
 return YES;
 } else {
 return   NO ;
 }
 }

2. Flexible return status bar + navigation bar height

Requirement: Flexibly obtain the height of the navigation bar + status bar as the starting point of the Y axis of a subview.

Macro Definition

 #define kStatusBarAndNavigationBarHeight (kIs_iPhoneX ? 88.f : 64.f)

Calling Example

 //Automatic adaptation
 _segmentedControl.frame = CGRectMake(0, kStatusBarAndNavigationBarHeight, kSCREEN_WIDTH, 55);

3. Extension: Get iOS system and App version information

Get iOS system version number: Returns a string

 + (NSString *)getSystemVersion{
 return [[UIDevice currentDevice] systemVersion];
 }

Get App version number: Returns a string

 + (NSString *)getAppVersion{
    NSDictionary *infoDic = [[NSBundle mainBundle] infoDictionary];
 // Get the App version number
    NSString *appVersion = [infoDic objectForKey:@ "CFBundleShortVersionString" ];
 return appVersion;
 }

4. Other issues related to iPhone X adaptation

In the process of adapting to iPhone X and Xcode 9, in addition to problems related to the navigation bar, another problem that often occurs is the problem related to UITableView. The following two methods can solve most of the misalignment problems.

When VC creates tableView properties, set it like this

 self.tableView.estimatedRowHeight = 0;
 self.tableView.estimatedSectionHeaderHeight = 0;
 self.tableView.estimatedSectionFooterHeight = 0;

You can also set

 //cell adaptive height
 self.tableView.rowHeight = UITableViewAutomaticDimension;
 //Estimated row height
 self.tableView.estimatedRowHeight = 44.0f;

About the safe area of ​​​​the root view

iOS has added a safeArea. In the old code, the code that specifies the relationship between the subview and the root subview needs to add a judgment: when iOS 11 is released, it needs to be changed to the relationship between the subview and the root subview's safe area. In this way, there will be no interference from any controls on the virtual home at the bottom of the iPhone X.

 if (@available(iOS 11.0, *)) {
    make.edges.equalTo( self.view.safeAreaInsets )
 } else {
    make.edges.equalTo( self.view )
 }

Of course, except for the tabbar, other views such as tableView or web page view can be placed in the bottom virtual home area. At this time, there is no need to emphasize that the subview must be placed in the safeArea, and the original old code does not need to be changed.