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) <tag.loo...@gmail.com> To: WSJT software development <wsjt-devel@lists.sourceforge.net> Sent: Tue, Feb 25, 2020 6:02 pm Subject: Re: [wsjt-devel] NetworkMessage request
I don’t see the relevance to my question :) In the wrong thread maybe? On Tue, Feb 25, 2020 at 2:54 PM Sam W2JDB via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: Hi Mike, If you are visually impaired, you may want to contact Rich K1HTV regarding a companion program called QLog that I developed and enhanced for blind ops to use with WSJT-X. It is Windows only. It has a local QSO database that you can import all your previous QSOs You can export new QSOs. I will log all WSJT-X QSOs and automatically uploads those QSOs to QRZ, Clublog and EQSL if you are a member of those organization. It announces all progression and it identifies the station and grid that you are calling/working. It even has an optional built in internet time sync function. You can call CQ, Call a station, filter replies and participate in the special events in WSJT-X without the need to create new log files to eliminate dupes. The program is free. Bill and Joe are aware of this program that I built for the blind ham community. 73, Sam W2JDB -----Original Message----- From: Sam L Kloberdanz <sam.kloberd...@gmail.com> To: WSJT software development <wsjt-devel@lists.sourceforge.net> 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) <tag.loo...@gmail.com> 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 message or a new one? Author of GridTracker- Stephen "Tag" Loomis / N0TTL On Mon, Feb 25, 2019 at 6:50 PM Mike Maynard <m...@k2gc.net> wrote: 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 contrasting colors, >etc). Obviously it would not allow for any change in QSO progression. That would still require direct intervention with WSJT. In my setup... I have a keypad that I programmed to set the QSO progression using hot-keys. the screen I run WSJT on is a little hard to read at a glance. It takes time to focus on it where it is. Sure I could adjust my resolution, but then I lose space on the screen for other things. A larger display of current WSJT status could be a welcome option to some of us with poorer eyesight. Enabling such a UDP packet would allow such development to happen. ThanksMike On Thu, Feb 21, 2019 at 4:39 PM Bill Somerville <g4...@classdesign.com> wrote: 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 just not seeing it, any pointer would be great! Thank you for your time! Stephen Loomis / N0TTL / GridTracker developer. Hi Stephen,welcome to the group.The WSJT-X UDP protocol is meant to aid the WSJT-X operator but with the expectation that QSOs will be progressed from with WSJT-X by user interaction with the software. Because of that a message that echoes the current outgoing message doesn't seem to add any value. Can you please explain in detail how such a message would be used?73 Bill G4WJS. _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- MikeK2GCwww.k2gc.net_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
