<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Project Wait and Pounce FT8</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/</link><description>Recent changes to Project Wait and Pounce FT8</description><atom:link href="https://sourceforge.net/p/wait-and-pounce-ft8/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 09 Jan 2026 12:33:26 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/wait-and-pounce-ft8/feed.rss" rel="self" type="application/rss+xml"/><item><title>JTDX-notice modified by f5ukw</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/JTDX-notice/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v8
+++ v9
@@ -3,6 +3,8 @@
 First, you have to disable automatic logging of QSO.

 Make sure `Settings &amp;gt; Reporting &amp;gt; Logging &amp;gt; Enable automatic logging of QSO` is **unchecked**
+
+`JTDX rc-10` requieres that `Settings &amp;gt; Reporting &amp;gt; Logging &amp;gt; Prompt me to log QSO` is **checked**

 You might also need to accept UDP Reply messages from any messages

@@ -11,6 +13,10 @@
 Set `AutoTX` as **enabled**. This setting allows double-clicking on a decoded signal to activate TX.

 We realize that not being able to automatically log your QSOs with JTDX can be annoying, however, **Wait and Pounce** autonomously keeps an `ADIF` file with the QSOs made while **Wait and Pounce** is running.
+
+-----
+
+While using JTDX and **Wait and Pounce**, you can enable a task automation feature so that **Wait and Pounce** simulate click on the prompt when JTDX logged a new QSO.

 -----

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">f5ukw</dc:creator><pubDate>Fri, 09 Jan 2026 12:33:26 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf9a13c60d145c66c96edaead504dafa476800a35</guid></item><item><title>JTDX-notice modified by f5ukw</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/JTDX-notice/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v7
+++ v8
@@ -9,8 +9,6 @@
 `Misc Menu &amp;gt; Accept UDP Reply Messages &amp;gt; any messages`

 Set `AutoTX` as **enabled**. This setting allows double-clicking on a decoded signal to activate TX.
-
-Set `EnableTX` as **enabled**. 

 We realize that not being able to automatically log your QSOs with JTDX can be annoying, however, **Wait and Pounce** autonomously keeps an `ADIF` file with the QSOs made while **Wait and Pounce** is running.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">f5ukw</dc:creator><pubDate>Sun, 28 Dec 2025 17:48:06 -0000</pubDate><guid isPermaLink="false">https://sourceforge.nete80ab2a2af5f465cdba4bfa02482cd8604313f9e</guid></item><item><title>JTDX-notice modified by f5ukw</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/JTDX-notice/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v6
+++ v7
@@ -9,6 +9,8 @@
 `Misc Menu &amp;gt; Accept UDP Reply Messages &amp;gt; any messages`

 Set `AutoTX` as **enabled**. This setting allows double-clicking on a decoded signal to activate TX.
+
+Set `EnableTX` as **enabled**. 

 We realize that not being able to automatically log your QSOs with JTDX can be annoying, however, **Wait and Pounce** autonomously keeps an `ADIF` file with the QSOs made while **Wait and Pounce** is running.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">f5ukw</dc:creator><pubDate>Sun, 28 Dec 2025 17:39:14 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd90db334d46a1b7b6037691753cf5d5f4582464b</guid></item><item><title>JTDX-notice modified by f5ukw</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/JTDX-notice/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v5
+++ v6
@@ -22,6 +22,11 @@

 `Settings &amp;gt; Reporting &amp;gt; Primary UDP Server &amp;gt; Apply text filters to transmission of the UDP message` is **checked**

+alson 
+
+`Settings &amp;gt; Filters &amp;gt; Show CQ messages only` and `Show CQ/RRR/RR 73 only` are **unchecked**
+
+
 -----

 We realize that not being able to automatically log your QSOs with JTDX can be annoying, however, **Wait and Pounce** keeps a separate ADIF file with the QSOs made while **Wait and Pounce** is running. These can be copied into your main log later.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">f5ukw</dc:creator><pubDate>Fri, 27 Jun 2025 05:42:52 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netcd23a94baf0e52cb4d0745d343e359aebdabaf31</guid></item><item><title>JTDX-notice modified by f5ukw</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/JTDX-notice/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v4
+++ v5
@@ -8,7 +8,7 @@

 `Misc Menu &amp;gt; Accept UDP Reply Messages &amp;gt; any messages`

-Set `AutoTX`as enabled (This setting allows double-clicking on a decoded signal to activate TX)
+Set `AutoTX` as **enabled**. This setting allows double-clicking on a decoded signal to activate TX.

 We realize that not being able to automatically log your QSOs with JTDX can be annoying, however, **Wait and Pounce** autonomously keeps an `ADIF` file with the QSOs made while **Wait and Pounce** is running.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">f5ukw</dc:creator><pubDate>Fri, 13 Jun 2025 18:43:12 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net2057781e04d7a5e693fcf35499e4cdc60bdc2d7e</guid></item><item><title>JTDX-notice modified by f5ukw</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/JTDX-notice/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v3
+++ v4
@@ -7,6 +7,8 @@
 You might also need to accept UDP Reply messages from any messages

 `Misc Menu &amp;gt; Accept UDP Reply Messages &amp;gt; any messages`
+
+Set `AutoTX`as enabled (This setting allows double-clicking on a decoded signal to activate TX)

 We realize that not being able to automatically log your QSOs with JTDX can be annoying, however, **Wait and Pounce** autonomously keeps an `ADIF` file with the QSOs made while **Wait and Pounce** is running.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">f5ukw</dc:creator><pubDate>Fri, 13 Jun 2025 18:41:55 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netb287658eb8371bf0686ff77de0472c5c1e5f0bd0</guid></item><item><title>JTDX-notice modified by f5ukw</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/JTDX-notice/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -12,7 +12,9 @@

 -----

-To make sure JTDX and **Wait and Pounce** run smoothly, you need to have the same list of callsigns shown in **Wait and Pounce** and in the main decoding window from JTDX. In order **for Wait and Pounce** to provide a reliable  service to JTDX it is possible for it to initiate a QSO. The action to reply to a callsign is exactly equivalent to the user double clicking the message in the "*Band activity*" window. 
+To make sure JTDX and **Wait and Pounce** run smoothly, you need to have the same list of callsigns shown in **Wait and Pounce** and in the main decoding window from JTDX "*Band activity*". In order **for Wait and Pounce** to provide a reliable  service to JTDX it is possible for it to initiate a QSO. The action to reply to a callsign is exactly equivalent to the user double clicking the message in the "*Band activity*" window. 
+
+**Wait and Pounce** will NOT reply to any station if only shown on the "*RxFrequency*" area. 

 For JTDX users make sure you set:

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">f5ukw</dc:creator><pubDate>Tue, 25 Mar 2025 13:18:30 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9a3778c63827506a3c095dfbb76ad3be0a934ad9</guid></item><item><title>Settings modified by Morelle Cédric</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/Settings/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v7
+++ v8
@@ -1,4 +1,4 @@
-The settings consist of 5 specific setting groups:
+The settings consist of 6 specific setting groups:

 -----
 `Server`
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Morelle Cédric</dc:creator><pubDate>Tue, 28 Jan 2025 11:09:11 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf0edb9d0373dc018efa56e28b6fec79c5ff1ec26</guid></item><item><title>Settings modified by Morelle Cédric</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/Settings/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v6
+++ v7
@@ -35,7 +35,7 @@
 *Maximum waiting delay (minutes)*: This setting will be used if no more Wanted Callsign are decoded but you already started to reply to a station decoded on a previous sequence. If you lost signal for several minutes, it will reset the focus for the called station, and will wait for next Wanted Callsign decoded.

 -----
-`Sounds`
+`Sound Alerts`

 -----
 `Worked B4`
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Morelle Cédric</dc:creator><pubDate>Tue, 28 Jan 2025 11:06:48 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6c85b372e92743a29e6cb87051754be4a7646169</guid></item><item><title>Settings modified by Morelle Cédric</title><link>https://sourceforge.net/p/wait-and-pounce-ft8/wiki/Settings/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v5
+++ v6
@@ -1,7 +1,7 @@
 The settings consist of 5 specific setting groups:

 -----
-`Server`:
+`Server`

 *Primary UDP Server*: Automatically **Wait and Pounce** will detect your local IP address. This IP and port have to be set in your WSJT or JTDX instance to allow Wait and Pounce to communicate.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Morelle Cédric</dc:creator><pubDate>Tue, 28 Jan 2025 11:06:21 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net34309fc05580a45ad70f9a2f2e81bac2fbee6b49</guid></item></channel></rss>