> > WSJT-X is open source. You can make those changes you are suggesting, > thereby customizing your station operations.
Yes I know that. But: However, do not be surprised if you actually loose a lot of > confirmations... My station. My logbook. My rules. Yes and so my proposal is to make the "short QSO" the default for WWDIGI. The contest's rules, that everybody in the contest plays by. Contesters will like the higher QSO rates. Maybe it will catch on more generally, maybe not. And I would be happy to implement this as a patch against 2.4.0-rc4 or whatever version, if I had reason to think it would be accepted. 73, Paul K6PO On Fri, May 7, 2021 at 5:34 PM Jeff Stillinger via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > WSJT-X is open source. You can make those changes you are suggesting, > thereby customizing your station operations. There is no licensing > restrictions that would stop you from doing so (see GPL 3). > > However, do not be surprised if you actually loose a lot of > confirmations. Yes, I am one of those stations that expect the basic > exchange format as outlined in the User Guide to be completed in order to > be confirmed. My station. My logbook. My rules. I will always > complete any QSO regardless. I just don't log for confirmation the ones > that have missing pieces. I strongly believe this helps maintain the > integrity of awards. But... that is me. Someone else may feel > differently. It's all good in the rf hood. > > > > > On 5/6/21 3:28 PM, Martin Davies G0HDB wrote: > > The FT4 mode was introduced in WSJT-X version 2.1.0 in 2019; the release > notes and announcements state that the mode is intended for use in HF > digital contesting where 'quick-fire' exchanges such as those achieved > using RTTY are desired. I'd like to suggest a change that would help > achieve this aim a bit better; the following applies to v2.1.0 and all > subsequent versions up to and including v2.3.1 (I haven't yet tried any of > the RC versions of v2.4.0). > > An FT4 (and an FT8!) QSO generally looks something like the following: > > CQ K1JT FN20 > K1JT G0HDB IO82 > G0HDB K1JT -10 > K1JT G0HDB R-08 > G0HDB K1JT RR73 > K1JT G0HDB 73 > > Currently, the logging window only pops open on my screen to prompt me to > log the QSO when the final (Tx5) '73' message is being sent - this is to > all extents and purposes superfluous because the QSO has been successfully > completed when K1JT has sent his RR73 (and I've received it). My sending > the superfluous '73' message extends the overall duration of the QSO by > adding a further Tx period at my end of the sequence so I can't move on to > trying to start the next QSO. > > I'd like to suggest that the logging window is opened when I've *received* > the other station's RR73 message and that sending the final Tx5 '73' > message is either removed from the sequence altogether or is made > optional. This would help to improve the overall throughput of FT4 QSOs. > > The code to open the logging window on receipt of an incoming 'RR73' > message and to desist from sending the Tx5 '73' message must already exist > within the app because that's what already happens when I operate as a > Hound in FT8 Fox & Hounds mode - when I receive the Fox's 'RR73' the > logging window pops open and my system doesn't send the unnecessary Tx5 > '73' . > > I'd actually like to see the logging window open in any mode when I either > send *or receive* an RRR or RR73 message - in my opinion that would align > the prompting to log the QSO much more closely with the completion of the > exchange of the essential information for the QSO and would leave the > sending of a final '73' as an optional nicety. > > -- > 73, Martin G0HDB > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <#m_6602682828413212526_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > _______________________________________________ > wsjt-devel mailing > listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > -- > Jeff Stillinger - KB6IBB > KB6IBB Laboratories > Wylie, Texas - United States > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
