tlf-devel
[Top][All Lists]
Advanced

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

Re: When writing the Cabrillo file the exchange is not prompted


From: Nate Bargmann
Subject: Re: When writing the Cabrillo file the exchange is not prompted
Date: Tue, 22 Nov 2022 06:14:24 -0600

* On 2022 22 Nov 03:35 -0600, Csahok Zoltan wrote:
> Hi Nate,
> 
> OK, the issue is in the internal definition of the ARRL-SS contest.
> For some (most likely historical) reason exchange_serial is set
> to true for this contest. The meaning of this field has probably
> drifted from "exchange has a serial number part" to "exchange is a serial
> number only", thus not matching ARRL-SS any more.
> 
> The quick solution is to comment out the offending line in src/setcontest.c:
> @@ -219,7 +219,7 @@ contest_config_t config_arrldx_dx = {
>  contest_config_t config_arrl_ss = {
>      .id = ARRL_SS,
>      .name = "ARRL_SS",
> -    .exchange_serial = true,
> +//    .exchange_serial = true,
>      .points = {
>         .type = FIXED,
>         .point = 2,
> 
> As exchange_serial (also controlled by SERIAL_EXCHANGE) has precedence over
> CABRILLO-EXCHANGE, the value you set as exchange was always ignored.

You're the best!

That did the trick.  Also, I got an error for my format being too wide
and thought about it then went back into logcfg.dat and modified the
CABRILLO-EXCHANGE value by removing the quotes to:

CABRILLO-EXCHANGE= # A 83 KS

And it works as expected!  I suspect that I am the first to use TLF in
SS for a long time so do apply this patch as I would consider that line
the culprit.

> I tested it for a generic contest so this issue didn't pop up.

Hence why I sent you everything I had just to see if the problem would
turn up for you.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Attachment: signature.asc
Description: PGP signature


reply via email to

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