Re: [wsjt-devel] NetworkMessage request

2020-02-25 Thread Tag Loomis (Tag)
t; Sorry, I was addressing this to Mike as he mentioned "some of us with > poorer eyesight". > > 73, > > Sam W2JDB > > > > -Original Message- > From: Tag Loomis (Tag) > To: WSJT software development > Sent: Tue, Feb 25, 2020 6:02 pm > Subj

Re: [wsjt-devel] NetworkMessage request

2020-02-25 Thread Sam W2JDB via wsjt-devel
Hi Tag, Sorry, I was addressing this to Mike as he mentioned  "some of us with poorer eyesight".  73, Sam W2JDB   -Original Message- From: Tag Loomis (Tag) To: WSJT software development Sent: Tue, Feb 25, 2020 6:02 pm Subject: Re: [wsjt-devel] NetworkMessage request I don

Re: [wsjt-devel] NetworkMessage request

2020-02-25 Thread Tag Loomis (Tag)
; From: Sam L Kloberdanz > To: WSJT software development > Sent: Tue, Feb 25, 2020 5:24 pm > Subject: Re: [wsjt-devel] NetworkMessage request > > I’ll have to call tomorrow, I’m hung for the rest of the day.. > > > Sam > N0GTO > > On Feb 25, 2020, at 2:11 PM, Tag

Re: [wsjt-devel] NetworkMessage request

2020-02-25 Thread Sam W2JDB via wsjt-devel
Message- From: Sam L Kloberdanz To: WSJT software development Sent: Tue, Feb 25, 2020 5:24 pm Subject: Re: [wsjt-devel] NetworkMessage request I’ll have to call tomorrow, I’m hung for the rest of the day.. SamN0GTO On Feb 25, 2020, at 2:11 PM, Tag Loomis (Tag) wrote: Just over a year now and no

Re: [wsjt-devel] NetworkMessage request

2020-02-25 Thread Sam L Kloberdanz
I’ll have to call tomorrow, I’m hung for the rest of the day.. Sam N0GTO > On Feb 25, 2020, at 2:11 PM, Tag Loomis (Tag) wrote: > > Just over a year now and no reply.. > > Could we be notified at a bare minimum if Tx 6 is being transmitted and its > contents are in the existing status messag

Re: [wsjt-devel] NetworkMessage request

2020-02-25 Thread Tag Loomis (Tag)
Just over a year now and no reply.. Could we be notified at a bare minimum if Tx 6 is being transmitted and its contents are in the existing status message or a new one? Author of GridTracker - Stephen "Tag" Loomis / N0TTL On Mon, Feb 25, 2019 at 6:50 PM Mike Maynard wrote: > Bill, > > From wh

Re: [wsjt-devel] NetworkMessage request

2019-02-25 Thread Mike Maynard
Bill, >From what I can tell, it looks like Stephen is just trying to get the actual currently transmitting packet. This would be an operational aid - for example: It would allow a developer the ability to create a status screen that is much easier to see (maybe larger type? different contrastin

Re: [wsjt-devel] NetworkMessage request

2019-02-21 Thread Tag Loomis
At a minimum: Just knowing TX 6 is why we’re transmitting would help greatly. I can see by what i’m requesting, others COULD create an automation tool. But I don’t see how with just TX 6 knowledge. Thanks again. ___ wsjt-devel mailing list wsjt-dev

Re: [wsjt-devel] NetworkMessage request

2019-02-21 Thread Tag Loomis
I totally understand that the processing is handled by WSJT-X with user interaction. It would be nice to know, with a status message when the user is transmitting, what they are transmitting. If they are calling “CQ” but the DX Call box hasn’t been cleared, I have no way of knowing this. So

Re: [wsjt-devel] NetworkMessage request

2019-02-21 Thread Bill Somerville
On 21/02/2019 21:02, Tag Loomis wrote: First time message to the group. Would it be possible to have the current transmitting message  be emitted in either in the Status Out message after “Special operation mode (quint8)” as utf8 *OR* a brand new message type? If it’s already present and I’m

[wsjt-devel] NetworkMessage request

2019-02-21 Thread Tag Loomis
First time message to the group. Would it be possible to have the current transmitting message be emitted in either in the Status Out message after “Special operation mode (quint8)” as utf8 OR a brand new message type? If it’s already present and I’m just not seeing it, any pointer would be gr