Re: [Tlf-devel] v1.4 topics

2018-11-03 Thread Ervin Hegedüs
On Fri, Nov 02, 2018 at 11:21:57PM -0500, Nate Bargmann wrote: > * On 2018 02 Nov 12:30 -0500, Thomas Beierlein wrote: > > P.S.: The 'todo' list now: > > > Consider requiring a key press on the first screens when Tlf is started > without a log file. They often close too quickly to read all the >

Re: [Tlf-devel] v1.4 topics

2018-11-03 Thread Ervin Hegedüs
Hi Thomas, and all, On Fri, Nov 02, 2018 at 06:28:57PM +0100, Thomas Beierlein wrote: > * automatically switch back to 'Run' mode from "grab spot" after QSO I thought it too, that's a missing feature > * switch to hamlib's freq_t for frequencies ( and maybe factor out > hamlib stuff to a separ

[Tlf-devel] ARRL SS fixes

2018-11-03 Thread Nate Bargmann
I've pushed a couple of patches to my repository offering some fixes for ARRL Sweepstakes. One makes necessary corrections to the arrlss rules file and the other replaces the '---' strings in the log entry line with ' ' when NO_RST is used. My quick test showed this did not break Cabrillo gener

Re: [Tlf-devel] debian test failure

2018-11-03 Thread Csahok Zoltan
Managed to install a Sparc64 system and reproduce the issue. It is a test-only error due to only storing a pointer instead of saving the actual message string during the tests. Some of these strings are generated in local variables that may "disappear" before it comes to actually check them. It's

Re: [Tlf-devel] debian test failure

2018-11-03 Thread Ervin Hegedüs
Hi Zoli, On Sat, Nov 03, 2018 at 09:25:49PM +0100, Csahok Zoltan wrote: > Managed to install a Sparc64 system and reproduce the issue. > > It is a test-only error due to only storing a pointer instead of > saving the actual message string during the tests. > Some of these strings are generated in