Post by WX2S on Mar 5, 2022 1:32:15 GMT
Mar 4, 2022 16:49:44 GMT WX2S said:
...
If so, then it breaks compatibility with WSJT-X. www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc4.html section 4.7:
...You have done something with the wsjtx_log.adi file, no one dared to do before :-) Now, as we know the reason for
your problem - and the possible bug in .159, change the .adi to the one line header and all is fine. A task of a minute,
Be careful what you ask for, because you might get it...
Done. 2.2.159 still locks up when I attempt to set my call and grid in a newly-created JTDX.ini file.
This does not happen in 2.2.158.
It also supports Mike's previous statement that ADIF headers can be multi-line. Just to check, I imported the ADIF with the original header into the ADIF Master tool. It didn't raise any syntax errors.
Looking at the ADIF standard also supports Mike on this, and in fact gives a specific example of a multi-line header. www.adif.org/312/ADIF_312.htm#ADI_File_Format
Just so we are both certain that I followed your instructions correctly, here are the first few lines of the edited wsjtx_log.adi:
WSJT-X ADIF Export<eoh>
<Band:3>10M <Call:5>RW3YA <DXCC:1>0 <Freq:6>28.076 <Mode:2>CW <Operator:4>WX2S <QSL_Rcvd:1>R <QSL_Sent:1>Y <QSO_DATE:8>20120101 <TIME_OFF:6>000000 <TIME_ON:6>000000 <QTH:10>Bryansk-39 <RST_Rcvd:3>599 <RST_Sent:3>599 <TX_PWR:5>100.0 <QSLMsg:39>Sorry, am not QSL manager for HC2WAT/8! <QSLSDATE:8>20160504 <CONT:2>EU <ITUZ:2>29 <CQZ:2>16 <GRIDSQUARE:6>KO85ss <ADDRESS:65>Dekhanov George G.
241039
<Band:3>10M <Call:5>RW3YA <DXCC:1>0 <Freq:6>28.076 <Mode:2>CW <Operator:4>WX2S <QSL_Rcvd:1>R <QSL_Sent:1>Y <QSO_DATE:8>20120101 <TIME_OFF:6>000000 <TIME_ON:6>000000 <QTH:10>Bryansk-39 <RST_Rcvd:3>599 <RST_Sent:3>599 <TX_PWR:5>100.0 <QSLMsg:39>Sorry, am not QSL manager for HC2WAT/8! <QSLSDATE:8>20160504 <CONT:2>EU <ITUZ:2>29 <CQZ:2>16 <GRIDSQUARE:6>KO85ss <ADDRESS:65>Dekhanov George G.
241039
If I had to take a guess, the wsjtx_log.adi file is getting reprocessed when there is a change to JTDX.ini or at startup. In lieu of having an explicit "reload" button in Settings->Notifications as WSJT-X does. This is why the lockups only happen after the settings are changed or on startup.
I'm surprised that no one ever tried to import an ADIF from a logger before. It seems like something really basic to make the highlighting match what you'd really worked. Maybe most users turn off or ignore the highlighting and rely on JTAlert to tell them what they had and had not worked before.
Siemens software has been called a celebration of unnecessary complexity... Don't get me started...
-S.