Try adding nonatomic and strong to your property. @property (nonatomic, strong) IBOutlet UITextField *textField; Also, did you set the XIB in the storyboard to your subclass and drag the UITextField

Hi All, I’ve started move over to using the correct Manual Layout Methods as per my recent posts. The methods are: resizeWithOldSuperviewSize WindowTrackerView .view Property SubviewA All

@interface TextTableCell : UITableViewCell @property IBOutlet UITextField *textField; @end TableCellView.xib File’s Owner = TextTableCell Outlet textField = UITextField View UIView contains

Use an XIB for the subclass of tableViewCell, create a UIOutlet property for the UITextField, assign the subclass to the XIB’s class and wire up the UIOutlet property to the UITextField. Don’t

iOS 12, Xcode 10 I have a subclass of UITableViewController. The UITableView should use UITableViewCells with UITextFields (for data entry). So I created MyTableViewCellWithTextField which has:

NSMeasurementFormatter is a magical tool which converts all stuff just into the right form the user wants to see. But what about the other way round? I have a TextField labeled “Desired

Excellent. Just what I needed. Contrary to my expectations Celsius/Fahrenheit is *not* part of Locale, but set in System Preferences → Language & Region → Temperature. I can’t find “rounds

I haven't played with it myself, but maybe NSMeasurementFormatter? --Andy

I want to know, given a certain NSLocale (e.g. NSLocale.currentLocale), how to represent: Temperature (K, °C or whatever) Distance (km, miles, furlongs, lightyears, … ) Speed (m/sec, km/h,

Hi, It’s not so much it can’t handle it, its that it takes way to long to do the design in Xcode/Interface Builder and what I am doing is not that difficult but there is a lot of it. Also their

HI, Thanks for this, I did something like this a long while back and must have confused the “Display” path with the “Layout” path, thanks for putting me on the right track again. The its

That should be reasonable, I don’t recall whether you’ll need to create a mapping model or not to actually migrate the existing store. It does mean that all of the instances will wind up shoved

So, a little background. The model on the server has a number of types that inherit from a common class that contains a number of common properties. The original authors of the iOS app created a bunch

If you put the entities themselves in an inheritance relationship, Xcode will generate code reflecting that. I would only do this for “strongly” related entities though since entity inheritance

Hi Chris, Thanks, that’s good to know for the easy path. What about the case where I want to update the model to reflect the class hierarchy? Based on what the Common superclass will handle, I can

In fact you don’t even need a new model version, you can just refactor the code. We made sure that Core Data’s concept of entity inheritance is independent of class hierarchy, so you don’t

When you find a use case it doesn’t handle, consider the various container views available, and if those don’t help, definitely write a radar. Apple is always improving things, and if you report

This is incorrect: “layout” methods were added when autolayout was introduced in Lion (10.7). Before that, you used “frame” and “display” methods, and it was generally the responsibility

Hi, I’m confused then! The “layout” method has been around a lot longer than Auto Layout and it worked in conjunction with the Auto-Resizing options (defined in the Size Pane in IB). I assumed

I have inherited some code where Core Data entity classes look something like this: @interface Entity1 : NSManagedObject Something* common1; Something* common2; Something* common3; SomethingElse*