-
Notifications
You must be signed in to change notification settings - Fork 50
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
Suggestion: Add option to reload/refresh state modules from Statemachine Editor #10
Comments
I agree, this would be useful. In fact, I have a feature on my to-do list
which adds an automatic reload whenever you save any state file in your
editor. I did not prioritize it that high because it is rather a
convenience feature, but I consider this issue as an upvote and might in
fact have some time during the weeks after Christmas to implement it.
|
pschillinger
added a commit
that referenced
this issue
Dec 17, 2017
I implemented a first version of the updating feature. Does this improve your workflow as desired? Please let me know any feedback about how the feature works for you or if you found bugs there in the corresponding PR #13. Thank you! |
pschillinger
added a commit
that referenced
this issue
Apr 3, 2018
Update states when source code changes (see #10)
alireza-hosseini
pushed a commit
to alireza-hosseini/flexbe_app
that referenced
this issue
Jun 12, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I am prototyping a state machine with some custom state modules, I often realize that I want to modify a state class in some way (e.g. add/remove parameters, add/remove outcomes).
I can edit the module file and make my desired changes; however, those changes are not reflected in the Statemachine Editor GUI.
Instead I have to save my behavior (not always possible), and close/open the FlexBE app.
It might be beneficial to have a 'reload/refresh' button in the Statemachine Editor to update the list of available states and update the state block within the Editor.
Then the workflow would be: Epiphany -> edit module file -> click 'refresh/reload' in Editor -> ...
The text was updated successfully, but these errors were encountered: