4/5/24 I have listed below a few suggestions to consider for an updated release of the logger…
Auto-populate “Their QTH” field from call lookup source, when adding new records…
Remember last “mode” used so it will pre-fill next entry unless changed…(No need to re-type the same thng as last itme for each new entry)
Add “Refresh” button to top near “Clear” or on top right side to immediately show log changes done during editing… (without going out of the logger & returning …
Add pull-down menu for “Preferences” for settng up pre-defined log data fields, headings, columns, etc… major upgrade?? optonal??
Been using this logger daily and you guys are doing a great job …73’s Dave, k3dgr
We are following you here a lot and we love your suggestions, thank you so much! I have a few quick followup questions for you here if you don’t mind!
1. Auto-populate “Their QTH” field from call lookup source, when adding new records…
What do you want it to populate to? We were thinking to use this field soon for some POTA updates to enter the park. 2. Remember last “mode” used so it will pre-fill next entry unless changed…(No need to re-type the same thng as last itme for each new entry)
Great suggestion - right now we pick up the mode based on logic with the frequency. We can add this too. 3. Add “Refresh” button to top near “Clear” or on top right side to immediately show log changes done during editing… (without going out of the logger & returning …
I didn’t understand which log changes you aren’t seeing, maybe it is a bug? If you log a contact, the logged contact should appear immediately below in the Entries. 4. Add pull-down menu for “Preferences” for settng up pre-defined log data fields, headings, columns, etc… major upgrade?? optonal??
This is coming soon! I estimate about 2 weeks. We are calling it Logbook Settings. You will have the ability to predefine a Logbook Template, Location, and other settings.
Thank you so much for your help and for being an early believer in our product, we are working around the clock to make sure this is a great experience!
JIm, Thanks so much for the quick reply…I use this log daily for my main one and update xlog and CQRlogger in Linux on my office machines and I use it daily to start my day… Thanks again for all the hard work your guys are doing…Looks great …73’s Dave
Andrew… Sure it’s where the station is located, their town, etc… My QTH is PHilipsburg,Pa and grid locator FN00vv to pin-point the QTH… The ARRL and others havepublished a list of all “Q” signals that are used by most all hams and you can probably just Google to find the list. For Example: from "Ham Radio Academy’’ … [https://hamradioacademy.com/resources/q-signals-q-codes/]
Some of the “Q” signals are used dail;y but WRL wants you to use the "stations Town or location.in the logger…
Hope this helps out a bit…
cheers, Dave,k3dgr
Absolutely! Maybe the reason I wasn’t clear on how the field was to be used is because it doesn’t auto-populate. I assumed it would be for home QTH city, POTA park, or something like that, but it wasn’t completely clear what the intended use was. It was probably meant to be left up to user discretion, however, it would make sense to either auto-populate based off of the Gridsquare field, or be repurposed for something like a POTA or SOTA reference. Then again, the latter may not be needed with the upcoming release of templates.
Andrew… yes, I have already mentioned a few things to be done with the logger as I use it daily… and have them listed under my suggestions before to Jim… Thanks for mentioning it again…
