Cannot trust the min/max/step values for sliders in Breaking Ground robotics parts

[Dunbaratu]

This has caused us some headaches in kOS.  It seems the Breaking Ground UI elements in the Part Action Window have several KSPFIelds who's official values for range.minValue, range.maxValue, and range.stepIncrement have no relationship at all to reality.  What the user is allowed to alter in the window often goes outside those claimed ranges, or does not require the rounding that the stepIncrement claims.

 

Example: For ModuleRoboticServoPiston, the KSPField called "target extension" claims it takes values from 0 to 100, rounded to the nearest 1.0.  The window I am seeing when I use the "1P4 Telescoping Hydraulic Cylinder" actually goes from 0.0 to 2.5, and seems to let me pick values like 1.25 and so on.

Is there somewhere my C# code can query to find the correct answer to the question "what is the min/max value this slider can take, and how does it round?".  These DLC parts seem to be ignoring the normal means for me to query that.  Supporting them in kOS would mean having to make hardcoded special case exceptions just for these specific fields on these specific parts, since the values I can read about them aren't true.

I've gotten the same problem from the angle ranges on the rotating parts - the min/max/step values reported aren't true.

Also, the KSPField display values on the PAW only update when the PAW is visible.  From the point of view of a UI this makes sense, I guess.

This is all adding up to me thinking I'm going to have to write a special-case module for kOS to talk to the robotic servos. 

Edited June 6, 2019 by Steven Mading