thomas@utah-cs.UUCP (Spencer Thomas) (05/29/85)
I have been trying to figure out how to further customize my MacTerminal (V1.1). In particular, I am trying to send "function key" sequences. A recent posting to net.sources.mac mapped control-9,0,-,= onto arrow sequences, so this gave me a start. I found that the KMRC #256 resource seemed to control what was sent for key codes >= x80. It is apparently an array of 16 bit values, indexed x80 .. xfe (there are two more 16 bit numbers at the beginning, x80 and xfe). The entry for x80, for example, is x0141, and is sent as <esc>[A. The entry for x90 is x0250, and is sent as <esc>OP. By experimentation, I have determined that 00xx is not sent 01xx is sent as <esc>[X (where 'X' = xx) 02xx is sent as <esc>OX 03xx is sent as (xx & ~x40) 04xx appears to be the same as the RESET menu item, but without confirmation. (I'm not completely sure about this one.) 05xx sends the answerback message 06xx sends a break, the length of which is determined by xx (I don't know the multiplier.) 07xx also appears in the table, but is not bound to a key. I don't know what it does. Does anybody know more about this table? The definitions above appear to be hard wired into the program, is this true? Or, is there some way to add to the list of possibilities? What effect does 07xx have? Are there other possible codes? I attempted to experiment with this table by copying the resource to a MacTerminal document, but was not successful. Later, looking at it with the resource editor, I found that the resource was marked preload/locked. Is there any way to load this from a document file? (without being forced to do so?) There are also KMRC resources 257 and 258. Does anyone know what these do? I assume they must have something to do with the 3270 emulation, but why are there two? Finally, it appears that in 1.1 MacTerminal, the option key cannot be used as a shift/control type key. When you press option, you get the "arrows" cursor, and the normal key entry (from the KICH table) is used. Does anyone know if this is fixed in the new release (which I haven't seen yet)? Please respond to me by mail, and I will summarize interesting responses to the net. AdThanksvance =Spencer (decvax!utah-cs!thomas, thomas@utah-cs.ARPA)