Laurie, VK3AMA via wsjt-devel kirjoitti 21.2.2023 klo 13.06:
This is not a bug. WSJT-X has always behaved this way, emitting a UDP
status message with each character typed.
I would not like to see this long-standing behavior changed.
de Laurie VK3AMA
(JTAlert author)
Like always; I guessed that!
What is set in stone, stands there.
I do highly prefer backward compatibility, but but fixing this does not
break anything. I expect nobody is interested in partial callsigns.
There is also another "feature" that is not so nice. (but I know it is
also set in stone and I do not expect this to be fixed. Just want to
show it too)
If you send UDP #4 or #15 to set new target call status #1 will first
reply with old call and immediate after that the new call that was set
Getting Call : by UDP #1
Getting Call : by UDP #1
*Settting call: IU8CFX by UDP #4 * <----------setting new target call
/Getting Call : by UDP #1/**the immediate response is *existing old call*
*Getting Call :IU8CFX by UDP #1***right after that comes the call that
was set**
Getting Call :IU8CFX by UDP #1
Getting Call :IU8CFX by UDP #1
Getting Call :IU8CFX by UDP #1
Getting Call :IU8CFX by UDP #1
Getting Call :IU8CFX by UDP #1
Getting Call :IU8CFX by UDP #1
*Settting call: JE8VZK by UDP #4* <----------setting new target call
/Getting Call :IU8CFX by UDP #1/ **the immediate response is *existing
old call**
**Getting Call :JE8VZK by UDP #1* right after that comes the call
that was set
Getting Call :JE8VZK by UDP #1
Usually clients do response either with ACK or echoing the sent message.
At least in industrial world that I used to while still working.
Due to these the companion program must fix things with timeout timers
to guess when proper responses are available from wsjt-x.
--
--
Saku
OH1KH
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
