Thanks for your reply. I followed some of the discussions - also on the band (s) there is just no "BEST" solution - its just a personal feeling, may be habitude - so I try to adjust myself to what is offered as many persons involved have tried to optimize the program /with success)
73,
Charly
Neil Zampella schrieb am 23.10.2017 18:37:
Hi Charly,
I can only speak to the frequency list issue. These release candidates are advanced BETA programs, they are not final. Once the program goes to general release, you would not have to worry about resetting the frequency list.
The list reset 'should' not happen if you stay on RC3 and move to any future release candidate or general release program.
As to your other issue. The tx=rx lock has caused more issues than anything else, if you have read the README file included with RC3, the normal way to select a station calling CQ by double clicking the decoded line in the Rx window works the same has it has since WSJT-X 1.5 . You double click, and BOTH the Tx & Rx move to the CQ caller's frequency. There is no need to lock them when you are replying to CQs. If you are calling CQ, you really DO NOT want to keep that locked because if you answer someone off frequency, your TX is then pulled to the answerer's frequency, thus moving you all over the spectrum.
Does this help?
Neil, KN3ILZOn 10/23/2017 10:58 AM, Karl Barth wrote:Thanks for explaining your comment rules, so I registered as proposed.
73, Charly
My personal comment again:
Hello,
I use WSJT-x in ist various versions since abt 2 years and have seen many changes and improvements and for sure, I appreciate all the efforts put in such a complex software.
I did not experience any major faults or bugs - and had very few situation where the system was frozen.
However, personally I am not really pleased with one of the modifications introduced in 1.8 RC3.
-
I personally prefer the frequency settings (split or locked) in FT8 and other modes as it was programmed up to V1.8 RC2.
>From my point of view, split operation (over here) is only needed during ES openings whe we see with big pile up. Outside ES the majority of VHF/UHF users seem to operate "simplex"
I guess there are 50:50 pro and contra - so I take is "as is".
What I like to have added to WSJT.-x when updating the software is more important for me (and others?) :
a) Many european users have likely build up their own frequency tables, adjusted to reflect the national restrictions in Europe (mainly on 4m and 6m - but also on other VHF/UHF bands)
Every update (or reset) re-creates the default frequency tables. An option NOT to override existing databases would be really helpful.
I have not found a way how to save and/or restore my personal frequency table to avoid a manual recreation of that table after every update.
Thanks for reading
73,
Charly, DF5VAE
------------------------------------------------------------------------------ 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
