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

Implemented TriggerAU's suggested fix to range limit #2554

Merged
merged 1 commit into from Jul 18, 2019

Conversation

Dunbaratu
Copy link
Member

Fixes #2531

I got some feedback from SQUAD team member TriggerAU about this problem and he pointed me to the API call that SQUAD uses to obtain the float ranges, and it encapsulates some of the work needed to find the cases where a float range is getting overridden by another float range. This method call TryGetFieldUIControl seems to do everything right and obtain the true ranges that game is actually using.

{
// I have no clue what this actually looks like in the UI? What is a
// user editable 2-D vector widget? I've never seen this before.
if (convertedVal != null)
Copy link
Member Author

Choose a reason for hiding this comment

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

The above looks like a large edit, but if you look carefully, all it is is just a change of indent level.

@Dunbaratu Dunbaratu merged commit 272d0a7 into KSP-KOS:develop Jul 18, 2019
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.

Wrong conversion for PartModuleField values using Robotic Parts
1 participant