Function key remapping on PC client
Posted 05 October 1999 - 03:04 PM
We are just starting to use the GUI client for windows and all the
function keys are different then the Dumb Terminals. I have tried
to use the remapping of keys in the .ini files but that doesn't
seem to 'take' and also played with $CRT but have had no results
in making the GUI function keys consistant with our current
application. Any suggestions?
Posted 06 October 1999 - 05:36 PM
Ask PRO IV Ltd why this is so and they will tell you that this is to keep in line with GUI standards. It's the same reason that you have to use CTL-BREAK instead of CTL-C to break out of a function (CTL-C is the GUI standard for copy to clipboard).
Posted 06 October 1999 - 06:00 PM
At first, we hated it. Over time, we saw it as an advantage.
Posted 06 October 1999 - 06:54 PM
Mainly move the window key to F9 instead of F4.
Also with our dumb terminals and PC's using a third party to
connect to UNIX we mapped the F7/F8 keys on our own paging
screens. They don't even work on the GUI since we usually don't
allow mode changes in our screens.
Posted 10 October 1999 - 01:06 PM
re-enable Mode processing!
I was going to suggest adjusting the entries in the
screen definition for GUICLR. (Utilities - Screen Defns) I found
that theses did affect the operation of the GUI client - and here we were able to alter
the PgUp/PgDn key and function keys. Here I would suggest
reversing the entries for F4 and F9.
We use Solaris and P4 4/514 At this stage we abandoned the GUI as unworkably
slow and unreliable - it makes Win95 look rock solid. However, careful use of colour
helps us a great deal.
Another poss. is to look a at a Keyboard remapper to run under Windows and fool
(easily) the P4 GUI client that way.
Posted 08 December 1999 - 03:55 PM
ProIV v4.0 r528 (AIX RS6000)
I am trying to setup our own $CRT for our GUI terminals and need to find the HEX equivilent of a function key when pressed. Example, on PROIV default $CRT definition CRTL-1 is FNKEY 33 (hex: 1B5B32337E), but I want to change that to be FNKEY 40 (hex: ????) to minimize coding changes. Any Ideas?
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users