You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 Properties associated with the "Projector Mode" checkbox that typically appears in the Options dialog for a sim that has this feature.
The first Property is profileNameProperty, the name of the selected ColorProfile. The choices are typically "default" or "projector", and it's presented as a pair of radio buttons in Studio. For example, for Gas Properties:
The second Property is internal to ProjectorModeCheckbox, a joist common-code component. It maps profileNameProperty to a boolean value, as required by Checkboxes in general. It currently doesn't appear in Studio because of lack of support for dynamic elements (Options dialog is created on demand). When it does appear, it will look like a typical Checkbox in Studio, featured by default. In Gas Properties, it's phetioID would be:
The question is whether to instrument projectorModeEnabledProperty. It is sufficient to instrument profileNameProperty, and projectorModeEnabledProperty is an internal implementation detail. If instrumented, it would be as a convenience, at the expense of exposing internals of ProjectorModeCheckbox.
projectorModeEnabledProperty is currently instrumented, because Checkboxes expect their associated Property to be instrumented (so that they can create a linked element). If that's not desired, we'll need to investigate how to get around that -- a good thing to do, since I don't think that's a valid expectation.
Creating this issue based on feedback by @jessegreenberg in #569 (comment).
There are 2 Properties associated with the "Projector Mode" checkbox that typically appears in the Options dialog for a sim that has this feature.
The first Property is
profileNameProperty
, the name of the selected ColorProfile. The choices are typically "default" or "projector", and it's presented as a pair of radio buttons in Studio. For example, for Gas Properties:The second Property is internal to
ProjectorModeCheckbox
, a joist common-code component. It mapsprofileNameProperty
to a boolean value, as required by Checkboxes in general. It currently doesn't appear in Studio because of lack of support for dynamic elements (Options dialog is created on demand). When it does appear, it will look like a typical Checkbox in Studio, featured by default. In Gas Properties, it's phetioID would be:gasProperties.general.navigationBar.phetButton.phetMenu.optionsDialog.content.projectorModeCheckBox.projectorModeEnabledProperty
The question is whether to instrument
projectorModeEnabledProperty
. It is sufficient to instrumentprofileNameProperty
, andprojectorModeEnabledProperty
is an internal implementation detail. If instrumented, it would be as a convenience, at the expense of exposing internals ofProjectorModeCheckbox
.projectorModeEnabledProperty
is currently instrumented, because Checkboxes expect their associated Property to be instrumented (so that they can create a linked element). If that's not desired, we'll need to investigate how to get around that -- a good thing to do, since I don't think that's a valid expectation.Since this came up in the context of Gas Properties PhET-iO design phetsims/gas-properties#30, assigning to @arouinfar.
The text was updated successfully, but these errors were encountered: