2.1.x Release Notes

2.1.16 2017-12-06

New features

Per-band log reports are now html pages instead of text files, and include operator name, station name, radio ID, and Run/Pounce ID for each QSO. Thanks WA1Z.


When choosing a great circle map image file, SkookumLogger now recognizes both “tif” and “tiff” file extensions.

SkookumLogger now automatically scrolls an activity table only when the table is sorted on the frequency column and there is no selected row.

This release has numerous behind-the-scenes changes intended to solve a problem that I cannot reproduce myself: erratic spacing between characters when W4CB is sending the received call. One of these changes is discussed in more detail below to document for myself when the change was introduced.

SkookumLogger uses the ORSSerialPort framework (created by the author of Aether). That framework has a background thread that efficiently monitors a serial port connection. When the thread receives data, it notifies SkookumLogger by calling a function on the main thread. I modified that behavior to optionally notify on the monitoring thread instead of the main thread. This is more efficient but SkookumLogger must be careful not to do anything with the received data that involves functions that must run on the main thread. I have enabled that option for (only) the WinKeyer connection. So far I haven’t seen any problems with this but please let me know if you hit a reproducible issue that seems to involve the keyer.

Misfeatures fixed

Poor code was causing a needless pause before beginning CW message sending. Thanks W2RU.

The band change data in the statistics report was broken for the second radio in 2T2R, and incorrectly counting an extra band change for each radio at the beginning of a contest. Thanks JH5GHM.

SkookumLogger was counting double multipliers in the ARRL 160m contest; now DXCC countries that are in ARRL sections are excluded as country multipliers. Thanks WA1Z, W9JJ.

2.1.15 2017-11-11

Misfeatures fixed

Calls with more than 9 characters caused a crash in the partial matching code. Now the partials list will show only the first 9 characters of calls longer than 9 characters. Thanks GØDVJ.

2.1.14 2017-11-10

New features

In 1T2R, if you type an ampersand (&) followed by a frequency and return in either call field while Run has transmit focus, the subreceiver will be set to that frequency. If Pounce has transmit focus, or if Radio 1 doesn't have a subreceiver, or if Radio 1 is in SPLIT mode, or if the subreceiver diversity mode (K3) is on, nothing happens.

Help has a new topic named Text Commands in the Log Window section.

Logging Preferences has a new chooser for QSO Entry Font that affects the text in all of the entry fields except the Call field.

The Rate Tracker has two added items in each of the QSOs Per Hour and the Minutes Elapsed Since Last QSO boxes. These items set the thresholds for warn and alert coloring of the bars within the boxes. The labels for the QSOs Per Hour bars have the alert color (red) when the corresponding rates are zero. Details are described in Help. Thanks JH5GHM.


When there is an exact match to a partial call, the matched call is shown first in the list of possible matches. Also, the delimiters surrounding calls have changed (see the tooltip), and the calls are aligned vertically on the first character in the call instead of on the leading delimiter.

The Fills QSO entry from nearby activity option in Activities preferences no longer changes the radio frequency and does not change keyboard focus. See the Activity Preferences topic in Help.

The Automatically turn rotator option in Logging preference now applies only when the selected transmit antenna has the Rotary bearing type. The Green Heron and Easy Rotator Control rotator types ignore the set bearing command when the current bearing is within 2 degrees of the new bearing. Thanks G6NHU.

Inconsolata has been added to the list of fonts that may appear in the Fixed Pitch Fonts menu in Logging preferences. The font will appear only if installed on your computer. Thanks JH5GHM.

The CQ causes Pounce to Run focus switch Configuration options for 1T1R and 1T2R no longer exist. The focus change now always happens when necessary.

The start dates for the Stew Perry 160m contest are now set to the bogus date.

The SkookumNet Merge Logs command now has a do-you-really-want-to-do-that alert. Thanks GØDVJ.

Numerous updates were needed for the RSGB Club Calls Contest. Fixed a problem with start date. Updated the database of RSGB Club names and codes. Changed Contest name to RSGB 160m AFS (Club Calls) Contest. Changed mode from SSB to Mixed. Changed Club Status entry field to accept only HQ, CM, or NC. Convert old status codes from Exchange database to new codes on the fly. Set default Club Code field to “----”. Revised QSO point values. Added detection of RSGB HQ stations. Added multipliers as Other type. Revised Cabrillo QSO record format. Thanks GØDVJ.

The algorithm for computing a not-at-all-random serial number for the UKEICC Random Serial Contest has been replaced by a really-random serial number generator that doesn’t require feeding a call to the algorithm. If the UKEICC adjudicators choose not to trust that SkookumLogger logs what was sent, I won’t care.

Misfeatures fixed

The Time Tracker window now remembers its position and whether or not the Offtimes disclosure view is hidden. Thanks G6NHU.

A corrupted country aliases file was causing empty call signs to be treated as valid, resulting in unexpected information in the QSO entry fields. Thanks JH5GHM.

New York QSO Party In New York was failing to identify multipliers properly. Thanks W2CS, K2QO.

A missing semicolon in a command sent to K3 radios was causing bizarre behavior especially affecting 1T2R. Thanks W2RU.

Morse ► Tune Mode did nothing. Now it is a toggle that works, named Key Down to avoid conflict with Radio ► Tune Mode.

A harmless problem when quitting SkookumLogger was generating crash reports that were discovered when next starting SkookumLogger. Thanks AE4RM.

An unsafe programming practice was, rarely, resulting in a crash. Thanks JH5GHM.

The SkookumNet Merge Logs command was performing the Reset Log function, clobbering the next serial number among other things. Thanks GØDVJ.

Links to the ARRL log submittal web page for all ARRL contests, and to the rules page for ARRL SS were broken. Thanks W2RU.

High Sierra issues

File ► New Log From Existing… causes a silent error and fails to save a new log. The command has been removed. Workaround: duplicate and rename the log in Finder, then open that file. Thanks GØDVJ.

Anchors in the help book aren't found.

2.1.13 2017-10-12


SkookumLogger no longer attempts to predict start dates for contests that choose them by throwing darts at a calendar. Instead, the start date for a new log is set to January 1 of the current year.

The Kenwood Radio module makes use of Quick Memories to remember run frequency when toggling between running and S&P in 2T2R. Thanks JH5GHM.

In 2T2R, grabbing an activity to radio 1 or to radio 2 now automatically changes the submode for the radio to pounce. Thanks JH5GHM.

MacOS 10.13 (High Sierra) has changed the appearance of some standard user interface items. The most egregious change noted so far affects the bars in the Rate Tracker; bars with tick marks beneath them now have different vertical sizes than bars with no ticks. So, the ticks option has been turned off for all bars. Thanks GØDVJ.

Misfeatures fixed

In the UKEICC Random Serial Contest, the not-so-random serial was not being initialized correctly for the first QSO in a new log. Thanks GØDVJ.

Logic for identifying CA stations in CQP was failing to flag stations in California.

Logic for pre-filling exchange information in CQP was not implemented at all.

The sent serial number for CW QSOs was increasing by 2 when the “Reserve serial number when sent option” in Logging preferences was on. Thanks VE3AYR.

2.1.12 2017-09-20

New features

Added UKEICC Random Serial contest in the Regional group. This has involved considerable modifications to internal handling of sent serial numbers. Please be alert for unexpected behavior. Thanks GØDVJ.


The accurate locator crosshairs are drawn somewhat larger and thicker on the Great Circle map. Thanks GØDVJ.

The list of Mexican states has been updated. This affects the ARRL 10m contest. Thanks W9JJ.

All email addresses for submitting logs to ARRL have been removed. Thanks W9JJ.

The algorithm for computing distance between two latitude, longitude coordinate pairs, borrowed from hamlib, has been replaced by a function provided by Apple’s location services. The companion hamlib algorithm for computing bearing between those coordinates has been replaced by a direct implementation of the spherical trigonometry solution. Now, changing Great Circle map zoom factor no longer causes a target point to change its location relative to the map.

SkookumLogger now does a better job of determining whether or not a call might be needed in US state QSO parties. The primary improvement involves using the AD1C cty_wt_mod.dat file to determine call areas. Thanks WA1Z.

SkookumLogger now does a better job of tracking the NEQP, 7QP, INQP, State, Province, and DX kinds of exchanges that can appear in the same NEQP log.

Misfeatures fixed

Fixed a case where the can receive QTCs activity flag did not appear for a call that had not received any QTCs because there were no QTCs available to send when the activity was created. Thanks JH5GHM.

Fixed an egregious bug where the can receive QTCs activity flag did appear for calls that had received 10 QTCs. Thanks JH5GHM.

2.1.11 2017-08-22

New features

The Great Circle Map now distinguishes two kinds of target locations by drawing either crosshairs or a blob. Crosshairs correspond to locations determined from Maidenhead locators found in the current log or in your Exchange Database. A blob corresponds to a less precise location determined using Countries database coordinates for the centers of relatively large geopolitical areas. Thanks GØDVJ.

Activity tables have a new column with title °, showing the short path bearing from your location to the call of the activity. The bearing is computed when the activity is created, using the same approach as for the Great Circle Map target location. The new column will show up to the right of others, possibly outside the window. You can move, resize, show, and hide the column in the usual way. Thanks DL7ALM.

Basic support has been added for the Yaesu FT-1000MP radio. Thanks GØDVJ.

The Activity ► Call Refused QTC command adds the call in the active QSO entry box to a list of calls that refused when you asked to exchange QTCs. Calls in that list appear in Activity tables flagged with the prohibited emoji: 🚫. The command is hidden except for the WAEDC contest. The list is emptied when you start SkookumLogger, reset the log, or change to a different log.


The statistics report for WAEDC contests now includes the QTC count. Thanks JH5GHM.

QTC times are now left-padded with zeros to be 4 digits wide.

SkookumNet is now more tolerate of unusual types of abuse, such as breaking the network connection without first leaving SkookumNet. The affected host computer now detects that situation and automatically leaves the network. Other computers discover the lost host more quickly, instead of stalling for 60 seconds, and they report the host as lost instead of throwing an unexpected time-out exception causing a crash. Thanks GØDVJ and WA1Z.

The K3 radio type now saves the P3 Options choice for each band in your preferences file, and restores the P3 to the stored value when the radio changes bands. The initial choice for each band is Narrow. This change works around behavior in the K3/P3 firmware that interfere with the per-band memories in the P3. Thanks W2RU.

Misfeatures fixed

Hopefully, a rare bug relating to handling activity table updating when the main receive frequency changes has been squished. Thanks JH5GHM.

TimeTracker now examines QTC Series time stamps along with QSO time stamps when determining off times for WAEDC contests. Thanks JH5GHM.

2.1.10 2017-08-02

New features

SkookumLogger now supports the Swedish Monthly Test. Thanks SMØTHU.

Rate Tracker Changes

The values in the QSOs Per Hour and Elapsed Time Since Last QSO boxes in the Rate Tracker are determined from the subset of QSOs made by the computer displaying the Rate Tracker when that computer is a member of SkookumNet and Partner Mode is off.

The Last 10 QSOs and Last 100 QSOs items in the Rate Tracker window are now Last 10 Min and Last 100 Min.

The three bars in the QSOs Per Hour box of the Rate Tracker are colored red when the value is less than 20% of Maximum Rate, yellow when the value is between 20% and 50% of Maximum Rate, and otherwise green.

The bar in the Elapsed Time Since Last QSO box is colored green when the value is less than 50% of Maximum Elapsed Minutes, yellow when the value is between 50% and 70% of Maximum Elapsed Minutes, and otherwise red.


SkookumNet Changes

Window ► SkookumNet opens a new window that consolidates SkookumLogger features related to operating in a contest with two or more stations connected via a local area network:


The window title show the Computer Name as set in your Sharing preferences, also known as the Host name. SkookumLogger fills the station name field for each QSO with the host name so that it can determine which network member logged the QSO.

The Join SkookumNet checkbox was in Logging preferences. The Partner Mode checkbox was a toggle item in the Log menu. These two items behave as before, and Partner Mode behavior is unchanged.

The Merge Logs button replaces the Sync With Peer and Merge With Peer items in the Log menu. This command merges the logs of other hosts into the log of the host that started the processing, then replaces the other logs with the merged log.

The upper text box in the window shows network status messages, previously displayed in the Information window. The text box also shows messages from stations on the network prefixed by the operator call at the time the message was sent. Type anything into the center box followed by return to send a “gab” message to all network members. Use View ► Toggle Gab to alternate between the gab entry box and the Log window.

The table at the bottom of the window shows the Run and Pounce frequencies and modes for other SkookumNet hosts. A checkmark indicates which of Run or Pounce has transmit focus.

When using SkookumNet and Partner mode is not enabled, Log ► Correct Last QSO and Log ► Delete Last QSO now apply to the most recent QSO in the subset of all QSOs for the host station name.


Other Changes

In 1T1R and 1T2R, when the radio changes band while Run has transmit focus, the frequency and mode on the new band are copied to Pounce. Thanks WA1Z.

Hawaii QSO Party rules have been updated. The contest now has different required off time (none) and different QSO points (not band-dependent).

Misfeatures fixed

For WAEDC contest only and receiving spots from DX Cluster, SkookumLogger would crash sporadically due to a poorly-done fix in 2.1.9 relating to flagging activities. Thanks JH5GHM.

2.1.9 2017-07-14

New features

Added a great circle map for WRTC2018 entrants.

Activity ► Create will now accept “invalid” callsigns, like CR?K, allowing you to create placeholders in activity tables that you can quickly return to later. Invalid calls are annotated with your Zero-point font and color. Thanks W2RU, WA1Z, JH5GHM.

When an activity is created, an existing activity with the same call is automatically deleted, because it is unlikely that the same station has more one transmitter CQing on the same band. In this release, existing activities are deleted only when both the call and mode are matched. Thanks WA1Z.


Support for the RSGB International DX Contest has been updated to accommodate rules changes made by RSGB. Thanks GØDVJ.

The Pass Information window is no longer cleared when you log a QSO. Instead, it updates after you enter the third character of a new call. Additionally, when using SkookumNet, the call monitored by the station's Pass Information window is independent of QSOs logged by other stations. Thanks WA1Z.

The Fills QSO entry from nearby activity option in Activities preferences no longer clears the QSO entry fields when there is no nearby activity.

The QTC Series table now can be sorted only on the UTC column.

Misfeatures fixed

Changing the Table Update Interval in Activities preferences did not take effect until SkookumLogger was restarted.

The module for the TenTec Eagle radio was not reading information from the radio, although it could set radio frequency and mode. Thanks N9TB.

Deleting an activity table entry was not deleting the corresponding entries in activity tables of SkookumNet members.

The <subrx> activity item was being displayed when the radio configuration was 1T1R.

The size of the target dot on Maidenhead maps was too large. Thanks GØDVJ.

Sending “his call” concurrently with saving the log was causing irregular spacing between characters in the call. Thanks WA1Z.

Attempting to create a Statistics report for a log with no valid QSOs caused a crash. Thanks W6TN.

Using space bar consistently while receiving QTCs was failing to include the last QTC when finishing a series. Thanks WA1Z.

Attempting to flag activities for calls that can send/receive QTCs was causing a crash.

2.1.8 2017-06-30

New features

SkookumLogger now supports the ARRL 222 MHz and Up Distance Contest, for bands up 23cm. Thanks K5ND.

SkookumLogger now supports the RSGB 80m Autumn contests. Thanks GØDVJ.


Considerable housecleaning has been applied to the Xcode project, to remove items no longer in use, and to make the internal organization the same as the external file structure.

Many small changes affect only operating as a WRTC 2018 entrant:

The sent report token (^) is automatically included in the Morse Exchange message depending on whether or not the contest rules require sent report. You should not include the token when customizing your Morse Sent Exchange Template in the Sent Exchange Editor.

The Host Call and Operator calls in the Cabrillo Settings sheet are now displayed as uppercase with fixed-width characters.

The width of the Station column in the Log table is now adjustable.

The Band Changes table in the Statistics Report now adapts to one or two radios for any number of stations.

The Continent Breakdown table now always appears in the Statistics Report; previously it appeared only for contests that have Country multipliers.

Misfeatures fixed

Applying a change (tab or return) in the Morse Sent Exchange Template field of the Sent Exchange Editor no longer resets the template to the value derived from the individual sent exchange fields.

Some items in the Messages menu were not being disabled properly.

Using the Phantom Radio was causing a harmless error report when SkookumLogger started. Thanks JH5GHM, KG5HVO.

2.1.7 2017-06-20

New features

Spacebar in QTC tables columns for calls and decimal digits now acts like the tab. Thanks WA1Z and GØDVJ.

The Score Breakdown table in the Statistics report now includes a column for QSO points. Thanks JH5GHM.

The WinKeyer emulation in the YCCC SO2R Box is now supported. See Help for details. Thanks JH5GHM.


Items in the Edit menu that do not apply for contesting, such as spell-checking, are now hidden. These items led to rare crashes.

The Off Times table in Time Tracker now updates the end and duration data for the last entry while that off time is in progress. Thanks GØDVJ.

The Define Country window title has been changed and the help documentation expanded to note that the function can be used to make SkookumLogger accept call signs that would otherwise be rejected as invalid.

Misfeatures fixed

A potential crash when processing information received from an ICOM radio has been addressed. I cannot test this repair so please let me know if you encounter a change in SkookumLogger behavior with that type of radio. Thanks KA1IS.

The Score Breakdown table in the statistics report was missing headers for the SSB and Data columns. Thanks WA1Z.

2.1.6 2017-05-19

New features

SkookumLogger now has a scheme for promptly detecting duplicates in contests that have “rovers.” A rover is a call that you can work many times on the same band and mode, as long as the received location (county, state, grid square, etc.) is different for each QSO. Similarly, if you are a rover yourself, then you can work the same station again and again from each location that you visit.

The new scheme depends on you to identify calls that are rovers. You do that by ticking the checkbox in the Rover column of the log table after working a rover. You only need to do that once; SkookumLogger then ticks the checkbox for all QSOs with that call. The Rover column is hidden for contests that do not have rovers. If you don’t see the column when you think you should, scroll the log sideways to be sure that it isn’t located “outside” the log window. When you are a rover yourself, simply change the location field in the Sent Exchange Editor when you enter a new location.

This scheme more promptly detects duplicates because you no longer need to enter the received location for all calls, only for calls that are rovers. Thanks W2CS and AA4GA.

File ► Statistics Report now generates html output instead of plain text. When you run the command, which may take several tens of seconds depending on the size of your log, SkookumLogger will open the output in your web browser. Use the browser Save command to stash the report wherever you want to on your computer. The relatively new File ► Rate Breakdown Report command behaves the same way. Also, the statics report command no longer generates per-band text log files; instead use File ► Per-band Log Files. Thanks WA1Z.

The new Activity menu, just to the right of the Log menu, brings together activity-related commands that were previously in other menus, including the context menus for each Activity table. Those context menus have been removed.

The two pairs of activity grab commands for the 2T2R configuration do not have keyboard shortcuts, but shortcuts can be defined in the usual way System Keyboard Shortcuts preferences. When defining a shortcut, be sure exactly match the menu item title — everything up to and including the trailing parenthesis. Case and special characters matter.

Code relating to the Great Circle Map has been revamped to deal with a very poor internal design. All previous functionality still exists. There is a new Map menu on the menu bar that appears only when the Great Circle Map Window is open. That menu has items that previously cluttered the Antenna menu, and four new “Hide” toggle items that determine visibility of annotations and controls surrounding the map image.

Map ► Change Great Circle Map opens a file chooser for loading a great circle map file located anywhere on your computer. No more fussing with getting the map file into your Applications Support folder with exactly the right name. And you can load any image file that you have downloaded from Maps to see what the world looks like for the person at the other end of your QSO — when you have nothing better to do of course.

The Maps web page has been updated with higher quality map files; however your existing map file will work as before. All of the previous map files have been removed from the web site; let me know if I failed to provide a replacement for your location.

Misfeatures fixed

SkookumLogger was failing to check that a spot received from DX Cluster that contained “QSX” in the information field also contained a frequency after the QSX before attempting to decode the offset data, resulting in a crash. Thanks GØDVJ.

SkookumLogger was reporting exceptions generated by a mysterious system component named NSRemoteView. SkookumLogger now ignores those exceptions instead of forcing an abort. Thanks GØDVJ.

It wasn’t possible to redefine keyboard shortcuts for activity windows because the menu item titles were exact duplicates of items in the Radio 1 ► Band ► menu. The latter items now have distinct titles. Thanks JH5GHM.

The Messages menu item label for message 13 was not being updated correctly after editing in Morse Messages Editor. Thanks JH5GHM.

2.1.5 2017-04-30

Misfeatures fixed

SkookumLogger now prevents crashes caused by creating an empty sent exchange field in the Sent Exchange Editor. I've not a clue why anyone would want to do that.

Changes to the off time code in 2.1.4 resulted in unbounded consumption of memory and inexplicable processing delays during a contest. Thanks GØDVJ.

2.1.4 2017-04-28

New features

The Time Tracker now includes a table of begin, end, and duration for off times. All of the off-time related items are relocated into a normally-hidden view, since most contests do not have off-time requirements. The Cabrillo export includes OFFTIME: records for each entry in the table. As far as I know, only the Helvetia contest will process these records. Thanks WA1Z and HB9CEY.

Activities created by skimmers now automatically time out after 10 minutes. The Activity Age Limit preference affects only non-skimmer activities and may be smaller or larger than 10 minutes. Thanks GØDVJ, W2RU.

File ► Rate Breakdown constructs a rate breakdown table for the current log, saves it as RateBreakdown.html in your Applications Support folder, and opens it in your web browser. Thanks WA1Z.


When changing transmit focus will cause a band change, SkookumLogger now proactively informs amplifiers and antenna switches about the frequency change so that they can react in parallel with the transceiver band change. Previously, amplifiers and switches were informed only after a band change was detected by polling the transceiver. After kicking off the band change, SkookumLogger waits briefly before performing any other actions so that, for example, sending a message will not begin until the delay expires. The duration of that delay is 0.6 seconds, the minimum needed for clean band-changing at my station. This technique does not apply to the 2T2R configuration. Thanks W6SX, W2RU.

The Sent Exchange CW message token (&) now excludes the sent signal report. You may need to revisit your Messages preferences and edit messages in existing logs. Define message 2 as "^ &", then replace "&" in other messages with "{2".

Nearly every rule for the Helvetia contest was changed late last year. As usual I was completely unaware of the changes until today; I have attempted to update SkookumLogger, but with inadequate time to fully test. Thanks HB9CEY.

Misfeatures fixed

Creating a new log was stalling activity table updates until you switched to another log and back.

Changing items in the Log Settings sheet had no apparent effect until you manually performed Rebuild Checksheets.

2.1.3 2017-04-21

Important Notice

This version requires macOS version 10.10 (Yosemite) or newer, dropping support for 10.9 (Mavericks). In fact, 10.9 has been unsupported since at least far back as 2.0.9. Sorry!

New features

Added contest: Japan International DX Contest, both sides, both modes.

SkookumLogger now automatically runs Log ► Rebuild Checksheets after you log a QSO if the log contains any QSOs marked as suspect. Rebuilding stalls user interaction briefly, where the duration of the stall depends on the size of your log. The new Automatic Rebuild QSO Limit preference in the Logging preferences pane disables the automatic update for logs containing more QSOs than the limit. The default limit is 0 QSOs, so that behavior is the same as in previous releases. I experience a slight delay for a log with 200 QSOs on my 2.7 GHz Late 2012 iMac.


The subject of emails created by File ► Submit Log Via Apple Mail now includes both the call that you used during the contest and the Cabrillo name of the contest.

Major rules changes for the 2017 YUDX contest were discovered and addressed, during the contest.

More changes have been made to the problem reporting feature to reduce the number of spurious reports and to make the user interface a bit more obvious. I appreciate your patience with this sometimes annoying feature; it has helped me resolve several issues I would have otherwise never known of, such as the incompatibility with macOS 10.9.

The Xcode project now uses CocoaPods for three third-party components, CocoaAsyncSocket, ORRSerialPort and Sparkle. That simplifies my life, but will affect any other developers who want to use the SkookumLogger project.

Misfeatures fixed

Corrected the macOS version check that warns when trying to start SkookumLogger on unsupported older versions.

2.1.2 2017-04-11

Misfeatures fixed

Version 2.1.1 was silently refusing to open previous logs. Thanks GØDVJ.

2.1.1 2017-04-11


Logs that that you save with this release will not be usable with previous releases of SkookumLogger. Logs saved with previous releases are usable with this release.

New features

Changing the Fixed Pitch Font preference immediately changes the text displayed in the Log table, so you can assess which font is more readable. Restart SkookumLogger after making the change to see the effect in other windows like the activity windows. Let me know if you have a fixed-pitch font that doesn’t show up on the list in Logging preferences.

If the active call field is not empty when you choose View ► Focus Log Search Field, the call field content is copied to the search field and the search function is applied. The search only makes sense if the Search Field is set to Call. Thanks JH5GHM.

If the “Automatically search” option is enabled in Logging preferences, then typing into a call field filters the log to show only QSOs with calls that contain what you have typed. The search begins when you type the third character. Thanks JH5GHM.

If, in a Call field, you type a colon followed by 4 digits representing a time as ‘hhmm’ and press return, SkookumLogger filters the log table to show only QSOs within two minutes of that time. You may optionally omit the leading h digit when it is zero. The time specification may be entered by itself or following a call sign.

The Prefix Checksheet now has an Area (continent) chooser. Thanks GØDVJ.

The SkookumLogger ► Automatically Check for Updates command toggles whether or not SkookumLogger periodically looks for updates. If an update is available, you will be asked whether or not to download and install it. The check is performed once per day.

The new command Log ► Correct Last QSO is enabled when the QSO entry box with keyboard focus has at least one field that isn’t empty. Choosing the command copies the content of non-empty fields into the latest logged QSO, where “latest” means the QSO with the most recent UTC. Logging preferences has a new item named Correct Last QSO Special Key; you should be able to figure out what that does. As always, changing a logged QSO may also require using the Log ► Rebuild Checksheets command.

The new “Refuse to log any QSOs” option in Logging preferences prevents accidentally logging any QSOs. This is intended for use by peer computers in SkookumNet that are not making QSOs. Thanks GØDVJ.

The new Radio ► Set Radio from QSO command sets the radio frequencies and mode to the values in the selected QSO in the log table. If no QSO is selected, the most recent QSO is used. The command is available only in 1T1R and 1T2R configurations, and is intended to simplify “netting” a peer computer in SkookumNet when using the SkookumLogger partner operating features. Thanks GØDVJ.


The behavior of the Grid and Report entry fields is now less bizarre and better-described in the Log Window/QSO Data Entry and Log Window/Entry Formatting Rules Help topics.

The rule for Other multipliers in Yuri Gagarin DX Contest has been updated. Apparently the multiplier is any call ending in “yyGC”, where yy is number of years since the Gagarin space flight in 1961.

Misfeatures fixed

The error report that was presented when cancelling the New Log dialog is now suppressed.

A crash when using an ICOM radio with SkookumLogger may have been fixed.

The Morse Message Editor now allows empty label and content fields instead of causing SkookumLogger to refuse to save the log file.

SkookumLogger was deciphering the DXCC code of “CEØY/W1MJ” as K instead of CEØY.

Some sequences of logging QSOs, deleting QSOs, rebuilding checksheets and Undo were causing crashes. Thanks W2RU.

The Substitute Contest Name Chooser, which was supposed convert old logs containing retired contest names to new logs with a suitable new contest name and the same content, was miserably broken. Now it happily Just Works.

Flagging rovers was choosing apparently random QSOs as having the same call sign.

2.1.0 2017-03-30

New features

View ► Focus Log Search Field moves keyboard focus to the search field, where you can begin typing to show log entries with calls that match what you type, as you type. When you are done, use View ► Focus Recent QSO Entry, default shortcut F10, to clear the search and return keyboard focus to the most-recently-focused QSO entry field. The default shortcut for the new command is ⌘F10; in previous releases that shortcut was assigned to the Antenna ► Set Rotator to Target Bearing command, which now has no default shortcut.

The WinKeyer speeds for the two QSO Entry boxes are now shown at the lower right corner of the entry boxes, with the box identification labels relocated to the upper right corner.

The new command Antenna ► Set Rotator to Target Long Path Bearing does what I hope you would expect, with no default shortcut. Thanks W2RU.

SkookumLogger now tracks duplicate status of calls in QSOs that are marked SQ because they are invalid. This change allows you to make additional QSOs with that call, knowing whether or not those QSOs are dupes.

SkookumLogger now declares valid any call that is an exact match for an entry in the cty_wt_mod.dat file maintained by AD1C, or for an entry in your countryAliases file. You can add entries to your countryAliases file in the Define Country window.

With the exceptions above, valid calls must match one of several patterns for the sequence of letters and digits in the call. This release adds the pattern “starts with one or more letters and ends with three or four digits”. The calls BX100 and VX3100 match this pattern, they were previously declared invalid.


The recently-introduced error reporting feature no longer reports issues that SkookumLogger knows how to handle, such as internet ping timeouts and unresponsive serial devices.

Sparkle, the framework that handles updating SkookumLogger, has been, ummm, updated.

Misfeatures fixed

The Log ► Rebuild Checksheets command is now automatically triggered when you finish editing log settings via Log ► Cabrillo Settings…. Previously, checksheets were cleared but not repopulated. Thanks GØDVJ.