-
Notifications
You must be signed in to change notification settings - Fork 4
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
quadraticProperty
and savedQuadraticProperty
have different phetioReadOnly
metadata
#200
Comments
No. I'll make it so. |
Done in the above commits. @arouinfar please review, close if OK. |
Looks like you accidentally did this one backwards and made |
That's not possible - Do you really want me to restore |
Understood, thanks @pixelzoom.
Yes, please. The original design spec included presetting the saved quadratic. This is feasible to do with he API if Studio is being used to predetermine the saved quadratic. I've detailed how to use the 'Get Command' functionality to do this in examples.md:
|
Changes to |
For phetsims/qa#959
@Nancy-Salpepi asked over Slack:
The reason for this discrepancy is that
quadraticProperty
is read-only, but then I started wondering why we treat these two properties differently. Consulting the PhET-iO design doc, I found these requirements:This appears to be the reason why the
quadraticProperty
is read-only but thesavedQuadraticProperty
is not. That said, I don't know if we would have made the same decisions if starting over today. If clients want to create a quadratic with the API, they need to communicate with three different properties (one for each coefficient in the equation). It seems more convenient for instructional designers to export the desired quadratics using the 'Get Command' functionality in Studio, and then share the code with the wrapper developer. This is the method we recommend for creating a saved quadratic for comparison purposes.@pixelzoom would you have any reservations about changing
quadraticProperty
tophetioReadOnly: false
?The text was updated successfully, but these errors were encountered: