[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData unresolved keypath after save

Subject: Re: CoreData unresolved keypath after save
From: Noah Lieberman <email@hidden>
Date: Mon, 31 Jul 2006 22:32:42 -0700
Delivered-to: email@hidden
Delivered-to: email@hidden

Thanks, unfortunately it's with newly saved files... it's not a datamodel format issue.

Anyone else have any ideas?

Thanks,

Noah


On 31-Jul-06, at 10:07 , George Orthwein wrote:

Does this happen with new saved files or are you opening a saved doc from a previous version? (i.e. did you just add the flightDate attribute?)

If the latter, the result here would apply: http://www.google.com/search?hl=en&q=NSRunLoop+ignoring+exception+% 27unresolved+keypath&btnG=Google+Search
If the former... I dunno. :)
George

| | | Noah Lieberman | President | Coradine | 250-354-1135 | AIM:email@hidden ---- "When Once you have tasted flight, you will forever walk the earth with your eyes turned skyward, for there you have been, and there you will always want to be." -Leonardo da Vinci

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

This email sent to email@hidden

References:
	>CoreData unresolved keypath after save (From: Noah Lieberman <email@hidden>)
	>Re: CoreData unresolved keypath after save (From: George Orthwein <email@hidden>)

Prev by Date: Re: Checkbox in NSOutlineView. Must move mouse > 3 pixels to toggle
Next by Date: Re: NSMenuItem protocol and incompatible types.
Previous by thread: Re: CoreData unresolved keypath after save
Next by thread: Hit-detection via NSApp's -sendEvent:
Index(es):
- Date
- Thread

Home