On Feb 4, 2015, at 5:43 AM, Jonathan Mitchell jonat...@mugginsoft.com wrote:
On 4 Feb 2015, at 13:27, Roland King r...@rols.org wrote:
If I have an observation pattern which is set up, and the previous one torn
down, in setXXX:(id)xxx like you do then my dealloc usually goes
[ self
On Feb 4, 2015, at 05:43 , Jonathan Mitchell jonat...@mugginsoft.com wrote:
Is it normal for superclasses to message during dealloc?
I would still like to know what people’s expectations are here.
It is normal for classes to message during dealloc, so it’s normal for
superclasses to do so.
On 4 Feb 2015, at 21:16, Jonathan Mitchell jonat...@mugginsoft.com wrote:
In my arc app I dispose of observers in -dealloc.
The pattern I have established seems to work well but one case has me
rethinking my approach.
Everything pivots around NSViewController -representedObject;
-
In my arc app I dispose of observers in -dealloc.
The pattern I have established seems to work well but one case has me
rethinking my approach.
Everything pivots around NSViewController -representedObject;
- (void)setRepresentedObject:(id)object
{
if (self.representedObject) [self
On 4 Feb 2015, at 13:27, Roland King r...@rols.org wrote:
If I have an observation pattern which is set up, and the previous one torn
down, in setXXX:(id)xxx like you do then my dealloc usually goes
[ self setXXX:nil ]
which both removes the observers and sets the property to nil so
