Internet Spot Filters now support a second token, <blacklist>. This token expands to a list of the calls in your activities blacklist, for use in filtering those calls at the DX Cluster to reduce spot traffic. See the About DX Cluster topic in the Overview section of SkookumLogger Help.
Added support for Yaesu FT-1200, duplicating FT-2000 support with speed changed to 38400. Thanks GØDVJ.
The Generic QSO Party contest type now provides more complete support for typical QSO party rules, for use when SkookumLogger doesn’t explicitly support a particular event. See the new About Generic QSO Party Rules topic in the Overview section of SkookumLogger Help. Use this module if you want to operate NEQP and 7QP and INQP concurrently. You can submit the same Cabrillo file to all three event sponsors. Thanks K9QJS.
For contests with ITU or CQ zone in the exchange, SkookumLogger prefills the zone using the call and the Countries database. If you log a different zone, as may happen when you work someone who sends you a serial number for example, some contest sponsors will penalize you for logging the “wrong” zone. SkookumLogger now tags QSOs with logged zone different from expected zone with the SQ (Suspect QSO) flag, so that you can quickly find them in your log. If you determine that an SQ-tagged QSO should not be altered, turn off the “Export SQ as X-QSO” option in Export preferences before creating your Cabrillo file.
The changes in serial I/O and K3 timeout handling introduced in 1.9.15 have been removed.
ORSSerialPort 1.8.0 with SkookumLogger customizations has been merged into the code base. Thanks AC7CF (ORSSerialPort) and WD7K (customizations for microHAM protocol).
In the ES-Open HF Championship Contest, SkookumLogger was failing to identify calls outside Estonia as zero-pointers. Consequently they showed up as needed in activity windows. Thanks GØDVJ.
In the Yuri Gagarin DX Contest, all QSOs were being marked as suspect, the email address for submitting the log was malformed, and the list of special stations was outdated. Thanks WA1Z.
Special Keys in Logging preferences has two new items, Begin QSO and End QSO. When you are in run mode, Begin QSO sends messages 5 and 2, and End QSO sends message 3 and logs the QSO. When you are in pounce mode, Begin QSO sends message 4 and End QSO sends F2 and logs the QSO. In 2T2R, the run/pounce decision is tied to the yellow gumdrop for each radio (pounce when you see the gumdrop). Thanks JH5GHM.
Changing the Operator for a logged QSO (via the popup menu in the log table) now also sets the current operator to that choice. So, a new operator who forgot to “login” can fix a QSO that he just logged and not have to also choose himself in the Log ► Operator ► menu. Thanks GØDVJ.
In 2T2R, a receive frequency change of the radio with transmit focus creates an activity and clears the QSO entry fields if the submode is Pounce and the call field is not empty. Enabled by a new checkbox option in Configuration preferences. Thanks JH5GHM.
In 2T2R, logging a QSO creates an Activity table entry when the submode is Pounce. There is no preferences option (1T1R and 1T2R already do this). Thanks JH5GHM.
The minimum sizes of all checksheet windows have been changed to prevent clipping of the controls above the tables. Thanks GØDVJ.
Exchange guessing now happens when you navigate out of the call field, instead of on every call character typed. Thanks JH5GHM.
Experimental change to a Serial IO parameter. I’ve not found the change to have any effect in SkookumLogger, but please be alert for changed behavior with serial devices.
K3 radio module now reports timeouts to the Information Messages window and does not post an alert and disconnect. Instead, it keeps to polling the radio, which will either succeed because the timeout was a spurious event, or will report more timeouts. In the latter case, disconnect and reconnect yourself; maybe it will recover, maybe not, let me know. And let me know if you can identify what you were doing when the disconnect happened.
SkookumLogger was pre-filling serial numbers in the RDXC contest. Thanks WA1Z, JH5GHM.
SkookumLogger was failing to create two off periods when separated by one QSO. I've also observed bad off-period data. TimeTracker code has been scrubbed, rinsed, and hung out to dry. Bad off-periods could affect also affect the last-100 rate computation; if you see that then use Log ► Rebuild Checksheets to reconstruct the off-periods table.
See the new help page titled “Disabling Text Entry Focus Animation” in the Reference section if you would like to stop the pulsating border effect in Yosemite.
The content of checksheet table cells with 0 QSOs is now empty instead of the digit zero, to make it easier to identify needed entities. Thanks WA1Z.
The multiplier list for the UBA Spring Contest has been updated. A few were removed, a few were added with full name “Undefined” because the contest sponsor doesn’t see fit to provide that information. Thanks GØDVJ.
Sometimes logging a QSO resulted in two log entries with the same data. Thanks JH5GHM and WA1Z.
The "Pounce receive frequency change creates activity” options for 1T1R and 1T2R were not creating activities but were clearing the entry box. Thanks VE7GM.
Shift-Tab (backward-tab) wasn’t always tabbing to field immediately to left. Thanks GØDVJ.
If both call fields had content, then switching keyboard focus while sending one call would continue sending the middle of the other call. Thanks W2RU.
The Mode popup button in Log Setttings was disabled for “contests” that had no start date information. These were generally the events listed in the Nontest group. Thanks WA1Z.
When keyboard focus is changed to a Call entry field and the call in the field contains a question mark, the question mark is selected. Otherwise, as before, the cursor is positioned at the end of the call. Thanks WA1Z.
The Special Key box in Logging preferences has a new checkbox labeled "Remap '.' key to '?' key". When this checkbox is enabled, a period typed when a Call entry field has keyboard focus is replaced by a question mark. Thanks GØDVJ.
The Power QSO entry field now accepts 'N' and 'T' along with digits and any of 'KWQRP'.
When keyboard focus is changed from one QSO entry field to another, the content of the newly-focused field is selected. There are two exceptions to this behavior. One is the Call field behavior described above. The other is Report fields, where the S digit is selected.
It is no longer necessary to "apply" spot filter edits before choosing the Update Spot Filter function in Internet preferences.
Additional radio control updates have been provided by JH5GHM for the TS-590S and FTDX-3000.
The Regions statistics summary table was missing for certain contest types. Thanks GØDVJ.
Some UBA country multipliers were not being identified consistently. Thanks GØDVJ.
Cabrillo export silently failed when the log contained QSOs with empty station name fields. Thanks WB5EIN.
The Indiana QSO Party was missing the sent report entry field.
Some checksheets windows had no content until after a QSO was logged. Thanks many.
The onT (on-time) column in the rate statistics table sometimes had negative values. Thanks many.
In 1T1R, when changing transmit focus to an entry box with frequency equal to 0, first copy current radio frequency and mode to initialize. Thanks KV9W.
The CW North American Sprint is now a supported contest.
SkookumLogger now presents a "Getting Started" alert (for new users) at start up, to reduce confusion about what to do when no log window appears. The alert has a "Don't show again" button.
Radio control for Kenwood and Yaesu FT-3000 has been updated to support custom hardware between the computer and radio. Thanks JH5GHM.
In 1T2R the Autofill from activities option was active when Neither was selected. Thanks GØDVJ.
The FT-2000 radio module was sending an incorrect code that caused the DVR record indicator to blink. Thanks GØDVJ.
The “Operating Scheme” concept (SO2V, SO2R) has been replaced by a “Configuration” concept with three choices: One Transmitter One Receiver (1T1R), One Transmitter Two Receivers (1T2R), and Two Transmitters Two Receivers (2T2R). The Wizardry preference pane has been replaces by the Configuration preference pane, with some of the Wizardry preferences relocated to Logging, Messages, and Activites preferences. Part of the new concept is separation of transmit focus and keyboard focus, with some new messages that help to automate management of focus. See Help for details.
Indiana QSO Party inside Indiana is now a supported contest. See the “Entering a QSO” topic in Help, last paragraph, for discussion of how to deal with straddling a county line.
Preference panes have been reordered and widened so that all buttons on the toolbar are visible for every pane. Thanks GØDVJ.
CW speed control has been cleaned up. See the About WinKeyer topic in Help.
The sent serial number no longer appears in the Sent log table column. Use the Sent Serial column if you want to see it. Thanks JH5GHM.
The “SM” (Suspect Multiplier) concept is gone. Instead, when you log a QSO, SkookumLogger marks the QSO as SQ if it can’t determine the multiplier(s) for the QSO; Log ► Explain Suspect QSO describes the problem.
In 2T2R starting a CW CQ with radio 2 and toggling radio (F9) to radio 1 wasn’t aborting the message. Thanks WA1Z.
The last-100 rate computation was going berserk for logs with multiple off periods. Thanks WA1Z.
The Area chooser in the Regions checksheet had no areas.
The multiplier status string in the logging window now identifies QSOs that count for more than one type of multiplier. Thanks GØDVJ.
The CW and SSB buttons in the check sheet window now appear only if the contest has per-mode multipliers and the log category is mixed-mode. Thanks JH5GHM.
SkookumLogger now supports the new type of multiplier in the Hungarian DX Contest, HA-DXC member numbers.
Serial number reservation now has an option that restores the original behavior (reserve when logged rather than reserve when sent). See the About Serial Numbers page in SkookumLogger Help Overviews. Requested by GØDVJ.
The Edit menu has been restored, so that common commands like Select All, Copy and Paste are available in SkookumLogger text fields. Thanks WD7K.
When the SO2R operating scheme is active, the CW speed indicator next to the Beacon CQ button is hidden and the speeds for each radio are shown at the top right corner of their QSO data entry boxes. Each of the three speeds is saved separately and restored when you start SkookumLogger. Thanks JH5GHM.
Several bugs relating to SO2R operating scheme message sending and automatic transmit switching have been squished. See the About SO2R page in SkookumLogger Help Overviews for updated description of behaviors. Thanks WA1Z.
When toggling between the two QSO entry boxes with calls entered in each box, the check partials pane was showing matches for the wrong box. Thanks GØDVJ.
SkookumLogger now supports more than 100 contests. As a user convenience, each contest has a link to the sponsor’s web site page containing the contest rules. Keeping those links current has been a constant annoyance. This release replaces many of those direct links with links to appropriate contest summary pages at the WA7BNM web site. Bruce does an excellent job of keeping that information current (including links to the sponsors’ sites), in spite of sponsor indifference. These links are accessed via Help ► WA7BNM Contest Rules Summary. Bruce doesn’t have summary pages for some contests; for those cases the original scheme remains in place — the WA7BNM menu item is replaced by Help ► Open Rules Web Site. If you find a broken link or a better URL for those cases, let me know.
Tapping up or down arrow keys with keyboard focus in a QSO data entry field steps radio 1 frequency as determined by Wizardry preferences. Now, tapping control-up-arrow or control-down-arrow similarly steps radio 2 frequency. As noted earlier, radio 1 is always used for the SO2V operating scheme and radio 2 is additionally available in the SO2R operating scheme. Thanks JH5GHM.
Activities ► Tables ► Open Recent is a new command that reopens all of the activity windows that were open when you last chose the Activities ► Tables ► Close All command. Thanks W2RU.
The Export preferences pane now has two tabs. The Cabrillo tab provides defaults for all of the Cabrillo category items when you create a new log. As before, you can change the item choices for each log in the Log Settings sheet. You can also a define default soapbox comment.
SkookumLogger Help has a suggestion for how to use Grab Partner Call via a single key, in the Using Partner Mode page.
JH5GHM provided code supporting the DATA mode feature introduced in 1.9.8 for Kenwood radios and the FTDX3000. Katsuhiro also fixed an issue with RIT/XIT for the TS-590.
Somehow the SkookumLogger author determined that WA7BNM had changed his call to K7WA. Wrong. The relevant menu items have been changed and information added to credits.
Serial I/O for the ACOM 2000A has been changed to avoid errors during amplifier warmup. Typically, set up serial I/O and connect once in Serial preferences, then turn amplifier power on and off as desired using the RCU button. There is no device time-out for the 2000A.
Logic that avoids sending mode commands to the K3 when the K3 mode is already set properly has been corrected. Sending mode commands causes stalls in P3 sweeps.
The SO2R scheme for automatically switching transmit focus now works for both CW and SSB modes. Thanks WA1Z.
Code for all of the six check sheets has been scrubbed as part of adding support for mixed-mode contests. Check sheet windows now have “CW” and “SSB” radio buttons that choose the mode for the QSO totals shown in the tables. For single-mode contests, or when you have chosen a single-mode entry category, the appropriate button is selected and the other button is disabled. Thanks JH5GHM.
The Zone check sheet now has a Continent filter and shows only zones with at least one QSO.
Check sheets provide a complete listing of entities that you have worked and are not well-suited to quickly answering questions like “Which bands/modes need a particular entity?” Consider using the Pass Information window for those kinds of questions.
Two additional contests are supported, both in the National group: the UBA DX Contest (CW and SSB) and the ES-Open HF Championship. Thanks GØDVJ.
Typing DATA into a call field changes QSO mode if the connected radio supports that mode. This is presently implemented for K3 and Phantom radios, and is intended to minimally support logging RTTY QSOs.
When a call entry field became key, the field content was selected, instead of being deselected with the cursor positioned after the last character. Thanks W2RU.
The tqsl application must be located in the Applications folder in order to be found by SkookumLogger; otherwise the Upload to Logbook of the World command is mysteriously disabled. The Help document has been updated to explain the issue. Thanks W2RU.
The partner feature enables collaboration via SkookumNet for multi-operator entrants. See the Using Partner Mode item in SkookumLogger Help. Thanks GØDVJ.
Considerable effort to determine why SkookumNet sometimes fails to communicate among the local network members concluded that there is no fault in the SkookumLogger code. See the About SkookumNet item in SkookumLogger Help. Thanks JH5GHM for the initial report, and apologies that it was discovered at his WRTC 2014 operation.
GØDVJ noticed that toggling between QSO entry boxes cleared all the other fields in the new entry box when the call field was empty. After quite a bit a trial-and-error, we found that this behavior is a consequence of choosing the “Backspacing to erase call clears QSO entry fields” Wizardry option. This is an example of an unexpected and mysterious side-effect — that is why they are named Wizardry choices. As a rule, do not enable options that you do not really need for your style of operating. Then, enable them one at a time and use SkookumLogger to ensure that you haven’t created a configuration with “odd” behavior.
Each of the Generic contests has an Info field. The content of that field is now saved in the log’s internal exchange archive when you log a QSO, and is used in guessing the exchange for subsequent QSOs with the same call. Thanks WD7K.
Logic for setting the sent serial number for each QSO has been changed to ensure that the logged serial matches the transmitted serial when interleaving QSOs in the two QSO entry boxes. The logic relies on your using SkookumLogger to play a message containing the serial number token and applies for both CW and SSB. If you fail to play such a message before logging a QSO, SkookumLogger will behave as before. See “About Serial Numbers” in SkookumLogger Help.
Message labels are now editable in the Sent Exchange and Messages editor. The Messages menu displays these labels. Any message with label containing “CQ” will be recognized by the “Automatically change QSO entry box focus” SO2V Wizardry option. Thanks W2RU.
The received call token may now appear anywhere within a CW message, and may appear multiple times. However, call sign type-ahead applies only when the token is the first character in a message chain.
Disable the + and – buttons for adding and deleting items in the Buddies list when there is an active DX Cluster connection. Thanks WA1Z.
When opening the Morse Keyboard in the SO2R operating scheme, ensure that the transmit radio corresponds to the focused QSO entry box. Thanks WA1Z.
When toggling the focuses QSO entry box while a message is playing, the transmit radio no longer switches in the middle of the message. Thanks WA1Z.
When beacon CQ is active and the “Typing stops Beacon CQ” option is checked, the option is applied only when the transmit radio matches the focused QSO entry box in the SO2R operating scheme. Thanks WA1Z.
The Bump Transmit Frequency command appears in the Radio 1 menu in the SO2V operating scheme. As before, it appears in the SO2R menu in the SO2R operating scheme. Thanks JH5GHM.
The scheme for inserting spaces between chained CW messages has been revised to prevent spurious spaces surrounding the F5 messages and following the last message. The changes have also corrected re-ordering of chained messages containing the F5 message. Thanks WA1Z.
Contest rules for RSGB UKAC and 80m SSB AFS have been updated, including a drastic modification to the multipliers for UKAC which required adding a second check sheet (Other) in SkooumLogger. The Locator check sheet shows all locator multipliers; the Other check sheet shows UK locators that are now “double mults”. Thanks GØDVJ.
The choice checkbox for enabling the SO2R operating scheme is now located in the Logging preferences panel.
The Scheme menu has been renamed SO2R and is hidden when the SO2V operating scheme is enabled.
The Radio 2 menu is hidden when the SO2V operating scheme is enabled. You must use Radio 1 for this scheme; SkookumLogger ignores Radio 2.
Radio menu items that apply only for SO2R are hidden when the SO2V operating scheme is enabled. Thanks W2RU.
Logged activities are not added to activity tables in SO2R mode.
1.9.4 had a nasty bug discovered by WA1Z. The symptom was that the Messages menu failed to appear when you clicked on it. It is unlikely that most users will have encountered this bug, as it is the result of corruption of the SkookumLogger preferences file when choosing to play Message 19. Thanks WA1Z.
The invert step direction preference was broken.
Some users have had problems with their K3 radios disconnecting for no apparent reason. This version has additional logic for that radio type which watches for apparent stalls in communication with the radio and stops polling until either the stall clears or the 60-second no-response time-out occurs. Thanks W2RU and WA1Z.
Serial devices that were successfully connected and then disconnected sometimes failed to reconnect until SkookumLogger was restarted. Thanks W2RU.
Two notes have been added to the Trouble section of SkookumLogger help, describing what to do if the Sent Exchange and Messages Editor window fails to open, and why you may not be able to add entries to your Buddies list. In each case, these are misfeatures, but I’m documenting easy workarounds rather than making the code more complex.
SkookumLogger now supports 20 messages. The six new messages, numbered 15 through 20, are available only in new logs. F15 through F19 are the default shortcut keyboard assignments. As always you can use System Preferences to assign different shortcuts, but first set the Menu Titles in your Messages preferences to something more interesting than the defaults.
Bump Transmit Frequency is a new command on the Scheme menu. Its purpose is to change your run frequency by just enough to cause skimmers to spot you again. It works like this:
The bump indicators appear adjacent to the right end of the radio frequency display in the relevant QSO entry box, showing which delta is in effect so that you know what will happen next. In the SO2R scheme, the command applies to the transmit radio — the one with the red gumdrop — and the delta is remembered separately for each radio. In the SO2V scheme, the command applies to the frequency in the Run QSO entry box and is ignored when the Run box isn’t active. The delta is remembered for Radio 1.
“Stepping” changes the radio to transceive on the new frequency. The size of the step is 100 Hz.
In the SO2V scheme, if the “Automatically change QSO entry box focus” Wizardry option is checked the radio transmit frequency change will toggle keyboard focus from Run to Pounce. The workaround is to turn off that option if you want to use the Bump Transmit Transmit frequency command with the SO2V scheme. Also, unexpected behavior ensues if SPLIT is on and the two VFOs have different frequencies when you trigger the command. Workaround: do not use SPLIT while running on CW.
The yellow gumdrop indicating that arrow keys step VFO A instead of RIT was in the wrong QSO entry box for the SO2V scheme.
The awkward recent change to improve responsiveness for large logs has been removed, including the “Guess exchange from logged QSOs” and the “For logs less than xxx QSOs” options in Logging preferences. SkookumLogger now inserts exchange information into the exchange database when you log a QSO, and performs all exchange guessing by looking for the call in the exchange database. This is much faster than searching the log for QSOs with the call. As before, the external copy of your exchange database is not changed unless you choose File ► Update Exchange Database.
Each QSO entry box now has up to three gumdrops at the top left corner next to the radio mode. They are red, green, and yellow, respectively, and have help tags when you can’t remember what they mean. A red gumdrop indicates the current transmit radio. Green gumdrops indicate which radio(s) you are listening to. A yellow gumdrop indicates that the up/down arrow keys will step VFO A instead of RIT offset. These indicators apply for both the SO2V and the SO2R operating schemes.
The mode chooser in the Pass Information window has been removed. Instead, when the log’s mode category is Mixed (you set this via Log ► Settings…) each cell in the Pass window matrix has a pair of symbols for CW and SSB, left-to-right. The check symbol (✔︎) indicates worked, an x indicates needed (not worked). Thanks JH5GHM.
In activity tables, worked buddies are now shown with the Myself & Buddies color and the Worked Before font. Activity tables have a new filter choice, Buddies, which shows only activities for your buddies in the tables. Thanks GØDVJ.
SkookumLogger has a new special key command name Stop Sending. This provides an alternative to the escape key or tapping your paddle. Stop Sending also aborts DVR play. Thanks W2RU.
SkookumLogger was failing to perform important processing when navigating out of the call field. This bug was introduced in 1.9.2.
The Edit and Font menus have been removed. Thanks JH5GHM.
The “Arrow keys in Pounce fields step VFO A” option for SO2V option was stepping VFO A in the Run fields as well. Thanks W2RU.
The statistics report for the ARRL 10m contest wasn’t showing data relating to country multipliers. Thanks GØDVJ and others.
The Scheme menu now has items for controlling, via a YCCC SO2R Box, which radio you are listening to in your headphones.
In the SO2R scheme, when you start playing a message SkookumLogger first changes the transmit radio if necessary to correspond to the active QSO entry box. Thanks WA1Z.
In the SO2R scheme, setting frequency or mode by typing into a call field affects the radio for the active QSO entry box instead of the transmit radio. Thanks JH5GHM
Each Radio menu has an item for choosing whether the arrow keys step RIT offset or VFO A. These apply only for the SO2R scheme. The similar option for the SO2V scheme remains in the Wizardry/SO2V preferences tab. Thanks JH5GHM.
In the SO2R scheme, small circles ("gumdrops") are drawn at the top left corner of the Radio 1 and Radio 2 boxes. A red gumdrop indicates which radio is the transmit radio. Green gumdrops indicate which radios are listened to. The gumdrop colors match the LED indicators on the YCCC SO2R Box. Thanks JH5GHM.
In the SO2R scheme, the menu items for copying between the two QSO entry boxes are not available because it is too dangerous to set both radios to the same frequency. However, SkookumLogger does not prevent you from doing that yourself.
Serial device disconnects are reported in the Information Window and the window is opened if necessary. Thanks W2RU.
Nearly all of the pages in the Help document have been reviewed and updated.
SkookumLogger was deciding that all entrants were DX when creating a new log for the ARRL 10m contest.
A reminder: SkookumLogger no longer automatically rescores your log when you edit a Log table field. You must cause the rescan yourself using the Log ► Rebuild Checksheets function. There is no default shortcut for this menu item; I assign ⌘R.
Another reminder: If you use multiple monitors with SkookumLogger and want to preserve window positions on all screens, turn off the “Displays have separate Spaces” option in your Mission Control preferences. Otherwise, OS X gathers all open SkookumLogger windows onto the same screen as the main window; that is an OS X “feature.”
There have been many behind-the-scenes changes in SkookumLogger which have likely introduced new bugs. Please let me know if you encounter a reproducible problem.
You can control the sequence of columns visited by pressing the tab key in the Log table by dragging the column titles to rearrange the columns, then quitting and restarting SkookumLogger. Thanks JH5GHM.
If you experience too-frequent time-outs with a K3 radio, check whether or not you are using the latest production firmware in your K3. If you have a P3 between your computer and K3, also check the P3 firmware version. Thanks WW4B.
SkookumLogger now changes Alpha 87A tune settings when band changes only when the amplifier is in operate mode. Thanks W2RU.
The “Invert frequency step direction in LSB” Wizardry option now has an additional option, “Only in SSB mode”. Thanks JH5GHM.
Many changes have been made to clarify and expand SkookumLogger appearance and behavior for the two “operating schemes”, SO2V and SO2R. In the SO2V scheme, you operate with one radio, possibly with a sub-receiver. In the SO2R scheme, you operate with two radios, with the restriction that you cannot transmit at the same time with both radios.
SkookumLogger now has two Radio menus labeled Radio 1 and Radio 2, and another new menu labeled SO2R. The Radio menus are identical, but may have different items enabled depending on the capabilities of the transceivers selected in Serial preferences. SkookumLogger also now supports two amplifiers, each associated with the corresponding radio and controlled through the Radio menus.
Radio ► Save Drive Power now remembers radio power settings separately (per-band) for each transceiver type in standby mode and for each amplifier type in operate mode. Existing settings are lost; you will need to create new ones. If there is no saved power setting when Radio ► Autoset Drive Power is enabled and band or operate mode changes, 25W is set for operate and 100W is set for standby.
The SO2R menu has these commands:
There are many new menu items. They all have unique names and no shortcut keys. You can use Keyboard System preferences to define shortcuts for the commands you use frequently. Most existing menu item names and shortcuts have not been changed.
The items in the SO2R preferences pane have been moved to the Wizardry preferences pane, and the SO2R pane has been deleted. The Wizardry preferences pane now has three tabs. The General tab has options that apply in both operating schemes, while the SO2V and SO2R tabs have options that apply only for their respective schemes.
An unusual combination of the hide signal report entry field options was preventing navigation out of the call field with the space-bar.
The source call for activities created internally is now always the current operator call. Previously it was sometimes the call for the sent exchange. Thanks W2RU.