Message 12 is part of the JT messages. It contains the latest QSO saved. If you set Log4OM to MONITOR a JT provider instead of an ADIF provider the application will continuously try to read JT messages as ADIF strings, that is not correct. If you want to use "message 12" in the JT protocol you shoul...

There is a flaw that may occasionally lock down the user interface in V2 since 2.7, or lock only the main grid.
We fixed the second one while we fixed almost 99% of occurrences of lock for the whole program.
We will release soon

If you can provide me a list of valid sats with those columns it would be great. Please use this format if possible: Displayed name ADIF value Tx freq in khz Rx freq in khz mode TX mode RX Separated by ; So name should be "AO-7 U/v" or similar Btw in Log4OM I don't have possibility to save different...

Anyway, changing the default value is not so complex. I will change it to the default value set for confirmations. If someone was used with SEND will eventually file a complaint and we add an option to allow users what value should be selected as default when opening QSL manager and selecting LOTW (...

but i need multiple queries and in-memory double list scroll to match data and fill the QSO class with their own data.
Much slower than a json serialization made once, in memory

That's strange.
the file i'm distributing with Log4OM has those indexes (PK is index):

PRIMARY KEY (
band,
callsign,
mode,
qsodate
)

There is still wide space for optimizations. Actually Log4OM relies on some inner structures (json) filled into text fields, and performs unboxing in memory. That give us flexibility to add more external services in the future simply adding an enumeration into a class, without needs to work on DB si...

Please define "extremely slow query" and the number of QSO in your log.

I know that and it's a design choice. There are 3 ways to store confirmations (and other data structures). 1) store into a JSON structure will allow me to add future services without changing the database structure. It's a bit slower but everything else is performed in memory. Single access to datab...

Thanks for reporting. Fixed in next release