Xref: utzoo comp.sys.amiga:16630 comp.sys.amiga.tech:107
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!rochester!ur-tut!dpvc
From: dpvc@ur-tut (Davide P. Cervone)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: NoisyReq anomaly
Message-ID: <1504@ur-tut.UUCP>
Date: 24 Mar 88 22:54:13 GMT
References: <4599@garfield.UUCP> <25089@amdahl.uts.amdahl.com>
Reply-To: dpvc@tut.cc.rochester.edu.UUCP (Davide P. Cervone)
Organization: Univ. of Rochester Computing Center
Lines: 26
Keywords: vt100 2.8

In article <25089@amdahl.uts.amdahl.com> kim@amdahl.uts.amdahl.com (Kim DeVaughn) writes:
>Ever notice while resizing a window or moving it around that an in-progress
>file xfer *stops* until you release the L-Mouse-Button?  Well, it does [see,
>led's on modems *are* good for something].
>
>This is not restricted to vt100's window(s) either, but applies to any window
>in the system.  This can cause havoc if you're trying to talk to a system that
>doesn't relax their timeout specs between packets.

This has to do with layers.  When you size or move a window, Intuition locks
the screen's layers so that rendering does not occur to the window or screen
while you are moving the window around.  In general, this is a good thing, 
but it also means that any I/O to a window on that screen will block until
you let go of the window.  I assume that VT100 is updating a status window
(telling you how many packets are transfered).  This update is being blocked,
so VT100 does not go on to receiving the next packet until the output occurs.
That's the holdup.  There's very little that can be done about it,
unfortunately.

Holding down the MENU button also locks the layers.

>/kim
>UUCP:  kim@amdahl.amdahl.com

Davide P. Cervone
dpvc@tut.cc.rochester.EDU