Agreed. In addition, as a CQ caller, you have no control over the order in which WSJT-X decoded the received calls and who's first.
AFAIK, the "persistent" caller can remain 1st if he calls on a frequency lower than the other callers and the signal is strong enough to be decoded on the first pass... I also fail to understand the objections to this feature request. Using the feature is completely optional and no operational change is required by anyone who doesn't need it. On the other hand, in this long discussion I have not seen alternative solutions for the problematic scenarios describes by the supporters of the proposal. 73 Zeev 4X5ZS On Wed, Dec 4, 2019 at 7:42 AM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > It's not a lockout file. > > The idea is very simple. > > Right now call first always picks the 1st decode...ergo the problem.... > > So the idea is that once a call is worked it gets put in a list (doesn't > matter whether or not you log it). The call first logic checks the list > and ignores anybody in it. > If call first does not trigger then the 1st entry that was detected would > be used. > So it would all be completely transparent, only temporarily blocks calls, > and clears itself. > > If you have 5 people calling you it will go 1,2,3,4,5 and start over again > whereas right now it's 1,1,1,1,1, ad nauseum. > > For the most part nobody would even notice this was happening except the > 1st decode may not be the one chosen. > > de Mike W9MDB >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
