Log4OM

VE3EY

I'd like to join the 'me too' bandwagon. I went on to install latest MariaDB on a new Ubuntu server last night and ran into this problem. Server version: 10.6.16-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04 (current - working) Server version: 10.11.6-MariaDB-0ubuntu0.23.10.2 Ubuntu 23.10 (new) I was scratc...

VE3EY

Thank you Nolan. This feature ties into a feature request i submitted earlier. When a DXpedition is active simultaneously on number of bands and modes, this feature helps find out where they are currently active. Without the callsign filter, the high volume of spots makes it impossible to track cert...

VE3EY

Hi Nolan.
I am not sure what 'Show cluster grouped [recommended]' option is meant for, but after I unchecked it, callsign filter is now working. I think this feature is great and thank you to LOG4OM author for incorporating it. Thanks for pointing this out Nolan
73

VE3EY

There is a new feature in latest beta called "Callsign filter" which imho is very useful. For example, 4U1UN callsign filter will filter/display when entered in the callsign filter 2023-05-26 15_15_23-LOG4OM 2 v.2.27.1.10 [Profile_ New config].jpg But there seems to be some issues with the...

VE3EY

Thanks Terry and I appreciate your feedback. This is what I am kind of doing today but instead of LOG4OMs Cluster Management window, I use DXLog telnet client. It works but it is kludgy and it involves some clicking and typing commands around. The hope was for a simplistic approach of doing the same...

VE3EY

Thanks Slav but I can't see how this will help. I am using Alerts myself but it serves a different purpose IMHO.

Basically what I was looking for is that last 10 (or so) spots are listed for any call which is entered in the QSO entry window.

Regards.

VE3EY

This mostly pertains mega DX expeditions where DX is simultaneously active on a number of different bands and modes but their DX spots get mixed up with others and are hard to find. Presently I can't find a way to easily figure this part out from within LOG4OM. I end up producing this output such as...

VE3EY

Thanks Nolan. Appreciate your response. While I did not mention this in my original post, this attempt was actually made from within QSO manager. I guess I can try deleting contact in batches of 100 QSOs maybe? Edit: I did select all 1400 QSO's with select/deselect button. The rows pending deletion ...

VE3EY

Log4OM v.2.26.0.0 I need to delete about 1400 QSOs which I have inadvertently imported via ADIF import. Basically they are duplicates. I normally unlock the yellow padlock and hit delete button when deleting smaller number of contacts from the log, but in this case, delete key does not seem to work ...

VE3EY

Hello LOG4OM2 2.25.00 on Windows 10. I have several station callsigns within one single log, but all contacts count for one single DXCC award program. I have a discrepancy for granted credits totals between LOTW and LOG4OM (Award status - statistics). I went on to manually assign the missing granted...

Search found 11 matches

Re: MariaDB configuration problems

Re: Feedback on v2.27.1.10 beta (May 25, 2023 release)

Re: Feedback on v2.27.1.10 beta (May 25, 2023 release)

Feedback on v2.27.1.10 beta (May 25, 2023 release)

Re: DX spots

Re: DX spots

DX spots

Re: Deleting 1400 QSOs

Deleting 1400 QSOs

Multiple station calls and lotw credits