Track available bounds was null after reset all.

[samreid]

Track available bounds was null after reset all.

[samreid]

Fixed above and will be ready for review in the next dev version.

[samreid]

The bug exhibited by this problem was that tracks wouldn't smooth out after reset all.

[bryo5363]

@samreid can you please elaborate on this issue? I am not really sure what to look for here.

[samreid]

I created this problem using these steps:

1. Select Playground screen
2. create a track
3. press reset all
4. create a track
5. try putting the 1st control point on top of the 3rd control point => it doesn't smooth out.

Hopefully fixed in the latest version. Let me know if you need further discussion.

[bryo5363]

@samreid after refreshing I was able to reproduce a track like this.

Then the weird behavior ensues...

https://drive.google.com/file/d/0B7WUaZM7uvVKeTRHb3g5amN1MzA/edit?usp=sharing

[samreid]

Thanks for the screencast, that is very helpful!

[samreid]

The latest problem may be addressed by #207.

[bryo5363]

This issue is still apparent on iPad @samreid

[samreid]

I could not reproduce either of the two above problems on Win8/Chrome. Can you please specify which problem you are seeing? Can you create the problem on Win8/Chrome?

[bryo5363]

I was able to produce this on Safari 6.1.6 OSX 10.8.5

[bryo5363]

Still able to produce a track like this in Safari 9537.78.10.17.1

It is easy to produce tracks like this. All you need to do is keep dragging new tracks and the bounds will not be enabled.

[samreid]

I expect the above track to be somewhat rare with students, and it may be very difficult to solve, so perhaps this shouldn't prevent publication.

[ariel-phet]

Interviews suggest that students are not interested in creating these sorts of tracks. Usually, they try to make loops, so I am in agreement that it should not prevent publication, with a caveat.

@samreid, I am fine if such tracks are able to be produced, but I am not fine if the smoothing behavior goes away when reset all is pressed. I could not reproduce this issue on Win 7 chrome. Is it specific to safari, or what is going on here?

[samreid]

The primary problem for this issue (about the smoothing being broken after reset all) was solved above in 0ceb742

Closing based on @ariel-phet's remarks.