If I read this correctly, I've noticed this odd 
behavior in screen observation usage, not programming.

For a common example use an NMMGR screen with more 
that 2 fields.  

Use your arrow key and position your cursor above 
two fields that will follow in succession.

Hit tab.

a)  On a dumb terminal such as a HP700/92 the cursor will
stop at the first field.

b)  In QCTerm you will probably notice that your cursor
'skipped' the first field you'd expect it to stop 
at, and stop at the second field.

Note this does not happen when first entering a freshly
painted block mode screen.  One must move the cursor with
the arrow key to somewhere else on the screen and then
hit Tab.  

It's also something that can be lived with, one can either
position the cursor two fields back and hit tab to get
where you want the cursor to be, use arrow keys, or use
the mouse to force position the cursor.

BT


Tracy Johnson
MSI Schaevitz Sensors 

> -----Original Message-----
> From: John Pitman [mailto:[log in to unmask]]
> Sent: Monday, August 11, 2003 7:47 PM
> To: [log in to unmask]
> Subject: [HP3000-L] QCTERM, BLOCK-LINE MODE
> 
> 
> Sorry, I'll make some noise.
> 
> How do I get QCT to handle Block Line mode? It seems to be 
> skipping fields
> when I do Escd, Read to transfer data....
> 
> jp
> ----- Original Message -----
> From: "Gary Sielaff" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Tuesday, August 12, 2003 9:30 AM
> Subject: [HP3000-L] quiet
> 
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *