Hi Gary, I understand what you mean. I would never suggest disabling anything automatically. I was thinking of a checkbox option that would allow the user to prevent "instant" responses to any CQ that was not followed directly by a call sign. You idea of a warning message is pretty much what I was asking for... as long as it delays the TX along with the message. In fact, I like your idea a lot. I find it nearly impossible to answer any CQ fast enough to get the station on the first call. I'm usually several seconds into the RX cycle before I can actually respond to a CQ. And in many cases, I'm at 13 or 14 seconds when I make my selection. So in this case, responding to an "Are you sure....?" message is no problem. It won't cause any unnecessary delays. The user would have about 15 seconds to respond to the warning.
As far as filtering out CQ DX, etc. programmatically, my suggestion is to simply verify that CQ is followed by a call sign. If anything other than a call sign follows the CQ, it must be a directional CQ. And finally, you mentioned JTDX. To be honest, I had not heard about this software until I read your email. I just took at quick look at the JTDX webpage. I will definitely download and evaluate it. Chuck KG6PH On Sun, 7 Oct 2018 at 17:01, Gary Hinson <g...@isect.com> wrote: > Hi Chuck. > > > > The issue of ‘directional CQs’ applies at both ends: when I’m calling “CQ > EU”, it can be annoying to be called by a slew of non-Europeans, especially > if they all pile up on ‘my’ frequency, obscuring any weak EU sigs under an > unsightly red blob. With JTDX, we have an option for “Strict directional > CQ operation” that (I think!) does not autorespond to callers from the > wrong areas. > > > > On the other hand, the original FT8 protocol only gives us two characters > to play with in our standard CQ calls – not enough room for, say, “CQ NOT > NA” or “CQ AF LP ONLY” except as un-clickable free-text messages. It > would be possible to alternate between various areas in successive CQs e.g. > CQ EU then CQ AF then CQ AS … but it’s awkward to do quickly (especially > while fending off unwanted callers) and confusing for callers. > Impracticable, really. > > > > In practice, as with legacy modes, even polite and compliant DXers will > sometimes monitor a CQer calling another area and, if they are not getting > a response, try calling them speculatively “to let them know they are > getting out” or “just for a quicky” – and they may be lucky. So blocking > calls and responses to other areas may prove unpopular. > > > > Showing a warning/confirmation message, though, would work better I think > – something like “He’s calling CQ EU but you are not in Europe. Do you > really want to respond? Click here to call him anyway …” > > > > The program would need to be told or calculate our areas, and “CQ DX” > would be, let’s say, challenging to interpret programmatically. > > > > 73, > > Gary ZL2iFB > > > > *From:* Chuck Furman <chuck.fur...@gmail.com> > *Sent:* 08 October 2018 10:19 > *To:* pence.b...@gmail.com > *Cc:* wsjt-devel@lists.sourceforge.net > *Subject:* Re: [wsjt-devel] New feature request > > > > Gary Hinson and Bill Pence, > > You guys both got my point! By the time your brain picks someone to call, > and your fingers click the mouse, the screen updates. The result is that > you end up clicking on the wrong row. FT8 is fast. You only have 15 seconds > to think. Before you even realize what you have done, at least one call has > gone out. Let’s be honest, many of us multi-task. Some people work multiple > bands at the same time, or operate FT8 and talk on VHF/UHF, or watch TV, or > check out the FT8 Facebook groups, etc. One mistaken mouse click can result > in multiple calls to someone who is not interested in contacting you. > > My preferred solution is a way to disable TX when you click on a CQ that > is directed to DX, NA, EU, ZL, etc. I’m sure there are other good > solutions. > > Chuck > KG6PH > > > > On Sun, 7 Oct 2018 at 16:01, Bill Pence <pence.b...@gmail.com> wrote: > > Nope. He says as he clicked, the display scrolled, so the call he intended > was now above his mouse pointer. > > > > On Sun, Oct 7, 2018, 3:53 PM Gary McDuffie <mcduf...@ag0n.net> wrote: > > > > > On Oct 6, 2018, at 19:59, Chuck Furman <chuck.fur...@gmail.com> wrote: > > > > Several times I accidentally clicked on a station calling CQ DX or some > other directed CQ. This often happens just as the Band Activity window > updates. I click on a CQ, but as the window updates, I find that I've > actually clicked on another station who was calling CQ DX. > > Sorry, I don’t get it. The line is printed all at once. DX appears at > the same time CQ appears on the same line on the same screen, so why are > you clicking on it? That action seems only possible when the station > changes his mind and sends his second CQ as CQ DX after a prior unqualified > CQ. > > Gary - AG0N > > _______________________________________________ > 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
