03-20-2005 02:11 AM
03-20-2005
02:34 AM
- last edited on
11-26-2025
06:35 PM
by
Content Cleaner
I think you misunderstood the concept of the event structure. Once the event structure has "started", it waits for one of the registered events to occur, and only when it occurs will the event structure continue. In your case, the inner loop is not iterating at all, because it's still stuck on it's first run. It will iterate once for every time one of the events you configured will occur. If, in one of those iterations, it will see that the stop button is T, the loop will stop. Your outer loop is also not iterating because your inner loop is blocking it by not stopping. To do what you want, you have 3 options - move the event structure to a seperate loop (so the stop button is unaffected by it), add a timeout (the small hourglass on the top left corner) or add a case for pressing the stop button and then wire the T to the stop condition out of that case. To comply with both your requests, your best method is to move the event structure to an indepedent loop. You should keep in mind that the outer loop will not run as long as the inner one is running. Here [broken link removed] is an event structure tutorial. I'm sure you can find some others on this site. Also, look at the examples in the Example Finder (search for "events").
03-20-2005 02:44 AM
03-20-2005 03:19 AM