Frode and The Community-at-large, Yes its invalid – the discussion has clearly identified that and I suspected that at the first post. The community has done a great job in clarifying this not only just for me but also lots of others.
No more discussion needed on that subject of the callsign validity forever as it is repetitive and it has been most clearly identified …. WSJT-X has correctly prevented Tx response to the station…. Good Job ☺ But… There is a point that many of you are missing here and that I am trying to get across … So I’ll place this in a container for clarity: -------------------------------------------------------------------------------------------------------------------------- Why has the stream been decoded (good) and the logic allowed it to be identified – displayed - as coming from Morocco (bad)? The station should not display that it has come from Morocco in the first place as the call violates the rules of callsign structures for that DXCC entity. That is the real point I am making here ! -------------------------------------------------------------------------------------------------------------------------- There are many ways that this could be adjusted when the codebase for r2.2.2 is examined with some methods having greater impact than others to the codebase – If this behaviour has not been addressed already with other tweaks that may have entered the codebase > r2.2.2 (which we know is awaiting the Hamlib go). There is no point posting changes to the codebase as it is closed … what I could post may upset something else unknown to me. So therefore we have to post “anomalies identified” and rely on the intelligence of our core development team to consider, rate and implement changes if necessary. Many many many posts of mine have been about refactoring logic to prevent and eliminate false decodes and user confusion. This is a false lead issue reported here created a user confusion issue in a number of stations at the time that contacted me (Remember many of us hunt DX in packs !). I could validate the confusion issue when it presented itself. Therefore I have a responsibility to report the matter to the community !!! Almost all my posts are around improving utility especially for the “learner” and decreasing end-user confusion ☺ 73 Steve I VK3VM / VK3SIR
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
