fix: Regenerate yaml, carryTrim => trimSource cleanup (#3121)
PR #2995 didn't take into account the data model storage actually does change when you change a variable name. Boxer yaml generation was missed in earlier PR. * chore: Run `generate-yaml.sh` * chore(cpn): carryTrim -> trimSource * fix(build): Boxer missing from `generate-yaml` * dodgy attempt to read old carryTrim * fix: Don't break the byte boundary + reorder * fix(yaml): indentation for attributes that should not be output * chore: Regenerate YAML after rebase --------- Co-authored-by: raphaelcoeffic <raphael.coeffic@frafos.com>
This commit is contained in:
co-authored by
raphaelcoeffic
parent
4e09bd7b8c
commit
46cc979875
@@ -95,8 +95,9 @@ PACK(struct MixData {
|
||||
PACK(struct ExpoData {
|
||||
uint16_t mode:2;
|
||||
uint16_t scale:14;
|
||||
uint16_t srcRaw:10 ENUM(MixSources) CUST(r_mixSrcRaw,w_mixSrcRaw);
|
||||
CUST_ATTR(carryTrim, r_carryTrim, nullptr); //pre 2.9
|
||||
int16_t trimSource:6;
|
||||
uint16_t srcRaw:10 ENUM(MixSources) CUST(r_mixSrcRaw,w_mixSrcRaw);
|
||||
uint32_t chn:5;
|
||||
int32_t swtch:9 CUST(r_swtchSrc,w_swtchSrc);
|
||||
uint32_t flightModes:9 CUST(r_flightModes, w_flightModes);
|
||||
|
||||
Reference in New Issue
Block a user