I can't figure it out, but I am 100% sure it is needed. Let's say I have 2 actors, Root-A <-> Nested-B Root-A has a "helper UI loop", in the actor core, and front panel visible. Nested-B is a "controller". So I see the Nested-B as a "controller", and I interact via Root-A to send messaged to its queue, for example: 1) set parameters 2) run the test the "run test" inside Nested-B, just "batch send" to ITSELF some messages (they are the "test-steps", because a test is made up by N steps. Right? so Imagine each test step is just a wait (N) seconds. Suppose I want to ABORT the test. I want to send abort message in front of queue. But how? how can I flush the queue? After abort, the actor should not quit, but stay alive for another test run. In my root I should avoid sending other messages to the Actor-B loop, what is the best strategy? Disable UI controls? I a user click 5 times "run test" button, I don't want to queue 5 runs of course.

Actor Framework Discussions

How to flush AF queue?

I agree with having a helper loop handle all the heavy lifting as being the best solution, leaving the message loop always ready to handle new messages.

Message 11 of 11

(470 Views)

Actor Framework Discussions

How to flush AF queue?

Re: How to flush AF queue?