-
Notifications
You must be signed in to change notification settings - Fork 69
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
Extending the external API to allow for interaction with flight planning #2144
Comments
Having thought this through more, the actual set of functions would be (this is an exhaustive list):
Specifying an invalid vessel or manoeuvre index would throw an exception. These are all read only, as allowing write access to the flight planning is a rather more complicated task. One obvious issue is that manoeuvres are indexed, and may change if the user alters the flight plan. I don't currently have a good solution for notifying any external mods of this occurring. |
(Sorry for the late answer, been busy.) All these APIs seem to make sense, and look stable enough that we could implement them no matter what we do with the flight plan in the future. I might take a stab at implementing them for the next version (del Ferro). |
They make sense, but it is not clear whether they are needed after all; quoth @RCrockford on discord:
Closing this for now. |
I would like to be able to read (and potentially modify) flight planning manoeuvre nodes from another mod (specifically kOS). This allows for instance the ability to plan a manoeuvre and then have it automatically executed by a flight computer.
I am proposing extending the external API to give access to functions such as (not an exhaustive list):
principia__FlightPlanExists
principia__FlightPlanGetManoeuvre
principia__FlightPlanGetGuidance
principia__FlightPlanGetInitialTime
The text was updated successfully, but these errors were encountered: