philmoz

> I interpreted your number 3 as backing up newer version files when a downgrade was detected and not using them. > > I am suggesting backing up older version...

If an automatic backup was made when the user upgraded their firmware version, and they were told where the backup was saved, then why do we need to do anything...

I'm not against doing something when a downgrade is detected; but making a backup of the newer files at that point is a bit like shutting the barn door after...

Yes that's what I'm thinking: if firmware major.minor > radio.yaml major.minor - Show 'Upgrading...' page - Backup MODELS and RADIO to BK_xxx_YYYYMMDDHHMM folder with progress bar (xxx is radio.yml major.minor...

> > I interpreted your number 3 as backing up newer version files when a downgrade was detected and not using them. > > I am suggesting backing up older...

Will std::sort handle the UTF-8 translation strings correctly for all languages?

> It will be a few days before I even think of looking at this, but I can do the tests for T20, TPro, and TProV2. I expect the T20...

I have added setup for custom switches to the radio hardware page (and radio data structure) so you can define type, name and startup position at the radio level. ...

I think the core changes are done for the firmware (pending any bug fixes). @elecpower for Companion I have yaml read / write working and have updated the model &...

The default for SW1-6 should be model setup, 2POS and group 1 for all of them to mimic the current way it works.