Conference hydra::amiga_v1

Good news:

This question, or a very similar one, was asked and answered in this
conference before. I'd say more than a year ago, probably in a terminal
emulator note, and I have a vague recollection that John Sauter answered it.

Bad news:

Since I didn't have the problem I don't recall the answer. So you'll
have to go looking with the information I gave, or wait until someone
who actually knows something about this answers...;-)
Dave

    Your memory's better than mine.  I don't use VLTjr and I seldom use VTX
    (never from home) so I can't imagine what I'd be able to contribute to
    answering this question.
        John Sauter

Sorry John.
Apparently my memory is much worse than yours.

I thought you or someone made a comment about the way
different applications read or interpret keypad input, and at least
speculated on how VTX, or some other application, was
different. The terminal emulator in question ( I don't think it was
VLT) made some asssumtions that worked with most applications but not 
others.

I seldom use VTX either. I'll do what I should have done it the first place -
wait until someone >>who actually knows something about this answers...;-)

Dave

    I don't use VTX much, but I thought I'd like to check the status
    of an IEG order.  I discovered the pf1-4 works in place of the 
    A2000's numeric keypad.  
    
    VTX must do some thing really strange because VLTjr works with ALL
    other VT application I have written or use. 
    
    FWIW, I really like VLTjr.
    
    ... Rich

    I wrote a VT100 emulator for a RS Model 100 once and it didn't work
    initially with VTX either.  The problem stems from the fact that
    the except for the PF1-PF4 keys, the rest of the keypad send either
    an escape sequence or the number/character on the keycap.  The
    application is supposed to send a software switch to tell the terminal
    which mode it is in.  VLTjr must not recognize the software switching
    of the keypad.
    
    The simple solution is to just use the regular keyboard equivalents
    of the keypad keys.  For example, when you need to press Gold (PF1)
    and then keypad 7, press Gold (PF10 and the '7' on the top row of
    the regular keys.  Similary, to exit press Gold and then the regular
    period key.  Gold RET = Gold ENTER etc.  

From note 705.140  (March  1988) 

>    VMS, and some programs, sometimes send a "set conformance level"
>    escape sequence to the terminal.  Usually it is "set conformance
>    level 2, 7-bit controls".  Smokey may be misinterpreting this to
>    mean that it is supposed to _receive_ only 7 bits.  The sequence
>    actually means that the terminal is supposed to _transmit_ control
>    characters (not graphic characters) in 7-bit.  Terminals are supposed
>    to receive control characters in both 7- and 8-bit forms, no matter
>    what they transmit.

>    TPU (upon which NOTES is based) sends both 7- and 8-bit controls,
>    but (last I heard) can receive only 7-bit controls.  EDT sends
>    only 7-bit controls (VT100 legacy) but can receive both 7- and
>    8-bit controls.
>        John Sauter
Rich,

This may or may not help with your VTX problem. It may even be totally 
unrelated, but I guess I was impressed when I read it. Since this is an 
old note, the information about TPU and NOTES may be out of date. The 
discussion in note 705, replies in the 130-150 range may help (or confuse)
you though.

OK, NOW I'll be quiet...
Dave

    The problem is really VLT. When the keypad is not in application mode
    the PF1-PF4 keys should still send the appropriate escape codes instead
    of the ()/* characters. I had noticed this in the first version of
    VLT that I tried, I was just expecting it to be fixed later. Maybe
    it will take a mail msg to the author to point this out.
    
    The workaround mentioned previously is will work if you manually select
    the pulldown to set the keypad to application mode under VLT. (then
    just use the PF keys on the keypad and the numeric keys from the main
    keyboard).
    
    	Steve.
    

    I've seen the same problem using VLTjr and SEDT from home.  Not all the
    keypad functions work correctly.  SEDT does work correctly with
    HANDSHAKE 2.12 however so I agree with Steve, it's a VLT bug.
    
    ...Ed