Re: Fred Siegmund
> Try Tucnak.
I tried, and do not understand it at all. I failed to get it to do
any sensible thing. And then it just crashed.
I'd also prefer if tlf would also support the VHF+ bands, with however
bad feature set, as long as it writes the correct frequency to the log
file.
73,
Re: Csahok Zoltan
> Hello Herve,
>
> python-config in Debian/Ubuntu is part of python3-dev package. Not sure about
> the OS you are using.
> For a reference you can check the step "Install dependencies" in
> https://github.com/Tlf/tlf/blob/master/.github/workflows/ci-build.yml
Also make sure you
Re: Thomas Beierlein
> Two points here:
>
> - Journaling is easy, but to be honest TLF provides quite some
> robustness in that sense too. I have not heard any complies about
> lost data in all the years.
Some time last year, I was auditing (well, reading) the tlf source to
check that. There
I finally found the time to finish this. Thanks to Nick Craig-Wood
(@ncw) for merging his patch with this one!
Pull request: https://github.com/Tlf/tlf/pull/294
Re: Thomas Beierlein
> > The general feature (calling stop_morse) already works, only the
> > support in rigctld was missing.
> >
> Jus
Re: Thomas Beierlein
> Am Fri, 29 Oct 2021 22:40:10 +0200
> schrieb Christoph Berg :
>
> > Re: To tlf-devel@nongnu.org
> > > In fact aborting the message does work, but rigctld isn't properly
> > > forwarding the request through for the IC-7610 here.
Re: To tlf-devel@nongnu.org
> In fact aborting the message does work, but rigctld isn't properly
> forwarding the request through for the IC-7610 here.
\stop_morse was simply not implemented in rigctld yet, but the patch
has already been merged:
https://github.com/Hamlib/Hamlib/commit/8cba9d7ee93
Re: Thomas Beierlein
> But anyway - your work looks promising. What most users will miss is
> the ability to abort the message. It would be good to have a
> solution for that problem before merging it in.
In fact aborting the message does work, but rigctld isn't properly
forwarding the request thr
Re: Onno VK6FLAB
> Hi Christoph,
>
> Out of interest, why did you not add hamlib functionality to cwdaemon
> instead?
I want to get rid of extra moving parts. Tlf is already talking to
Hamlib directly for the frequency and mode, why not use that
connection for keying as well?
I have a cwdaemon-c
Hi,
I've been poking around with adding support for CW keying via Hamlib
to Tlf. I have it somewhat working. :)
https://github.com/df7cb/tlf/tree/hamlib-cw
Basically the status is:
Working:
* Hamlib keyer is activated by HAMLIB_KEYER keyword
* CW sending works
* setting CW speed
Re: Drew Arnett
> Dumb question: why 25 rows? Sorry for asking first, before examining code.
I think you can start with more rows and then resize to 20 rows and it
still works. The restriction seems to remain from the time where
resizing the window wasn't supported. (With less rows things start
Re: Nate Bargmann
> ../../tlf/src/cqww_simulator.c:155:15: warning: adding 'int' to a string does
> not append to the string [-Wstring-plus-int]
> "+++" + 3 - slow);
> ~~^~~
> ../../tlf/src/cqww_simulator.c:155:15: note: u
11 matches
Mail list logo
