www.dl2rum.de

I have installed version 2.12. The App Store is offering 2.13 but it is not updating my app - and not offering to update .... Strange ! Matthias

Hi Kes, I use below applescript to log qso in RumlogNG.It works fine on my end: on run tell application "cocoaModem 2.0" set theCallsign to callsign of qso set OpName to operator name of qso set theMode to modemName if the theMode = "psk modem" then set theMode to "PSK"...

Thank you for the 2.2 version. Its really working perfect in every respect now ! Using FTdx5000, DigiKeyer2, Mac OSX El Capitain 10.11.1. Even the CocoaModem with updated Applescripts integrates very nicely. Stability towards CAT is much more stable now than in RumLog. Now I have done the full migra...

Thomas, Your hopes are fulfilled ... My (big) mistake .. Everything OK !
73 - Matthias

I see that the 1.1 version now also is available in the App Store .. I have installed it from the App Store - but the Maps are not working in this version.
73 LA0FA/Matthias

Thanks - works perfectly !!
73 LA0FA/Matthias

I have introduced HC2AO/8 with a valid timeperiod in the DXCC exception list - for a new QSO it is correctly recognised as HC8. But I can not change to correct DXCC when editing a QSO already in the log. When I converted/imported the classic DB i saw the QSO was corrected wrongly to HC - and now I a...

RumLogNG consequently recognizes HC2AO/8 as Ecuador while it is Galapagos (HC8). Also Clublog recognises it as HC8. I can't find it in the invalid or exception list either.
In RumLog Classic its OK.
73 LA0FA

I have some problems to get the application to react when clicking(double-clicking) on a spot on band map.
The call is rarely taken over in the QSO registration and no TRX QSY is happening. When clicking on the DX - Spot
in the DX-SPot window everything works fine.
73 LA0FA.

The CAT support of FTdX5000 works with those settings (with the exception of cw memory read/save)