Re: [Tlf-devel] Issues with contest scoring w/git code, OK w/1.2.4.5 version in opensuse
Hi Adam, Am Tue, 02 Jul 2019 16:59:49 -0700 schrieb Adam Clark : > Hi all, > > When exporting my Canada Day log to cabrillo, I noticed that tlf > wasn't paying much attention to multipliers - one on each band > instead of the correct counts. This was with the git version of tlf. > thanks for the bug report. It is really helpful to get feedback from TLF users. We will look into it. > When I loaded up the old stable, the multipliers seemed fine and the > score seemed fine. You mean the 1.2.4 version? Other distros have 1.3.2 stable in meantime. > > I'm attaching (hopefully all of) the relevant files - "canadaday" is > actually in a subfolder "rules/" so, "rules/canadaday". > > I can provide further information if anyone wants screenshots of what > each version of tlf looks like with this data. > Thanks. But I hope that the given information is enough. 73, de Tom DL1JBE. -- "Do what is needful!" Ursula LeGuin: Earthsea -- ___ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] Issues with contest scoring w/git code, OK w/1.2.4.5 version in opensuse
Hi all, When exporting my Canada Day log to cabrillo, I noticed that tlf wasn't paying much attention to multipliers - one on each band instead of the correct counts. This was with the git version of tlf. When I loaded up the old stable, the multipliers seemed fine and the score seemed fine. I'm attaching (hopefully all of) the relevant files - "canadaday" is actually in a subfolder "rules/" so, "rules/canadaday". I can provide further information if anyone wants screenshots of what each version of tlf looks like with this data. Thanks, 73, Adam 40SSB 01-Jul-19 04:47 0001 KA6BIM 59 59 162 ab 2 7141.0 80SSB 01-Jul-19 04:53 0002 VE7RAC 59 59 BCab 20 3775.0 80SSB 01-Jul-19 04:54 0003 VE7BC 59 59 BC10 3790.0 80SSB 01-Jul-19 04:58 0004 VE5MX 59 59 SK10 3757.0 80SSB 01-Jul-19 04:59 0005 VE7SCC 59 59 BC10 3765.0 40SSB 01-Jul-19 05:02 0006 VE3MIS 59 59 ON10 7150.9 20SSB 01-Jul-19 16:00 0007 VE4BAE 59 59 MBab 10 14151.0 20SSB 01-Jul-19 16:03 0008 VE3MIS 59 59 ON10 14188.0 20SSB 01-Jul-19 16:05 0009 VE4VT 59 59 MB10 14238.0 20SSB 01-Jul-19 16:13 0010 W3LL 59 59 4872 14176.0 20SSB 01-Jul-19 16:13 0011 VE3KZ 59 59 ON10 14170.0 20SSB 01-Jul-19 16:34 0012 N6RO 59 59 1194 2 14208.0 40SSB 01-Jul-19 17:38 0013 VE6KD 59 59 BC10 7160.0 15SSB 01-Jul-19 17:47 0014 N8OO 59 59 976 ab 2 21242.1 20SSB 01-Jul-19 21:38 0015 VE5FX 59 59 SK10 14183.6 20SSB 01-Jul-19 21:40 0016 N4PN 59 59 8982 14220.5 20SSB 01-Jul-19 21:42 0017 W6AFA 59 59 1512 14225.8 20SSB 01-Jul-19 21:44 0018 K6SRZ 59 59 6362 14244.0 20SSB 01-Jul-19 21:51 0019 VX4WARC59 59 MB10 14197.0 20SSB 01-Jul-19 21:56 0020 VA2QR 59 59 QC10 14204.0 20SSB 01-Jul-19 22:01 0021 VE5MX 59 59 SK10 14215.0 20SSB 01-Jul-19 22:22 0022 K3ZO 59 59 3522 14171.2 20SSB 01-Jul-19 22:24 0023 N1UR 59 59 26 2 14196.0 20SSB 01-Jul-19 22:25 0024 VA2RAC 59 59 QC20 14205.1 20SSB 01-Jul-19 22:26 0025 N8OO 59 59 1224 2 14212.0 20SSB 01-Jul-19 22:51 0026 VE3DC 59 59 ON10 14221.0 20SSB 01-Jul-19 23:24 0027 VO2RAC 59 59 NL20 14167.4 40SSB 01-Jul-19 23:33 0028 VE7AFZ 59 59 BC10 7171.0 40SSB 01-Jul-19 23:39 0029 VA6DJ 59 59 AB10 7171.0 40SSB 01-Jul-19 23:49 0030 VE7RAC 59 59 BC20 7190.0 RULES=canadaday # # # # # TLF-LOGCFG.DAT v. 1.1.0 # # # # Uncomment the options you# # want to enable. See tlf.doc # # for a description of the # # options. You can keep diff- # # erent versions for different # # contests. I keep separate# # configuration files for # # each contest. If you enable # # more than 1 mutually exclu- # # sive options, the last one # # will be efective.# # # # # # # #CTCOMPATIBLE # # # # # EDITOR # # # # # #EDITOR=joe EDITOR=vi #EDITOR=e3 #EDITOR=mcedit # # # # # CALL # # # # # CALL=VA7AQD # # # # # # Time offset from UTC # # # # # TIME_OFFSET=0 TIME_MASTER # # # # # LAN PORT # # # # # addnode only OTHER nodes !! # #ADDNODE=10.0.0.115 #ADDNODE=192.168.1.2 # THISNODE=A # LAN_DEBUG # # # # # KEYERPORT# # # # # NETKEYER #NETKEYERPORT=6789 #NETKEYERHOST=127.0.0.1 # # #
Re: [Tlf-devel] Entry issues & key issues
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 : > > 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 Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
Re: [Tlf-devel] Entry issues & key issues
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 Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
