Invalid lookup

[N6KZB]

It is not giving the exact match, JUST FYI

Annotation 2020-03-12 070809.jpg (50.73 KiB) Viewed 5630 times

[KI5IO]

It is not giving the exact match, JUST FYI


Annotation 2020-03-12 070809.jpg

Mike,

It is working as designed. It does lookups a character at a time. How fast one is with keyboard entry can also affect this search/display.

[KD0ZV]

Not to mention its helpful in searching based on any part.

So if you are trying to look someone up based on their suffix you can. I have had to do that before because I could not remember anything but their call district and suffix.

[N6KZB]

Thanks for the responses.
It is when you enter a call that you have started a QSO with, and then hit "worked before", then this:

Annotation 2020-03-14 075025.jpg (55 KiB) Viewed 5558 times

And yes it does it in a search also. Just wanted to pass along to the software team. Minor issue in the scheme of things, since the LoTw is the greatest. Adios

[KI5IO]

Thanks for the responses.
It is when you enter a call that you have started a QSO with, and then hit "worked before", then this:

Annotation 2020-03-14 075025.jpg

And yes it does it in a search also. Just wanted to pass along to the software team. Minor issue in the scheme of things, since the LoTw is the greatest. Adios

Mike,

The program is working as designed for the call-sign display. Now you seem to have a "typo" for that additional call ??

[N6KZB]

No, not a typo, two different calls.
But thanks anyway.

Adios

[N6KZB]

Any thoughts to a fix on this?
This is not the same call.
I can see if it was xxxxx/xx, a call with a suffix, such a /mm or /xe2.

Thanks....

[KD0ZV]

Any thoughts to a fix on this?

Its not broke.

Its working as designed.

The only thing they could add is a checkbox for verbatim where it would show only that call.

[N6KZB]

That would do it, give the user the ability to each EXACT match or not.

Frustrating to go to search and see other calls mixed in.

Good thought OM.