[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: XY4 murmur
- Subject: Re: XY4 murmur
- From: Carl Distefano cld@xxxxxxxx
- Date: Mon, 18 Sep 2000 23:27:07 -0400 (EDT)
Reply to note from Leslie Bialler Mon, 18 Sep
2000 14:49:35 -0400
-> Through the menu, or by editing your settings.dfl file, set the
-> duration of error messages to 1. The default is 18, which is
-> equal to one second.
Default WA? No, no, all Mr. Krok need do is insert an Error
Suppression command at the beginning of his program: BX es 1Q2 .
Finito. Xy4 reinstates error messaging automatically when the
program terminates; no need to clutter your code with an ES 0
command.
(One of the minor pleasures of Xy4 is that error suppression
actually works. In Xy3 programming it caused all sorts of loutish
behavior and had to be used sparingly, or not at all; disabling
Error Beep with default EB=0,0 was the standard workaround.
Happily, that sort of kludge is no longer necessary -- hasn't been
for seven or eight years.)
Default WA is primarily to fine-tune the user interface for manual
editing. If you want XyWrite to wait every time an error message is
displayed, set default WA to, say, 45 (for a pause of 2.5 seconds).
I prefer to set WA to 0 and crank it up to a higher value only when
needed, typically to debug XPL code. I'm talking about the
situation where two errors occur in quick succession, and the second
error message overwrites (and thereby masks) the first. Temporarily
increasing WA to an artificially high value forces XyWrite to pause
for several seconds after the first error, so that the message can
be read. For this to work, you have to change any ES 1 command in
the program to ES 0. Default WA has no effect with Error
Suppression turned on.
In short, use default WA to *highlight* errors. Morris's problem is
the opposite; he wants to suppress them while his program executes.
For that, use ES 1.
--
Carl Distefano
cld@xxxxxxxx
http://users.datarealm.com/xywwweb/