-
Notifications
You must be signed in to change notification settings - Fork 2
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
Suggested change in Template #349
Comments
Oh, I also
|
Great suggestion! It will be included in the coming release. |
Here is why I passed the "My Response Args" in to case structure. If caller send sync message of "Macro: DoSomething" to callee, which is consist of several sub-states. This wire is needed to pass the actual return value from the middle state in "Action: Step3". \\ sub-states of "Macro: DoSomething"
Action: Step1
Action: Step2 \\ return value
Action: Step3 Caller will get the return value as response for "Macro: DoSomething" after all sub-states are executed by callee. But anyway, I agree with you that the users could easily do it by themselves. That's a corner case. I accept the change. It helps the template looks better. :) |
The first impression a new User gets of your template is the large number of wires coming out of the "Parse State Queue++".
It gives the impression that this framework is going to be hard to understand. It looks complex. Here is my suggestion of moving things around a bit:
I've
The text was updated successfully, but these errors were encountered: