Mike if the intent was not to shorten the time for a QSO, then what was the
purpose?
Once again, see my example if I’m sending Tx3 and waiting for Tx4. The station
I’m working sends Tx4 once, and logs the contact because typically when we see
a popup, it generally means to do something. I might not hear his single
transmission of Tx4, whether it is on meteor scatter, EME or HF.
73 de Sebastian, W4AS
> On Jan 1, 2017, at 5:15 PM, Black Michael <[email protected]> wrote:
>
> It doesn't shorten the time for a QSO. You must be referring to the idea
> that RRR is the last message for the CQ side. Seems the fast mode people
> still send a 73 which isn't surprising. But the EME people and HF want the
> RRR to be last.
>
> Can't argue with it being an option, can you? Should make everybody happy.
>
> de Mike W9MDB
>
>
> From: Jay Hainline <[email protected] <mailto:[email protected]>>
> To: 'Black Michael' <[email protected] <mailto:[email protected]>>; 'WSJT
> software development' <[email protected]
> <mailto:[email protected]>>
> Sent: Sunday, January 1, 2017 4:08 PM
> Subject: RE: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
>
> I don’t know for certain why this was changed in the first place except the
> JT65 HF crowd is always looking for a way to sidestep a sequence to shorten
> the time for a QSO. This does not work in the meteor scatter VHF world where
> you are relying on random data bits to fly in on a meteor for less than 1
> second and you are trying to decode just what the guy on the other end has
> received. If it aint broke, don’t fix it.
>
> I hope I don’t get black balled for being negative like the Ham Radio Deluxe
> people do to users of their software. Lol ;-)
>
> 73 Jay KA9CFD
>
> From: Black Michael [mailto:[email protected] <mailto:[email protected]>]
> Sent: Sunday, January 1, 2017 3:39 PM
> To: WSJT software development <[email protected]
> <mailto:[email protected]>>
> Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
>
> I think the consensus solution would be to make it a user option.
> Seems the meteor scatter people have the most problems with it since they
> were quick to speak up.
>
> I had proposed at one time to make the "Prompt me to log QSO" a tri-state box
> so one could check 73, 73+RRR, or none. But seems the binary choice is
> clearer and there are no other tri-state checkboxes in WSJT-X.
>
> So this patch makes it optional with an added option line below the current
> prompt option. All worlds should be happy with this.
>
> https://www.dropbox.com/s/s5xwpc39bubmzxx/rrr_option.patch?dl=1
> <https://www.dropbox.com/s/s5xwpc39bubmzxx/rrr_option.patch?dl=1>
>
>
>
> de Mike W9MDB
>
>
> From: Seb <[email protected] <mailto:[email protected]>>
> To: WSJT software development <[email protected]
> <mailto:[email protected]>>
> Sent: Sunday, January 1, 2017 1:26 PM
> Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
>
> IMHO the introduction of the log QSO prompt when you are sending RRR does not
> solve or help anything.
>
> It is useless when you are doing meteor scatter. If I’m sending Tx3 and the
> other station hears that and sends Tx4 and then logs the contact, it is not a
> valid QSO because I have no idea if the other station has heard my report. I
> will end up sending Tx3 several times until I just give up on the contact.
>
> 73 de Sebastian, W4AS
>
>
>
> On Jan 1, 2017, at 9:38 AM, Jay Hainline <[email protected]
> <mailto:[email protected]>> wrote:
>
> This was introduced in r7431. I think its bad form to get a prompt to log the
> QSO when you are sending RRR. How do you know if your QSO partner has
> received it if he does not send 73 back to you??
>
> Jay Hainline KA9CFD
> Colchester, IL EN40om
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
