• 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: Observing NSArrayController's content, shouldn't it be simple ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Observing NSArrayController's content, shouldn't it be simple ?


  • Subject: Re: Observing NSArrayController's content, shouldn't it be simple ?
  • From: George Orthwein <email@hidden>
  • Date: Mon, 7 May 2007 17:30:59 -0400

On May 7, 2007, at 4:06 AM, Yann Bizeul wrote:

But all I get each time I add an object is :
{kind = 1; new = <null>; old = <null>; }

Short answer is: this is an old known bug, AFAIK. You must observe the source Array to get new/old values.


Since there is no source array with Core Data, you can either loop through and compare old/new manually... or you could possibly use NSNotifications. Also see NSManagedObjectContextObjectsDidChangeNotification.

Others may have better ideas. :)

George
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Observing NSArrayController's content, shouldn't it be simple ? (From: Yann Bizeul <email@hidden>)

  • Prev by Date: Re: Leaks with Core-Data while fetching data
  • Next by Date: n00b cocoa bindings question
  • Previous by thread: Observing NSArrayController's content, shouldn't it be simple ?
  • Next by thread: Re: Observing NSArrayController's content, shouldn't it be simple ?
  • Index(es):
    • Date
    • Thread