04-16-2014 12:54 PM - edited 04-16-2014 01:40 PM
Never put loops in the timeout frame, use the outer loop instead and keep state and set the timeout to a fixed small value while tasks are being processed and switch back to the existing timeout calculation when the tasks are not executing.
If you want the tasks to complete and only stop at the next timeout, you could place the stop button in the TRUE case of the time manipulation code. Make sure to label the boolean text of the TRUE state e.g. as "waiting for tasks to complete..." or similar. leave it at latch action.
You can remove the stop event, it is no longer needed.
04-16-2014 01:27 PM
@altenbach wrote:
Never put loops in the timeout frame, use the outer loop instead and keep state and set the timeout to a fixed small value while tasks are being processed and switch back to the existing timeout calculation when the tasks are not executing.
If you want the tasks to complete and only stop at the next timeout, you could place the stop button in the TRUE case of the time manipulation code. Make sure to label the boolean text of the TRUE state e.g. as "waiting for tasks to complete..." or similar. leave it at latch action.
Thanks. Got it 😉