Re: [wsjt-devel] Autoseq on previous QSO
No, it's not intuitive. Better is: Single click = lookup; Double click = call. On Mon, Oct 15, 2018 at 6:00 PM Tom Melvin wrote: > > Would it not just be easier to Un-Tick the ‘Double Click on call sets TX > Enable’ in Settings - you can click to your hearts content, do the DX > lookup, play with QRZ etc. > > Make sure they have finished and when you are happy with split/freq etc. > just click Enable button > > Lot less chance of making errors > > Tom > GM8MJV > > > > > On 15 Oct 2018, at 19:55, Carey Fisher wrote: > > Yes, Gary's right. I would like a single click (or ???) to do the lookup > so I don't have to "quickly jab the Halt Tx button". > > On Mon, Oct 15, 2018 at 2:39 PM Gary McDuffie wrote: > >> >> >> > On Oct 15, 2018, at 11:22, Black Michael via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> wrote: >> > >> > Maybe we have a different opinion of the path-of-least-resistance here. >> >> Personally, I often double click a line just to have the callsign looked >> up and get the grid, whether I intend to work him or not. I just have to >> quickly jab the halt tx button to be sure it doesn’t go out or at least is >> limited to a second or so transmit, if that. >> >> Gary - AG0N >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > > > -- > Carey Fisher > careyfis...@gmail.com > > ___ > 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 > -- Carey Fisher careyfis...@gmail.com ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Autoseq on previous QSO
No...it's not easier as I never want to turn that off. For example I almost exclusively use JTAlert and single-clicking a CQ there starts a QSO just like one would want. And JTALert also gets it right when clicking on a non-CQ where all the messages get generated but Enable Tx is not turned on. But double-click in WJST-X on a non-CQ that's not for you and off we transmit. I don't do that nearly as often as the "normal" operating mode and I may be in Hold Tx Freq or not...so having to check other boxes on/off is not conducive to smooth operating. Others have voiced similar things like clicking just to get the DX Call box to populate (then JTAlert gets it and you can easily do a QRZ lookup). You could make it so that if Rx/Tx offsets are different you allow Enable Tx it but getting that nitnoid about different beahviors depending on what you're doing is probably not good. I don't see the problem with having to click Enable Tx whenever you are tailending somebodyseeing as how that is specifically what you want to do it's very intuitive that you have to smoosh another buttonand if you don't then you don't impact anybody but yourself. de Mike W9MDB On Monday, October 15, 2018, 5:01:52 PM CDT, Tom Melvin wrote: Would it not just be easier to Un-Tick the ‘Double Click on call sets TX Enable’ in Settings - you can click to your hearts content, do the DX lookup, play with QRZ etc. Make sure they have finished and when you are happy with split/freq etc. just click Enable button Lot less chance of making errors TomGM8MJV On 15 Oct 2018, at 19:55, Carey Fisher wrote: Yes, Gary's right. I would like a single click (or ???) to do the lookup so I don't have to "quickly jab the Halt Tx button". On Mon, Oct 15, 2018 at 2:39 PM Gary McDuffie wrote: > On Oct 15, 2018, at 11:22, Black Michael via wsjt-devel > wrote: > > Maybe we have a different opinion of the path-of-least-resistance here. Personally, I often double click a line just to have the callsign looked up and get the grid, whether I intend to work him or not. I just have to quickly jab the halt tx button to be sure it doesn’t go out or at least is limited to a second or so transmit, if that. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Carey fishercareyfis...@gmail.com ___ 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Autoseq on previous QSO
Would it not just be easier to Un-Tick the ‘Double Click on call sets TX Enable’ in Settings - you can click to your hearts content, do the DX lookup, play with QRZ etc. Make sure they have finished and when you are happy with split/freq etc. just click Enable button Lot less chance of making errors Tom GM8MJV On 15 Oct 2018, at 19:55, Carey Fisher wrote: > Yes, Gary's right. I would like a single click (or ???) to do the lookup so I > don't have to "quickly jab the Halt Tx button". > > On Mon, Oct 15, 2018 at 2:39 PM Gary McDuffie wrote: > > > > On Oct 15, 2018, at 11:22, Black Michael via wsjt-devel > > wrote: > > > > Maybe we have a different opinion of the path-of-least-resistance here. > > Personally, I often double click a line just to have the callsign looked up > and get the grid, whether I intend to work him or not. I just have to > quickly jab the halt tx button to be sure it doesn’t go out or at least is > limited to a second or so transmit, if that. > > Gary - AG0N > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > -- > Carey Fisher > careyfis...@gmail.com > > ___ > 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
Re: [wsjt-devel] Autoseq on previous QSO
Yep. I'm with Carey. Tail-ending is a time-honored tradition in other modes. It works on FT8. Andew Ellis NO6E Rogue River / Bandon, OR Sent from BlueMail On Oct 15, 2018, 11:24, at 11:24, Carey Fisher wrote: >I tail-end a lot. I've gotten a lot of contacts that way without >waiting >for a DX station to call CQ which they don't do a lot of times. I >always >make sure my xmt freq is clear before I start this. > >I would like to see a single click populate the DX station field so I >can >check QRZ before actually calling. > >On Mon, Oct 15, 2018 at 1:24 PM Black Michael via wsjt-devel < >wsjt-devel@lists.sourceforge.net> wrote: > >> Maybe we have a different opinion of the path-of-least-resistance >here. >> >> If one is running without Hold Tx and dealing with CQ's it's not >logical >> to have to click that to prevent transmitting when your QSO partner >comes >> back with a late RRR or 73. This seems to happen quite frequently. >> >> If you are running with Hold Tx it's not a problem...but even then >it's >> usually too late in the cycle for your transmit to be any good >anyways so >> why enable it by default? If you double-click them early for >tail-ending >> you should have plenty of time to click the button. >> >> I operate about 50/50 between Hold Tx and not so when I get a late >reply I >> really never know what mode I'm in that quickly. >> >> Of course, could be an option as just may depend on operating >> practice...but adding more options has never been a popular solution. >> >> Mike >> >> >> On Monday, October 15, 2018, 12:10:26 PM CDT, Bill Somerville < >> g4...@classdesign.com> wrote: >> >> >> On 15/10/2018 17:59, Black Michael via wsjt-devel wrote: >> > I never tailend a QSO that way...working them split is the way to >go. >> >> Hi Mike, >> >> working split and tail-ending are orthogonal, in fact doing both >should >> be best practice for efficient tail-ending, isn't this a key reason >why >> we have the "Hold Tx Freq" on the main window rather than the >inelegant >> and inflexible "Tx=Rx" it replaced. I don't understand your comment >> about repeats, repeats by the running station will be visible since >> double-clicking them puts you on the other period. Repeats by a >station >> in QSO with the running station are fine, you simply fail to >tail-end, >> no different from tail-ending of phone or CW and you just have to >wait >> your turn again. >> >> >> 73 >> Bill >> G4WJS. >> >> >> >> ___ >> 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 >> > > >-- >Carey Fisher >careyfis...@gmail.com > > > > > > > > >___ >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
Re: [wsjt-devel] Autoseq on previous QSO
Yes, Gary's right. I would like a single click (or ???) to do the lookup so I don't have to "quickly jab the Halt Tx button". On Mon, Oct 15, 2018 at 2:39 PM Gary McDuffie wrote: > > > > On Oct 15, 2018, at 11:22, Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > > Maybe we have a different opinion of the path-of-least-resistance here. > > Personally, I often double click a line just to have the callsign looked > up and get the grid, whether I intend to work him or not. I just have to > quickly jab the halt tx button to be sure it doesn’t go out or at least is > limited to a second or so transmit, if that. > > Gary - AG0N > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Carey Fisher careyfis...@gmail.com ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Autoseq on previous QSO
> On Oct 15, 2018, at 11:22, Black Michael via wsjt-devel > wrote: > > Maybe we have a different opinion of the path-of-least-resistance here. Personally, I often double click a line just to have the callsign looked up and get the grid, whether I intend to work him or not. I just have to quickly jab the halt tx button to be sure it doesn’t go out or at least is limited to a second or so transmit, if that. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Autoseq on previous QSO
I tail-end a lot. I've gotten a lot of contacts that way without waiting for a DX station to call CQ which they don't do a lot of times. I always make sure my xmt freq is clear before I start this. I would like to see a single click populate the DX station field so I can check QRZ before actually calling. On Mon, Oct 15, 2018 at 1:24 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Maybe we have a different opinion of the path-of-least-resistance here. > > If one is running without Hold Tx and dealing with CQ's it's not logical > to have to click that to prevent transmitting when your QSO partner comes > back with a late RRR or 73. This seems to happen quite frequently. > > If you are running with Hold Tx it's not a problem...but even then it's > usually too late in the cycle for your transmit to be any good anyways so > why enable it by default? If you double-click them early for tail-ending > you should have plenty of time to click the button. > > I operate about 50/50 between Hold Tx and not so when I get a late reply I > really never know what mode I'm in that quickly. > > Of course, could be an option as just may depend on operating > practice...but adding more options has never been a popular solution. > > Mike > > > On Monday, October 15, 2018, 12:10:26 PM CDT, Bill Somerville < > g4...@classdesign.com> wrote: > > > On 15/10/2018 17:59, Black Michael via wsjt-devel wrote: > > I never tailend a QSO that way...working them split is the way to go. > > Hi Mike, > > working split and tail-ending are orthogonal, in fact doing both should > be best practice for efficient tail-ending, isn't this a key reason why > we have the "Hold Tx Freq" on the main window rather than the inelegant > and inflexible "Tx=Rx" it replaced. I don't understand your comment > about repeats, repeats by the running station will be visible since > double-clicking them puts you on the other period. Repeats by a station > in QSO with the running station are fine, you simply fail to tail-end, > no different from tail-ending of phone or CW and you just have to wait > your turn again. > > > 73 > Bill > G4WJS. > > > > ___ > 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 > -- Carey Fisher careyfis...@gmail.com ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Autoseq on previous QSO
Maybe we have a different opinion of the path-of-least-resistance here. If one is running without Hold Tx and dealing with CQ's it's not logical to have to click that to prevent transmitting when your QSO partner comes back with a late RRR or 73. This seems to happen quite frequently. If you are running with Hold Tx it's not a problem...but even then it's usually too late in the cycle for your transmit to be any good anyways so why enable it by default? If you double-click them early for tail-ending you should have plenty of time to click the button. I operate about 50/50 between Hold Tx and not so when I get a late reply I really never know what mode I'm in that quickly. Of course, could be an option as just may depend on operating practice...but adding more options has never been a popular solution. Mike On Monday, October 15, 2018, 12:10:26 PM CDT, Bill Somerville wrote: On 15/10/2018 17:59, Black Michael via wsjt-devel wrote: > I never tailend a QSO that way...working them split is the way to go. Hi Mike, working split and tail-ending are orthogonal, in fact doing both should be best practice for efficient tail-ending, isn't this a key reason why we have the "Hold Tx Freq" on the main window rather than the inelegant and inflexible "Tx=Rx" it replaced. I don't understand your comment about repeats, repeats by the running station will be visible since double-clicking them puts you on the other period. Repeats by a station in QSO with the running station are fine, you simply fail to tail-end, no different from tail-ending of phone or CW and you just have to wait your turn again. 73 Bill G4WJS. ___ 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
Re: [wsjt-devel] Autoseq on previous QSO
On 15/10/2018 17:59, Black Michael via wsjt-devel wrote: I never tailend a QSO that way...working them split is the way to go. Hi Mike, working split and tail-ending are orthogonal, in fact doing both should be best practice for efficient tail-ending, isn't this a key reason why we have the "Hold Tx Freq" on the main window rather than the inelegant and inflexible "Tx=Rx" it replaced. I don't understand your comment about repeats, repeats by the running station will be visible since double-clicking them puts you on the other period. Repeats by a station in QSO with the running station are fine, you simply fail to tail-end, no different from tail-ending of phone or CW and you just have to wait your turn again. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Autoseq on previous QSO
Tail-ending a QSO that way is not good as you don't know if any repeats are going to occur on the QSO that's in progress\ which see to happen quite a lot I see very little tail-ending going on (in fact almost none). I never tailend a QSO that way...working them split is the way to go. I don't know about everybody else but 100% of my cases when I double-click such an entry I have to turn off Enable Tx as that's not the behavior I want. Mike On Monday, October 15, 2018, 11:39:34 AM CDT, Bill Somerville wrote: On 15/10/2018 17:07, Black Michael via wsjt-devel wrote: > One other thing we seem to need is double-clicking on a message that > is not a CQ or does not contain your callsign should not enable > transmission. Can't think of why you would want to transmit in such a > situation and is much more likely to cause QRM than anything > elseparticularly in FT8. Hi Mike, I don't see a problem with what you describe above, this is how to tail-end a QSO, should be normal practice and rather than causing QRM does the opposite by making a QSO without the running station having to call CQ again. 73 Bill G4WJS. ___ 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
Re: [wsjt-devel] Autoseq on previous QSO
On 15/10/2018 17:07, Black Michael via wsjt-devel wrote: One other thing we seem to need is double-clicking on a message that is not a CQ or does not contain your callsign should not enable transmission. Can't think of why you would want to transmit in such a situation and is much more likely to cause QRM than anything elseparticularly in FT8. Hi Mike, I don't see a problem with what you describe above, this is how to tail-end a QSO, should be normal practice and rather than causing QRM does the opposite by making a QSO without the running station having to call CQ again. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Autoseq on previous QSO
Many times need to double-click somebody sending another RRR or 73.
I think we can relax the QSO sequencing such that double-clicking on a message
with a different dxcall can select the correct responding message.I've been
running this for a couple weeks and it seems to behave quite nicely. So when
somebody comes back after another QSO is in progress the correct Tx message is
selected to respond to them.
One other thing we seem to need is double-clicking on a message that is not a
CQ or does not contain your callsign should not enable transmission. Can't
think of why you would want to transmit in such a situation and is much more
likely to cause QRM than anything elseparticularly in FT8.
de Mike W9MDB
@@ -4322,7 +4323,8 @@ void MainWindow::processMessage (DecodedText const&
message, Qt::KeyboardModifie
if(message_words.size () > 3 // enough fields for a normal message
&& (message_words.at(1).contains(m_baseCall) || "DE" ==
message_words.at(1))
- && (message_words.at(2).contains(qso_partner_base_call) or bEU_VHF_w2))
{
+ //&& (message_words.at(2).contains(qso_partner_base_call) or bEU_VHF_w2)
+ ) {
if(message_words.at(3).contains(grid_regexp) and m_nContest!=EU_VHF) {
if(m_nContest==NA_VHF){
@@ -4360,7 +4362,8 @@ void MainWindow::processMessage (DecodedText const&
message, Qt::KeyboardModifie
}
} else { // no grid on end of msg
QString r=message_words.at (3);
- if(m_QSOProgress >= ROGER_REPORT && (r=="RRR" || r.toInt()==73 ||
"RR73" == r)) {
+ //if(m_QSOProgress >= ROGER_REPORT && (r=="RRR" || r.toInt()==73 ||
"RR73" == r)) {
+ if(r=="RRR" || r.toInt()==73 || "RR73" == r) {
if(ui->tabWidget->currentIndex()==1) {
gen_msg = 5;
if (ui->rbGenMsg->isChecked ()) m_ntx=7;
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
