Yup...it does behave that way. On purpose I would imagine. If you had problems decoding it perhaps you want to hang on to it. How is it supposed to determine when to delete it after you've expressed interest in it?
Ergo the menu option to erase all *.wav files. Mike W9MDB -----Original Message----- From: John Nelson [mailto:j...@rmnjmn.demon.co.uk] Sent: Monday, September 15, 2014 1:54 PM To: WSJT software development Subject: Re: [wsjt-devel] Plan for beta release of WSJT-X v1.4 Mike, Try this. Let WSJT-X be in Monitor mode. Now suppose that you are looking at a particular trace and after the Decode takes place sometime after 52 seconds you notice that your trace was not decoded. Shame. Now press the Decode button, say around 10 secs in the next cycle in hte hope that decode might be successful. Monitor your save directory for the next couple of cycles. When I do this, a wav file will be left and not deleted. --- 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
