-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
FC3 migration to Module #276
Conversation
@@ -98,6 +98,29 @@ function Module:defineFloat(identifier, arg_number, limits, category, descriptio | |||
return control | |||
end | |||
|
|||
function Module:define8BitFloatFromGetter(identifier, func, limits, category, description) |
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.
Remember to add documentation, and also tests for any new control
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.
fixed
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.
Will you be adding tests to ModuleTests?
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.
Yes I will try.
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.
We should really get the define8BitFloatFromGetter
added to the module tests before merging this so we can make sure it's tested and correct.
OK. So that is quite a lot of work isn't it? |
It should be really similar to the tests for defineIntegerFromGetter. Check out |
FC3 added to test suite Test pattern for module name changed to allow _UPDATE_COUNTER Module:define8BitFloatFromGetter documented
Removed old code remnant from Module DCS_API* files list_indication documentation corrected
Good catch. I wasn't aware of the value_range field in the json. We should look at what that's actually for. If that's the dcs output, then it doesn't really serve any value and we can remove it. |
Done! |
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.
A couple minor opportunities to clean things up a bit more, but otherwise looks good!
No description provided.