On Aug 23, 2004, at 4:32 PM, [EMAIL PROTECTED] wrote:
I'd say this IS a bug, a documented bug, but still a bug.
If the beep command accepts parameters, it should be able to handle those
parameters - without the user having to consult the documentation or exception
reports - or, worse yet, having to program around the bug. If a wait is required
for beep parameters, it should be built into the beep command.
I think there is way too much stuff like this in the current Revolution;
things that don't work logically, or obviously, but get explained away in the
documentation.
I agree.
I can write a little handler to work correctly on multiple platforms. If I can do that, then RunRev can take care of the beep for different platforms.
Even so, the timing I get (when timing beeps) suggests that the bug is really something else.
Dar
****************************************
Dar Scott Consulting
http://www.swcp.com/dsc/
Programming Services
****************************************_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
