Setting Default Function Keys

[Peter Bateman]

Georgia:

  To test is quick is trying to setup the function keys.

   QUICK term=HP2392 NOTERMPOLL  > DMPfile

    ^

    FCOPY FROM DMPFILE;TO=;HEX;CHAR

    You should see the standard QUICK labels in the mess displayed on your 
screen.
    Oh, it might lock your terminal as well.

   I believe you could do something like PUSH RESTORE LABELS in the 
INITIALIZE procedure.
   Check the manual for the syntax.

   When people have problems with function keys just after startup the 
problem is often
   related to network flow control. Sometimes saying term=HP2392-TRANS or 
term=HP2392-X25
   helps.  Ask your network people if XON/XOFF is supported?

  I heard you say if the users have their function keys are set going into 
QUICK then they are OK.

  In the QUICK udc you could set the function keys the QUICK standard keys.
  i.e. echo escape sequences to set F1 - F8 and an escape sequence to enable 
and
  display the function keys. Check your reflections or hp terminal manual 
for the exact code.

Regards,
Peter




>From: Georgia Miller <georgia_miller@mail.gfps.k12.mt.us>
>Reply-To: Georgia Miller <georgia_miller@mail.gfps.k12.mt.us>
>To: PowerHouse Listserv <powerh-l@lists.swau.edu>
>Subject: Setting Default Function Keys
>Date: 12 Sep 2003 15:27:28 -0600
>
>I am using PH819C on an HP3000.  I have discovered that the default Quick 
>function keys (f1 - f8), are not getting set for any of my users.  I have 
>been using Powerhouse for over 20 years and I have always used the default 
>setqkgo files and function key settings.  I don't know what version, this 
>quit working, but I have discovered that the only way the function keys get 
>set is if you do a KL action field command.  We are using reflections on 
>Mac's and PC's.  I know in the past when we had dumb terminals they got set 
>properly, even though we programmed the function keys to do other things 
>such as logon's.  I discovered that the user's that do have function keys, 
>thier default function keys in Reflections are set to Quick's default 
>function keys.
>
>Did this function go away when we got the ability to program the function 
>keys?  I do have one system that is using dynamic instead of standard 
>function key mode and those get set when you go into Quick and then the 
>Reflection default function keys get reset when you exit Quick.
>
>I would like it to automatically set the function keys to the Quick default 
>function keys when Quick is launched and then reset the Reflection default 
>function keys back when exiting Quick.
>
>I see that you can set what you want the default functions keys to be in 
>the SETQKGO file.  It is not logical that I have to tell Quick the default 
>Quick function key setting in each of my QKGO files for Quick to work the 
>way it used to work in the past.  Especially when Quick knows what the 
>default function key settings are better than I do.
>
>Could the problem be Reflections, my terminal emulation program?  I have 
>another terminal Emulation program for GUI screens called VBView, but it 
>doesn't seem like the function keys are getting set properly in that 
>either.  It was not designed for Quick, but Quick Screens will work in it.
>
>Georgia Miller
>Great Falls Public Schools
>Great Falls, Montana
>
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.swau.edu
>Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
>Unsubscribe: "unsubscribe <password>" in message body to 
>powerh-l-request@lists.swau.edu
>http://lists.swau.edu/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail