Splitting the UI and data processing code would mean a major rewrite of the project. It might be much easier to implement some
API, e.g. REST-based, for the functions that are currently performed via the UI. Then WSJT-X would run with its main window
minimized or hidden on the remote system, and
[.exe] executable.
-- 73, Joe, K1JT
On 1/7/2024 10:58 AM, Alex, VE3NEA via wsjt-devel wrote:
Hi Joe,
Thank you for considering my submission. This change will allow jt9.exe to be used for decoding the MSK144 signals either from
a wav file or from the shared memory. There were requests
just a bit about your intended purpose and any supposed advantages?
-- 73, Joe, K1JT
On 1/6/2024 8:12 AM, Alex, VE3NEA via wsjt-devel wrote:
Hello team,
I have made changes to the jt9.exe code to allow it decode MSK144. This does not affect the existing functions of WSJT-X, so
it is a low
Hello team,
I have made changes to the jt9.exe code to allow it decode MSK144. This does not affect the existing functions of WSJT-X, so it
is a low risk change, and I would like it to be merged to the main branch. The modified files are attached. Do I need to do
anything else to make my
