On 3/7/19 6:37 PM, Deisher, Michael wrote:
Thanks for the quick reply, Bill. Do you (or any others on the list)
have any recommendations for implementing this "below" wsjtx? In my
current setup, wsjtx seems to "lock" the serial device so that other
apps (e.g., flrig) cannot access it. It makes sense, but I remember
reading about people experimenting with virtual serial devices and
such that allow multiple applications to share the rig. This seems a
bit fraught with potential issues (e.g., two masters with conflicting
commands) but could allow simple things like reading/displaying
status information.
Hi Mike,
I cannot understand how such a setting can work well without any control
conflicts. There is no serialization, no arbitration. Perhaps I'm
thinking to much in the computer science logic.
Best wishes,
Claude (DJ0OT)
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
