Exact vs. Partial match in Previously worked table
Exact vs. Partial match in Previously worked table
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.
Best wishes,
Ted Szypulski
K2GAV
Kenwood TS-990, Elecraft KPA-1500
Ted Szypulski
K2GAV
Kenwood TS-990, Elecraft KPA-1500
- G4POP
- Log4OM Alpha Team
- Posts: 10808
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Exact vs. Partial match in Previously worked table
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?
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?
73 Terry G4POP
Re: Exact vs. Partial match in Previously worked table
I'd like to choose if I want to see that, or to NOT see K7PTX when I'm currently talking to K7PT.
Best wishes,
Ted Szypulski
K2GAV
Kenwood TS-990, Elecraft KPA-1500
Ted Szypulski
K2GAV
Kenwood TS-990, Elecraft KPA-1500
Re: Exact vs. Partial match in Previously worked table
Any news about this question? Especially for short callsigns I often get several useless hits in F8:
An exact match option would be very helpful.73 Olaf DK2LO
Re: Exact vs. Partial match in Previously worked table
I also think it would be a very good addition, as an option.
73,
Jim N6VH
73,
Jim N6VH
Re: Exact vs. Partial match in Previously worked table
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.
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.
73 Olaf DK2LO
Re: Exact vs. Partial match in Previously worked table
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?
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?
73 Olaf DK2LO