thanks for your hints - in the attached version of btech.py, I tried to implement them.
I it's OK from your point of view, I will soft-commit a patch for it (and afterwards try to do the same for the baofeng-common-driver).
BTW: Should I open a separate issue for each affected driver?
73,
Michael
> Hmm, yeah, I think that's a bug, and probably pretty confusing to users.
> However, I expect the intent there was to initialize the settings if you
> were opening that memory for the first time. So, probably what should
> happen is:
>
> if extra:
> set_extra()
> elif not mem.empty and (mem was empty):
> initialize_extra()
>
> That last "was empty" part would require looking at the current memory
> map to see if it looks like a deleted memory.
>
> Jim, does that make sense?
>
> Michael, are you offering to fix up the drivers that behave this way?
>
> Thanks!
>
> --Dan
Dan,
I'm not 100% certain, but I think this is something that I got from
Pavel. It didn't seem to be working as expected for my recent driver
work so my "fix" was to leave it out.
What you propose makes sense.
Jim