Page 1 of 1
Exact vs. Partial match in Previously worked table
Posted: 12 Aug 2020, 12:14
by K2GAV
I suggest a choice of Exact match or Partial match when looking up stations previously worked via the button in the new entry area, or via the F10 key.
Re: Exact vs. Partial match in Previously worked table
Posted: 29 Aug 2020, 14:26
by G4POP
So you dont want to see when you worked K7PT and he was...............
K7PT/P in New York
G/K7PT in the UK
K7PT/MM when he was rounding Cape Horn
G/K7PT/M while driving across the UK?
You just want to see K7PT in Phoenix?
Re: Exact vs. Partial match in Previously worked table
Posted: 31 Aug 2020, 15:33
by K2GAV
I'd like to choose if I want to see that, or to NOT see K7PTX when I'm currently talking to K7PT.
Re: Exact vs. Partial match in Previously worked table
Posted: 05 Sep 2020, 21:45
by VK7XX
K2GAV wrote: 31 Aug 2020, 15:33
I'd like to choose if I want to see that, or to NOT see K7PTX when I'm currently talking to K7PT.
I like this one.. add me to the "yes please" list
John
Re: Exact vs. Partial match in Previously worked table
Posted: 07 Jul 2021, 07:20
by dk2lo
Any news about this question? Especially for short callsigns I often get several useless hits in F8:
- WKDB4.jpg (241.51 KiB) Viewed 9274 times
An exact match option would be very helpful.
Re: Exact vs. Partial match in Previously worked table
Posted: 09 Jul 2021, 00:49
by N6VH
I also think it would be a very good addition, as an option.
73,
Jim N6VH
Re: Exact vs. Partial match in Previously worked table
Posted: 21 May 2022, 14:36
by dk2lo
Any news?
I just realized that WKDBANDMODE gives wrong result: I have not worked ZA/G4PVM on 10m CW. F10 confirms that. Result of WKDBANDMODE is probably wrong because I have worked G4PVM on 10m CW.
- ZA G4PVM-WKDBANDMODE.jpg (177 KiB) Viewed 7966 times
- G4PVM.jpg (108.87 KiB) Viewed 7966 times
Re: Exact vs. Partial match in Previously worked table
Posted: 04 Feb 2024, 12:52
by dk2lo
Any news on this subject?
If I have worked a CALL LOG4OM will tell me that I have worked P5/CALL already which is definetely wrong. So if I would rely on LOG4OM I will loose these contacts with P5 - not good.
This behaviour is a main weakness of LOG4OM and an option for "Exact match" would be a solution.
Any chance to get this option in a future release?
Re: Exact vs. Partial match in Previously worked table
Posted: 14 Sep 2024, 14:11
by K2GAV
It looks like more than just I like the idea of choosing either Partial or Exact matching in Worked Before windows.
I hope it can be implemented in a future update. It's been over four years since it was suggested.
Thanks for all the great work to the Log4OM crew. It's a great logging program.
Ted
K2GAV
Re: Exact vs. Partial match in Previously worked table
Posted: 20 Sep 2024, 07:18
by dk2lo
By doing a search for "exact match" in the forum you will find that the desire for an "exact match" option is much older. Already on 20 September 2013 G3XOV asked this under the topic "QSO Information". This feature request came up again and again by several users through the following years.
It would be a great improvement of LOG4OM if this feature will be considered. I am sure there is a big desire to get an "exact match " option.
Thank you for the best logging software available but with the potential for enhancement.