Hi all,
good to hear you could fix the problem at your side Drew.
I am a bit late with answering as I am just two days away from holiday
and there are quite some things to finish before.
I did some double check on the code in meantime and there are only 3
places where the run mode is changed:
PBKAC as I suspected. (Why would I be the only one with a problem
with such basic functionality.)
The indicator in the upper left hand corner is 'Log' for run mode and
'S' for search and pounce. OK. The source code made that obvious.
Ugh. For some reason I was thinking 'Log' was a 3rd mode.
Hi Drew,
On Thu, Aug 01, 2019 at 02:42:23PM +, Drew Arnett wrote:
> Thanks for digging in, Ervin.
>
> I will look at that pull request. Another difference in my case is
> that I'm using my pywinkeyerdaemon with a K1EL (www.hamcrafters.com)
> 'WinKeyer USB'.
Thanks for digging in, Ervin.
I will look at that pull request. Another difference in my case is
that I'm using my pywinkeyerdaemon with a K1EL (www.hamcrafters.com)
'WinKeyer USB'. https://github.com/drewarnett/pywinkeyerdaemon (One
diff though, as I need to update it for the later
Hi Drew,
On Thu, Aug 01, 2019 at 02:17:13AM +, Drew Arnett wrote:
> I just tried a fairly new desktop hard disk (less than a year old)
> with an older USB 2.0 to SATA adapter. I put my local working
> directory there (logcfg.dat, rules, cty, partials, log), and the same
> bad behavior
I just tried a fairly new desktop hard disk (less than a year old)
with an older USB 2.0 to SATA adapter. I put my local working
directory there (logcfg.dat, rules, cty, partials, log), and the same
bad behavior persists. Will install buster to hard disk (not via USB
adapter) and see how that
I just subscribed to the tlf-devel list, so I should get those emails
in my mailbox now. (I was using the archive web page.)
I will respond to Ervin and Tom's emails. Tom's first.
Yes, your assumption is correct. I am using CW. NETKEYER works great!
Yes, the bad behavior is reproducible.
I
Drew, Thomas, and all,
On Tue, Jul 30, 2019 at 02:26:25PM +, Drew Arnett wrote:
I don't have Debian Buster actually, but have a Debian SID - it's
not so far from Buster :), and all related components are same as
your side:
# dpkg -l tlf *hamlib* | grep ^ii
ii libhamlib++-dev:amd64 3.3-5+b1
Hi all,
On Wed, Jul 31, 2019 at 07:57:31AM +0200, Thomas Beierlein wrote:
> Am Tue, 30 Jul 2019 14:26:25 +
> schrieb Drew Arnett :
>
> I tested tlf-1.3.2 (compiled from the sources here) with your
> provided settings (Thanks) and it worked as expected - staying in RUN
> mode after stopping
Hi Drew,
welcome to the list and thanks for the report.
Am Tue, 30 Jul 2019 14:26:25 +
schrieb Drew Arnett :
> Hi,
...
> I think I've used run mode before, but not much I think. I could not
> get it to work this time. Observed behavior:
...
> Run mode has problems. Start auto CQ which
Hi,
I tried using the tlf packaged with Debian buster for the IARU HF
contest. I had a problem with trying to operate in run mode.
I've used TLF and been very happy with it in the past. Love the
leanness. Love the keyboard only operation.
I think I've used run mode before, but not much I
11 matches
Mail list logo
