Closed pixelzoom closed 6 months ago
hmmm... I am not sure if this should be part of the region and culture work. It seems like non-default layoutBounds is odd in general, so I'm inclined to try the default bounds out and see what happens...
Same as in https://github.com/phetsims/balancing-act/issues/109, removed the custom layoutBounds. Assigning back to review
Hmmm. Okay this does change a lot of the sizing of stuff which I think will need to be readjusted to match the published version... I'm not sure if it's worth the time to do that or if that's within the scope of this publication. I don't think I fully understand the pros and cons of switching over to the default layout bounds from a maintenance and user perspective...
@pixelzoom can you provide more context on any compelling reasons for why this work should be prioritized? Or is this only worth it for PhET-iO?
From Dev Meeting today it was decided that we would like to close all these issues as won't do. Before doing so we will need to revert the commits.
To avoid having to revisit this topic in the future, and to make it clear to future maintainers, I recommend a code comment wherever non-default layoutBounds are used.
For sims that have already been published with PhET-iO, something like this in BLLConstants.ts:
// While these layoutBounds differ from the default, PhET-iO customizations may rely on these bounds.
// So do not change. See https://github.com/phetsims/beers-law-lab/issues/289.
LAYOUT_BOUNDS: new Bounds2( 0, 0, 1100, 700 ),
Or for non-PhET-iO sims, something as simple as this in RAPConstants.ts:
SCREEN_VIEW_LAYOUT_BOUNDS: new Bounds2( 0, 0, 835, 504 ), //TODO https://github.com/phetsims/reactants-products-and-leftovers/issues/75
Changes reverted. Feel free to review and close @marlitas
Sounds good let's close!
This sim currently uses non-default
layoutBounds
. In ArithmeticView.js:Per https://github.com/phetsims/phet-io/issues/1939...
layoutBounds
should not be changed for published PhET-iO sims because doing so may disrupt client customizations. So evaluate whether to changelayoutBounds
before publishing a PhET-iO version.If you decide not to change layoutBounds, document why in ArithmeticView.js, and refer to this issue.