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

[Adam Clark]

Hi Thomas,

That's very interesting - and this past weekend I was working the RAC Canada 
Day contest a bit (and I likely have some questions soon about how to build an 
appropriate rules file as well) and I didn't experience the same behaviour.

However, I hope that the tab vs. enter bit is treated like an issue that 
requires resolution.  I don't believe it shouldn't matter how one gets to the 
exchange field - if I've put in an exchange and hit enter, I want to log the 
QSO, and it shouldn't matter how I wound up getting to the exchange field in 
the first place.  Can you imagine if a GUI treated you differently depending 
on whether you clicked on a text entry field vs tabbed in to it vs. hit enter 
to get to it, and then refused to enter the data (or cleared it out) when you 
went to click OK?  heh.

Thanks and 73,
Adam

On Monday, July 1, 2019 11:28:25 AM PDT 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
> 
> Am Sun, 30 Jun 2019 08:48:12 -0700 schrieb Adam Clark <address@hidden>:
> > Hi Zoli,
> > 
> > Upon further testing, if I use the following sequence:
> > 
> > - input call
> > - Hit Tab to move the cursor to the exchange field
> > - Input exchange
> > - Hit Enter
> > 
> > The exchange is erased and upon re-entering the exchange and pressing
> > Enter, it is logged.
> > 
> > If, I use Enter to move from the call sign entry to the exchange
> > fields, pressing Enter in the exchange field is logging on the first
> > try.
> > 
> > I have attached my logcfg.dat and arrlfd as requested, too.
> > 
> > Thanks!
> > 73,
> > Adam
> > 
> > On Saturday, June 29, 2019 9:56:20 AM PDT Csahok Zoltan wrote:
> > > Hi Adam,
> > > 
> > > Thanks for the update. I also tried it with Konsole (v18.04.0, KDE
> > > 5.54) and the cursor keys worked.
> > > 
> > > For the FD issue: is this the sequence that you use?
> > > - input call
> > > - Enter << cursor moves to exchange field
> > > - input exchange
> > > - Enter << here your exchange gets erased, QSO is not logged
> > > 
> > > Maybe send me your logcfg.dat and rules file, as with my setup it
> > > works and I beleive I don't nothing special.
> > > 
> > > 73,
> > > Zoli
> > > 
> > > On Fri, Jun 28, 2019 at 03:45:54PM -0700, Adam Clark wrote:
> > > > Hi again Zoli,
> > > > 
> > > > Just thought I'd let you know that I tested with the git version
> > > > of tlf, and adding some test entries (still using the field day
> > > > setup/config), I have to re-enter the exchange each time.
> > > > 
> > > > However, cursor keys work, so that's a bonus!
> > > > 
> > > > 73,
> > > > Adam