Hi Bill,
Ok. Thanks for the reply. No Worries. Cheers.
73,
Sam W2JDB
-----Original Message-----
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Wed, Jan 6, 2021 2:09 pm
Subject: Re: [wsjt-devel] WSJT-X: UI wdiget tab navigation ordering
Hi Sam,
WSJT-X follows long established operating practice, when starting a QSO the
operating frequency is set and kept the same throughout the QSO. Moving during
a QSO requires direct intervention by the operator.
The FT8 decoder in WSJT-X is capable of decoding more than signal on the same
frequency, time synchronization differences are not particularly relevant.
Weaker underlying signals are revealed to the decoder by subtracting an exact
facsimile (both amplitude and phase) of previously decoded signals, then trying
the decoding again on the remaining waveform.
73
Bill
G4WJS.
On 06/01/2021 18:48, Sam W2JDB via wsjt-devel wrote:
Hi Bill,
Testing 2.3-RC3 – So far so good. Made the necessary adjustments to the
different tab sequences so that is no longer an issue. My program recognizes
the current running WSJT-X version and now reacts correctly whether you are
using WSJT-X 2.2.2 as well as 2.3-rc3. If you have not done so, you don’t need
to change anything with tab sequencing on my account in the next release.
I did notice one item that may cause inadvertent QRM. I replied to a station
calling CQ. As I did not have Hold TX checked, WSJT-X moved automatically to
the calling CQ offset. After logging the QSO, I replied to another calling
station that was a few Hertz away from the previous caller and as expected
WSJT-X moved to the second caller offset. After my first reply, the second
station moved to another clear offset but WSJT-X stayed on the second caller
first offset. While the QSO was completed, I think that WSJT-X should have
moved again to the second caller new offset as I still did not have Hold TX
checked.
Looking at the screen at the DT time and offset values, I believe that the
reason WSJT-X was able to decode the second caller even though he was just a
few Hertz away from the first called is because the first caller DT was 1.1
while the second caller DT was 0.1.
Anyway, that is just an observation.
Have a great day and thanks again.
73,
Sam W2JDB
-----Original Message-----
From: Sam W2JDB mailto:w2...@aol.com
To: g4...@classdesign.com mailto:g4...@classdesign.com;
wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net
Sent: Tue, Jan 5, 2021 7:53 pm
Subject: Re: [wsjt-devel] WSJT-X: UI wdiget tab navigation ordering - was Re:
WSJT-X 2.3.0-rc3 - wsjtx_app_version utility
Hi Bill,
Thanks for the email. I just have to make sure that it all works. Just
thought I would mention it.
It wasn't until I started making QLog visually impaired friendly that I
realized how important the tabbing sequence really is in the UI.
I am already modifying QLog to take care of this situation so that it can be
used with 2.2x and 2.3x
Keep up the great work with this product. I can assure you that the blind
hams are having a great time with this.
Have a safe and healthy 2021.
73,
Sam W2JDB
-----Original Message-----
From: Bill Somerville mailto:g4...@classdesign.com
To: wsjt-devel@lists.sourceforge.net
Sent: Tue, Jan 5, 2021 6:38 pm
Subject: [wsjt-devel] WSJT-X: UI wdiget tab navigation ordering - was Re:
WSJT-X 2.3.0-rc3 - wsjtx_app_version utility
On 05/01/2021 21:49, Sam W2JDB via wsjt-devel wrote:
Downloaded the new version and started testing it with my program (QLog) for
the visually impaired. Noticed some weird tab sequences in the Generate Std
Msgs group of controls.
In Ver 2.2 pressing Shortcut keys Ctrl+6 then Shift+Tab changed focus to the
tx6 input box. Subsequent multiple Shift+Tab key strokes shift focus to the
previous Tx input boxes.
In Ver 2.3-rc3 pressing Shortcut keys Ctrl+6 then Shift+Tab changes focus to
the [1] control in the group. The next Shift+Tab changes focus to the Hold Tx
Freq check box. If you press Ctrl+6 then the TAB key, focus shifts the tx1
input box. The next TAB key press shifts focus to the tx6 input box, the next
TAB moves you to the [tx5] button, another TAB moves to the [tx2] button, next
TAB move to the tx2 input, followed by a TAB to the tx4 input. Just an FYI
73,
Sam W2JDB
Hi Sam, I don't think anyone has consciously attempted to define any sort of
logical flow of Tab/Shift+Tab widget navigation for the WSJT-X main window. I
have defined the ordering for the next release but be aware that it may vary
when widgets are changed in the future. 73
Bill
G4WJS.
_______________________________________________
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
