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
Similar to #314, for phetsims/qa#818 ... I inspected occurrences of link and lazyLink, looking for cases where restored state might be overwritten. I found this case, which was also present in the previous (1.4) release.
The range of the Population graph's x-axis is overwritten when restoring state. To reproduce:
Go to the Lab screen
Press the "Add a Mate" button
Let the simulation run until the Population graph starts auto-scrolling to the left. Checking "Limited Food" around generation 3 will ensure that bunnies don't take over the world.
Pause the sim.
Scroll the Population graph fully to the left, so the leftmost x-axis tick mark is 0. The left arrow button (below the graph) is disabled, the right arrow button is enabled. Like this:
Press "Preview Sim" in Studio.
Note that in the Preview, the Population graph's x-axis is fully scrolled to the right, not fully scrolled to the left. The left arrow button is enabled, the right arrow button is disabled. Like this:
In general, if a listener for aProperty sets the value of bProperty, then that code typically needs to be short-circuited when restoring state. The general pattern is:
Fixed in the above commit. @Nancy-Salpepi since you verified #314, would you mind verifying this one in master? If it looks OK, please label as status:fixed-awaiting-deploy.
Similar to #314, for phetsims/qa#818 ... I inspected occurrences of
link
andlazyLink
, looking for cases where restored state might be overwritten. I found this case, which was also present in the previous (1.4) release.The range of the Population graph's x-axis is overwritten when restoring state. To reproduce:
Relevant code in PopulationModel.js, line 183:
In general, if a listener for
aProperty
sets the value ofbProperty
, then that code typically needs to be short-circuited when restoring state. The general pattern is:The text was updated successfully, but these errors were encountered: