Home/ Questions/Q 103249
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T01:05:39+00:00

I have a case where the child view sends notification to its parent view.

  • 0

I have a case where the child view sends notification to its parent view. Now I’m calling addObserver: in viewWillAppear: and removeObserver: in viewWillDisappear:. But, I’m guessing this is not correct since viewWillAppear: calls when view is refreshed. 

[[NSNotificationCenter defaultCenter] addObserver: (id)observer selector: (SEL)aSelector name: (NSString *)aName object: (id)anObject];  [[NSNotificationCenter defaultCenter] removeObserver: (id)observer name: (NSString *)aName object: (id)anObject];

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Actually, this is a bad idea. When memory gets low, your view controller may get sent a memory warning. The default behavior in this instance is to clear out your view (if you’re not currently on screen). In this case, you could get the viewDidLoad message sent a second time (after the memory event, when your view is brought back on screen by its navigation controller.) Thus you’ll have two registrations of the same object, but only one removal (in its dealloc)

    A better solution is either to set a flag saying you’ve registered, or to register in your init method.

    • 0