[chirp_devel] Architectural question: skip-only memory in chirp?
Dan Smith
Tue Jun 27 16:12:39 PDT 2017
> Does chirp natively support an alternate memory of always-skipped
> frequencies? I feel it’d be better for chirp to be able to read/write
> memories 901-999, but I’d really hate for somebody to think that they
> can store [really important] operational items in those spaces.
Just refuse to store a memory in that range if the skip bit is not set,
and always return it as set when you fetch those out. The user will get
an immediate error that the memory can't be saved if they try to unset
the skip flag.
--Dan
More information about the chirp_devel
mailing list