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

2011-12-21 Thread Jerry Krinock
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. ___

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

2011-12-05 Thread Greg Parker
On Dec 4, 2011, at 5:49 PM, Jerry Krinock wrote: > At one point, running in Mac OS 10.7, one of my invocations gets invoked, and > … > > #00x913761fa in NSBeep > #10x9b6f0e1d in __invoking___ > #20x9b6f0d59 in -[NSInvocation invoke] > #30x976458ea in __NSFireDelayedPerform > #4

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

2011-12-04 Thread Kyle Sluder
On Dec 4, 2011, at 5:49 PM, Jerry Krinock wrote: > At one point, running in Mac OS 10.7, one of my invocations gets invoked, and > … > > #00x913761fa in NSBeep > #10x9b6f0e1d in __invoking___ > #20x9b6f0d59 in -[NSInvocation invoke] > #30x976458ea in __NSFireDelayedPerform > #4

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

2011-12-04 Thread Jerry Krinock
At one point, running in Mac OS 10.7, one of my invocations gets invoked, and … #0 0x913761fa in NSBeep #1 0x9b6f0e1d in __invoking___ #2 0x9b6f0d59 in -[NSInvocation invoke] #3 0x976458ea in __NSFireDelayedPerform #4 0x9b6b0996 in __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CAL