Running CQRLOG 0.9.3 on Debian SID and stable:
I tried to correct the "MY Locator" field in the database so it does match the locator of my used profile by using the Group Edit function.
Creating the filter by using the profile was no problem, also running the Group edit on the selected entries works fine but running my usual QSL Card selection I noticed only 2 QSL cards selected...
The reason was simply that I used a mix of Upper and lower case letters in the group Edit function to set the new loactor ( == JN48jv ) but the filter does only look for "My Locator" in only UPPER case format (== JN48JV) and I found no way to enter any lower case letters in the input box of the filter.
No way to select the lower case datasets to correct the problem :) (but the "profile" so this time no big problem for me..)
So the problem seems to be that you may chance at least the "My Locator" field running the Group Edit to a format that the selection function does not expect or allow to enter. This may end up in datasets that can't be selected any more other than running the SQL console.
73 de Olaf / DL5YBZ
Hi Olaf,
thank you for bug report, I just fixed it. Now locator, my own locator and other upper case fields are stored corectly.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Petr,
again tnx for your fast fix, it is a real pleasure to see CQRLOG getting better and better!
73 de Olaf / DL5YBZ
There is still a bug related to this in 2.3.0 (001) Maidenhead Grid Locators have the 5th and 6th characters as lower case:
https://en.wikipedia.org/wiki/Maidenhead_Locator_System
When you set up a filter that contains a 6 digit grid, the CQRLOG program forces your text to be all caps, however it searches the database in a case sensitive manner. So if you filter for DM03UT, it will not find DM03ut.
I am not on the beta, so I don't know if this has been fixed already.
I already used the group edit to change my locators to all caps, but this bug should be fixed.
73,
KK6KC
Kirk Crawford
KK6KC
Lomita, CA, USA
Hi!
Writing locator is quite "wild". Many sources are using "all caps", just try with google search.
Even my boats navigator (Garmin) uses "all caps" for displaying locators.
And because of that both low and upper case should work. But of course program can do internal conversion to up/up/nr/nr/low/low before handling and storing locators.
Thanks for reporting.
It would be nice if bug reports could be directly written to GitHub/Issues to remind programmers, but unfortunately that needs a GitHub account.
I'll add that to https://github.com/ok2cqr/cqrlog/issues as reminder not to forget this issue.
--
Saku
OH1KH