• 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: Why would a working -[NSInvocation invoke] call NSBeep() ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why would a working -[NSInvocation invoke] call NSBeep() ?


  • Subject: Re: Why would a working -[NSInvocation invoke] call NSBeep() ?
  • From: Jerry Krinock <email@hidden>
  • Date: Wed, 21 Dec 2011 19:08:55 -0800

On 2011 Dec 05, at 13:14, Greg Parker wrote:

> You should file a bug report asking for -beginSheet:... to log a real error message or throw an exception instead of beeping.

Done (a few weeks ago, forgot to send this).  Problem ID is 10557689.

_______________________________________________

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: 
 >Why would a working -[NSInvocation invoke] call NSBeep() ? (From: Jerry Krinock <email@hidden>)
 >Re: Why would a working -[NSInvocation invoke] call NSBeep() ? (From: Greg Parker <email@hidden>)

  • Prev by Date: Re: CoreData and 3 level Master/Detail tableView
  • Next by Date: Get property values of a UI element in an Cross-possess manner without Accessibility APIs ?
  • Previous by thread: Re: Why would a working -[NSInvocation invoke] call NSBeep() ?
  • Next by thread: NSComboBoxCell drop down programmatically
  • Index(es):
    • Date
    • Thread