Units of measure labels missing from many input boxes

[Nealius]

There are quite a few triggers wtih text input for area/size/altitudes that are missing labels indicating the units of measure used. A couple examples being:

-AAA min/max engagement altitude is MSL rather than AGL
-unit's altitude higher/lower is in meters regardless of metric/imperial UI settings

I believe most of these are annotated in the manual, but common sense dictates that the annotations should also be next to the input field in the UI, particuarly when there's inconsistency in what uses which unit of measure.

Edited May 2, 2024 by Nealius

[TEMPEST.114]

This has been mentioned many times. The whole UI/UX is very ‘anti-ux coder’ utilitarian themed and written by people who knew how everything works under the hood but think end users are mind readers - nothing has been designed with the end users in mind. Labels, units, descriptions and even utterly missing information (see my recent bug report on the helper gates for the manual/real life test vs what the devs were thinking but never conveyed).
 

We need a ui/ux programmer/designer to overhaul the M.E. But that’s probably never going to happen. We all just learn by trial & error or asking the same questions over and over again ad infinitum. 
 

New creators just keep finding the same stuff we’ve been saying for a decade.

Edited May 3, 2024 by TEMPEST.114

[Nealius]

What gets me is that it isn't that hard to think about things from the users' perspective, yet they seem completely unable to do so.

[TEMPEST.114]

6 hours ago, Nealius said:

What gets me is that it isn't that hard to think about things from the users' perspective, yet they seem completely unable to do so.

Most 'coders' don't or won't think about anything other than getting the technical stuff done (the bit they're interested in) and the UI is just a frustration or annoyance. 

There's a reason why UI/UX programmers are rare but valued.