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 ...
Search found 122 matches
- 20 Sep 2024, 07:18
- Forum: Feature suggestions
- Topic: Exact vs. Partial match in Previously worked table
- Replies: 9
- Views: 11002
- 13 Jun 2024, 08:49
- Forum: Feature suggestions
- Topic: "ESC" key behaviour in Keyer interface
- Replies: 3
- Views: 12512
Re: "ESC" key behaviour in Keyer interface
Any news?
I suffer from the same problem. "ESC" should only stop TXing but should not delete the Call of my QSO partner.
Please change the current "ESC" misbehaviour.
I suffer from the same problem. "ESC" should only stop TXing but should not delete the Call of my QSO partner.
Please change the current "ESC" misbehaviour.
- 08 May 2024, 07:47
- Forum: Feature suggestions
- Topic: Allow free-form RST in CW mode?
- Replies: 28
- Views: 17027
Re: Allow free-form RST in CW mode?
Thank you for this option available from
Good to see that LOG4OM is getting better and better.
So I was able to log my recent Aurora QSOs with a report adding the A suffix - perfect!Good to see that LOG4OM is getting better and better.
- 04 Feb 2024, 12:52
- Forum: Feature suggestions
- Topic: Exact vs. Partial match in Previously worked table
- Replies: 9
- Views: 11002
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 ...
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 ...
- 04 Feb 2024, 12:37
- Forum: Error reports
- Topic: Winkeyer Paddle not working correctly
- Replies: 8
- Views: 6694
Re: Winkeyer Paddle not working correctly
Just testing LOG4OM 2.31.0.0 and I found that the paddle with my microham CW keyer works now without stuttering. Also the "CLEAR BUFFER" message in the Winkeyer communication log does not show up any more.
Thank you for solving this issue!
Thank you for solving this issue!
- 21 May 2022, 14:36
- Forum: Feature suggestions
- Topic: Exact vs. Partial match in Previously worked table
- Replies: 9
- Views: 11002
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.
- 03 Jan 2022, 16:38
- Forum: Error reports
- Topic: Winkeyer Paddle not working correctly
- Replies: 8
- Views: 6694
Re: Winkeyer Paddle not working correctly
Hi Terry,
sorry I am disappointed that it is refused to take care of such an essential problem which concerns several users not able to use paddles with the winkeyer interface.
For me it is not an acceptable solution to replace the microham hardware which is working fine with other programs.
Most ...
sorry I am disappointed that it is refused to take care of such an essential problem which concerns several users not able to use paddles with the winkeyer interface.
For me it is not an acceptable solution to replace the microham hardware which is working fine with other programs.
Most ...
- 30 Dec 2021, 12:12
- Forum: Error reports
- Topic: Winkeyer Paddle not working correctly
- Replies: 8
- Views: 6694
Re: Winkeyer Paddle not working correctly
Hi Terry,
this problem was already reported as "WINKEYER BEHAVIOUR" at 13th June 2019 by K0HB and was confirmed by others.
I also was Beta tester for LOG4OM but it is sad if my support is not welcomed any more.
this problem was already reported as "WINKEYER BEHAVIOUR" at 13th June 2019 by K0HB and was confirmed by others.
I also was Beta tester for LOG4OM but it is sad if my support is not welcomed any more.
- 30 Dec 2021, 11:33
- Forum: Error reports
- Topic: Winkeyer Paddle not working correctly
- Replies: 8
- Views: 6694
Re: Winkeyer Paddle not working correctly
Unfortunately I never received a reply. Paddle works with several other logging programs as described before. I recently also tested Swisslog successfully.
With LOG4OM the Winkeyer Communication Log shows "CLEAR BUFFER" message always when the problem happens with LOG4OM Winkeyer option and Paddles ...
With LOG4OM the Winkeyer Communication Log shows "CLEAR BUFFER" message always when the problem happens with LOG4OM Winkeyer option and Paddles ...
- 08 Jul 2021, 13:14
- Forum: Error reports
- Topic: ESC no longer aborts transmission in Winkeyer window?
- Replies: 11
- Views: 5996
Re: ESC no longer aborts transmission in Winkeyer window?
Terry,
I used Help-User Guide-English (force update) and got the result above. After doing it again I received your version. So something was wrong with my first upgrade.
Nevertheless I would like the old ESC-key behaviour.
I used Help-User Guide-English (force update) and got the result above. After doing it again I received your version. So something was wrong with my first upgrade.
Nevertheless I would like the old ESC-key behaviour.