Re: NSManagedObjectContext's undoManager is nil on macOS

2018-09-06 Thread Rick Mann 
"although remember that both NSError** out parameters and exceptions are 
autoreleased and do not escape block lexical scope happily"

That statement needs to be linked to clarification.

> On Sep 6, 2018, at 12:56 , Jeff Nadeau  wrote:
> 
> This behavior changed in 10.12  for applications linked against that SDK or 
> later. It’s listed in the “Behavioral changes” section of the Core Data 
> release notes for that year: 
> https://developer.apple.com/library/archive/releasenotes/General/WhatNewCoreData2016/ReleaseNotes.html#//apple_ref/doc/uid/TP40017342-CH1-DontLinkElementID_10
>  
> 
> 
> There's a documentation bug to correct the information on the 
> NSManagedObjectContext class doc. I’ll give it a little bump.
> 
> Going forward, you can set the undoManager property with your own 
> NSUndoManager after you’ve initialized the context.
> 
> - Jeff
> 
>> On Sep 5, 2018, at 7:33 PM, Dave Fernandes  
>> wrote:
>> 
>> The docs say:
>> "In macOS, a context provides an undo manager by default; on iOS, the undo 
>> manager is nil by default.”
>> 
>> However, I am finding on macOS 10.13.6, the undoManager is always nil when 
>> creating a MOC. Is this new behavior expected for High Sierra, or is it a 
>> bug?
>> ___
>> 
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> 
>> 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:
>> https://lists.apple.com/mailman/options/cocoa-dev/jnadeau%40apple.com
>> 
>> This email sent to jnad...@apple.com
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/rmann%40latencyzero.com
> 
> This email sent to rm...@latencyzero.com


-- 
Rick Mann
rm...@latencyzero.com


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: NSManagedObjectContext's undoManager is nil on macOS

2018-09-06 Thread Dave Fernandes 
Ah - thank you! I should read those release notes more carefully. Will close 
the bug I just filed.

> On Sep 6, 2018, at 3:56 PM, Jeff Nadeau  wrote:
> 
> This behavior changed in 10.12  for applications linked against that SDK or 
> later. It’s listed in the “Behavioral changes” section of the Core Data 
> release notes for that year: 
> https://developer.apple.com/library/archive/releasenotes/General/WhatNewCoreData2016/ReleaseNotes.html#//apple_ref/doc/uid/TP40017342-CH1-DontLinkElementID_10
>  
> 
> 
> There's a documentation bug to correct the information on the 
> NSManagedObjectContext class doc. I’ll give it a little bump.
> 
> Going forward, you can set the undoManager property with your own 
> NSUndoManager after you’ve initialized the context.
> 
> - Jeff
> 
>> On Sep 5, 2018, at 7:33 PM, Dave Fernandes > > wrote:
>> 
>> The docs say:
>> "In macOS, a context provides an undo manager by default; on iOS, the undo 
>> manager is nil by default.”
>> 
>> However, I am finding on macOS 10.13.6, the undoManager is always nil when 
>> creating a MOC. Is this new behavior expected for High Sierra, or is it a 
>> bug?
>> _
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: NSManagedObjectContext's undoManager is nil on macOS

2018-09-06 Thread Jeff Nadeau 
This behavior changed in 10.12  for applications linked against that SDK or 
later. It’s listed in the “Behavioral changes” section of the Core Data release 
notes for that year: 
https://developer.apple.com/library/archive/releasenotes/General/WhatNewCoreData2016/ReleaseNotes.html#//apple_ref/doc/uid/TP40017342-CH1-DontLinkElementID_10
 


There's a documentation bug to correct the information on the 
NSManagedObjectContext class doc. I’ll give it a little bump.

Going forward, you can set the undoManager property with your own NSUndoManager 
after you’ve initialized the context.

- Jeff

> On Sep 5, 2018, at 7:33 PM, Dave Fernandes  wrote:
> 
> The docs say:
> "In macOS, a context provides an undo manager by default; on iOS, the undo 
> manager is nil by default.”
> 
> However, I am finding on macOS 10.13.6, the undoManager is always nil when 
> creating a MOC. Is this new behavior expected for High Sierra, or is it a bug?
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/jnadeau%40apple.com
> 
> This email sent to jnad...@apple.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com