There are two distinct dot syntaxes being used here. They look the same, but they do different things depending on what they are operating on and what is being done with it: The first myView.frame is a shorthand for [myView frame], a method call that returns a CGRect struct by value. myFrame.origin.x is accessing ordinary … Read more
One way to solve this is to re-declare the property in your subclass’s class extension, and then add an @dynamic statement so that the compiler won’t create an overriding implementation of that property. So something like: @interface SuperClass () @property (nonatomic, strong) id someProperty; @end …. @interface SubClass () @property (nonatomic, strong) id someProperty; @end … Read more
It is still recommended to copy because you want to avoid something passing a mutable string and then changing it without you knowing. A copy guarantees that the string you have will not change.
If you are using the Modern Objective-C Runtime (that’s either iOS 3.x or greater, or 64-bit Snow Leopard or greater) then you do not need to define ivars for your properties in cases like this. When you @synthesize the property, the ivar will in effect be synthesized also for you. This gets around the “fragile-ivar” … Read more
Nonatomic Nonatomic will not generate threadsafe routines thru @synthesize accessors. atomic will generate threadsafe accessors so atomic variables are threadsafe (can be accessed from multiple threads without botching of data) Copy copy is required when the object is mutable. Use this if you need the value of the object as it is at this moment, … Read more