[chirp_devel] RadioSettings when used within mem.extra
Group,
For some reason, I cannot get RadioSettingValueInteger() to work for setting values in a "mem.extra" RadioSettingsGroup(). When I use it here (the same as I would in "_get_settings(self)", I get no errors but the setting does not display in the CHIRP Memory Properties Editor.
Only one driver currently attempts to use RadioSettingValueInteger() this way (tk760G.py). But like I am experiencing, the settings (there are 2: "Bank it belongs" and "Ch number in the bank") are not visible in the CHIRP Memory Properties Editor.
I have no problems using RadioSettingValueBoolean() or RadioSettingValueList() for providing settings in the "mem.extra" RadioSettingsGroup() (even tricky ones where the Boolean values are inverted).
So for years I have just been creating a list of integers and using RadioSettingValueList() to get around this issue (and apparently everyone else, except one, has been too).
What I am trying to find out is; is this a CHIRP bug, or, am I doing something wrong, or, am I not doing something that needs to be done differently for the "mem.extra" RadioSettingsGroup()? Do any of you have any ideas about this?
Thanks, Jim KC9HI
Memory extra settings currently only appears to support RadioSettingValueBoolean and RadioSettingValueList; the behaviour when any other type is provided is to simply ignore it. It probably wouldn't be difficult to add support for additional types such as RadioSettingValueInteger given that the IntChoiceEditor is already defined (although never instantiated). I have no context as to the history as to why this is the case, but should be easy to implement and test.
https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/ui/memdeta...
On Wed, Jul 28, 2021 at 3:06 PM Jim Unroe via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
Group,
For some reason, I cannot get RadioSettingValueInteger() to work for setting values in a "mem.extra" RadioSettingsGroup(). When I use it here (the same as I would in "_get_settings(self)", I get no errors but the setting does not display in the CHIRP Memory Properties Editor.
Only one driver currently attempts to use RadioSettingValueInteger() this way (tk760G.py). But like I am experiencing, the settings (there are 2: "Bank it belongs" and "Ch number in the bank") are not visible in the CHIRP Memory Properties Editor.
I have no problems using RadioSettingValueBoolean() or RadioSettingValueList() for providing settings in the "mem.extra" RadioSettingsGroup() (even tricky ones where the Boolean values are inverted).
So for years I have just been creating a list of integers and using RadioSettingValueList() to get around this issue (and apparently everyone else, except one, has been too).
What I am trying to find out is; is this a CHIRP bug, or, am I doing something wrong, or, am I not doing something that needs to be done differently for the "mem.extra" RadioSettingsGroup()? Do any of you have any ideas about this?
Thanks, Jim KC9HI _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
Memory extra settings currently only appears to support RadioSettingValueBoolean and RadioSettingValueList; the behaviour when any other type is provided is to simply ignore it. It probably wouldn't be difficult to add support for additional types such as RadioSettingValueInteger given that the IntChoiceEditor is already defined (although never instantiated). I have no context as to the history as to why this is the case, but should be easy to implement and test.
Yep, just not implemented. I'm sure it's because the radio or radios I was working on at the time had no integer settings in mem.extra so I just didn't implement it.
I just sent a patch that seems to work for me, although the tk760 driver doesn't appear to actually save the bank, probably because there was no way to change it in the UI and test.
Jim, if you want to give this a test, I can either apply it as-is, or you can include it in whatever you're planning to submit that uses this.
--Dan
On Fri, Jul 30, 2021 at 6:40 PM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Memory extra settings currently only appears to support RadioSettingValueBoolean and RadioSettingValueList; the behaviour when any other type is provided is to simply ignore it. It probably wouldn't be difficult to add support for additional types such as RadioSettingValueInteger given that the IntChoiceEditor is already defined (although never instantiated). I have no context as to the history as to why this is the case, but should be easy to implement and test.
Yep, just not implemented. I'm sure it's because the radio or radios I was working on at the time had no integer settings in mem.extra so I just didn't implement it.
I just sent a patch that seems to work for me, although the tk760 driver doesn't appear to actually save the bank, probably because there was no way to change it in the UI and test.
Jim, if you want to give this a test, I can either apply it as-is, or you can include it in whatever you're planning to submit that uses this.
Dan, it works as I would expect it to. You can "apply it as-is". Thanks!
Jim
On Fri, Jul 30, 2021 at 9:18 PM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Dan, it works as I would expect it to. You can "apply it as-is". Thanks!
Cool, do you have a bug open already for something I can "charge" this to?
You can submit it as needed for issue #6769. Thanks.
Jim
participants (3)
-
Dan Smith -
Jim Unroe -
Kosta Arvanitis