I’ve started calling this UMRLog.
For now, it’s Icom only. I’m trying to simplify some of the controls and tailor it for contest logging, like field day. Maybe POTA.
Lou suggested some messaging, or log combining across the network. This would require the first instance to be the master, and might have some issues if the network barfs. Maybe later on that. messaging requires a “server”.
Anyway, as I’ve been tweaking the code, Gemini seems to want to totally change the aesthetic of the site AND breaks functionality a lot. I hit a roadblock with some of the logging features I wanted to add. On a whim, I threw the code at ChatGPT and told it what to fix. It executed flawlessly. I may be able to get something more in lines of what I had envisioned in the first place…
As I said, I’ve been doing some tweaking… added a whole host of things:
- Expandable / collapsable sections
- Added a multiplier tracker, and the ability to import a single column CSV of multipliers (ARRL sections, counties, countries, etc.). These are auto-parsed from the “Their Exchange” section
- Beefed up contest logging:
- Added the ability to increment a serial number, if your exchange has a number in it
- Don’t clear “My exchange” upon log entry
- Tab order modified (Callsign->Their Exchange -> all the others)
- Hitting Enter in “Their exchange” logs the QSO, and puts focus back on the callsign field
- Auto-enter 59 / 599 for exchanges when you don’t enter anything
- Fixed Cabrillo export.
One downside to the multipliers is that it won’t parse the log file for previously entered multipliers if you import it mid-contest.
I still have a lengthy to-do list… while this is a proof of concept, I kind of want to see how far I can take it.
- Click on a previous log entry to bring it up for editing / correcting (and delete?)(
- Correct where the Cabrillo export gets the file name callsign (it currently needs something entered in the logbook callsign field, and that’s a hassle)
- remove the “Filter” function (not something that will be used often)
- remove the memory function (just not something I see much use for… )
- Unsure on the VFO buttons… might remove those, too
- Allow export of the serial log
- Verify that [SRL] [other text] is the most complex exchange, so the serialization will work properly
- DVR should be hidden for radios that do not have that function
Limited dupe checking- maybe just indicators of “this contest” and “this contest AND this band”. Remember, I’m not rewriting N1MM or CQRLog…
Just as an indication of how quickly this is coming together, the next morning after initially writing this post, I decided to add live dupe checking. Within 10 minutes, ChatGPT had generated the code patches I needed for the desired functionality. The look was close to what I wanted, but the functionality was dead on.
And I STILL need to test it for the 705 and others….
Progress on the project is pretty quick, so I gave it a page of its own, rather than keep blogging about minor updates. More updates, and more recent versions of the page are HERE: UMRLog