NumericSetting: Stop values from binding to numbered input names.

[jordan-woyak]

The problem:
When the "..." button is clicked, the numeric setting is converted to an input expression. Unfortunately integers are also valid keyboard Input names and get handled by CoalesceExpression.
Despite the expression being 1, the "Sideways Wii Remote" setting turns off, because the keyboard's 1 key is not being pressed..
When the dialog is closed, the expression is correctly converted to a simple true value, but in the meanwhile, it's false, which is especially strange when quickly opening and closing the advanced window.
The Wii Remote Extension setting has the same issue.

The solution:
The sign of the value is always included to not match any Input names.

Alternatively, instead of always including the + sign, decimal places could be always included, but this is maybe equally weird for integer or boolean settings to appear as 1.0. Opinions?

[Miksel12]

Could true and false be added as keywords? Having to add a + sign to every number in order to differentiate between bindings and integers/bools seems not ideal. Having keywords for bools and decimal points for integers seems like a better solution, though probably more involved.

[jordan-woyak]

Could true and false be added as keywords? Having to add a + sign to every number in order to differentiate between bindings and integers/bools seems not ideal. Having keywords for bools and decimal points for integers seems like a better solution, though probably more involved.

true/false could be added, but they are maybe slightly out of place in the input expression language that effectively only has double values. If 1.0/0.0 is being used for int, I think I'd just as soon also do it for bool.

[AdmiralCurtiss]

Looks like a reasonable workaround to me.