• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Is this a bug in setKeys:triggerChangeNotificationForDependentKey:?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is this a bug in setKeys:triggerChangeNotificationForDependentKey:?


  • Subject: Re: Is this a bug in setKeys:triggerChangeNotificationForDependentKey:?
  • From: Tim Lucas <email@hidden>
  • Date: Wed, 27 Jul 2005 00:45:59 +1000

On 26/07/2005, at 12:47 PM, Óscar Morales Vivó wrote:

In one of my projects I've noticed that if in the +(void)initialize method of a base class I call setKeys:triggerChangeNotificationForDependentKey (and not call that same method with the same parameters for the derived class), it won't fire the corresponding key-value observing methods in my derived class.

I believe i've come across the same thing, but never had a chance to look into it further, so just duplicated the call in the derived class as well (this was outside of coredata).


I'll have a look in the next few days and see what I can come up with (and file a bug report as ncessary)

- tim lucas

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Is this a bug in setKeys:triggerChangeNotificationForDependentKey:? (From: Óscar Morales Vivó <email@hidden>)

  • Prev by Date: Re: NSDocument newbie
  • Next by Date: Re: Running out of memory with Core Data
  • Previous by thread: Is this a bug in setKeys:triggerChangeNotificationForDependentKey:?
  • Next by thread: File inspector application : document based or not ?
  • Index(es):
    • Date
    • Thread