On 06/05/2015 21:41, Michael Black wrote:
Hi Mike & Laurie,
The single message to set both tabs and enable the active one makes
more sense. Laurie was probably just carrying over his old logic to
messages that duplicated what he was doing which isn't necessary if
WSJT-X handles it all.
OK, the tab 2 behaviour might warrant two commands as the message switch
when transmitting will be instantaneous. I have checked in the changes
so far, no problem changing the behaviour if necessary.
Details in NetworkMessage.hpp as usual and I have updated
message_aggregator to use the new status and reply messages for a
reference implementation.
It's in the v1.5 branch as well as development.
Mike W9MDB
73
Bill
G4WJS.
*From:*Bill Somerville [mailto:[email protected]]
*Sent:* Wednesday, May 06, 2015 2:02 PM
*To:* [email protected]
*Cc:* [email protected]
*Subject:* Re: [wsjt-devel] FW: [HamApps-Beta] Re: UDP interface for
WSJT-X control.
On 06/05/2015 04:52, Michael Black wrote:
Hi Mike & Laurie,
On further reflection Laurie does have a wish list…
Mike W9MDB
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]]
*Sent:* Tuesday, May 05, 2015 9:58 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [HamApps-Beta] Re: UDP interface for WSJT-X control.
I was premature when I said "I don't think there is any additional
status data". I totally overlooked what I am doing with JTMacros.
Trying to determine the current operating state of the WSJT-X GUI
and where radio buttons and edit controls are located (which
breaks as soon as font sizes are altered) and generating mouse
clicks is very "hacky" and not ideal and now that font changing
is available, no longer a reliable technique.
My wish list ...
1. A status update when WSJT-X changes TX/RX state. I use this to
avoid sending free-text messages when WSJT-X is TXing. I am
currently using pixel color detection.
This is no problem and I have an implementation ready,
2. A Halt TX UDP command rather than sending keystrokes to GUI.
As this too,
3. A UDP command to accept free-text to either Tab 1 or 2. I am
currently detecting the active Tab using pixel color detection and
then determining the Free-text edit control position (Tab
dependant) before pasting the text into the edit field.
4. A UDP command to enable the free-text radio button on Tab 1 or Tab
2. If this becomes 2 separate UDP commands then a UDP status of
Active Tab will be needed.
Is there any reason why the above two items cannot be reduced to a
single message that sets the free text message in the current tab (it
can set the other tab too) and enables it for transmission.
I can't think of anything else.
de Laurie VK3AMA
73
Bill
G4WJS.
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
