Scratch that patch....it messes up the memory for tuningt....I'll fix it.
Mike
On Thursday, September 13, 2018, 2:30:14 PM CDT, Black Michael
<[email protected]> wrote:
The order of operation for adjusting the tuning power back to operational
power needs to change.It was causing a potential power spike for about 10-20ms
before tuning was actually turned off.So simply move it ahead of the power
adjustment.Tuning should most always be less than operational....so don't think
we need to have this on both sides of the tune power adjustment.
@@ -5905,6 +5908,17 @@
static bool lastChecked = false;
if (lastChecked == checked) return;
lastChecked = checked;
+
+ if (m_tune) {
+ tuneButtonTimer.start(250);
+ } else {
+ m_sentFirst73=false;
+ itone[0]=0;
+ on_monitorButton_clicked (true);
+ m_tune=true;
+ }
+ Q_EMIT tune (checked);
+
QString curBand = ui->bandComboBox->currentText();
if (checked && m_tune==false) { // we're starting tuning so remember Tx and
change pwr to Tune value
if (m_config.pwrBandTuneMemory ()) {
@@ -5924,15 +5938,6 @@
m_PwrBandSetOK = true;
}
}
- if (m_tune) {
- tuneButtonTimer.start(250);
- } else {
- m_sentFirst73=false;
- itone[0]=0;
- on_monitorButton_clicked (true);
- m_tune=true;
- }
- Q_EMIT tune (checked);
}
void MainWindow::stop_tuning ()
de Mike W9MDB
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
