TERM=vt100 does not work for function keys F-5 and above.

After some experimenting, I found that TERM=xterm works the best. TERM=konsole works ok, but has a strange flicker problem at times. So I use TERM=xterm.

I'm running Suse linux, with a KDE konsole window as a terminal. To use this, type the following in your window:

TERM=xterm
export TERM

It doesn't need to recompile oc or any programs.

It turns out that the vt100 emulator handles F-1 through F-4 differently than it does for F-5 and above. Seems that the old VT52 (or some such) only had four F keys. When they came out with the VT100 they added the rest. But the added keys use a different escape sequence than the first 4 F keys.

Looking at screenio.c, it can already handle up to 64 F keys, with Ctrl Alt and Shift combinations. If the os will pass them through.

I'm good with the 12 I get. Plus the up and down arrows, page up and down, home, and end keys.

I've enhanced screenio.c and screenio.cpy to return the tab key as 2007 and the back tab key as 2008, for the extended Accept statement. I don't think the changes apply to the screen section Accept, and I did not test the screen section at all. I believe the screen section uses the tab keys internally to hop between fields. I need the same functionality with the extended Accept statements.

Does anybody want a copy of my changes? I'm giving them under the oc GNU lesser license to the oc community. No warranty of any kind, etc... We need testers to test
a) it does not mess up the screen section accepts
b) numeric fields still work (I accept all fields alphanumeric and do my own numeric validations)
c) secure fields (passcode prompts I don't use)
d) MS windows (I don't use)
e) other platforms (VAX, etc)
f) any other tests that can be thought up

Also, the user guide needs to be updated. Let me know if I can change this, or to whom to send the changes.