Hi need explanation of this question

[gavinng]

Hi thanks for the suggestion! so does that mean need to use the state machines?

[altenbach]

Yes, you have several states. The state machine can be very simple.

[wiebe@CARYA]

---

@gavinng wrote:

Hi thanks for the suggestion! so does that mean need to use the state machines?

---

You never need a state machine.

You could use a state machine to get the behavior you want.

There are (many, many) alternatives. I prefer a state pattern, but that's OO (and therefor very difficult 😉). For a small thing like this, I probably put everything in a class that keeps it's own state...

[altenbach]

---

wiebe@CARYA wrote:

---

@gavinng wrote:

Hi thanks for the suggestion! so does that mean need to use the state machines?

---

You never need a state machine.

---

I agree, but it depends a little bit how broad the term is defined. (Something that retains a start tick across iterations and can be in several states (LED Skipped? Button pressed? 200ms elapsed? 1000ms elapsed? ) could already be called a (very primitive) state machine. 😉

[wiebe@CARYA · Accepted solution]

---

@altenbach wrote:

---

wiebe@CARYA wrote:

---

@gavinng wrote:

Hi thanks for the suggestion! so does that mean need to use the state machines?

---

You never need a state machine.

---

I agree, but it depends a little bit how broad the term is defined. (Something that retains a start tick across iterations and can be in several states (LED Skipped? Button pressed? 200ms elapsed? 1000ms elapsed? ) could already be called a (very primitive) state machine. 😉

---

Agreed.

Just trying to convey that a state machine is an option. Any solution should be a means to an end. Not something you feel like you need to (or, worse, are told to) use.