From 8223861b79c36a82e913642c8800b455f7b301a2 Mon Sep 17 00:00:00 2001 From: Arturs Bekasovs Date: Tue, 10 Dec 2013 17:10:27 +0000 Subject: [PATCH] Refs #6473. Setting initial values for inputs. --- .../MantidWidgets/src/MuonSequentialFitDialog.cpp | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/Code/Mantid/MantidQt/MantidWidgets/src/MuonSequentialFitDialog.cpp b/Code/Mantid/MantidQt/MantidWidgets/src/MuonSequentialFitDialog.cpp index a439f7ca0d73..48a2ce2e3cb4 100644 --- a/Code/Mantid/MantidQt/MantidWidgets/src/MuonSequentialFitDialog.cpp +++ b/Code/Mantid/MantidQt/MantidWidgets/src/MuonSequentialFitDialog.cpp @@ -20,10 +20,17 @@ namespace MantidWidgets { m_ui.setupUi(this); - // TODO: set initial values - initDiagnosisTable(); setState(Stopped); + // Set initial runs text + Workspace_const_sptr fitWS = m_fitPropBrowser->getWorkspace(); + m_ui.runs->setText( QString::fromStdString( getRunTitle(fitWS) ) + "-" ); + + // TODO: find a better initial one, e.g. previously used + m_ui.labelInput->setText("Label"); + + initDiagnosisTable(); + // After initial values are set, update depending elements accordingly. We don't rely on // slot/signal update, as element might be left with default values which means these will // never be called on initialication.