🚀 go-pugleaf

In article <1152@runx.ips.oz> sce@runx.ips.oz (Simon Evans) writes:
|
|Recently Brion Feinberg posted a patch to Smart Alarms that stopped
|its "incessant beeping". I thought I'd point out a couple of things
|that make this unnecessary (BTW Smart Alarms was developed in Australia,
...
|Both these suggest methods of preventing incessant beeping if you
|are not in front of your Mac - if you know that you will not
|be at your mac for some time, put up a dialog (eg a FKEY, or a DA
|that uses a dialog) before leaving the mac. Alternatively, install
|a screen saver that automatically darkens the screen and then you
|son't even need to remember to do something actively to prevent the incessant
...
|Note that the screen saver that installs itself as MacsBug and uses the
|alternate screen will probably not work for this, as SA just checks if
|an area of the menubar on the screen is dimmed - not the alternate screen.

FLAME ON!:

All of the above suggestions are workarounds!  You mean I have to explicitly
tell SA to not bother me with its "incessant beepings".  That makes it less
than worthless.

And as far as I'm concerned, Autoblack is the only way to go as far as current
screen blankers go! (I don't know about "Pyro!")  It's pretty obvious why the
above workarounds don't work with Autoblack, they're workarounds.

Why can't we have software that works right in the first place?

FLAME OFF!:

Sorry about that, but I found the workarounds mentioned above insult my
intelligence as a Mac user.

The original poster seems to have the right idea.
-- 
Rich Straka     ihnp4!ihlpf!straka

Advice for the day: "MSDOS - just say no."