Under the current prototype users can define user extensions to the memory class by specifying a tuple in the radio features structure. This tuple defines the caption, type, and choices for each "user" defined memory which is then stored in the memory's "user" dictionary.
Yeah, I think I'm against making the memory editor too much larger. Having to stack a potentially unlimited number of settings in a horizontally-scrolling row just kinda sucks. Also, it is a little more clear that things like extra settings aren't included in, say, CSV exports since they're not part of the table.
I think there *has* to be some way to embed a button in a row. If not, we could just do a link or image thing or something and trigger opening the dialog on click. I'd much prefer that I think.
--Dan