On Sat, Feb 13, 2016 at 11:20 PM, Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
What if we changed that else to "elif setting._mutable:" ?
My tester reported back "I just tried it and when I edit the squelch/service settings, I get an error message that says, "Error in setting value: 'str' object has no attribute'_mutable'""
Sorry, should be element._mutable I think.
When using "elif element._mutable:", it get the following.
DEBUG: squelch ERROR: Exception running RadioJob: '_mutable' DEBUG: Reporting exception ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "C:\Users\Root\chirp.hg\chirp\ui\common.py", line 116, in _execute result = func(*self.args, **self.kwargs) File "C:\Users\Root\Documents\UV-5R\uv5r.py", line 1554, in se t_settings self.set_settings(element) File "C:\Users\Root\Documents\UV-5R\uv5r.py", line 1578, in se t_settings elif element._mutable: File "C:\Users\Root\chirp.hg\chirp\settings.py", line 350, in __getattr__ return self.__dict__[name] KeyError: '_mutable'
Pavel's method does work, but I see what you are wanting to do Dan. That would all new elements that have mutable set to False to be supported without needing to alter this section of code any further. I would like to see about make yours work.
Jim