Could this be related? It's the only place that m_diskData is set to false
which is required to delete the current file.
Seems to require you NOT be transmitting and m_monitoring to be false.
I'm betting it never tries to remove it under certain circumstances.
So put a qDebug statement in there and log all the file removes to see if
your left overs never even tried to be removed.
void MainWindow::on_monitorButton_clicked (bool checked)
{
if (!m_transmitting)
{
auto prior = m_monitoring;
monitor (checked);
if (!prior)
{
m_diskData = false; // no longer reading WAV files
// put rig back where it was when last in control
Q_EMIT m_config.transceiver_frequency (m_lastMonitoredFrequency);
setXIT (m_txFreq);
}
-----Original Message-----
From: John Nelson [mailto:j...@rmnjmn.demon.co.uk]
Sent: Monday, September 15, 2014 9:09 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Plan for beta release of WSJT-X v1.4
Mike,
I want to monitor this (.wav files remaining) and find out what actions
taken by the user (me) which can cause this to happen. Then it can be
fixed - if needed.
--- John G4KLA
----------------------------------------------------------------------------
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
