Antenna Targeting UX Improvements

[Clayell]

Additionally, fix bug where the targetMode could be set to an invalid mode the first time that the menu is opened
(for some reason this causes a harmless InvalidCastException in the Vector2 scroll view when it activates. GUI is weird)

Additionally, remove log spam from AntennaTarget.Awake()
(would get logged every time a target changed, which is just excessive)

[siimav]

If you feel like using the word "Additionally" then it should be a separate PR.

[DRVeyl]

I don't know why 10 digits is at all sane for these fields. I can see why "4" is 1 too few.

[Clayell]

I don't know why 10 digits is at all sane for these fields. I can see why "4" is 1 too few.

I would argue that more precision is better if the user wants it. 10 digits doesn't seem to break any of the UIs.



(deflection doesn't seem to use all of the digits because of the extra things it does)

[DRVeyl]

Sounds like 20 digits is the go-to! You can always make the UI bigger.
No, I don't think any-amount-of-precision is good UI or good UX. And "it doesn't break the UI" is not a good criterion. IMO you shouldn't have, or be asked to use, an amount that is more than gives you the functionality needed.
2 decimals latitude (0.01 degrees) on Earth is what, ~1 km?

[Clayell]

2 decimals latitude (0.01 degrees) on Earth is what, ~1 km?

Ok, that would require 6 characters for negative numbers though. -70.01. The original complaint was how 4 characters only allowed something like -70.. 6 characters seems fine I suppose. I'll do 7 for deflection to match the original code. (since it can have something in the hundreds place)