[Ham-Mac] QCluster 1.0.7 (221) released - Added modes, bearings and much more.

[Keith, G6NHU]

Updates since my last post:

• Added New Slots Club Log alert.
• Continued tidying the timings when QCluster is auto-started at login.  Please report any unexpected behaviour when auto-starting QCluster as opposed to manually launching it from the Applications folder.
• Fix applied to QCluster auto-updater timings.
• Disabled tab bar.
• Added JTTY as 'other' data mode.
• Add Modes to spot table.
• Update RTTY and FTx definitions.
• Allow both Not Worked and Not Confirmed to Club Log generated reports and indicate in LoTW column by form of either a crossed out w to indicate Not Worked or a crossed out c to indicate Not Confirmed (see here: https://groups.io/g/qcluster/topic/change_to_club_log_alerts_and/121443597).
• Add the ability to edit the alert from the summary screen of the New Slots alert.
• Slight variation in highlight colours. Two adjacent rows of the same alert will have a slightly different colour so it's not just full screen of the same colour.
• Performance updates to spot table and alert table switching.
• Add validation to entered Club Log credentials via setup page.
• Reduce Club Log automated lookup time to fifteen minutes.
• Add full Club Log error handling so it doesn't retry forever, or fail silently.
• Set alerts with the correct priority. 1 -> 2 -> 3 -> 4 -> Callsign -> New Slot.
• Add home Locator in Settings (used for bearing calculations).
• Add bearing as a tooltip to DX callsigns. Hover over the DX callsign in the spot table to get a bearing either directly to the station, if their exact grid is known, or an approximate bearing to the nominal location for that country as read from the CTY file. This relies on the home grid being entered in Settings.
• Fixed mode handling in Club Log alert setup pages.
• Updated LoTW database.
• Updated User Guide.

I include things in QCluster that I'll find useful and in the last couple of weeks, I've seen spots and found myself wondering what direction I need to point my aerial. Rather than have a specific column for bearing, I decided to do it via a tooltip because it's not needed for every station and I didn't want to increase the window size to make it fit. There's also the benefit that I don't need to calculate every bearing to every station as it's only done when you hover over a DX station. I'm happy with the way it's implemented here.

The full 40 page User Guide is here: https://qso365.co.uk/qcluster/qcluster-guide.pdf

QCluster is available via https://qso365.co.uk/qcluster
Direct .dmg download https://qso365.co.uk/qcluster/qcluster.dmg
There is a groups.io group https://groups.io/g/qcluster
My blog article about QCluster is here https://qso365.co.uk/2026/08/qcluster-a-native-dx-cluster-client-for-macos/

73 Keith.