Conference turris::tpu_notes

    I use the KEA! terminal emulator from Attachmate.  KEA! V4.2 introduced
    mouse support (ANSI point sequences).  That is, if you point and click
    in the terminal window the appropriate ANSI terminal point escape
    sequences (screen position and mouse button) are fired down the wire to
    the host.  This should be essentially the same thing that DECterm does
    when you have done a SET HOST from a DECterm session and use TPU on a
    remote node.
    
    I find that although TPU does correctly reposition the cursor to the
    place I did the point/click, other things don't quite work right.  
    
    For example, I run TPU with SET CURSOR BOUND.  On a DECterm session if
    I click on a portion of the screen that is past the end of the line
    then the cursor is properly positioned at the true end-of-line rather
    than at the place where I was pointing when I clicked the mouse. 
    However, when using a KEA! session the cursor is actually repositioned
    at the place where I clicked, even though I have SET CURSOR BOUND.
    
    Another example: when I click on the title bar nothing happens when I
    use KEA.  That is, it doesn't change buffers if I click on the buffer
    name; doesn't toggle Write/Read-only, Insert/Overstrike,
    Forward/Reverse.
    
    If I click on the Command line the command prompt does appear.  If I
    click on the message line I can scroll thru messages using the arrow
    keys.
    
    Initially I thought "Well, I guess KEA! didn't completely get the
    sequences right."  But when I mentioned it to the KEA! support people
    they said that all they do is fire down the position/mouse button
    sequence to the host.  
    
    It does appear something must be different in how TPU treats DECterm
    terminals vs telnet terminals (I haven't tried LAT).  I mean how could
    KEA! be causing the SET CURSOR BOUND command to be ignored?
    
    Does anyone have any thoughts on this?
    
    	Thanks,
    
    	Paul

    Hi Paul,
    
    Sorry to be so late in responding. Unfortunately, we don't have the
    KEA! package, so we can't test it out for ourselves.
    
    I glanced through the EVE code that does mouse support but didn't see
    anything that caught my attention. EVE just uses TPU's internal
    definitions of mouse click escape sequences.
    
    It is strange that some actions appear to work and some don't. I wonder
    if telnet terminals transmit all ANSI mouse commands properly.
    
    Does KEA! support protocols other than telnet? I'm wondering if
    creating a LAT session might exhibit different behavior, for example.
    
    -- Daryl

    Hi Daryl,
    
    Thanks a lot for the reply.  Guess what.  I just got a beta kit today
    for the next release of KEA! (V5).  After installing it and doing some
    testing I find that the mouse now works as expected.  I guess the
    whining I did during the last field-test payed off.  :-)
    
    I don't know what they changed but it seems to work right now.  It
    appears that something KEA! V4.2 was doing confused EVE.
    
    Thanks again for taking the time to look into this.
    
    	Paul

    Thanks, Paul, that's good to hear.
    
    -- Daryl