From d2ef4d21b3012f72928c1d4b769aa2aacba700ac Mon Sep 17 00:00:00 2001 From: gxalpha Date: Sat, 12 Aug 2023 00:21:46 +0200 Subject: [PATCH] UI: Don't cap auto-config wizard FPS whole number precision at 2 Capping the precision for whole numbers results in scientific notation being used for any number that's larger than what can be displayed with the given precision. In case of 2, that would be anything larger than 99, resulting in 120 for example to be shown as 1.2e+02. Let's not cap the precision for whole numbers ourselves and just use the default value (which at the time of writing would be 6). --- UI/window-basic-auto-config.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UI/window-basic-auto-config.cpp b/UI/window-basic-auto-config.cpp index 9cccf0ebdec0d5..2357808126bae8 100644 --- a/UI/window-basic-auto-config.cpp +++ b/UI/window-basic-auto-config.cpp @@ -136,7 +136,7 @@ AutoConfigVideoPage::AutoConfigVideoPage(QWidget *parent) (long double)ovi.fps_num / (long double)ovi.fps_den; QString fpsStr = (ovi.fps_den > 1) ? QString::number(fpsVal, 'f', 2) - : QString::number(fpsVal, 'g', 2); + : QString::number(fpsVal, 'g'); ui->fps->addItem(QTStr(FPS_PREFER_HIGH_FPS), (int)AutoConfig::FPSType::PreferHighFPS);