Can PowerHouse "catch" an arrow key stroke?
Martijn Nabben (Fairfax)
Martijn.Nabben@fairfaxnz.co.nz
Tue, 20 Jul 2004 10:11:26 +1200
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C46DDD.55B1FDC4
Content-Type: text/plain;
charset="iso-8859-1"
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_001_01C46DDD.55B1FDC4
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 5.50.4937.800" name=GENERATOR>
<STYLE>@font-face {
font-family: Wingdings;
}
@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=325045621-19072004>Hi
all, and in particular Joe, Peter, Christina
and Mikael,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=325045621-19072004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=325045621-19072004>Thank
you all for thinking along with me to find a workable solution for the
fieldmarked menu option screen.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=325045621-19072004>(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></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=325045621-19072004>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></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=325045621-19072004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=325045621-19072004>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. </SPAN></FONT><FONT
face=Arial color=#0000ff size=2><SPAN class=325045621-19072004>This appears to
be the most maintainable, understandable and most compliant with PowerHouse
technology solution that works optimal for us.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=325045621-19072004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=325045621-19072004>Thanks
again and enjoy the rest of your week!</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=325045621-19072004>Martijn</SPAN></FONT></DIV></BODY></HTML>
------_=_NextPart_001_01C46DDD.55B1FDC4--