On September 25, 2007 at 05:55, Ernie Bornn-Gilman said...
Not at all true. You operate the Flag Test to determine
the state of the Flag so that the next command,
IF flag is set do this, ELSE do that
will know the state of the flag. If you don't do the
Flag Test, the IF/ELSE command will always act as though
the flag has not been set.
I don't understand what you are saying. The flag test option is an IF/THEN/ELSE statement. You can't do a flag test to determine state and then do a separate IF/THE/ELSE statement.
The flag test is
IF yourflagname is SET then do the following operation
ELSE (IF NOT SET) THEN DO THIS OPERATION
END or _____________________________________
No, the Flag Test is "Tell me which state the Flag is
in." Once that is known, IF/ELSE statements can work
with the now known flag state.
No. as stated above, the flag test tests if the flag is set and then performs the operations between this line and the else staement. If its not set it performs everything after the Else.
What still doesn't make sense to me is that the Flag Test
is needed at all. I would think that the operation of
"IF Flag is Set" would include looking at the flag to
see if it is set, but it doesn't. That's what I said
that I think is dumb.
It does look but I would imagine the issue could stem from the fact that the flag was never set in the first place. The first operation that runs on a remote, like power system up, should set the state of all of the flags. Not sure if this is the case, but if the flag was never initialized, set to ON or OFF in the first place, the flag test might not work properly.
Hey, maybe I'm wrong about this. But my experience has
been that IF/ELSE statements work when preceded by a Flag
Test and don't work when not.
Still do get it becuase the Flag test is an IF/ELSE statement on its own.
And don't forget to include the command that sets or unsets
the flag to be ready for the next process.
I agree.
