On 22/02/2023 6:52 pm, Saku via wsjt-devel wrote:
What is set in stone, stands there.
I do highly prefer backward compatibility, but but fixing this does
not break anything.
While a change would not break anything, it will introduce a change
that will require users to change their
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
On 21/02/2023 9:40 pm, Saku via wsjt-devel wrote:
Found annoying property of UDP Status (#1) message.
If you enter new callsign to DXCall column the new status message is
sent after every letter you type. This makes receiving program very
hard to decide when there is complete callsign
Hi!
Found annoying property of UDP Status (#1) message.
If you enter new callsign to DXCall column the new status message is
sent after every letter you type. This makes receiving program very hard
to decide when there is complete callsign available. (needs timeout
routine because of this)
