I'm pretty weak on MVC patterns, but my understanding is keeping a clean separation between radio drivers (model?) and the UI (view/controller?)
Right.
Could this be done from radio driver if we can signal some sort of logical partiioning? Ideas: Allow RadioSettingsGroup (RSG) nesting. Multiple RSGs within a tab (i.e., top-level RSG) would signal UI/view to attempt to render one nested RSG per column. Or maybe same idea above as RSG subclassing, i.e., RadioSettingsSubGroup. Or maybe appending something akin to a column break, e.g., RadioSettingsGroupColumnBreak, to the list which would signal UI to draw to a new column in the list.
You could do it with the group I guess, but logically it's more of a multi-value setting element I think. Setting is just a subclass of Group with one thing, so having a subclass that stores one and a subclass that stores a bounded set makes sense to me.
Later we could use nested groups to add tabs within a setting group page, and thus doing this for a band's hi/low settings would confuse that. The thing he wants is really "the 30m limits, which is composed of a high and low value".
While we are on this subject, I have desired a (long) description field for some radio setting values which would act like a tooltip.
We have the ability to store the __doc__ bits with the RadioSetting/Group, which is what that was for. I thought the settings editor would use those for tooltips, but maybe that never got implemented?
Another desire was the ability to have a label or (read-only) textarea field for informational purposes in the UI.
Sure, a ReadOnlyStringValue class that looks just like string but causes the UI to emit a Label instead of an Entry would be easy. I think Tom was saying he wanted something like that recently.
--Dan