Log4OM

w9mdb

Thanks for fixing the window location after upgrade. Just two more known problems on my list. #1 cluster Alert sound/email still going out even when cluster filter has filtered it out (e.g CW alert when CW is filtered). #2 Hamlib settings lost at random times....cannot repeat this easily but happens...

w9mdb

I have two different configurations in Log4OM.

The cluster filters are common to both instead of being separated.

I want them separated.

w9mdb

This has been a long-standing problem.
On every upgrade the window position is reset.
Reinstalling the same version does NOT lose the window position...only an upgrade.

w9mdb

What we want is for the cluster config to be save by configuration selection -- not just generic "user". Maybe just change the "user" part of the file name to the configuration value?
So we can have different filters in different configs.

w9mdb

Got an audio and email alert for a CW cluster spot (new country) A52A even though the CW filter is unchecked -- digital and phone were checked.
It seems the audio and email alerts for CW are still going out even though they should not with CW unchecked.
Using version 2.26.0.6

w9mdb

LAYOUT_CLUSTER_MAIN_USER.JSON

Seems that we would want this to be by configuration and not generic to all configs.
Isn't the main reason for configs to be by user? Or is there some reason a different config would always want to use the other config's settings?

w9mdb

If anybody is doing anything other than FT8 on that frequency range they are nuts. And it's my bandplan I want to modify (user customized one if you're not familiar) and not necessarily updating the default ones. Although I would maintain that as of today the FT8 bands for the appropriate ranges (e....

w9mdb

Been trying to get FT8 spots (would also apply to FT4) on the standard frequencies to show "Spot Mode" of FT8 instead of a blank. If FT8 is in the comment field it gets put into the Spot Mode. But if, for example, a spot on 14074 comes in without a comment Spot Mode shows blank. Goal here ...

w9mdb

JTAlert instructions in the manual are incomplete and inaccurate.

Step #5 talks bout turning on "Resend WSJT-X" which is not needed.

And it does not show the needed Connection for the port 2235 ADIF message from JTAlert.

w9mdb

Yes...that was it...I had TRACE as the default logging level since I tend to keep that running to trap any problems.

Search found 310 matches

Re: Window location lost during upgrade

Re: LAYOUT_CLUSTER by configuration

Window location lost during upgrade

Re: LAYOUT_CLUSTER by configuration

Cluster filter ignored for audio/email alerts

LAYOUT_CLUSTER by configuration

Re: FT8/FT4 spots

FT8/FT4 spots

JTAlert Setup Update

Re: Unique Key