Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support arbitrary starting states for StateMachine #1458

Merged
merged 2 commits into from
Nov 21, 2019

Conversation

avanwinkle
Copy link
Collaborator

While StateMachine devices can support arbitrary state names for their progression, they currently must use start as their initial state.

This PR allows State Machines to define any of their states to use as the initial state, with start as the default value. As a result, there should be no breaking change for existing machines that do not specify starting_state:.

Tests included!

* dev: (32 commits)
  0.53.0-dev.76
  implement oc detection procedure
  fix CS
  0.53.0-dev.75
  behave a bit more like spike
  0.53.0-dev.74
  expose oc_time as config option
  0.53.0-dev.73
  fix LED wait times
  fix timings
  0.53.0-dev.72
  use known working command
  0.53.0-dev.71
  update spike
  0.53.0-dev.70
  behave more like the spike game
  0.53.0-dev.69
  add another missing parameter
  0.53.0-dev.68
  Spike Firmware 0.49.0 compatibility
  ...
@jabdoa2
Copy link
Collaborator

jabdoa2 commented Nov 21, 2019

Very well done!

@jabdoa2 jabdoa2 merged commit 76d850a into missionpinball:dev Nov 21, 2019
@avanwinkle avanwinkle deleted the state_machine_starting_state branch December 4, 2023 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants