-
Notifications
You must be signed in to change notification settings - Fork 9
Call the steps method after super.loop #311
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
Conversation
Removed code from opmode.py that calls the steps method. In mrc_class_method_def.ts: Renamed classSpecific and getClassSpecificForInit to superInitParameters and getSuperInitParameters. In mrc_steps.ts: Added constant STEPS_METHOD_NAME and changed the steps method name to _steps. In python.ts: Added constant PERIODIC_METHOD_NAME. In extended_python_generator.ts: Changed finish method to add the code for calling the steps method to the end of the loop method. Renamed getClassSpecificForInit to getSuperInitParameters.
alan412
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to the other review comment, do we want to warn the user if they don't have a loop or steps in an opmode?
…face into pr_issue_298
…od, show a warning on the opmode details block.
Done. |
alan412
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good. A few minor things.
…face into pr_issue_298
…that needs to be translated.
alan412
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Call the steps method after super.loop.
Changed the steps method name to _steps.
Let the user delete the loop method in an OpMode.
Fixes #298