Personally, I think this would be a great approach. It doesn’t defeat the timer. It only offers an alternate button to reset it. It also tells you where you might be in the countdown timer cycle.
Side comment: The reality of a big DX pile-up is that the Hounds have no clue at all just how many callsigns the Fox has entered into the queue and how often the queue fills up. Those are determined by the Fox, right? It’s not like at the deli where you take a number and decide to go grab a quart of milk because the sign behind the counter says “67” and you just got “92” from the ticket generator. Hounds have to guess. Since the “N List” parameter for a Fox can be set to as high as 100, doesn’t that mean that a Fox with a fast Enter key finger could have 50 minutes of QSOs in the queue for a single stream operation? That’s assuming no repeats are needed for whatever reason. (Obviously more streams improves the backlog, assuming the propagation allows for multiple streams, especially with a low power Fox.) Actually, I don’t know many callsigns will fit into the QSO queue, only that the sorted list maximum can be set to 100. So, that 50 minute example could be much smaller or much larger! 73, Clarke K1JX > On Jul 28, 2022, at 4:04 PM, Richard V Zwirko via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > If you chase DXpeditions using the Fox/Hound mode, you are probably aware > that you need to toggle the Tx Enable button Off and then On before the 90 > second timeout period. If you don't, after 90 seconds the Tx Enable turns off > and you stop transmitting. Many, if not most of us, have been caught by the > timeout timer before we could reset it. > > When set up as a Hound F/H, how about converting the WatchDog timer in the > lower right corner of the WSJT-X main screen to a 90 second countdown timer? > The WD timer is of no use when running as a Hound. If this suggestion can be > implemented in a future version of WSJT-X, how about being able to reset the > 90 second timer by clicking on the WD box? And to really be helpful, how > about sending a series of beeps to the default sound card speaker for the > last 5 or 10 seconds of the 90 second timeout period. > > Comments? > > 73, > Rich - K!HTV > _______________________________________________ > 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
