[chirp_devel] Issue with Baofeng Firmware Version

Pavel Milanes (CO7WT)
Sun Feb 14 13:12:03 PST 2016


Excellent solution,

This is a baofeng issue (now), but may be it can be expanded to cover 
other models.

As good practice, non mutable settings must be non editable directly or 
indirectly.

I will check my drivers to look for this...

73

El 14/02/16 a las 16:01, Jim Unroe via chirp_devel escribió:
>> Try this:
>>
>> diff -r 9752a42d4a0d chirp/drivers/uv5r.py
>> --- a/chirp/drivers/uv5r.py     Mon Feb 08 14:14:28 2016 +0000
>> +++ b/chirp/drivers/uv5r.py     Sun Feb 14 07:53:08 2016 -0800
>> @@ -1574,7 +1574,7 @@
>>                       if element.has_apply_callback():
>>                           LOG.debug("Using apply callback")
>>                           element.run_apply_callback()
>> -                    else:
>> +                    elif element.value.get_mutable():
>>                           LOG.debug("Setting %s = %s" % (setting,
>> element.value))
>>                           setattr(obj, setting, element.value)
>>                   except Exception, e:
>>
> Thanks Dan. Exactly what I was looking for. Works great. I will submit
> a patch for this soon.
>
> Jim
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>




More information about the chirp_devel mailing list