Many thanks Bill...all comments noted and much appreciated.
Cheers,
AllanVK4EME VK4QG
Sent from Samsung tablet.
-------- Original message --------From: Bill Somerville <[email protected]>
Date: 2/06/2017 6:59 PM (GMT+10:00) To: [email protected]
Subject: Re: [wsjt-devel] Issues with recent WSJT-X releases
Hi Allan,
firstly a request to you. Please start a new thread on the mailing
list when raising a new topic. You appear to have replied to an
existing thread and changed the subject line, this can mean your
message is not see by those using thread email clients unless they
open the thread you ahve attached your message to.
Comments in line below about the issues you have raised.
On 02/06/2017 05:51, Allan Downie wrote:
Issue
1. Waterfall controls. The controls below the MSK144
Waterfall disappear after a mode change. Upon returning to
MSK144 from any other mode, the waterfall controls have gone. I
have edited WSJT-X.ini to change all instances of
'HideControls=true' to false, but the issue returns immediately.
Often even starting up directly after and edit and save, with
the controls being hidden. This was happening in r7688 in all
modes but now only appears to be occurring with MSK144 and
ISCAT. Very occasionally the controls will reappear after a mode
change. I have had instances (rare) where at start-up this does
not occur at all until the program is shut-down and
started again. Incidentally I do NOT have 'Hide menus and
labels' checked under 'View'.
There is a minor defect that is causing the hide menus and labels
option to set or reset when starting WSJT-X or changing modes. Aside
from this you can always reset the option for a specific window by
giving keyboard and mouse focus to the window and pressing CTRL+M.
Hopefully we will find the source of the instability before the next
release of WSJT-X.
As
an aside, if one was curious/foolish enough to check 'Hide menus
and labels', as I was, there doesn't appear to be any obvious
way of reversing the process other than editing the WSJT-X.ini
file. Also keyboard shortcuts no longer work.
See above.
Issue
2. Sub-modes. I am finding that a sub-mode change in one
mode is affecting the sub-mode in another mode. For example if I
set JT4 to 'F' or 'G' sub-mode and then change to JT65 say, I
will be in JT65C, regardless of where it was previously. If I
then do nothing but go back to JT4 it will be in JT4C.
Similarly, QRA64 will be in 'C' sub-mode. I could then change
QRA64 to 'A' and all the other modes will be moved to 'A'.
The sub-mode is not stored with the mode so when changing mode the
sub-mode will remain unchanged if the current sub-mode is valid in
the new mode. There have been some improvements made to sub-mode
handling in the latest development sources but as yet sub-mode is
not recalled with mode changes. Similar comments apply to the
frequency tolerance and T/R period controls.
Issue
3. Auto Seq. The Auto Sequence check box in MSK144 will
uncheck itself upon changing to any another mode and returning
to MSK144.
Auto sequencing is also not recalled with mode. In this case I
suspect it is unlikely to change as auto-sequencing can cause
automatic transmissions in certain specific circumstances. Having
transmit start automatically just because the mode has changed
would be considered a misfeature by many users.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
