I’m raising again the issue of the DXCC worked window in the RSGB Commonwealth Contest (CC). Bjorn you may recall that we exchanged mails a while back on this. The problem is that the CC is perhaps unique in that the first THREE QSOs with a Commonwealth call area count for bonus points. As currently implemented, all the DXCC window shows is whether there has been at least one QSO with a call area whereas Win-Test also indicates whether the three QSOs have been achieved, through changes in colour in the DXCC window. ISTR that Bjorn said this was tricky in DXL because of the way the DXCC world window worked. I’m just wondering whether there is any prospect of a fix for this. Other than this, DXL goes from strength to strength – great work everyone. 73, Don, G3BJ / G5W |
| Reply Like More |
| Yes, there are two fundamental problems with DXLog in BERU and we have a ticket in our backlog for this that today is close to a year old. 1. When logging a QSO, all bandmap spots from the same DXCC are marked as not being a multiplier anymore even when you have not worked the multiplier three times. (Incoming spots are however always correctly displayed as valid multipliers until the count of three)2. There is no graphical representation of the gradual progress (unworked, worked, no longer a multiplier) in the worked DXCC window or bandmap. I have reverse engineered the code and understood roughly where the problems are but the required changes are quite dramatic and unfortunately well beyond my abilities. Björn |
DX Log and Commonwealth Contest
17 Monday Jan 2022
Posted in News