Do Not Use Long_while()!

Spire_Jeff · December 2007

This is currently in the text sorting thread, but it was so not nice to me, I decided it needed it's own thread.

The help file briefly states that: NOTE: DEFINE_EVENTs events are still processed even if mainline is in a LONG_WHILE. LONG_WHILE should not be used in Events. It may cause unexpected results.

I am here to tell you that IT WILL cause MAJOR delays. I didn't have any problems with things not evaluating correctly, but the statement in question took about 5-10 minutes to operate based on LONG_WHILE and only 3 seconds based on WHILE.

Hope this helps someone in the future,
Jeff

Joe Hebert · December 2007

Spire_Jeff wrote:

but the statement in question took about 5-10 minutes to operate based on LONG_WHILE and only 3 seconds based on WHILE.

You asked for a LONG_WHILE and you got a REAL_LONG_WHILE.

Marc Scheibein · December 2007

Interesting.... I know that NetLinx makes no difference between WHILE (Axcess: automatically canceled after 0.5 secs), MEDIUM_WHILE (no automatic cancellation, no processing of bus -> Axcess killer) and LONG_WHILE (no cancel, but operating bus)

Do Not Use Long_while()!

Comments

Leave a Comment

Categories