|
|
Post by Atsu JE1DRU on May 5, 2022 9:33:36 GMT
As you worked a DX station at a remote GL, the Notifications teat the same station as a new one when you find him again at your home GL (and vice versa).
The same wsjtx_log.adi file is used in common between the remote GL and the home GL.
Is there any way to make all worked stations shown as "worked B4"?
|
|
|
|
Post by Arvo ES1JA on May 5, 2022 12:23:44 GMT
If You use same file then it should work, when correctly linked then even when multiple instances are running in same time then New/B4 detection changes immediate after wsjtx_log.adi update ( logging QSO ). If You don't see this then something is wrong with file linking or if different callsign is used then Use current callsign is selected in Settings/General/Logbook filtering.
|
|
|
|
Post by Atsu JE1DRU on May 6, 2022 10:59:05 GMT
Hi Arvo,
Thank you for your feedback.
I run v.2.2.159 with 3 different profiles under my single callsign.
As well, it is a single PC. The profiles are the following:
1) Rig #1, home GL (QM05)
2) Rig #2, remote GL (PM95)
3) Rig #3, home GL (QM05)
All those profiles share the same wsjtx_log.adi by means of hard link.
Obviously, each profile has an exclusive folder to save its ini file and QSO record files in.
Apparently, there is nothing wrong.
If a station worked at home GL is shown as a new one at remote GL (and vice versa), it may be JTDX's specification to me.
But, if this can be changed by editing the ini file or whatever I would like to know it.
Thanks
|
|
|
|
Post by Arvo ES1JA on May 6, 2022 15:08:20 GMT
unset "Use current grid" in logbook Filtering
|
|
|
|
Post by Atsu JE1DRU on May 8, 2022 22:16:50 GMT
OK. Thanks a lot, Arvo.
|
|
|
|
Post by Arvo ES1JA on May 9, 2022 4:54:56 GMT
JTDX allows this like configuration, but in general this is not a good practice. You may be called endless by Grid hunters but Your JTDX will ignore them as B4 from Your second location.
|
|
