Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added modeActivationConditions parameter group #1107

Conversation

martinbudden
Copy link
Contributor

No description provided.

@martinbudden martinbudden added this to the 1.6 milestone Jan 16, 2017
@martinbudden martinbudden merged commit e8beb3f into iNavFlight:development Jan 16, 2017
@martinbudden martinbudden deleted the in_pg26_modeActivationConditions branch January 16, 2017 18:59
#endif
}
PG_REGISTER_ARR(modeActivationCondition_t, MAX_MODE_ACTIVATION_CONDITION_COUNT, modeActivationConditions, PG_MODE_ACTIVATION_PROFILE, 0);
PG_REGISTER(modeActivationOperatorConfig_t, modeActivationOperatorConfig, PG_MODE_ACTIVATION_OPERATOR_CONFIG, 0);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it wise to waste a whole PG to modeActivationOperatorConfig which is only used together with modeActivationConditions? Isn't it better to combine the two PGs?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I sort of think that as well. Trouble is modeActivationCondition is an array, and so I wasn't sure how best to combine them. My general approach is to just get things working and not think too hard about getting it exactly right - that would considerably slow down the process.

Once all the PGs are done, I intend to go through them again making minor adjustments.

There are also some discussions to be had about what is in a profile and what is not - I've also deferred that until they are all done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants