Re: getting behind NSBeep
Re: getting behind NSBeep
- Subject: Re: getting behind NSBeep
- From: Michael Hopkins <email@hidden>
- Date: Fri, 15 Feb 2002 16:28:41 -0800
This wouldn't be a bug in Cocoa. NSBeep() calls SysBeep() from the Carbon
API, so the issue is related to a change in the implementation of SysBeep()
and doesn't have anything to do with Cocoa. There was probably no mention in
the cocoa release notes because nothing in NSSound has changed.
I believe that SysBeep() was changed so that it does not trigger a new sound
if one is already playing. This was a fix that requested because people in
the mac community were notorious for having multiple second beeps and wound
get really annoyed if too many beeps were queued up.
-Michael Hopkins
On 2/15/02 12:57 PM, "email@hidden"
<email@hidden> wrote:
>
Date: Fri, 15 Feb 2002 13:32:26 -0500
>
Subject: Re: Getting behind NSBeep
>
From: Bill Cheeseman <email@hidden>
>
To: Cocoa-Dev Mail <email@hidden>
>
>
on 02-02-15 12:11 PM, Andreas Monitzer at email@hidden wrote:
>
>
> 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.
>
>
If that were so, one would expect to read about the change in the Cocoa
>
release notes. But there's nothing there.
>
>
And it certainly wouldn't have surprised the AppleScript engineers, who were
>
in fact surprised to discover that AppleScript's very common "beep n"
>
command doesn't work any more.
>
>
I think it's a bug, and I think it's deep in the system, not Cocoa-specific.
_______________________________________________
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.