Re: keypad & sql*forms
Date: Fri, 4 Sep 1992 18:59:44 GMT
Message-ID: <1992Sep4.185944.1292_at_oracle.us.oracle.com>
In article <1992Sep3.133806.971_at_src.honeywell.com> kdady_at_src.honeywell.com (Ken Dady) writes:
]
] Is there a way to re-define the numeric keypad on a
] VT100, Sun keyboard, Mac (running telnet) to be used
] as a 'normal' keypad with SQL*forms? i.e. Keys
] interpreted as numbers instead of functions. The
] numlock key seems to have no effect.
I'll have to admit ignorance on Sun and Mac, but here's the deal on the VT100:
The VT100 is so function key-poor that the numeric keypad had to be stolen for function keys. You may be able to work around this problem by:
- Removing any keys you're not using, and will never want to use;
- Using the SQL*Forms 3.0 menu, where applicable (like, for [Enter Query] or [Next Record])
- Squishing all the remaining keys into [Control-something], [Esc something], [Esc Esc something],...
If you can do that, use oraterm to define the new keymap, and remove the "\e=" and "\e>" from the terminal setup and reset strings. The first string puts the keypad in "application" mode, the second in "normal" mode.
(In fact, you might want to swap the modes: instead of going into application mode on entry and normal on exit, you can go into normal on entry and application on exit.)
- Bill K.
Bill Kaufman, | "Maybetheyhadaridiculousstatementtomakeaboutsomethingt Corporate Lackey | heyhadntexperiencedPossiblySamhadadifferentopinionthawkaufman_at_us.oracle.com | tnobodyeverconsideredimportant." -- the Meat Puppets Received on Fri Sep 04 1992 - 20:59:44 CEST