Can PowerHouse "catch" an arrow key stroke?
Joe Boyle
joeboyle_adt@hotmail.com
Tue, 20 Jul 2004 18:25:53 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0009_01C46E86.FDFFCF90
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
just for completeness ( and it all depends on how much you want a certain
type of processing :-)), you could always have had a separate qkgo file for
this setup and called it from the screen menu using syntax like that below,
subscreen Screen1
command label " the other qkgo" quick auto=the_other_qkgo.qkg
subscreen Screen3
etc.
I've seen it used on VMS ( and no, it wasn't my handy work :-) )
_____
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Martijn Nabben
(Fairfax)
Sent: 19 July 2004 23:11
To: powerh-l@lists.sowder.com
Subject: RE: Can PowerHouse "catch" an arrow key stroke?
Hi all, and in particular Joe, Peter, Christina and Mikael,
Thank you all for thinking along with me to find a workable solution for the
fieldmarked menu option screen.
(Re-)mapping the arrow keys is a bright idea, but it would interfere with
the functionality of a lot of other screens within the same application.
Bringing the description field inside the cluster makes it display with
every occurrence; this would be standard PowerHouse, but doesn't comply with
the user requirement as the description is way too long to fit in the screen
as an occurrence.
We have now decided to move away from the fieldmarking and have introduced a
temporary description field outside the cluster with as many designer "help"
procedures as there are occurrences. The user can enter "h1" - h30" in the
action field and depending on the occurrence, the procedure assigns the
value of the description field to the temporary item and displays it. This
appears to be the most maintainable, understandable and most compliant with
PowerHouse technology solution that works optimal for us.
Thanks again and enjoy the rest of your week!
Martijn
------=_NextPart_000_0009_01C46E86.FDFFCF90
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Message</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>just for completeness ( and it all =
depends
on how much you want a certain type of processing </span></font><font =
size=3D2
color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:Wingdings;
color:navy'>J</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>), you could =
always have
had a separate qkgo file for this setup and called it from the screen =
menu
using syntax like that below,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:36.0pt'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>subscreen
Screen1<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:36.0pt'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>command
label “ the other qkgo” quick =
auto=3Dthe_other_qkgo.qkg<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:36.0pt'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>subscreen
Screen3<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:36.0pt'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>etc…<o:p></=
o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:36.0pt'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p>=
</span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I’ve seen it used on VMS ( =
and no,
it wasn’t my handy work </span></font><font size=3D2 color=3Dnavy
face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></fon=
t><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'> )<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>
<hr size=3D3 width=3D"100%" align=3Dcenter tabindex=3D-1>
</span></font></div>
<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">powerh-l-admin@lists.sowder.com</st1:PersonName> =
[mailto:<st1:PersonName
w:st=3D"on">powerh-l-admin@lists.sowder.com</st1:PersonName>] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Martijn Nabben =
(<st1:City
w:st=3D"on"><st1:place w:st=3D"on">Fairfax</st1:place></st1:City>)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 19 July 2004 =
23:11<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
powerh-l@lists.sowder.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Can =
PowerHouse
"catch" an arrow key stroke?</span></font><o:p></o:p></p>
</div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Hi all, and in particular Joe, =
Peter,
Christina and Mikael,</span></font><o:p></o:p></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Thank you all for thinking along =
with me
to find a workable solution for the fieldmarked menu option =
screen.</span></font><o:p></o:p></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>(Re-)mapping the arrow keys is a =
bright
idea, but it would interfere with the functionality of a lot of other =
screens
within the same application.</span></font><o:p></o:p></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Bringing the description field =
inside the
cluster makes it display with every occurrence; this would be standard
PowerHouse, but doesn't comply with the user requirement as the =
description is
way too long to fit in the screen as an =
occurrence.</span></font><o:p></o:p></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>We have now decided to move away =
from the
fieldmarking and have introduced a temporary description field outside =
the
cluster with as many designer "help" procedures as there are
occurrences. The user can enter "h1" - h30" in the action =
field
and depending on the occurrence, the procedure assigns the value of the
description field to the temporary item and displays it. This appears to =
be the
most maintainable, understandable and most compliant with PowerHouse =
technology
solution that works optimal for us.</span></font><o:p></o:p></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Thanks again and enjoy the rest of =
your
week!</span></font><o:p></o:p></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Martijn</span></font><o:p></o:p></p>=
</div>
</div>
</body>
</html>
------=_NextPart_000_0009_01C46E86.FDFFCF90--