I'm pretty weak on MVC patterns, but my understanding is keeping a clean separation between radio drivers (model?) and the UI (view/controller?)
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.
While we are on this subject, I have desired a (long) description field for some radio setting values which would act like a tooltip.
Another desire was the ability to have a label or (read-only) textarea field for informational purposes in the UI.
On Dec 30, 2014, at 1:54 PM, Dan Smith dsmith@danplanet.com wrote:
For now this display will just be a long list like other settings. I don’t think I want to hold up an initial cut at the h9800 that Jens and I have been working on to build a new setting class.
Sure, sounds good. Thanks!
--Dan
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