Options should fallback to default when non-numerical input is given

[elexis]

The current options page allows the user to enter arbitrary numerical values for some settings.

The min/max setting is implemented and working (f.e. observer limit), but when the user types a non-numerical or empty string, the input is not rejected but saved and passed to the code using it, causing errors in the affected components (at least the sound config).

[Vladislav Belov]

If #4039 would be finished (IMO, it should be finished), then the ticket will be irrelevant for the sound config.

[fabio]

Thanks for working on #4039! But this issue is still relevant when manually editing config files? (somewhat related also #3737)

[Vladislav Belov]

Replying to fabio:

Thanks for working on #4039! But this issue is still relevant when manually editing config files?

For sound config with sliders - no.

[fabio]

I meant ​editing user.cfg. One can still do that other than using the sliders.

[Vladislav Belov]

Replying to fabio:

I meant ​editing user.cfg. One can still do that other than using the sliders.

I too :P If you set sound.mastergain = "blabla" in user.cfg then you won't get any error, but value should be clamp(0, min, max).

[Imarok]

Move tickets to Misc. UI as "UI & Simulation" got some sub components.