• 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
Dealing with faults in CoreData / AppleScript
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Dealing with faults in CoreData / AppleScript


  • Subject: Dealing with faults in CoreData / AppleScript
  • From: Greg Hoover <email@hidden>
  • Date: Thu, 19 Nov 2009 19:19:33 -0800

I've been working through adding scriptability to my CoreData application but ran into a snag: accessing relationships may return a fault instead of the actual set of objects.  Is there an "accepted" way of solving this issue?  I don't want the accessor to "always" fault the objects in, just when they're being accessed from AppleScript.  Is creating another accessor the proper way to get around this?

Thanks,
Greg

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please 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

  • Follow-Ups:
    • Re: Dealing with faults in CoreData / AppleScript
      • From: Jim Correia <email@hidden>
  • Prev by Date: Re: tableView:setObjectValue:forTableColumn:row: not called when button pressed
  • Next by Date: resizing PDF obtained from dataWithPDFInsideRect:
  • Previous by thread: How to avoid text distortion
  • Next by thread: Re: Dealing with faults in CoreData / AppleScript
  • Index(es):
    • Date
    • Thread