Re: Idle handling, just not grokking it.
Re: Idle handling, just not grokking it.
- Subject: Re: Idle handling, just not grokking it.
- From: Bill Briggs <email@hidden>
- Date: Thu, 15 Nov 2001 13:53:40 -0400
At 9:25 AM -0800 15/11/01, Paul Berkowitz wrote:
On 11/15/01 8:54 AM, "Bill Briggs" <email@hidden> wrote:
At 11:28 AM -0500 15/11/01, Bill Cheeseman wrote:
What isn't working is the beeps. The simple script 'beep 2' or 'beep
3' only beeps once. I just verified this in AppleScript 1.7. How
could it not work in AppleScript 1.4 and 1.7? My old Script
Additions guide says this is proper syntax. I'm missing something
here, myself.
I'm experiencing the same phenomenon in 10.1. Multiple beep commands
give a solitary beep. It's as if the argument wasn't understood.
It seems to me we've heard about this before. There was an odd explanation,
along the lines of "it beeps too fast to hear any after the first" or
something like that.
I think you're talking about Chris Nebel's post (see below). In the
post he indicated that even a single beep wouldn't be heard unless a
delay was introduced, yet we get single beeps. Multiples are the ones
that go missing. Maybe he'll tell us what's going on.
- web
---------- reprint of earlier post ----------
Subject: Re: Script Menu In OS X
Cc: Applescript Users <email@hidden>
To: John W Baxter <email@hidden>
From: Christopher Nebel <email@hidden>
Date: Tue, 30 Oct 2001 16:54:05 -0800
On Tuesday, October 30, 2001, at 08:28 AM, John W Baxter wrote:
At 2:47 -0500 10/30/2001, Chris Nebel wrote:
It's a little weird about it, though -- if it doesn't see
"#!/usr/bin/perl", it executes it using /bin/sh, which means you can't
throw an arbitrary script at it. E.g., you couldn't use a csh script by
leading off with "#!/bin/csh". This might be construed as a feature,
but I'd consider it an iffy one at best.
Takes a powrful lot of construin' to call that a fitcher. ;-)
True, but you never know. I asked around, and it wasn't considered a
feature, merely a hack to get something usable in time for Seybold.
The author has agreed to revisit the issue soonish.
Selecting this one makes no sound.
#!/usr/bin/python
print """\aThis is a test"""
Your problem there is probably something else, since that's a valid
sh script as well. There's an architectural design point that makes
it difficult to write a script that beeps as its final action. The
difficulty is that sound output is owned by the process itself, so if
it plays an asynchronous sound (which "beep" always does) and
immediately terminates, the process, and therefore any sound output
it called for, is destroyed before you ever hear anything. You can
see the same thing with osascript:
osascript -e "beep" # the sound of silence...
osascript -e "beep" -e "delay 1" # now it beeps!
--Chris Nebel
AppleScript Engineering