Page 1 of 1
LAYOUT_CLUSTER by configuration
Posted: 19 Mar 2023, 16:58
by 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?
Re: LAYOUT_CLUSTER by configuration
Posted: 21 Mar 2023, 22:04
by IW3HMH
Log4om contains for each grid (main QSO, main UI cluster, and so on) a specific DEFAULT configuration (the non _user version) if any.
When user changes something or on first program closing the CURRENT user configuration is saved here.
If user removes his personalized configuration the default will be used, if any (if not, all fields for the specific grid will be shown)
Re: LAYOUT_CLUSTER by configuration
Posted: 21 Mar 2023, 22:22
by 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.
Re: LAYOUT_CLUSTER by configuration
Posted: 24 Mar 2023, 15:50
by IW3HMH
Sorry mike, can't get the point...
every cluster screen, in main screen, detached, cw and so on has it's own persisting grid config and parameters...
i'm missing what you need

Re: LAYOUT_CLUSTER by configuration
Posted: 24 Mar 2023, 15:59
by w9mdb
I have two different configurations in Log4OM.
The cluster filters are common to both instead of being separated.
I want them separated.