Re : event structure state machine

[Yamaeda]

The event structure subscribes to the registered events, if any of those happens it'll run. This includes the timeout event which'll auto generate after the wait time. I'd set 10 or 100 as fixed timeout to have a responsive program which still will be calm and wait for the events.

/Y

[crossrulz]

---

@rcote1 wrote:
Yes, that's what I did, but its the Timeout event that decides if its goig to be a 0 or -1 that the Timeout terminal takes. My question is, how does the timeout event gets notified of any event that need to be handled?

---

Why would the timeout case determine its own timeout?  That makes no sense to me.  The timeout should be determined based on what actions you are performing.  So it should be the button presses that determine the timeout.

Can you post some code so we can see where you are at?

[rcote1]

Is there a way to prioritize the other events if they happen instead of the Timeout event. I use a Timeout of 0 and if there are other events I would like them to be handled first. That would truly simplify.

[kbbersch]

Producer/Consumer.  This thread is going down a path that is not following best practices.  Handling the events in the same loop as the state machine makes no sense to me.  Separate the two.

[rcote1]

Here is my program.

Richard

[crossrulz]

---

@rcote1 wrote:

Is there a way to prioritize the other events if they happen instead of the Timeout event. I use a Timeout of 0 and if there are other events I would like them to be handled first. That would truly simplify.

---

If there is an event in the queue, the Timeout will not be selected.  The event that was queued up will run instead.  The given timeout is just how long the structure will wait for an event starting when the event structure was reached.  Events could be queued up before the event structure was reached.  If so, they will run, not the timeout.

[Yamaeda]

---

@kbbersch wrote:

Producer/Consumer.  This thread is going down a path that is not following best practices.  Handling the events in the same loop as the state machine makes no sense to me.  Separate the two.

---

You mean like the State Machine fundamental example?

It sounds like a valid design.

/Y

[kbbersch]

Using a Producer/Consumer design pattern with a queued state machine would make a lot more sense in this application.  There would be no chance of blocking the state machine.  Easier to extend.  Lots of pluses.