There it was…I should have looked there. ?Funny thing is, I didn’t change it. ?Didn’t unclick the “Enable” button in the World Map/DX Atlas panel that made my DXAtlas stop loading, either, but I managed to find that on my own. ?Seems like it all started around the time I installed the latest version of wsjtx, but maybe I just have a little gremlin in the machine…
Thanks (again) for the guidance. ?I’ll look harder next time my gremlin strikes.
73, Steve
toggle quoted message
Show quoted text
On Feb 22, 2025, at 2:07?PM, Dave AA6YQ <aa6yq@...> wrote:
?
On Sat, Feb 22, 2025 at 02:53 PM, Steve wrote:
I’m using JTAlert V2 for JTDX with JTDX. ?I recently installed WSJT-X v2.7.0 for use of the SuperFox/Hound mode. ?The former, of course, interoperates with DXLab quite well, automatically inserting contacts into my DXKeeper log. ?Since I haven’t installed and configured JTAlert for WSJT-X, I have to import those (occasional) QSOs by saving a copy of the wsjtx_log.adi, trimming the QSOs I don’t want to import, and using the Import QSOs function in DXKeeper.?They apparently import with another myQTH ID than the one shown in the default myQTH ID indicated in the Log Settings panel in the Log tab. ?I
+ Correct. When you're importing an ADIF file, the default "myQTH ID" for imported QSOs that don't specify one is governed by the "Substitute for missing QTH IDs" selector in the "Substitution options" panel on the Main window's "Import QSOs" tab. See
https://www.dxlabsuite.com/dxkeeper/Help/Import.htm#Substitution_Options
’m probably doing things the hard way, but it used to work without having the extra steps go in and modify the myQTH for each contact to my default (home) one after the transfer…
+ You evidently changed the "Substitute for missing QTH IDs" setting on the Main window's "Import QSOs" tab from when it "used to work".
? ? ? ? ?73,
? ? ? ? ? ? ? ? Dave, AA6YQ
