On Jun 13, 2018, at 19:22 , Casey McDermott wrote:
>
> Nearly always, the event loop is the best place to escape to.
This is not how current thinking goes, unless you mean something different from
what I think you’re saying.
If you’re implementing sanity (“should not happen”) checks, then the
We are updating a large Carbon accounting app to Cocoa. There is a ton of
C++ model-layer code. It originally was based on PowerPlant, but the new
interface is Objective-C
with many bridges to the C++.
Our Carbon event loop had a try/catch block, which caught most exceptions, and
then
continue
On Wed, 13 Jun 2018 15:26:26 -0700, James Walker said:
>Oh, cool. The " Information Property List Key Reference" seemed to
>indicate in one place that it's only for iOS, but now I see another
>place where it says macOS 10.8 and later. Do you happen to know if it
>works with the old AddressBoo
On 6/13/2018 12:58 PM, Sean McBride wrote:
On Wed, 13 Jun 2018 11:01:40 -0700, James Walker said:
On iOS, you can give the user a hint of why you need access to contacts
by putting a purpose string in the Info.plist. There isn't any way to
do that on macOS, is there?
There is: NSContactsUsage
___
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.c
On Wed, 13 Jun 2018 11:01:40 -0700, James Walker said:
>On iOS, you can give the user a hint of why you need access to contacts
>by putting a purpose string in the Info.plist. There isn't any way to
>do that on macOS, is there?
There is: NSContactsUsageDescription in your Info.plist
Cheers,
On iOS, you can give the user a hint of why you need access to contacts
by putting a purpose string in the Info.plist. There isn't any way to
do that on macOS, is there?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin
