Re: Getting behind NSBeep
Re: Getting behind NSBeep
- Subject: Re: Getting behind NSBeep
- From: Andreas Monitzer <email@hidden>
- Date: Fri, 15 Feb 2002 18:11:10 +0100
On Friday, February 15, 2002, at 05:41 , Bill Cheeseman wrote:
It used to be that calling NSBeep() twice in succession played two
system
beep sounds in succession. In some recent version of Mac OS X, this
broke,
and it now only sounds once.
An Apple engineer told the applescript-users mailing list a while ago
that
the same phenomenon observed in recent versions of AppleScript is
caused by
two system beeps playing simultaneously -- that is, the second beep
doesn't
wait for the first beep to finish.
I assume this is a bug lying somewhere deep in the system, and that it
will
be fixed very soon. If I'm wrong about that, I'd like to know it.
I think that it's not a bug, but a feature. In earlier versions of Mac
OS X I sometimes accidentally put something (like a book) onto the
keyboard and had to listen to the "invalid input" beeps for half an hour
or longer.
andy
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.