Richard. it has nothing to do with beeping at users. Multiple beeps
are VERY useful when debugging without entery the debugging mode and
following every or most lines of the code. Often much more convenient
than ssetting break points.
IMHO,
Joe Wilkins
On Apr 5, 2007, at 10:27 AM, Richard Gaskin wrote:
Jim Ault wrote:
I think of the beep command in Rev as one of the things that has been
included for backward compatibility. New users would have no way
of knowing
about the legacy features, and the docs do not cover every nuance,
nook and
crany, so it *is* more of an exercise in trivia. A very good
reason for
this list and its activity.
The beep command is generally useful enough that it should be
expected to work, legacy or no.
But in recent years the number of times computers beep at you has
greatly declined; these days the beep is used only in the rarest of
data-loss confirmations.
And it's nearly unheard of to beep at a user multiple times; I
suspect this rarity is why any issues with multi-beep sequences
hasn't been discovered before.
Users have a difficult enough life as it is, why would we want to
beep at them multiple times?
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
