[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tlf-devel] Entry issues & key issues

From: Csahok Zoltan
Subject: Re: [Tlf-devel] Entry issues & key issues
Date: Tue, 2 Jul 2019 20:04:20 +0200
User-agent: Mutt/1.10.1 (2018-07-13)

Thanks Tom for the clarification! It's indeed RECALL_MULTS that interferes
when used with Tab instead of Enter. I was able to reproduce it with Adam's
setup, while in my case it worked as I wasn't using this feature.
(and was using the Enter+Enter sequence)

btw while testing I realized that
tlf -f myconfig.dat
doesn't work, only
tlf -fmyconfig.dat
This one needs a fix, too.


On Mon, Jul 01, 2019 at 08:28:25PM +0200, Thomas Beierlein wrote:
> Hi Adam and Zoli,
> maybe I can add some additional information related to the exchange
> problem.
> Adam as Zoli told you the normal sequence is just to press ENTER after
> entering the call and again after the exchange. TAB is mostly to allow
> you to come back to the call input field from the exchange field for
> corrections.
> Normally in your input sequence (TAB and then ENTER) the exchange is
> kept intact but you have to press ENTER twice.
> ARRLFD is a little bit special here. It sets the RECALL_MULTS keyword
> automatically and tries to find an already known exchange from having
> worked the station on other band or from an INITIAL_EXCHANGE file to
> fill it in.
> If TLF has no information about the exchange field it clears the
> exchange field and that is what you can observe.
> So best would be to always use the ENTER key to switch to the next
> state of the QSO. 
> As a sidenote: Maybe we should rethink the behaviour of the
> RECALL_MULTS and it should only pick up old exchange if the comment
> field is empty. 
> 73, de Tom DL1JBE

reply via email to

[Prev in Thread] Current Thread [Next in Thread]