Not for nuthin' but: A. Why have 2 statements as shown. B. As a programmer with knowledge of CHAR and SEQ, why don't you figure this out for yourself. That's the basis for programming, learning the combinations of commands and statements.
Write a loop program and print the value of KEY, remembering what actual key you pressed. It's not that hard. Lemme throw in some other concerns. If you're venturing into capturing all the keys like <delete> and <insert>, you're embarking on keyboard mapping that's somewhat related to the emulator and the terminal emulation you are running. You would either have to stay generic (A-Z, 0-9 etc) or maintain lookup tables to convert the IN() values into multiple expressions. Also along those lines, certain single keystrokes like <Insert> may generate more than one submitted character and you'll have to digest them properly. It's a shame that we don't have access to the PC keyboard scancodes. I couldbe wrong on that last statement. my 1 cent. ----- Original Message ----- From: "Ralph Burton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 09, 2004 4:53 PM Subject: [U2] Unidata keystroke capture > I'm trying to determine for my homegrown editor > when a keystroke is pressed in Unidata. > > KEY = IN() > KEY.ID=KEY > > What do I need to do next to make the KEY.ID > into a useful value to check? > > CHAR? > SEQ? > > > Thanks, > Ralph > ------- > u2-users mailing list > [EMAIL PROTECTED] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
