Conference bulova::decw_jan-89_to_nov-90

Re: .0

This is a known problem.  There is a workaround which seems to fix it in most
cases: turn on the Lock User Features toggle button in the Customize General
dialog box.

				-- Bob

    Thanks Bob. Now it works. Although now I don't have the autorepeat
    feature even if I want it.
    
    Is it a problem with DECterm, sethost or WPS? Will it be fixed in the
    next release?
    
    Thanks.

Re: .2

I don't completely understand the problem, but I think there is a server or
Xlib bug of some kind that is aggravated when an application rapidly turns
auto-repeat on and off.  By locking user features in DECterm you are disabling
WPS+'s ability to turn auto-repeat on and off with an escape sequence; you
should still be able to turn auto-repeat on yourself from Cusomize.

In V2 (VMS V5.3) DECterm ignores the escape sequence altogether, even if you
haven't locked user features.  However, some people (including me) have still
seen the problem even in V2; I saw it when I was editing a file and tried to
use F13 to delete a word.  The "workaround" was to use the delete key a lot.

				-- Bob

This is a well known, very old, and much-complained-about bug in WPS.  WPS has
no right to be mucking about with auto-repeat in this way.

--PSW

    This is a mis-use of a sequence which should never have been defined in
    the first place.  The sequence turns autorepeat on and off on VT200
    terminals.
    
    I have found that 9 out of 10 times the bug appears on VSII/GPX
    systems, but has also been reported on other types.
    
    Since this happens on both VWS and DECwindows I will tell you what
    happens  in VWS, it's probably the same...
    
    When a keyboard attribute is changed, the driver actually resets *all*
    (or at least many) attributes not just one.  Many of the commands
    respond with mode change ack's.  These ack's arrive faster than the
    system can handle them and the input buffer gets data overruns and in
    the process loses any 'real' data that may have been among the burst.
    In this case what's lost is the key up transition.  So the driver (or
    server) thinks that a key is still down.
    
    The VWS solution was to disable the sequence for the terminal, which
    does not solve the problem but does make it less critical.
    
    _Fred

Re: .5

Thanks for the explanation, Fred.  Maybe this can be fixed in the later version
of the driver (I hope).

				-- Bob

If only the autorepeat has been turned on or off then the decwindows driver
will only modify autorepeat. We have never been able to determine exactly
what the problem is and it could well be a problem in the lk201 keyboard
hardware that causes data to be lost or it's 4 character fifo to overflow
if it is recieving mode changes from the driver, while also trying to ack
those changes and also trying to transmit the key transitions.

The thing I don't understand is why do you have to be running wps+ and be
set host. Maybe the timing delay and the buffering along the way is causing
characters to be delivered to wps+ that it is not expecting and it's getting
confused.

						Bill

    I dont know if this will help track down the problem but i think
    i remember that EDT used to use the autorepeat on/off technique
    to control (read slow) user input!
    
    Gerry

    
    Yes, it did but was this was removed sometime in the last century.
    
    

    	I discovered that the character repeat would only occurs after I
    type a TAB character on that line.  When I avoid typing TABs the
    problem goes away.  Does the TAB turn this repeat feature on some how?
    Weird!

    >>> < Note 1682.9 by SSPENG::KLEINSORGE "So sue me." >
    >>>
    >>> Yes, it did but was this was removed sometime in the last century.

    
    
    Well what a nice person you are!!!, perhaps you missed the phrase
    "used to" in my reply!!!
    
    Regards (and merry Xmas)
    
    Gerry

    
    I guess I forgot the :-) - it was just a conformation that yes it once
    did but hasn't for a very long time.