I have used duck, fart, squawk and announced sounds (like 1,2,3,4,5)
to trace and debug since HC began.
When a long-worked-on routine to gather many SQL conuries in a
recursive handler finally worked, I got this hilarious stutter-duck
sound that indicated success. At that point I was laughing so
uncontrollably that I had to stop for the day.
sqb
On 4/6/07, Joe Lewis Wilkins <[EMAIL PROTECTED]> wrote:
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.
An excellent point. I do seem to remember in HC I spent a lot of time
listening to beep combinations as my scripts ran to confirm 'entry' into
certain segments. Now I seem to do a lot of waiting for the debugger to open
at breakpoints, do a couple of 'steps' to confirm correct branching and then
pressing 'run'.
I know I can put text into the msg box, but usually I'm busy watching data
change in fields so it would be more convenient to have audible 'markers'.
If I remember correctly it was much easier in HC to play notes of different
pitch and duration.
--
stephen barncard
s a n f r a n c i s c o
- - - - - - - - - - - -
_______________________________________________
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
