Welcome to the group.
Fldigi does not communicate directly with MLDX at any level. However, as you already are aware, Fldigi can execute scripts to pass data to MLDX, including logging, and if an AppleScript were developed to pass the call or other information this would work as well. Unfortunately, there is no way to push that data (at present) from MLDX back to Fldigi, but it is not really needed. Fldigi also can do call lookups on its own; it is configured by going to the Configure Menu, QRZ/eQSL option. There is a large selection of choices for lookup within Fldigi. Thus, you can do the call lookup in Fldigi and then execute the macro that runs the AppleScript to save to MLDX.
Alternately, you can simply save all of your logs in Fldigi, and then import the logbook (it is an ADIF formatted logbook) straight into MLDX when you are done with your session. The latest beta versions of MLDX support dupe checking so you donât have to worry about importing duplicate QSO data.
Hope this is of help.
âReal radio bounces off the sky"
Post by w6jhb-BUHhNemail@example.com [linuxham]
I joined this group because I am hoping that in addition to the Unix theme, it is related to the Mac OS-X users, too. If not, please excuse me and point me in the right direction!
I currently am running OS-X on a 27" iMac. I use WSJT-X for JT65 and JT9 and have been using cocoaModem for PSK31 and just recently, RTTY. CocoaModem works OK, but I was told that FLDIGI offers a lot more flexibility. I also have been using MacLoggerDX for several years and like it a lot - it really suits my needs.
My question is: can FLDIGI be used to (1) pass a call to MLDX and tell it to lookup the call on whatever system the user is licensed for, and (2) tell MLDX to log the contact? I currently do this in MLDX via macros that run Apple Script commands.
Thanks, Jim / W6JHB