Closed tsawyer closed 3 months ago
Aside from that, this looks like a boolean setting, in which case I think it should be configured as "yes" or "no", not "1" or "0. I may have to make a pass through all the configuration and look for other boolean settings that should be changed.
Setting it to "yes" did not appear to remove the attenuator.
I may have to make a pass through all the configuration and look for other boolean settings that should be changed.
Ones and zeros for boolean are everywhere in the configs.
I may have to make a pass through all the configuration and look for other boolean settings that should be changed.
Ones and zeros for boolean are everywhere in the configs.
Yup, I think we should update that all before the release, to make it more user friendly. This is fairly minor, mainly a cosmetic change, so should be able to sneak that in.
Obviously the .conf files will require updating and perhaps the menus @Allan-N is building.
Obviously the .conf files will require updating and perhaps the menus @Allan-N is building.
I will be watching the commit logs and, if needed, will update the menus.
Turns out the CM119B (which is my device) is hardcoded to rxboost always on. Will comment confs and close with PR.
Changing the
rxboost
setting to 0 or 1 makes no difference. It appears the attenuator is always inserted as therxmixerset
must be 850 regardless of the rxboost setting.