-
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
instrument ScoreDisplay* types #69
Comments
@ariel-phet FYI. |
In case you were planning to dive right into this... Please hold off for a couple of hours, I'm making an API change that will make this a bit easier. |
API change completed. Status bars now create and manage their score display. So that makes this issue irrelevant:
|
Currently the only game that is instrumented is BAA, and it will be largely reworked before republish. I don't plan on working on this until we are working on stable api for a sim with a game. Unassigning myself. |
Understood--I suspect we will instrument these for the next stable PhET-iO game sim. Unassigning myself until then. |
ScoreboardBar
appears at the top of many games, and looks like this:In #66,
ScoreboardBar
was deprecated and replaced byFiniteStatusBar
, to accommodate enhancement requests by designers.One of the requests was to be able to use the new
ScoreDisplay*
types to display the score. The 4ScoreDisplay*
types were developed in #59 and #66, and they look like this:The score display in
ScoreboardBar
was implemented and instrumented for PhET-iO like this:Moving to
FiniteStatusBar
creates two issues for PhET-iO:(1) None of the
ScoreDisplay*
types are currently instrumented for PhET-iO. So until they are instrumented, we've lost PhET-iO support for the score display in any games that usedScoreboardBar
.(2) Instances of
ScoreDisplay*
types are not created byFiniteStatusBar
; they are created by the client and passed toFiniteStatusBar
as a constructor argument. So if the structure is exposed in thephetioID
(which it typically is) that structure is now totally different.I have no plans to address this. Assigning to @samreid and @zepumph so that they are aware of this.
The text was updated successfully, but these errors were encountered: