[chirp_devel] Question regarding issue #4121

[Michael Wagner]

Hi,

For the UV-5R, the effect was the same as for the KT-8900R, but the cause was a little bit different:
In set_memory, the driver unconditionally sets the whole memory to x00 (using _mem.set_raw("\x00" * 16)), before it applies all the settings from the UI.
And in the last step, it applies all available mem.extra-settings. But as mem.extra is non-empty only when editing the mem using properties/other, they are not set most of the time ...

(Just removing the unconditional reset of the whole memory does not work, it causes get_memory to fail when trying to edit a previously deleted memory.)

So I soft-commited a different solution for this driver (memorize the values of mem.extra before erasing the memory, and restore them afterwards. (see http://intrepid.danplanet.com/pipermail/chirp_devel/2016-October/004321.html )

73,
Michael (OE4AMW)