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
Browser: Chrome Version 61.0.3163.79 (Official Build) (64-bit)
Problem description: If a sensor is placed right in-between two identical charges, it will correctly show the value of 0 V/m, but the arrow displayed will remain the arrow from before it read 0 v/m. This is done most easily with snap to grid so it snaps into place between the two charges.
Steps to reproduce:
Turn on Values
Turn on grid
Turn on snap to grid
Place two identical charges on the screen spaced apart so that the midpoint can have something snap into its place
Place a sensor on the midpoint
Screenshot:
This was found in phet-io, where the report a problem option was unavailable, so there is no more troubleshooting information
The text was updated successfully, but these errors were encountered:
Also the degrees value says 0 regardless of what position it is pointing, and in State the upper and lower sims will point in different directions, with the lower sim always pointing in the same direction regardless of the direction the upper sim is pointing.
For phetsims/qa#37
Test device: Hanson
Operating System: Win 10
Browser: Chrome Version 61.0.3163.79 (Official Build) (64-bit)
Problem description: If a sensor is placed right in-between two identical charges, it will correctly show the value of 0 V/m, but the arrow displayed will remain the arrow from before it read 0 v/m. This is done most easily with snap to grid so it snaps into place between the two charges.
Steps to reproduce:
Turn on Values
Turn on grid
Turn on snap to grid
Place two identical charges on the screen spaced apart so that the midpoint can have something snap into its place
Place a sensor on the midpoint
Screenshot:
This was found in phet-io, where the report a problem option was unavailable, so there is no more troubleshooting information
The text was updated successfully, but these errors were encountered: