When using Statistics and awards and you right-click any validated entry other than a credit granted one you don't get the entry you click but always get the credit granted QSO.

de Mike W9MDB

Perhaps there's a regex parse gong on that fails with the suffix?

Mike

The data source is dxc.w3lpl.net:7373 I have a local filtering utility that passes it through and I've temporarily fixed it by removing the suffixes myself. You just need a CW Skimmer source so you can see calls with the suffixes that CW Skimmer can put in there. I haven't checked all signs with reg...

I think I found a bug in the cluster window Seems any spots where there is a suffix on the spotter aren't being seen. As you can see in the attached there are spots from W2NT-2, W1NT-6 and KU7T-2. None of which show up in the cluster window There are 11 spots received at 2325 but only 7 show up with...

This should be a relatively simple fix. The suffix on spot reporters is being truncated in the cluster window in Log4OM. For example.... W1NT-6 shows up as W1NT. ARCluster software does not understand suffixes at all so W1NT-6 gets put in CQ Zone 3 due to the W1 and Log4OM removes the suffix so we c...

Using 1.40.0.0

I've got "Use clublog..", "use Special...", and "Realtime Lookup..." checked.

TX7T is in clublog.xml correctly.

Unchecked are "Fill data..." and "Realtime previous..."

Turning on debug to max I see this

TX7T does not show up correctly here. I've updated all the databases and restarted Log4OM. I also tried logging it (from WSJT-X) and it does get inserted correctly as JTAlert does the DXCC lookup...but still the F2 tab in Log4OM shows Clipperton. I tested with a friend and his shows correctly on the...

In V2 the caching will solve most of the problem. The other problem besides being slow is the constant updating that takes places when hooked to one of the CW Skimmer cluster sites. They come in so often as to make clicking on anything impossible. So that's why I have my queueing program just dumpin...

I've seen this error a few times in the last couple of weeks. I've seen this in my own code using a "foreach" statement on a list and modifying the list inside of it. You have to use an ".Items" to get a copy of the list to work with. See the end of this message for details on invoking just-in-time ...

But why do we care about prefix/suffix? Seems we should have an option to turn this off so the query can be done with "=" instead of LIKE as I don't care about matching prefixes/suffixes. There's no database I know of that does anything but a full scan for LIKE selections. No way to index it unless ...