Thanks for reporting. Fixed in next release

For ease of use, Log4OM never displays MODE / SUBMODE in your QSO Data. It's purely matter of ADIF, and ADIF is an interchange format, nothing else. Instead, Log4OM use an internal set of modes, each mode is then described also as MODE/SUBMODE in ADIF concept, to be able to export and import back da...

I got it. Steps to reproduce: Reduce log4om as icon log a QSO from JTAlert log another QSO from JTAlert the first will be visible, the second no, and still not visible after refresh. The QSO is visible from other screens. It's some kind of concurrency, i'm still trying to understand why that happens...

iw3hmh (at) log4om.com
Thanks

Hi Chris, what logging method are you using?
DIrect? message 12? jtAlert?

My top priority is to address this issue. Unfortunately it doesn't happens on my system so it's really hard to catch. It's probably a resource lock due to concurrency somewhere in the user interface as all background thread works flawlessy. If you can often reproduce the issue we can give you a test...

SQ5TDZ wrote: ↑

11 Jun 2020, 08:22

hello Daniel
could it be done so that the information about the sign in the band map window was also colored like in the cluster window ?

you mean the background of the callsign for the "worked before"?

What happens here. QSO data retrieved from intarnal and external sources are related to some parameters. Callsign (that identifies the country) QSO Date (that collaborate into country identification and award / award reference valid date range) Band and mode (that are considered for awards preselect...

Hi Steven,
that's something i would like to have too.
Unfortunately space on the main UI is not so abundant, so i think i should add this as an alternative to the band map tool (maybe in a tab control)

i'm working on it