k0swe / wsjtx-go Goto Github PK

In order to support kel-agent Debian packaging, this library also needs its own Debian package.

See https://sourceforge.net/p/wsjt/wsjtx/ci/8f99fcce/tree/Network/NetworkMessage.hpp#l442.

See https://sourceforge.net/p/wsjt/wsjtx/ci/8f99fcce/tree/Network/NetworkMessage.hpp#l341.

See https://sourceforge.net/p/wsjt/wsjtx/ci/8f99fcce/tree/Network/NetworkMessage.hpp#l468.

The "Highlight Callsign" message can specify the invalid color, a sentinel value, in either the foreground or background color field in order to reset highlighting for that callsign. The current implementation doesn't have a way to specify that.

See https://sourceforge.net/p/wsjt/wsjtx/ci/8f99fcce/tree/Network/NetworkMessage.hpp#l477.

Currently this library can only listen to WSJT-X broadcasts. It should be able to send requests to WSJT-X.

This server is written in such a way that it assumes only one client instance of WSJT-X is going to connect. However, the protocol is flexible enough to allow multiple instances of WSJT-X to connect to a server. This server library will probably not handle that situation gracefully right now.

I don't have any personal need for this, but it's possible someone will run into this, in which case we can address it.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: Invalid JSON (parsing failed)
Message: Syntax error: expecting String near r" ], }

https://sourceforge.net/p/wsjt/wsjtx/ci/8f99fcce/tree/Network/NetworkMessage.hpp#l404

QDataStream::Qt_5_4 is used by newer versions of WSJT-X (see NetworkMessage.hpp). The differences between QDataStream::Qt_5_2 and QDataStream::Qt_5_4 are marginal and not relevant, since WSJT-X does not use any of the changed data types.

See https://sourceforge.net/p/wsjt/wsjtx/ci/8f99fcce/tree/Network/NetworkMessage.hpp#l350.

Right now the UDP server is hard-coded to bind to the "all hosts" multicast group IP address 224.0.0.1, and port 2237 (source). This should probably be customizable.