Tim C. wrote:
The cancel function will get more complicated, as i was planning on using a common cancel button to cancel For Loops in multiple consumer
events.
What are "Queue Occurances" (I think that is what you mentioned)?
Queues pass data from one loop to another and can store multiple items. Notifications do the same thing, but store a single item. Occurences are the basic level of these. It acts like a notification, but won't pass any data. Look in the synchronization pallete for all of these. Look at the examples in the example finder.
I would recommend using a notification. It will behave similarly to the queue you are already using, but will allow you to get the notification into the inner for loops to get them to end early. It is essentially a separate communication channel from your queue. You may need to use timeout with a very low value on the wait for notification so that you aren't pausing the for loop. It will allow the for loop to run, but if it gets a boolean true passed to it, it will stop the For loop.
