v1.85.4 Bug Fix Release and History File Refresh #451
w7sst
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
This release fixes several quality and behavior issues, including improvements to wildcard (
?) handling. Several Call History files have been updated. See the full list of resolved issues below.Installation
Download the
Morse.Runner.1.85.4.zipfile (also available in the Assets section below), Open the zip file, extract the folder to your DESKTOP, and runMorseRunner.exewithin this folder. Do not add these files to a previous release folder, or place in a windows program directory as this causes errors. You can safely copy yourMorseRunner.inifile from your previous install directory into the new install directory. After installing, read theReadme.txtfile for more information.Join our Community
You are invited to join our community effort. For more information, please visit the Morse Runner Community Edition project.
Our goal is to create a program you love to use, so please help by leaving any feedback you would like to share on our Announcements page or our GitHub discussions page.
Additionally, you can discuss or leave feedback at MorseRunnerCE on groups.io.
You have several ways to join in on our project and we look forward to hearing your ideas.
Release Details
Version 1.85.4 (May 2026)
General bug fixes and improvements...
Contest-Specific Improvements
General
Improve
?handling - exchange is no longer sent with partial callsignsEntering a
?after a partial callsign and pressing Enter now sends only the callsign with?. The user's exchange is no longer sent in this case, aligning with standard contesting practice of sending the exchange only after the full callsign is copied.Morse Runner suppresses the exchange whenever a
?is present in the callsign field.As an alternative, operators can use the F5 key (
HisCall) to send the copied portion of the callsign and prompt a repeat. Once the full callsign is entered, pressing Enter sends both the callsign and exchange.What's Changed
Full Changelog: v1.85.3...v1.85.4
This discussion was created from the release v1.85.4 Bug Fix Release and History File Refresh.
All reactions