#Noob Q Big Picture Parent-Child Machine Approaches

1 messages · Page 1 of 1 (latest)

queen grove
#

Say I have a parent machine orchestrating two child machines: an audio player and a timer.

  • orchestrationMachine (parent)
  • timerMachine (child)
  • audioMachine (child)

Intended result is parent orchestrating when different audio plays at different times -- while also allowing for all the normal pause, mute, volume etc functionality defined within the child audio player.

I understand how the parent machine invokes and triggers events within those children machines: play the audio at different times etc.

I get that.

But I don't see how the user can also interact with the various child machine audio controls of mute, volume etc for that instance that was invoked by the parent - without duplicating and bubbling up all those child machine events and actions at the parent level, just to share the same instance?

I'm sure I'm missing something fundamental. 🙂 Thanks!

proud cedar
#

state.children.get(‘<audio machine id>) will give you the instance of the audio machine