Log4OM

See below - I was working N7ML (4 character call) but the list also shows N7MLR (5 character call) . Charlie
W4EBB

Not an error, that´s the way how the worked before option is working. If you type in N7M you will
have the same result.

DF5WW wrote: 13 Dec 2021, 15:12 Not an error, that´s the way how the worked before option is working. If you type in N7M you will
have the same result.

Hi Jurgen
They are point of view, but I think it would be more correct for the listing, to refer only and only to the exact call, and not a kind of "wildcard" N7M*, for me it doesn't make sense but they are points of view.
We have to learn to live with what we have...

I will opt for a "more correct" list, especially since it would be easy to fix. And having another call sign when I want to see if I worked someone before serves absolutely NO purpose.

Charlie
W4EBB

I would also vote to search only for the full call in the "Worked Before" list.

Wait until the user hits the tab key or moves the focus to another area of the QSO entry page before trying to fill in the QRZ.com data and search the log for the same (not just similar) call.

73,
Larry N1FG

Larry,

I agree. I think both of your suggestions would be very useful. For those that want to see more calls, perhaps searching using a wild card such as * would be good.

73,

Jim N6VH

Hi,
the "main" problem is the callsign may be "hidden" in something different.
If you search N7ML it will show you N7MLR, and this is obviously not the same callsign, but applying a "strict" search on the callsign will show you "N7ML" (and that's possible), but will keep out all variations on the callsign, like:
N7ML/P
I3/N7ML
N7ML/QRP
and so on. Changing that is pretty easy, but a common solution will often not make everyone happy.
On this situation we decided to keep the filter "wide" letting the user reading and applying a personal filter on the result set (that is usually made by few contacts)

I can see your reasoning, but if it is a simple change is it possible to add this to a configuration that would allow each user to set either "strict" or "almost" selection criteria?

I think it also would save a great deal of effort (program wise) to wait until the user has finished the callsign entry before you do anything as to searching the log.

Just one users opinion of course, and I appreciate the work you (and the team) have done and continue to do.

73 and Merry Christmas!

Larry N1FG

Lele:
I could go for the strict/not strict option as a compromise.
Thanks
Charlie
W4EBB