I wasn't sure about this video as I usually have issues understanding accents like this, but this one was made very clear and was laid out well with an example of the problem it intends to solve from the beginning. Well done.
Hi , nice video , right now I'm working based on this package (first time btw), my process ocurs in a loop , that means during this process I fire triggers, transitioning my objects to 2 states: succeeded or failed, but when my loop ends I need to fire a final trigger let's say AllSuccessful, AllFailured or PartialSuccess depending of the result of my process , so my point is: once I fired these final triggers the state machine is able to move all objects in succeeded/failured state to the final state or should I do something manually like the actions / functions that you explain in the video ? once again many thanks for sharing, appreciate it
Thanks. excellent one. How to configure it for multiple iterations? Something like, if I fire Acceleration 3 times, then the state should be stopped. ?
I wasn't sure about this video as I usually have issues understanding accents like this, but this one was made very clear and was laid out well with an example of the problem it intends to solve from the beginning. Well done.
Glad it helped!
Very well organized and clear presentation(s) on the state machine topics. Nice work.
Thanks!
Very well done.... excellent pace and explained it in a very simple way
Glad it was helpful!
Hi , nice video , right now I'm working based on this package (first time btw), my process ocurs in a loop , that means during this process I fire triggers, transitioning my objects to 2 states: succeeded or failed, but when my loop ends I need to fire a final trigger let's say AllSuccessful, AllFailured or PartialSuccess depending of the result of my process , so my point is: once I fired these final triggers the state machine is able to move all objects in succeeded/failured state to the final state or should I do something manually like the actions / functions that you explain in the video ? once again many thanks for sharing, appreciate it
Thanks. excellent one. How to configure it for multiple iterations? Something like, if I fire Acceleration 3 times, then the state should be stopped. ?
That should be doable using an internal state table, as at this point it's beyond just an action, another dimension is now introduced
good walk through
Thanks
Thank you! Very nice explained :)
@Alexander Tomashchuk, thanks for watching!
amazing teacher
Thanks for watching!
Excellent tutorial
@Craig Munday, thanks for watching!
in 5:17 , car.configure(Car.state.Stopped), in the permit, (Car.Action.Start,Car.state.stopped), was it right? Should not be car.state.started?
Yes, you are correct, it should have been Started.
its awesome
Thanks!
Great video. Could you please share your source code. I could not find in your github.
Thanks for watching, I will do that
@@DotNetCoreCentral thanks lots, could you please share the url? thanks again!
how to store/pass current sate and action to the machine so that based on the current state it can go to the next state?
I am not sure what is the use case, as you configure the machine itself to react based on a state and action.
awoesome