Re: Beep broken in 10.1.4?
Re: Beep broken in 10.1.4?
- Subject: Re: Beep broken in 10.1.4?
- From: Christopher Nebel <email@hidden>
- Date: Thu, 25 Apr 2002 13:23:51 -0700
On Wednesday, April 24, 2002, at 05:41 PM, Sander Tekelenburg wrote:
At 12:53 -0700 UTC, on 23-04-2002, Christopher Nebel wrote:
The other problem is that sound output channels are considered
application resources in Mac OS X and are released when the application
terminates, even if they're not done playing. So the application
starts
to play a beep, then terminates, and the sound gets cut off.
Interesting. Would that lead to the logical conclusion that using
tell me
beep
quit
end tell
should ensure that the beep is actually played? I mean, I can see how
telling
another process to beep and then quit yourself would lose the beep. But
when
you tell yourself to beep and then quit, it seems reasonable to not quit
before having beeped.
You've got it exactly backwards. When a process quits, all its sound
channels are immediately released, whether they're done playing or not.
When you tell some other application to beep, that process is
responsible for playing the sound, so it doesn't matter whether you quit
or not.
Btw, IIRC you can have multiple beeps in Mac OS X if you're willing to
spell
them out:
beep
beep
beep
Only if you've got a sufficiently slow machine, and nothing that will
run Mac OS X is.
--Chris Nebel
AppleScript Engineering
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.