Actions
Feature #11138
closedMore robust handling of out-of-range settings
Start date:
02/05/2024
Due date:
% Done:
100%
Estimated time:
Chirp Version:
next
Model affected:
Any
I read the instructions above:
Yes
Description
Most radios right now will choke when loading the settings tab if any one setting is invalid or out of range. This is due to inadequate range checking and defensiveness in the drivers, but almost all of them assume the radio's memory is sound. This assumption is not reasonable for a variety of reasons.
It would be better if the CHIRP infrastructure and UI could help make such out of range issues easier to handle by allowing for settings to be "invalid" and only set them once they are corrected by the user. Loading invalid settings should be logged, marked, and made available for the user to fix. Something like this presentation:
Files
Updated by Dan Smith 10 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|d1ce2af28adb4dd78b95baeda152c66236d849b7.
Actions