Log4OM

Back to the initial subject:

The only way to resolve this to a large extent, which Daniele would no doubt not like, would be in the cluster for every U.S. call the program would query QRZ or HamQTH to get the current location. This is not fool proof as it relies on the station to have the correct data on the remote servers.

In the case of the HK0/N7UN, there is no QRZ data available. And, without asking N7UN, you would not know from his HK0 call if he was on HK0M or HK0S.

you are right; the file editng could not be a good approach

Editing a local table with a simple interface (in expert mode) could introduce the neede flexibility

Hi Don, you can edit every file in Log4Om configuration, included country definitions.
There is not a SINGLE configuration file that is not user-editable now and in future (except config.xml that stores your password and is simply encrypted in base64 to avoid tampering, even if this file is convertible back to plain text).

Tampering with country file is, as said, possible but will put your log outside of the normal update flow, that on country file is made almost weekly, so not recommended at all.

About the proposal to poll qrz/hamqth on every single call that appears on cluster the answer is, of course, no.

I will evaluate the possibility to create an user file with "static" countries (not an SCL file) where an user can add <callsign>;<dxcc> and have this written on the rock in the software. We will not mantain this file, that will be entirely on the final user side to manage beacons and other static situations.

Lele
Shall I add to Mantis?

Thanks Lele. All I can say is hurrah for

I will evaluate the possibility to create an user file with "static" countries (not an SCL file) where an user can add <callsign>;<dxcc> and have this written on the rock in the software. We will not mantain this file, that will be entirely on the final user side to manage beacons and other static situations.

Yes please Terry, add to Mantis, i will work on in a next release