Closed samreid closed 1 year ago
Also, on Thursday we discussed a fillInDynamic
sort of method in StringUtils, which would help move this forward. I think @jonathanolson is assigned, but I couldn't see a paper trail.
I made a first pass at this and it's working well. Will need more attention once we have fillInDynamic
and correct suffixes StringProperty
. Also, do I need to addLinkedElement
on this? I used TReadOnlyProperty<string>
everywhere, but not sure if that's a match for studio autoselect.
Studio autoselect seems like it's working great. All that's left here is waiting on 3 features:
.value
or .link
on StringProperty values inline.On hold until there is progress on those features.
I believe all of those items are done (*StringProperty, PatternStringProperty, and the .value/.link inline)
The remaining work for this issue is to convert fillIn
to PatternStringProperty
. I started on that for the circuit element readouts (when values is checked).
However, I found that these are not even PhET-iO instrumented. So it seems a question for the designers: which cases of fillIn
should be phet-io instrumented and/or studio autoselectable?
UPDATE: I'm also asking since it is nontrivial to add these features, so I want to make sure it's desired.
@samreid and I tested this with locales=* and runtime changes to locale are updating the sim strings nicely, so this issue can be closed. There are a few strings that are not being updated, but we will create a new issue for this.
May be easier once https://github.com/phetsims/mean-share-and-balance/issues/99 is complete.