-
Notifications
You must be signed in to change notification settings - Fork 123
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
Feature/prop bytes #161
Feature/prop bytes #161
Conversation
Signed-off-by: Paul Miller <[email protected]>
Signed-off-by: Paul Miller <[email protected]>
Signed-off-by: Paul Miller <[email protected]>
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.
Happy to Approve - just a simple question.
I forget how is the doc get updated so it's added to this list (pasted below)
There should maybe be a mention that this is exclusively assume constant step animation and the KF suite is used to find nearest ones if more than one... - also does an host expect the length to be constant for all frames (aside when null on a frame)?
By default the following parameter types animate…
I updated the custom example plugin code to correctly check for Bytes support and also added a test for correct handling of really large data (10MB). |
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.
Compiles OK for me. Looks good.
Ideally we should add C++ support, but this is good enough for the spec change. |
This pull request adds the new Bytes property type to the ofxParam.h header, and adds sample code to the existing example for the Custom parameter type.
Feature Issue #145