Entry issues & key issues

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Entry issues & key issues

Adam Clark
Hi all,

I recently discovered TLF and used it to play around with during this past
Field Day.  I had a couple of questions about it as I had two issues:

First, I was operating phone only and when I went to log a QSO, very often the
exchange field would just blank rather than enter the QSO.  Only once or twice
did hitting enter (with both callsign and exchange entered) actually log the
QSO on that attempt.  I can tell you it was tricky at times waiting for
confirmation of a QSO and hitting enter watching the exchange disappear after
it might have been sitting there for a few minutes.

The second item seems really strange but has obviously been an issue along the
way - arrow keys didn't function in it at all, so I wasn't able to make use of
any function that relied on them.

My environment was running tlf within kde's konsole.  After discovering cursor
keys weren't working, I tried running it with "TERM=linux tlf", but that
didn't help the issue.

So I suspect there's likely items that I may have not done appropriately in
logcfg.dat or elsewhere, but I haven't found the information on what the
issues might have been.  Pretty much everything else got working very easily,
including rig control, packet interface, cabrillo export, etc. and I am
grateful for finding this logger!

The packaged version I have installed here is tlf-1.2.4.5-lp150.3.3.x86_64
from the opensuse hamradio repository.

Thanks all in advance!
-Adam



_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Csahok Zoltan
Hi Adam,

Glad to hear that you used TLF during the FD. We strive improving it,
so any feedback (including bugs reports, of course) is welcome.

The issue (or at least something similar) in SSB mode I've also experienced:
one had press Enter twice to get the QSO logged. Now, however, I was not
fully able reproduce it using the latest version from git.
Were you in CQ or S&P mode? Did you use Enter or Tab to switch to the exchange
field?

Regarding the arrow keys I have to check it on a KDE system.

73,
Zoli


On Thu, Jun 27, 2019 at 12:15:27PM -0700, Adam Clark wrote:

> Hi all,
>
> I recently discovered TLF and used it to play around with during this past
> Field Day.  I had a couple of questions about it as I had two issues:
>
> First, I was operating phone only and when I went to log a QSO, very often the
> exchange field would just blank rather than enter the QSO.  Only once or twice
> did hitting enter (with both callsign and exchange entered) actually log the
> QSO on that attempt.  I can tell you it was tricky at times waiting for
> confirmation of a QSO and hitting enter watching the exchange disappear after
> it might have been sitting there for a few minutes.
>
> The second item seems really strange but has obviously been an issue along the
> way - arrow keys didn't function in it at all, so I wasn't able to make use of
> any function that relied on them.
>
> My environment was running tlf within kde's konsole.  After discovering cursor
> keys weren't working, I tried running it with "TERM=linux tlf", but that
> didn't help the issue.
>
> So I suspect there's likely items that I may have not done appropriately in
> logcfg.dat or elsewhere, but I haven't found the information on what the
> issues might have been.  Pretty much everything else got working very easily,
> including rig control, packet interface, cabrillo export, etc. and I am
> grateful for finding this logger!
>
> The packaged version I have installed here is tlf-1.2.4.5-lp150.3.3.x86_64
> from the opensuse hamradio repository.
>
> Thanks all in advance!
> -Adam
>
>
>
> _______________________________________________
> Tlf-devel mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/tlf-devel

_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Adam Clark
Hi there Zoli!

The pressing enter twice issue wouldn't have been much of an issue itself, to
be sure, but it was that it was erasing data the first time around that made
it difficult to work with.

I believe it was S&P mode - I didn't ever switch it or wind up calling CQ
anyway, so if it defaults to S&P mode then that would have been it.

I could try grabbing the code from git and seeing if it's affected the same
way or not - I may have a chance to (very casually) work the RAC Canada Day
contest this weekend, so could be fun to test TLF again.

Thanks and 73,
Adam

On Thursday, June 27, 2019 1:15:38 PM PDT Csahok Zoltan wrote:

> Hi Adam,
>
> Glad to hear that you used TLF during the FD. We strive improving it,
> so any feedback (including bugs reports, of course) is welcome.
>
> The issue (or at least something similar) in SSB mode I've also experienced:
> one had press Enter twice to get the QSO logged. Now, however, I was not
> fully able reproduce it using the latest version from git.
> Were you in CQ or S&P mode? Did you use Enter or Tab to switch to the
> exchange field?
>
> Regarding the arrow keys I have to check it on a KDE system.
>
> 73,
> Zoli
>
> On Thu, Jun 27, 2019 at 12:15:27PM -0700, Adam Clark wrote:
> > Hi all,
> >
> > I recently discovered TLF and used it to play around with during this past
> > Field Day.  I had a couple of questions about it as I had two issues:
> >
> > First, I was operating phone only and when I went to log a QSO, very often
> > the exchange field would just blank rather than enter the QSO.  Only once
> > or twice did hitting enter (with both callsign and exchange entered)
> > actually log the QSO on that attempt.  I can tell you it was tricky at
> > times waiting for confirmation of a QSO and hitting enter watching the
> > exchange disappear after it might have been sitting there for a few
> > minutes.
> >
> > The second item seems really strange but has obviously been an issue along
> > the way - arrow keys didn't function in it at all, so I wasn't able to
> > make use of any function that relied on them.
> >
> > My environment was running tlf within kde's konsole.  After discovering
> > cursor keys weren't working, I tried running it with "TERM=linux tlf",
> > but that didn't help the issue.
> >
> > So I suspect there's likely items that I may have not done appropriately
> > in
> > logcfg.dat or elsewhere, but I haven't found the information on what the
> > issues might have been.  Pretty much everything else got working very
> > easily, including rig control, packet interface, cabrillo export, etc.
> > and I am grateful for finding this logger!
> >
> > The packaged version I have installed here is tlf-1.2.4.5-lp150.3.3.x86_64
> > from the opensuse hamradio repository.
> >
> > Thanks all in advance!
> > -Adam
> >
> >
> >
> > _______________________________________________
> > Tlf-devel mailing list
> > [hidden email]
> > https://lists.nongnu.org/mailman/listinfo/tlf-devel
>
> _______________________________________________
> Tlf-devel mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/tlf-devel




_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Adam Clark
In reply to this post by Csahok Zoltan
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

On Thursday, June 27, 2019 1:15:38 PM PDT Csahok Zoltan wrote:

> Hi Adam,
>
> Glad to hear that you used TLF during the FD. We strive improving it,
> so any feedback (including bugs reports, of course) is welcome.
>
> The issue (or at least something similar) in SSB mode I've also experienced:
> one had press Enter twice to get the QSO logged. Now, however, I was not
> fully able reproduce it using the latest version from git.
> Were you in CQ or S&P mode? Did you use Enter or Tab to switch to the
> exchange field?
>
> Regarding the arrow keys I have to check it on a KDE system.
>
> 73,
> Zoli
>
> On Thu, Jun 27, 2019 at 12:15:27PM -0700, Adam Clark wrote:
> > Hi all,
> >
> > I recently discovered TLF and used it to play around with during this past
> > Field Day.  I had a couple of questions about it as I had two issues:
> >
> > First, I was operating phone only and when I went to log a QSO, very often
> > the exchange field would just blank rather than enter the QSO.  Only once
> > or twice did hitting enter (with both callsign and exchange entered)
> > actually log the QSO on that attempt.  I can tell you it was tricky at
> > times waiting for confirmation of a QSO and hitting enter watching the
> > exchange disappear after it might have been sitting there for a few
> > minutes.
> >
> > The second item seems really strange but has obviously been an issue along
> > the way - arrow keys didn't function in it at all, so I wasn't able to
> > make use of any function that relied on them.
> >
> > My environment was running tlf within kde's konsole.  After discovering
> > cursor keys weren't working, I tried running it with "TERM=linux tlf",
> > but that didn't help the issue.
> >
> > So I suspect there's likely items that I may have not done appropriately
> > in
> > logcfg.dat or elsewhere, but I haven't found the information on what the
> > issues might have been.  Pretty much everything else got working very
> > easily, including rig control, packet interface, cabrillo export, etc.
> > and I am grateful for finding this logger!
> >
> > The packaged version I have installed here is tlf-1.2.4.5-lp150.3.3.x86_64
> > from the opensuse hamradio repository.
> >
> > Thanks all in advance!
> > -Adam
> >
> >
> >
> > _______________________________________________
> > Tlf-devel mailing list
> > [hidden email]
> > https://lists.nongnu.org/mailman/listinfo/tlf-devel
>
> _______________________________________________
> Tlf-devel mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/tlf-devel




_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Csahok Zoltan
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
>

_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Adam Clark
Hi Zoli,

Sorry, I believe you wanted clarity on that previously and I forgot to add it
in.  I will test again later and let you know for sure, but I *believe* it was
exactly the sequence you described, though it is possible I'm using tab to
move to the exchange field and am not remembering currently.

I will double check on that and respond again.

Thanks!
73,
Adam

On Saturday, June 29, 2019 9:56:20 AM PDT you 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




_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Adam Clark
In reply to this post by Csahok Zoltan
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

_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel

arrlfd (1K) Download Attachment
logcfg.dat (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Thomas Beierlein-4
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 <[hidden email]>:

> 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  



--
"Do what is needful!"
Ursula LeGuin: Earthsea
--


_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Csahok Zoltan
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.

73,
Zoli



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
>
>

_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Reply | Threaded
Open this post in threaded view
|

Re: Entry issues & key issues

Adam Clark
In reply to this post by Thomas Beierlein-4
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 <[hidden email]>:
> > 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




_______________________________________________
Tlf-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tlf-devel