This is a minor thing and has been occurring for several revisions. I was
wondering if anyone one has seen this. When I first open WSJT-X and its in
another mode besides msk144, when I switch to msk144 mode, the Fast Graph
scale seems to default to 30 seconds even though T/R is set to 15 seconds.
T
Fix wrong startup period of MSK144 and refactor function calls for setTRPeriod.
https://www.dropbox.com/s/ztibvel0pigiaee/msk.patch?dl=1
de Mike W9MDB
On Monday, February 12, 2018, 7:26:55 AM CST, Jay Hainline
wrote:
This is a minor thing and has been occurring for several revisions
> On Feb 12, 2018, at 5:59 AM, Jay Hainline wrote:
>
> This only seems to happen when first opening WSJT-X. The bug does not appear
> again once it is open and have switched to other modes and back to msk144.
It doesn’t do it here…. BUT! … I use a different configuration for most
mode/band
Hi Neil,
Many thanks for catching these omissions in the v1.9.0 User Guide. Much
appreciated! Even when we "know" about the need for such updates, at
some level, we don't always remember. It's good to be reminded.
-- 73, Joe, K1JT
On 2/11/2018 8:32 AM, Neil Zampella wrote:
Hi
go
Gary, you didn’t follow the correct sequence of events to see the bug.
Open WSJT-X, change to msk144 mode.
Set T/R to 15 seconds. Fast Graph should also show 15 second time scale.
Switch WSJT-X to another mode from the Mode Menu, say FT8.
Close WSJT-X
Reopen WSJT-X. It should be in FT8 mode.
Swit
Hi Jordan,
My guess is that (at least at present) the interest here is minimal.
Your idea for exchanging much longer messages is pretty far from the
core goals of the modes supported in WSJT-X.
Please don't let my comment discourage you from proceeding as you wish,
toward something new.
Thanks Joe. I appreciate the response and encouragement.
I understand that this type of change would be a departure from the WSJT-X
goals. If you don't mind, I'd like to continue posting some of my
experiments here to the group to continue the conversation in the future.
If anybody else is interes
> On Feb 12, 2018, at 9:15 AM, Jay Hainline wrote:
>
> Gary, you didn’t follow the correct sequence of events to see the bug.
I was aware of that. That’s why I posted my exact test sequence. If I load a
config for one mode, I never change that mode. If I want another mode, I load
its conf
