[chirp_devel] Memory and RadioSettings

[Dan Smith]

> settings.py is copyrighted 2012, quite some time after the 2008
> chirp_common, so I guess this was a later effort to create some more
> elaborate value handling. I have the impression that this did not make
> it to the standard attributes of Memory, and that this would need very
> careful work to not break old drivers.
> I could also think of some ways to wire memory handling (in my case, no
> experience with other radio types) by implementing mapping functions.

I never had any intention to replace the base properties on the memory with those values. The "extra" settings are basically considered to be "incompatible things we'll never try to copy between dissimilar models", but that is not true of the base properties, which need to be pretty solid in order to (a) not break other drivers and (b) make it easy to set a memory from one model into another. The mechanism by which the validation happens could be modernized for sure, but I don't really want to make the properties (easily) override-able by the drivers for fear of creating incompatible (at the base attribute level) between models.

--Dan