[Date Prev][Date Next][Subject Prev][Subject Next][ Date Index][ Subject Index]

Recording Keystrokes bug



I don't remember seeing this nominated for Nathan's bug list. ...?
Does xyWin do the same thing? If so, I wonder if the bug survives in
the new release, which I suspect is TTG's primary concern with that list.

==================================== adpFisher  nyc

≪ Apparently there's a bug in keystroke recording that causes CrLf's
 [13+10] to be encoded incorrectly as 3-byte Ascii-14's (the double 16th
 note character in 3-byte form [255+48+69] <=> {255}0E). You can see this
 if you execute func RK, hit the Enter key (assuming CrLf is mapped
 thereto), and hit func RK again to stop recording. Then issue LDRK X to
 save the recorded keystroke to Save/Get X. Then SA %X, to save contents
 of X to a file. Open X.SAV in a hex editor and you'll see the 3-byte
 Ascii-14. Surely this is an error: they meant to encode CrLf as 3-byte
 _Ascii-13_ (the standard XPL and KBDfile coding), but ended up a bit
 off. ≫ 	--Carl