<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">This is now available in both mojo and
master branches.<br>
<br>
And it should look like this (not as it came out after I pressed
'send' on the last email.<br>
<font face="monospace"><br>
DX de SQ8T: 21074.0 ON4KST FT8 -15dB from JO20 1829H
JO20 1620Z KO10<br>
DX de YB1LUE: 7074.0 XE2CQ FT8 -10dB from DM12
2380Hz 6 1620Z 28<br>
DX de IZ1CJZ: 14145.0 CN0S Calling.cq..
IM63 1620Z 15<br>
DX de EA4FNX: 7066.0 EA4GCJ Sorteo
ACRACB 14 1617Z 14<br>
DX de SP2DDV: 3573.0 YO4DG FT8 -14dB from KN43
1138Hz 20 1620Z JO83<br>
DX de EA5AJX: 18101.5 WD5EED IM98<>EM44
FT8 MS 1620Z 14<br>
DX de N3TKE: 14233.0 LA5KO
JO59 1621Z MD<br>
DX de F4IZV: 14145.0 CN0S tnx
IM63 1621Z 14<br>
DX de YO9LL: 3518.8 OF9X QSX 3520.10
CW 15 1621Z 20<br>
DX de YO4RDK: 144360.0 PA5Y MSK144 +0 dB
JO21 1621Z 20<br>
DX de WA3ERQ: 18102.2
EA1TE 14 1621Z FN20<br>
DX de EA5D: 14081.0 W9CSX FT4 -07
JN00BB<>EM69 EM69 1622Z IM99<br>
DX de PA3BLS: 50280.0 OK1FRG
JO22LM<MS>JN79UV JN79 1622Z JO22<br>
DX de EA5AJX: 18101.5 AB9PM IM98<>EN54
FT8 WI 1622Z 14<br>
DX de YB1LUE: 7074.0 ZS6WMB FT8 -14dB
1620Hz 38 1622Z 28<br>
DX de PA5Y: 144360.0 PA1ADR Pse tx 2nd u spoil for al
JO22 1623Z JO21<br>
DX de W3LPL: 3503.0 KL7KY Heard in BC
BP51 1623Z FM19<br>
DX de UR6EM: 144360.0 PA5Y MSK144 +5 dB CQ
JO21 1623Z 16<br>
DX de EA1GCN: 7066.0 EA4GCJ Sorteo
Navidad 14 1623Z IN73<br>
DX de UR6EM: 144360.0 DF7RG MSK144 +6 dB HRD
JN68 1623Z 16<br>
DX de LU3MAM: 21018.2 EA7LM Gracias Jose QSO
IM67 1623Z FF57<br>
DX de ON5KQ: 7168.2 KW7Y cq dx - short pass,
strong WA 1623Z JO10<br>
<br>
(now pressing send again and hoping that it all stays nicely
formatted)<br>
</font><br>
On 10/12/2021 16:28, Steve - AA4U wrote:<br>
</div>
<blockquote type="cite" cite="mid:md5:+8hUsuWQ5FhyUkav3AUJFA==">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="auto">Thanks for the explanation!</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div id="composer_signature" dir="auto">
<div style="font-size:85%;color:#575757" dir="auto">Sent from my
Verizon, Samsung Galaxy smartphone</div>
</div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<div dir="auto" style="font-size:100%;color:#000000" align="left">
<div>-------- Original message --------</div>
<div>From: Dirk Koopman via Dxspider-support
<a class="moz-txt-link-rfc2396E" href="mailto:dxspider-support@tobit.co.uk"><dxspider-support@tobit.co.uk></a> </div>
<div>Date: 12/10/21 09:44 (GMT-06:00) </div>
<div>To: "Mike McCarthy, W1NR via Dxspider-support"
<a class="moz-txt-link-rfc2396E" href="mailto:dxspider-support@tobit.co.uk"><dxspider-support@tobit.co.uk></a> </div>
<div>Cc: Dirk Koopman <a class="moz-txt-link-rfc2396E" href="mailto:djk@tobit.co.uk"><djk@tobit.co.uk></a> </div>
<div>Subject: Re: [Dxspider-support] DXSpider v 1.55 build 0.221
</div>
<div><br>
</div>
</div>
There's an interesting little conundrum...<br>
<br>
It turns out that this is (and now was) Mojo behaviour, which I
clearly <br>
put in deliberately, in July last year [ed: git blame is good
here]) - <br>
which then got back ported to master in order to get the set/width
<br>
command and auto sizing console.pl there as well as in mojo. I
may not <br>
have been completely awake at the time of the original mod.<br>
<br>
Anyway, there is another problem which has been there since I
started <br>
putting stuff into these slots around the time field (ie since
2003), <br>
which is that the slots were not treated independently from each
other. <br>
Which meant that the first of the [grid, itu, cq, us state]
(depending <br>
on whether they are set) that matched for the spot would win and
if <br>
there was no entry for available for the other slot in that
category (eg <br>
G working W or one has a known grid square and the other doesn't)
then <br>
it would prevent the other slot being filled with coarser (as in <br>
location area) information. Also the order was wrong as usstate
was <br>
last, instead of second after grid square. So, as I was in there
fixing <br>
the reported problem and, given that this was the general idea in
the <br>
first place - which has never actually worked as I intended in
2003 - <br>
and has been never addressed or noticed since. I have now fixed it
thusly:<br>
<br>
DX de W3LPL: 18085.3 OY1CT Heard in PA 14 1532Z FM19<br>
DX de DL4MFF: 21074.0 AF4HX JN57IW<>EM85MM tnx <br>
ft8 NC
1532Z 14<br>
DX de EA8CPU: 7108.0 EA1GFC Especial Naviad inf ea1fdd
<br>
1cot. 14 1532Z 33<br>
DX de F6ARC: 7007.0 VU2TMP CQ 22 1532Z 14<br>
DX de SP5ELA: 3524.7 SM4CUQ CQN 14 1533Z KO02<br>
DX de DM8MH: 7074.0 MW7CCS FT8 -09dB from IO81 699Hz <br>
73! 14 1533Z
JO51<br>
DX de I3LTT: 7173.0 IT9JAV DMSM SM1743 + Strenna <br>
Natale JM67 1533Z
JN65<br>
DX de W3PRL: 14254.0 HA8JV KN06 1533Z FN00<br>
DX de TI3ATS: 7175.0 TI2BSH POTA ACTIVATION Call him <br>
!! 7 1533Z
EJ89<br>
DX de UR6EM: 144360.0 DJ6OL MSK144 +2 dB CQ JO52 1534Z
16<br>
DX de N6OKU: 14222.0 LA4UOA 59 in CA 14 1534Z CA<br>
DX de OE6PID: 7173.0 IT9JAV DMSM SM1743 + Strenna <br>
Natale JM67 1534Z
JN77<br>
DX de DM8MH: 7074.0 ON5MEV FT8 +03dB from JO10 2706Hz
<br>
73! 14 1534Z JO51<br>
DX de LZ2YO: 3764.0 LZ5RO JJ00 1534Z KN13<br>
DX de K6VHF: 50260.0 KI0E DM43<MS>DN13 ID 1534Z DM43<br>
DX de F1TXI: 21074.0 K1TKS IN96<>FN42 MA 1535Z IN96<br>
<br>
This is what set/dxgrid + set/usstate + set/dxcq or set/dxitu now
gives <br>
you.<br>
<br>
Obviously you can have just one or two of these active at once. <br>
Set/dxitu and set/dxcq remain mutually exclusive.<br>
<br>
Enjoy<br>
<br>
Dirk G1TLH<br>
<br>
</blockquote>
<br>
</body>
</html>