Simulation of Componentables will render components added after starting

[angusjfw]

Status	Ticket/Issue
Ready	Ticket

Main changes

• Simulation of Componentables will render components added after starting. Each tick the simulated component config is checked for new components and if found they are added to the sim.

Other notes (e.g. implementation quirks, edge cases, questions / issues)

• I had to make a fix to the Componentable class which maybe could be handled better. When using componentable.add_component with a 'name' parameter, the component's name is overridden with the parameter, presumably so that it is consistent with what the parent component will call it. But this did not override the name on the component's Recreatable config, so I had to change it to do so. Otherwise this meant that my sim code, which relies on the component names from the config to distinguish them, wouldn't add work with this code:

  pitop.add_component(Button("D1"))
  pitop.add_component(Button("D2"), name="button2")

  because pitop.button2.config['name'] == 'button' but did work with this

  pitop.add_component(Button("D1"))
  pitop.add_component(Button("D2", name="button2"))

So this works now but it feels not quite right messing with the recreatables _config... probably fine though.

Manual testing tips

• I updated an example as well as adding a test

[codecov[bot]]

Codecov Report

Base: 59.85% // Head: 59.81% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (488e1b4) compared to base (78dd869). Patch coverage: 20.58% of modified lines in pull request are covered.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #602 +/- ## ========================================== - Coverage 59.85% 59.81% -0.04% ========================================== Files 155 155 Lines 7811 7829 +18 ========================================== + Hits 4675 4683 +8 - Misses 3136 3146 +10 ``` | Flag | Coverage Δ | | |---|---|---| | unittests | `59.81% <20.58%> (-0.04%)` | :arrow_down: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pi-top#carryforward-flags-in-the-pull-request-comment) to find out more. | [Impacted Files](https://codecov.io/gh/pi-top/pi-top-Python-SDK/pull/602?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pi-top) | Coverage Δ | | |---|---|---| | [packages/simulation/pitop/simulation/simsprite.py](https://codecov.io/gh/pi-top/pi-top-Python-SDK/pull/602?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pi-top#diff-cGFja2FnZXMvc2ltdWxhdGlvbi9waXRvcC9zaW11bGF0aW9uL3NpbXNwcml0ZS5weQ==) | `40.90% <5.26%> (-0.76%)` | :arrow_down: | | [packages/simulation/pitop/simulation/simulation.py](https://codecov.io/gh/pi-top/pi-top-Python-SDK/pull/602?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pi-top#diff-cGFja2FnZXMvc2ltdWxhdGlvbi9waXRvcC9zaW11bGF0aW9uL3NpbXVsYXRpb24ucHk=) | `48.06% <35.71%> (-1.08%)` | :arrow_down: | | [packages/core/pitop/core/mixins/componentable.py](https://codecov.io/gh/pi-top/pi-top-Python-SDK/pull/602?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pi-top#diff-cGFja2FnZXMvY29yZS9waXRvcC9jb3JlL21peGlucy9jb21wb25lbnRhYmxlLnB5) | `75.43% <100.00%> (+2.22%)` | :arrow_up: | Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pi-top). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pi-top)

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.