2020.01.07 There is rc146(based on rc146_15) we will share on January 7th around 18:00 UTC if there is no major defects reported. Changelog: - added option to copy callsign to clipboard at double-click on the decoded message or at autoselection. By default this option is enabled, can be switched off in Misc tab of mainwindow UI. changed source files: mainwindow.cpp/h/ui added new parameters into JTDX.ini: "CallsignToClipboard" ------------------------------------------------------------------------------------------------- 2020.01.06 There is rc146_14, changelog: - user can add second callsign from a decoded message into wanted callsign list via CTRL+ALT+click on the message if the list has less than 20 callsigns and this callsign being not located in DxCall window. Wanted callsign list can be cleared via CTRL+ALT+A keyboard shortcut. - reset QSO history counters for new call when DxCall is changed with double click - at double click on decoded message cursor position shall be set prior to emitting of the selectCallsign(alt,ctrl) signal changed source files: displaytext.cpp, mainwindow.cpp, mousecommands.txt, shortcuts.txt ------------------------------------------------------------------------------------------------- 2020.01.05 There is rc146_12, changelog: - two more chars added in displaytext and decoders to fit messages like "CC2/CC1CCC BB2/BB1BBB R-15" in Band Activity and RX frequency text windows - eliminated ba2msg memory corruption that was made in rc146_1 - cty.dat file is updated to version CTY-2918 - LoTW users file is updated - rc146_12 is built with updated Hamlib as of 20200104 changed source files: cty.dat, cwfilter.f90, decoder.f90, ft4_decode.f90, ft8_decode.f90, ft8b.f90, jt9_decode.f90, jt9s_decode.f90, jt10_decode.f90, jt65_decode.f90, lotw-user-activity.csv, mainwindow.cpp, partint.f90, partint4.f90, partint8.f90 We recommend to rename|delete old JTDX.ini file as it can be broken by ba2msg memory corruption made in rc146_1. ------------------------------------------------------------------------------------------------- 2020.01.02 There is rc146_11, changelog: - 6 decoding pass SWL mode is moved to option, can be activated in 'Decode->FT8 decoding->6 pass SWL mode' tab of mainwindow UI changed source files: about.cpp, commons.h, decoder.f90, ft8_decode.f90, ft8_mod1.f90, jt9com.f90, mainwindow.cpp/h/ui added new parameter into JTDX.ini file: "sixPassFT8SWLmode" Known issues: - there is two more chars shall be added in displaytext and decoders to fit messages like "CC2/CC1CCC BB2/BB1BBB R-15" in Band Activity and RX frequency text windows. ------------------------------------------------------------------------------------------------- 2019.12.31 There is rc146_10, changelog: rc146_10 - SWL mode will utilize 3 more decoding passes if JTDX being run as single instance and CPU has more than three logical cores. User would need to make sure CPU is not coming into thermal throttling in this mode, and avoid usage of the SWL mode if FT8 decoding time is greater than 15 seconds. changed source files: decoder.f90, ft8_decode.f90, ft8_mod1.f90, ft8b.f90, sync8.f90, sync8d.f90 Multiple instances being detected from the rig-name key, it is unreliable approach and shall be reworked. Known issues: - there is two more chars shall be added in displaytext and decoders to fit messages like "CC2/CC1CCC BB2/BB1BBB R-15" in Band Activity and RX frequency text windows. ------------------------------------------------------------------------------------------------- 2019.12.31 rc146_9 - number of FT8 decoder threads shall not exceed number of logical cores - patch to Tx1 message generation for mix of /P and /R callsigns changed source files: commons.h, decoder.f90, jt9com.f90, mainwindow.cpp ------------------------------------------------------------------------------------------------- 2019.12.27 There is rc146_8, changelog: rc146_8 - patch: FT8 decoder shall process signals with "CQ ??? ???" AP mask if there is nonstandard callsign in DxCall window - improved DxCall searching if there is nonstandard callsign in DxCall window changed source files: ft8_mod1.f90, ft8b.f90 Known issues: there is two more chars shall be added in displaytext and decoders to fit messages like "CC2/CC1CCC BB2/BB1BBB R-15" in Band Activity and RX frequency text windows. ------------------------------------------------------------------------------------------------- 2019.12.27 rc146_7 - patch: program shall not attempt to start decoder if it is in the busy state (Decode button hung up on slow CPU in FT4 mode) - improved workaround to modulator start failure (no TX audio issue) changed source files: mainwindow.cpp ------------------------------------------------------------------------------------------------- 2019.12.25 There is rc146_6, changelog: rc146_6 - previous 'Decode button is hung up' workarounds withdrawn, we found root cause and have patched this issue in correct place of the code changed source files: decoder.f90, mainwindow.cpp/h ------------------------------------------------------------------------------------------------- 2019.12.25 rc146_5 - workaround: decoding autorecovery on next interval if jtdxjt9 process has missed .lock file deletion event (Decode button is hung up) changed source files: mainwindow.cpp/h ------------------------------------------------------------------------------------------------- 2019.12.23 There is rc146_4, changelog: rc146_4 - compound-to-compound QSO being only supported out of DXpedition Hound mode. Compound-to-compound callsign QSO Tx message format is changed, compound-to-/P and compound--to-/R callsign QSO being supported now between two JTDX users, Tx message generation could be improved in WSJT-X and MSHV to provide support for such QSO. changed source files: mainwindow.cpp ------------------------------------------------------------------------------------------------- 2019.12.21 There is rc146_3, changelog: rc146_3 - finalized workaround to Decode button stuck issue in FT4 and FT8 modes, being applied if reading wav files or to live decoding in multiple instances environment - patch to broken decoding of FT8 signals in scenario where both user's and correspondent's callsigns are nonstandard ones - compound-to-compound callsign QSO Tx message generation is supported now. At the moment compound-to-compound callsign QSO is possible between two JTDX users, Tx message generation could be improved in WSJT-X and MSHV to provide support for such QSO. ???/P and ???/R callsigns being not supported yet in this solution. changed source files: ft8b.f90, mainwindow.cpp/h rc146_2 - temporary workaround for Decode button stuck issue in FT4 and FT8 modes - attempt to patch modulator start failure(no TX audio issue) changed source files: decoder.f90, jt9a.f90, mainwindow.cpp/h rc146_1 - allow transmission of DXpedition special message from Tx2 - cursor position shall be stored/restored while operator's callsign&grid being edited in configuration - empty message shall be treated as false decode in FT4 decoder - some Decode control related code cleanup changed source files: Configuration.cpp, decoder.f90, displaytext.cpp, ft4_decode.f90, mainwindow.cpp/h -------------------------------------------------------------------------------------------------