Numeric widget and localized number formatting.

[AbdielKavash]

This is the penultimate (still need to do GT++, coming later today) and by far the largest set of changes to support localized number formatting in ModularUI.

• Replaces text fields where the user is expected to input a number with NumericWidget, supporting extended syntax and formatting. (See Added a numeric widget. ModularUI#62.)
• Replaces instances where a dynamic text field is being communicated between server and client with a purely client-side method. In some cases this allows the client to do localization on these texts correctly. (See Added a text supplier for TextWidget. ModularUI#69.)
• Modifies other instances where the UI displays a number to use a locale-aware formatter. (See Added locale-aware formatting of numbers. ModularUI#67.)

 

Notes:

• Most covers correctly understand the maximum possible amount of whatever they are measuring (items, fluids, EU, ...), so expressions like 50% or 100% - 1000 will correctly evaluate to the desired value.
• The positions of some fields in the Item Detector and Advanced Item Detector cover UIs have been moved around to be consistent with each other and other wireless covers. (Wireless frequency on top, cover data below.)
• The UI of Volumetric Flasks was completely redone, as it was godawful.
• Known bug: Robot Arm cover occasionally resets the adjacent slot value to 0 (instead of any slot). This is not caused by this PR, it was also an issue beforehand (Robot Arm cover resets to external slot 0 if not interacted with after placing. GT-New-Horizons-Modpack#15687). If the player interacts with the UI widget at any point and sets the slot to anything (including "Any" again), this is fixed and never happens again with the same cover.
• In a few places I have modified the amounts by which a value changes when the player ctrl- or shift-scrolls on a numeric field. For example, fluid-related fields will now change by 144 when ctrl-scrolled.
• I have specifically only changed places where numbers appear in a ModularUI window. This means that item tooltips, WAILA, scanner text, etc. will show the same number formats as before (almost always either #.# or #,###.#, regardless of regional settings). This could be looked at further if the feature is popular, but not before feature freeze.
• As a reminder, if a player finds the locally-formatted numbers annoying, the current locale can be forced in ModularUI config. This defaults to the system's locale as detected by JDK, but can be changed to any locale (for example, en-US).
• Tracking down every single instance where a mod writes a number is nearly impossible. I use a few heuristics and code searches, but it is very likely that I miss some places. If an UI displays an unformatted or wrongly formatted number somewhere, please report it to be fixed.

Some examples (click to expand):

Energy detector cover using the percent function of NumericWidget:

Some other functions in action:

Machine process (fr-FR locale):

New volumetric flask UI:

[miozune]

How about adding defaultFormat or smth to NumberFormatMUI, so that we don't need to write protected static final NumberFormatMUI numberFormat = new NumberFormatMUI(); everywhere?

[AbdielKavash]

How about adding defaultFormat or smth to NumberFormatMUI, so that we don't need to write protected static final NumberFormatMUI numberFormat = new NumberFormatMUI(); everywhere?

I thought about doing something like this, but the issue is somehow guaranteeing that the singleton format will never be modified. If someone decides to screw with, say, minimum number of decimal places of the global format, it will mess up every other UI opened after that one.

I thought about some solutions (strongly worded javadoc comment vs. an immutable subclass with a singleton), this is something that we can certainly return to either with MUI2 or after the stable release. I already have a couple other ideas to simplify this too.

[miozune]

I see, anyways great work!