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
It can often be confusing to new users when they type in a moving object's name, then change the Type, but there is still no object found, and the fields are not filled.
Due to the order of the fields (name, then type) an expected behavior would be to fill out the fields in that order and have the matching done after the type is set.
This also leads to the unexpected and hard to detect (if unlikely) bug that if I set the type to Non-sidereal, search for an asteroid, and find results, those results will stay if I change the type to Sidereal, type in a new asteroid name, and switch back to Non-sidereal. Thus leaving me with valid elements for the wrong target.
The text was updated successfully, but these errors were encountered:
It can often be confusing to new users when they type in a moving object's name, then change the Type, but there is still no object found, and the fields are not filled.
Due to the order of the fields (name, then type) an expected behavior would be to fill out the fields in that order and have the matching done after the type is set.
This also leads to the unexpected and hard to detect (if unlikely) bug that if I set the type to Non-sidereal, search for an asteroid, and find results, those results will stay if I change the type to Sidereal, type in a new asteroid name, and switch back to Non-sidereal. Thus leaving me with valid elements for the wrong target.
The text was updated successfully, but these errors were encountered: