search of short callsign

[TecnoTalarn]

Hello, I have detected a problem with the live search
IF the callsign is short, for example 7Q1, it does not find it in the list if I make a new contact.
It seems to expect longer callsigns, 4 characters or more... In normal conditions it is sufficient, but in contests or DXpeditions they may have shorter callsigns.

If I search for the contact in the database, it does appear.

[aa5sh]

That's weird I just entered K2P for a station I worked yesterday and it did seem to work. It looks like the code is written to be 3 or more characters.

[foldynl]

As @aa5sh mentioned, QLog searches for callsigns that are three or more characters long. It's important to note that it searches for valid callsigns. Unfortunately, I don't know which authority issued this callsign, but it is not a valid callsign—it's only a prefix. The suffix is missing. Since it's not a valid callsign, QLog skips the search.

If there will be more such "anomalies", I will try to change it. At this moment I leave it unchanged.

[kyleboyle]

Isn't 7Q* assigned to Malawi so 7Q is the prefix and 1 is the suffix

[foldynl]

in this case, 1 is number separates prefix and suffix. The suffix is defined as character string (source: https://en.wikipedia.org/wiki/Amateur_radio_call_signs). If you have batter source, please, could you share it ?

[kyleboyle]

I see what you mean now. the issuing authority isn't following the rule

[foldynl]

If more such anomalies (invalid callsigns) occur in the future, I will fix them.

Unfortunately, it's not just a matter of fixing one regex for callsigns, but a revision of the QLog, as I'm not sure where else it might cause problems.

[TecnoTalarn]

On this topic
with a longer callsign it also happens, when I send it from WSjtx, it does not search, although in the station statistics the callsign and the bands worked do appear.
If I enter it manually it appears correctly at the top.