Better way of updating m_lastQSOProgress, when signal report is first sent.

This commit is contained in:
Joe Taylor 2021-02-05 16:49:56 -05:00
parent 70f460355b
commit d4f4057751
1 changed files with 4 additions and 2 deletions

View File

@ -4783,7 +4783,6 @@ void MainWindow::doubleClickOnCall(Qt::KeyboardModifiers modifiers)
void MainWindow::processMessage (DecodedText const& message, Qt::KeyboardModifiers modifiers)
{
m_lastQSOProgress=m_QSOProgress;
// decode keyboard modifiers we are interested in
auto shift = modifiers.testFlag (Qt::ShiftModifier);
auto ctrl = modifiers.testFlag (Qt::ControlModifier);
@ -5192,7 +5191,10 @@ void MainWindow::processMessage (DecodedText const& message, Qt::KeyboardModifie
qDebug() << "aa" << m_lastQSOProgress << m_QSOProgress << rpt << m_lastMessageSent.trimmed();
// Keep signal report fixed during a QSO.
if((m_lastQSOProgress < REPORT or m_lastQSOProgress > ROGER_REPORT) and
(m_QSOProgress==REPORT or m_QSOProgress==ROGER_REPORT)) ui->rptSpinBox->setValue(n);
(m_QSOProgress==REPORT or m_QSOProgress==ROGER_REPORT)) {
ui->rptSpinBox->setValue(n);
m_lastQSOProgress=m_QSOProgress;
}
// Don't genStdMsgs if we're already sending 73, or a "TU; " msg is queued.
m_bTUmsg=false; //### Temporary: disable use of "TU;" messages