I am under the program in the simulator iOS 6.1/5.0 run properly, but iOS7 was invalid,
Will crash if you do not manually click on the layer directly back view
[ITableView selectRowAtIndexPath: [NSIndexPath indexPathForRow: 0 inSection: 0] animated: NO scrollPosition: UITableViewScrollPositionTop];
MAC mini (Mac OS X 10.9) + Xcode 5.0.1
Reply:
In the implementation of this line of code to make sure your tableview already loaded. At least the row index 0 must exist, otherwise, the program will be reported should be the exception
Reply:
In ah!
It just does not have to be elected to the effect on the screen, you must manually go to your own point,
Will have anti-white, this time there will be no problem back one level.
If you do not have any anti-white situation the next time it will crash when a layer,
System stops at main.m, and no error message
I was added to the command line
- (Void) tableView: (UITableView *) tableView commitEditingStyle: (UITableViewCellEditingStyle) editingStyle forRowAtIndexPath: (NSIndexPath *) indexPath
Reply:
Ah! Supplement:
I was on
- (Void) tableView: (UITableView *) tableView commitEditingStyle: (UITableViewCellEditingStyle) editingStyle forRowAtIndexPath: (NSIndexPath *) indexPath
The selectRowAtIndexPath: could this be, as elsewhere, did not notice.
Mainly when user click on [delete] Then, in commitEditingStyle: NSMutableArray really delete the data and re-display
So this time needs its own designated selectRowAtIndexPath:, because the system is no default
No comments:
Post a Comment