Fixed bug in clock schedule rules where "or After" schedule codes

were not displayed correctly.
This commit is contained in:
Patrick Linstruth 2019-05-04 08:24:02 -07:00
parent 31390b34d7
commit 45790ad80e
2 changed files with 2 additions and 2 deletions

View File

@ -64,7 +64,7 @@ RDSchedRulesList::RDSchedRulesList(QString clockname,RDConfig *config)
min_wait[i] = q1->value(1).toInt();
not_after[i] = q1->value(2).toString();
or_after[i] = q1->value(3).toString();
or_after_II[i] = q1->value(3).toString();
or_after_II[i] = q1->value(4).toString();
}
else {
max_row[i] = 1;

View File

@ -146,7 +146,7 @@ editSchedCodeRules::editSchedCodeRules(Q3ListViewItem *item,
}
comboBox_not_after->setCurrentText(item->text(3));
comboBox_or_after->setCurrentText(item->text(4));
comboBox_or_after->setCurrentText(item->text(5));
comboBox_or_after_II->setCurrentText(item->text(5));
label_description = new QLabel(this);
label_description->setGeometry( QRect( 200, 40, 300, 40 ) );