• 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
RE: Return values of NSAlert
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Return values of NSAlert


  • Subject: RE: Return values of NSAlert
  • From: Lee Ann Rucker <email@hidden>
  • Date: Wed, 22 Oct 2014 06:17:58 +0000
  • Thread-topic: Return values of NSAlert

Even the old selector-based one could return NSModalResponse values - I saw it happen once in some over-paranoid code that had a switch for the resultCode and an assert in the default case. Surprise, it wasn't handling Abort.

NSSavePanel doc shows it as just

- (void)beginSheetModalForWindow:(NSWindow *)window completionHandler:(void (^)(NSInteger result))handler

Apple probably decided NSModalResponse was more specific and didn't update the docs to say that's what we'd been getting all along.
________________________________________
From: cocoa-dev-bounces+lrucker=email@hidden [cocoa-dev-bounces+lrucker=email@hidden] on behalf of Gerriet M. Denkmann [email@hidden]
Sent: Tuesday, October 21, 2014 8:59 PM
To: email@hidden
Subject: Return values of NSAlert

NSAlert has: - (void)beginSheetModalForWindow:(NSWindow *)sheetWindow
               completionHandler:(void (^)(NSModalResponse returnCode))handler

NSModalResponse has three values: Stop, Abort, Continue - none of which bear any resemblance with the buttons: Default, Alternate, Other in my NSAlert.

Also the actually returned values are not among those in NSModalResponse.

They look like NSAlertDefaultReturn, NSAlertAlternateReturn instead - but this clearly cannot be the case, as these values are deprecated: "These constants are deprecated in 10.9 and will be formally deprecated in the following release"

The suggested alternative is NSAlertFirstButtonReturn, etc., which have values, which very much unlike the actual returned values.

And the header mentions:
"Note that these return values (i.e. NSAlertFirstButtonReturn  etc. ) do not apply to an NSAlert created via +alertWithMessageText:defaultButton:alternateButton:otherButton:informativeTextWithFormat:, which instead uses the same return values as NSRunAlertPanel.  See NSAlertDefaultReturn, etc. in NSPanel.h"

Which brings us back to the already deprecated values.

I am mightily confused.

Maybe somebody understands this.

Gerriet.


_______________________________________________

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
_______________________________________________

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


References: 
 >Return values of NSAlert (From: "Gerriet M. Denkmann" <email@hidden>)

  • Prev by Date: Re: Return values of NSAlert
  • Next by Date: iOS table views using multiple cell subclasses.
  • Previous by thread: Re: Return values of NSAlert
  • Next by thread: iOS table views using multiple cell subclasses.
  • Index(es):
    • Date
    • Thread