[chirp_devel] Question regarding issue #4121

Jim Unroe
Tue Oct 11 10:04:14 PDT 2016


> 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



More information about the chirp_devel mailing list