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

Separate pitch, yaw and roll gimbal enabling/locking #1622

Merged
merged 2 commits into from
May 5, 2016

Conversation

AlchemistCH
Copy link
Contributor

One of the new features of 1.1 - ability to enable/disable pitch yaw and roll response of the gimbals separately.
Added corresponding suffixes to the Gimbal part module.

@hvacengi
Copy link
Member

I'm going to tag issue #1587 here as it is the associated issue, but it won't fully fix it since that issue was focused heavily towards cooked steering.

@hvacengi hvacengi added this to the v1.0.0 milestone Apr 25, 2016
@hvacengi hvacengi self-assigned this Apr 30, 2016
@hvacengi hvacengi merged commit a3e1026 into KSP-KOS:develop May 5, 2016
@AlchemistCH AlchemistCH deleted the patch-3 branch May 5, 2016 16:43
AddSuffix("ROLL", new SetSuffix<BooleanValue>(() => gimbal.enableRoll, value =>
{
gimbal.enableRoll = value;
}, "Does the Gimbal respond to roll controls?"));
Copy link
Member

Choose a reason for hiding this comment

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

The indentation above looks really wonky. The braces shouldn't be at the same level as the "A" in "AddSuffix" because they're a continuation of the AddSuffix call. They should be indented further in.

@hvacengi hvacengi modified the milestones: v0.20.1, v1.0.0 May 12, 2016
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.

3 participants