You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the additional content support of BSManagedDocument and I'm curious as to the best place to put initialization code for new "Untitled" documents from the additional content perspective. For typical NSDocument subclasses one would use initWithType:error:, and for initializing CoreData aspects of the document with BSMD I am assuming that configurePersistentStoreCoordinatorForURL:ofType:modelConfiguration:storeOptions:error: is where I would do that. If I override initWithType:error: will that interfere with the CoreData initialization that BSMD handles? Thanks for any input.
The text was updated successfully, but these errors were encountered:
You should be fine to treat this like any regular document (assuming you're not planning to do something like writing to disk), and override initWithType:error:. Just make sure to call super! (I imagine failing to call it would break a great deal more than BSManagedDocument, mind 😄)
I'm using the additional content support of BSManagedDocument and I'm curious as to the best place to put initialization code for new "Untitled" documents from the additional content perspective. For typical NSDocument subclasses one would use initWithType:error:, and for initializing CoreData aspects of the document with BSMD I am assuming that configurePersistentStoreCoordinatorForURL:ofType:modelConfiguration:storeOptions:error: is where I would do that. If I override initWithType:error: will that interfere with the CoreData initialization that BSMD handles? Thanks for any input.
The text was updated successfully, but these errors were encountered: