Reply to note from cld@xxxxxxxx Mon, 15 Sep 2008 22:34:47 +0000
> If you must do this
I say "if you must" because there are inevitable tradeoffs when you
combine func XC and Helpkey in a single key. For one, you've got to
decide whether commands or U2 framenames are going to take
precedence. In other words, when you issue a CMline that is both a
valid native command and a valid U2 framename, which one will be
executed? The routine I posted earlier today favors native commands.
(Although it's arguable that framenames should take precedence, the
cons of that arrangement outweigh the pros, IMO.) In consequence,
you still need to maintain a separate, dedicated Helpkey to launch
framenames that coincide with native commands (or else forego the
value-added of these frames). For another, unless you're willing to
live with a constant harangue of beeps (and my routine presumes that
you're not), the informational PRompt that issues after certain
commands are completed -- e.g., the PRompt reporting the number of
changes after a CI command -- will not display (because the
subroutine that restores the Error Beep setting wipes it out), and
in some cases an incorrect and *misleading* message will display
instead. If you want to see the informational PRompt, you'll have no
choice but to maintain and use a separate, dedicated XC key to
launch these commands (or live with default EB=0,0; see below).
Once you realize that you still need separate XC and Help keys to
take full advantage of Editor and U2, it's a short step to junking
the combo key altogether. At least, that's what I've concluded every
time I've tried the combo: a day or two tops, and out it goes.
Decide for yourself.
BTW, the frame I posted earlier is a generic XC|Helpkey routine, not
suitable for use with the Enter key. For the Enter key, use the
routine below; the key assignment is
28|104=NOJM(,2,.,E,n,t,e,r,X,C,o,r,U,2,)
XPLeNCODE v2.0
b-gin [UNTITLED]
{{;5EnterXCorU2}} Use Enter key to eXeCute native command and
launch U2 frame [ arg(s)] (native commands take precedence o
ver framenames) [CLD][cr|lf]{002}{<}IF{<}VA$TX{>}<1{>}{<}SX01
,{<}VA$EB{>}{>}{<}SX02,{<}VAWA{>}{>}{<}SX01,"[BX_]d eb="+{<}I
S01{>}+",wa="+{<}IS02{>}+"[Q2_]"{>}[BX_]d eb=0,0,wa=0[Q2_][XC
_]{<}IF{<}ER{>}&{<}VA$ER{>}<>12{>}{<}SX02,{<}VA$ER{>}{>}{<}PV
01{>}[BX_]beep[Q2_]{<}SX01,"{<}VA\"+{<}IS02{>}+"{>}"{>}{<}SX0
1,{<}PV01{>}{>}{<}PR@01{>}{<}EX{>}{<}EI{>}{<}IF{<}ER{>}{>}{<}
SV02,{>}{<}IF{<}VA$MG{>}<>""{>}{<}SX02,{<}VA$MG{>}{>}{<}EI{>}
{<}PV01{>}{<}PR@02{>}[JM_]2.PrsCMline[Q2_]{<}IF{<}VA$ER{>}>13
51{>}{<}SX01,@upr({<}IS01{>}){>}{<}PRBad framename @01{>}{<}E
I{>}{<}EX{>}{<}EI{>}{<}PV01{>}{<}EX{>}{<}EI{>}[255+048+068]{0
02}[cr|lf]
-nd
XPLeNCODE
If your usual default Error Beep setting is EB=0,0 (no error beep),
these routines can be simplified, and the problem of smothered
informational PRompts avoided. Try the variant frames below (if
you're able to DECODE a second block of code in a single message),
after manually setting Default EB=0,0.
XPLeNCODE v2.0
b-gin [UNTITLED]
{{;5XCorU2}} Execute native command|launch U2 frame [ arg(s)]
(native commands take precedence over framenames) [variant f
or default EB=0,0] [CLD][cr|lf]{002}[XC_]{<}IF{<}ER{>}&{<}VA$
ER{>}<>12{>}{<}EX{>}{<}EI{>}{<}IF{<}ER{>}{>}[JM_]2.PrsCMline[
Q2_]{<}IF{<}VA$ER{>}>1351{>}{<}SX01,@upr({<}IS01{>}){>}{<}PRB
ad framename @01{>}{<}EI{>}{<}EX{>}{<}EI{>}{002}[cr|lf][cr|lf
]{{;5EnterXCorU2}} Use Enter key to eXeCute native command an
d launch U2 frame [ arg(s)] (native commands take precedence{032}
over framenames) [variant for default EB=0,0] [CLD][cr|lf]{00
2}{<}IF{<}VA$TX{>}<1{>}[XC_]{<}IF{<}ER{>}&{<}VA$ER{>}<>12{>}{
<}EX{>}{<}EI{>}{<}IF{<}ER{>}{>}[JM_]2.PrsCMline[Q2_]{<}IF{<}V
A$ER{>}>1351{>}{<}SX01,@upr({<}IS01{>}){>}{<}PRBad framename{032}
@01{>}{<}EI{>}{<}EX{>}{<}EI{>}{<}EI{>}[255+048+068]{002}[cr|l
f]
-nd
XPLeNCODE
Good luck.
--
Carl Distefano
cld@xxxxxxxx