Weird fiePro Behavior

[Jay R. Ashworth]

On Tue, Apr 20, 2004 at 06:10:32PM -0400, Kenneth Brody wrote:
> George Simon wrote:
> > But, when allowing you to enter a field in the cursor path screen, it
> > obviously does not stop when it finds that the first reference to the field
> > is protected.  It obviously reads the rest of the screen.
> > So why doesn't it do the same when a screen ,field_number statement is
> > encountered?
> > 
> > And, why is it a "bad thing" to have the same field on the screen twice,
> > once protected and once un-protected?
> 
> Because you have two copies of the field on the screen, each with a
> different value.  Which one "wins"?

You have that in your head as a question that can be asked because of
that scary thing we found out a few weeks back: that you read the
screen to get the values of the fields.

If, like everyone else in the industry, (except, come to think of it, a
physical 3270 mainframe terminal, which *someone* clearly spent too
much time with as a youth :-) you updated the "actual" field
on exit of the screen field, and then refreshed the screen, you would
not even be able to conceive it as a question, as I couldn't, until I
remembered.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson