(Solved for me by setting LC_NUMERIC="en_US.UTF-8", but potentially relevant here so letting you know)
I used the GUI in Ubuntu 22.04 with LC_NUMERIC=de_DE.UTF-8.
When I inserted e.g. 50.123456 with a ., it automatically made 5,0123456E7 out of it.
When I then stored the scenario with comma-separated floating point numbers and tried re-opening it, I got:
.
After setting export LC_NUMERIC="en_US.UTF-8" in my bashrc, I could use . everywhere and everything floating-point related worked ✅
So it looks to me like some places in the GUI adjust to the LC_NUMERIC setting, while others may be hard-coded to expect a dot, where the combination of both could cause issues.
(Solved for me by setting
LC_NUMERIC="en_US.UTF-8", but potentially relevant here so letting you know)I used the GUI in Ubuntu 22.04 with
LC_NUMERIC=de_DE.UTF-8.When I inserted e.g.
50.123456with a., it automatically made5,0123456E7out of it.When I then stored the scenario with comma-separated floating point numbers and tried re-opening it, I got:
After setting
export LC_NUMERIC="en_US.UTF-8"in my bashrc, I could use.everywhere and everything floating-point related worked ✅So it looks to me like some places in the GUI adjust to the LC_NUMERIC setting, while others may be hard-coded to expect a dot, where the combination of both could cause issues.