a puzzler

[Robert Haussmann]

> [...]
> > Edited the screen added the field in the upper left
> > section and told the user to check it out.  They looked
> > at it and were satisfied.  Thought the issue was closed.
> > 
> > Started getting reports that data entered into the field
> > was not "saving".  Users claimed they would update the
> > screen, change info in the field, <ESC> to save and the
> > the info would vanish.  Of course we suspected user error
> > at first, but after seeing it outselves, found it to be true.
> > It didn't matter what you changed the value to, it always
> > resorted back to the original value.
> 
> I haven't read any further yet, but my guess at this point is
> that the field was already on the screen (perhaps protected)
> further down.
> 

Doh!  That's exactly right!  The field was already at the
bottom of the screen (not protected).  

I haven't tested it yet, but now I've been wondering--if the
cursor path was such that the instance at the bottom of the
screen got updated, would the update "stick" (e.g., are the
fields read from left-->right and top-->bottom?

Bob