Some more testing has revealed that gets confused (on my system, at
least) when the keystroke has more than one byte loaded onto it. The length
of bytes for "Enter" with $H on it is showing as 3 bytes; having the jump
to WILDAZ loaded onto the space bar was similarly causing problems.
What is the proper way in XPL to deal with multi-byte key outputs?
I'm trying to work with func RK to record a series of keystrokes, then LDRK
to s/g 1 (not 01). I'm getting baffling response: has the right value
but a test with fails.
Here's the code:
XPLeNCODE v2.0
b-gin [UNTITLED]
{176}SV1,{177}[cr|lf]{176}LBA{177};*; LOOP [cr|lf][BC_]--hit{032}
any key (x = exit);*;[cr|lf][RK_];*; start recording keystrok
es[cr|lf]{176}LBb{177};*;[cr|lf]{176}IF{176}RC{177}=="x"{177}
{176}GLc{177}{176}EI{177};*; here I enter "abcd" then an x to
exit[cr|lf]{176}GLb{177};*;[cr|lf]{176}LBc{177};*;[cr|lf][RK
_];*;[cr|lf][BX_]ldrk 1[Q2_];*;[cr|lf];*;{176}IF{176}is1{177}
=="abcdx"{177}{177}[BC_]YES!{176}EX{177}{176}EI{177};*;[cr|lf
][BC_]{176}Pr@1{177}{176}EX{177}[cr|lf]
-nd
XPLeNCODE
I get a prompt showing: abcdx -- or I can put on the command line or
at the bottom of the file (BF) and get it too. But the test for it fails. I
looked at the result of at the bottom of the file with LIST.COM and
it's just the ASCII characters abcdx.
???
Harry Binswanger
hb@xxxxxxxx