Function Key labels on Windows
Don Baird @ Encore
dbaird@encoresyspros.com
Tue, 26 Apr 2005 20:09:50 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_002B_01C54A9B.E737B060
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Moving right ahead with our migration from the HP3000 to Windows, we are =
now coming to grips with the fact that the Windows Console does not =
support function key labels. Really a shame as this greatly reduces the =
practical use of function keys. We did some fairly tricky things, =
especially in DATA context, that we cannot re-produce. We did use =
several levels of function keys in our largest (read that "most =
important") screens.
We have designed a new means to navigate through our application using =
more menus, more Designer Procedures, more input from the Action box, =
more use of Info messages, and "fixed" function keys F1 - F12. We have =
all 12 working without relying on Shift or Alt or Ctl by modifying the =
TIC file.
Works OK, though it took "more" of practically everything, but still not =
as smooth (easy, intuitive, slick, better - fill in your favorite ) as =
using function keys and labels. Oh well.
That said, has anyone else dealt with this issue? Does anyone have any =
ideas? The latest New Features manual mentions connecting to the Windows =
Console via a terminal emulator - has anyone ever done this? How? Not =
sure we would go this route, but we are curious.
Has anyone ever "trapped" a key being pressed, like <F1>, or Ctl W? So =
we could do something like : IF FIELDTEXT =3D <F1> (Ctl W, whatever) =
THEN RUN SOME DESIGNER OR INTERNAL PROCEDURE ... If we could get this =
to work we could get a little of our "smooth" back. =20
Too bad you can't run Designer procedures in DATA context.
All ideas are welcome. Anyone who wants to talk about it feel free to =
give me a call - (972) 442-9718. If you are going through the same =
migration I can tell you what NOT to do.
Thanks.
Don Baird
EnCore Systems
------=_NextPart_000_002B_01C54A9B.E737B060
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1498" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Moving right ahead with our migration =
from the=20
HP3000 to Windows, we are now coming to grips with the fact that the =
Windows=20
Console does not support function key labels. Really a shame as =
this=20
greatly reduces the practical use of function keys. We did some =
fairly=20
tricky things, especially in DATA context, that we cannot =
re-produce. We=20
did use several levels of function keys in our largest (read that "most=20
important") screens.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We have designed a new means to =
navigate through=20
our application using more menus, more Designer Procedures, =
more input=20
from the Action box, more use of Info messages, and "fixed" =
function keys=20
F1 - F12. We have all 12 working without relying on Shift or Alt =
or Ctl by=20
modifying the TIC file.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Works OK, though it took "more" of =
practically=20
everything, but still not as smooth (easy, intuitive, slick, better =
- fill in your favorite ) as using function keys =
and labels. Oh=20
well.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>That said, has anyone else dealt =
with this=20
issue? Does anyone have any ideas? The latest New Features manual =
mentions=20
connecting to the Windows Console via a terminal emulator - has =
anyone ever=20
done this? How? Not sure we would go this route, =
but we=20
are curious.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Has anyone ever "trapped" a key being =
pressed, like=20
<F1>, or Ctl W? So we could do something like : IF FIELDTEXT =
=3D=20
<F1> (Ctl W, whatever) THEN RUN SOME DESIGNER OR INTERNAL =
PROCEDURE=20
... </FONT><FONT face=3DArial size=3D2>If we could get this =
to work we=20
could get a little of our "smooth" back. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Too bad you can't run Designer =
procedures in DATA=20
context.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> <FONT face=3DArial size=3D2>All ideas are welcome. Anyone who =
wants to=20
talk about it feel free to give me a call - (972) 442-9718. If you are =
going=20
through the same migration I can tell you what NOT to =
do.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Don Baird</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>EnCore Systems</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =
</FONT></DIV></BODY></HTML>
------=_NextPart_000_002B_01C54A9B.E737B060--