The "240202" code will be released on February 2, 2024.
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
Am 27.01.2024 um 14:43 schrieb Black Michael:
I don't see the 240202 update at
I don't see the 240202 update at your "find it here" link.
It points to
https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.7.1/
Mike W9MDB
On Saturday, January 27, 2024 at 04:14:00 AM CST, Uwe, DG2YCB via wsjt-devel
wrote:
Hi all,
Short information: Although I
Yes, but then we also have to remove the <> characters, because
otherwise it won't work for compound callsigns. But the following code
should do the job. Will be included in "240202".
...
&().replace("<","").replace(">","").contains(""+m_baseCall+"")
...
73 de DG2YCB,
Uwe
Should be able to use this instead. Your call always has a space before/after.
contains(" " + m_baseCall +" "))
Mike W9MDB
On Saturday, January 27, 2024 at 04:14:00 AM CST, Uwe, DG2YCB via wsjt-devel
wrote:
Hi all,
Short information: Although I could not reproduce this unwanted
Actually CW operators use apriori operation all the time.
When you're in a poor signal CW QSO with a dxepedition or such all you listen
for is your call sign -- not theirs. You assume (apriori) that they are the
ones responding and you have a sequence you follow so you just continue.
Mike
Reino,
Many thanks. I like to have all the background. So I cleared the concern
with a fresh TX5S QSO last night. FT8 blasted through all the CW
contest. I still got the missing decode in the RX Frequency window, though.
--73, Glenn, AF8C
On 1/27/2024 1:29 AM, Reino Talarmo via wsjt-devel
HI Uwe,
This should be eliminated, it resulted in several unintended transmissions
with the antenna not switched or amp not tuned. I like the fact that you
removed it.
By the way, with the "240202" update I also plan to deactivate this strange
function that pressing the RETURN or ENTER keys
Hi all,
Short information: Although I could not reproduce this unwanted effect
so far, I have now added another line of code as a test for my upcoming
'improved' 2.7.1-devel "240202" update, which has the effect that if you
are in FT8 Hound mode, all messages (below 1000 Hz) are really displayed
