Plugin Manipulation of MultiModeEngine - Events are private?

[Shadowmage]

Hi all,

I have a concept for a decoupler part that can automatically activate a secondary engine on a part when it decouples.  This would be, for example, for an SRB with integrated jettison motors.  The 'main' engine would be the SRB, using SolidFuel, the 'secondary' engine would be the jettison motors, using a second custom fuel type (JettisonFuel/etc).  The decoupler would trigger upon depletion of the main-engines resource (or whatever is specified in the decoupler config), which would then trigger the activation of the MultiModeEngine and the secondary jettison motors.

Normally when interacting with stock modules in this manner, I would call their publicly exposed GUI interaction methods, to trigger the action as if it was triggered by the player (seems to save a lot of headache / makes sure you are interfacing with the code in the right place/manner).

Now, the problem with this approach with MultiModeEngine is that everything appears to be private?  I was under the impression that things flagged with [KSPEvent] and [KSPAction] had to manditorily be public methods, but apparently this is not the case as I cannot locate any externally accessible methods that correspond with its actions/events.

So, the question is -- how to properly interface with MultiModeEngine module through a secondary module to trigger MultiModeEngine to switch from primary to secondary engine?  Can I get a reference to its Events["eventName"] or Actions["ActionName"] and trigger them from there?

Any other ideas on how to get this working?

 

Solution:

Yes, interacting with the methods through their Events[].Invoke() method works fine.  You just need to know the name of the method to trigger.

Edited December 12, 2015 by Shadowmage

[Shadowmage]

A little bit more poking around has revealed that the Events array -is- publicly accessible, and appears that it does have an Invoke() method that can be called on it.  Pretty sure I can interact with it through this method without too much difference from calling the event directly as if it were public.

Will update with info regarding the results as soon as I can test it out.

[sarbian]

Calling all @NathanKell on deck !

Yep, I had a look and the KSPAction and other methods should be public to work as other modules do

[NathanKell]

I'll fix it for 1.1.

[Shadowmage]

Thanks Sarbian and NathanKell.

Should calling the Events[""].Invoke() method work for the time being?

[sarbian]

I never tried but it should.

[NathanKell]

It should, yes.

[Shadowmage]

Yep, seems to work fine.  Thanks for the help guys.

Now I have Launch Abort Systems that auto-decouple and switch to jettison motors after the initial abort motors have run out their fuel.  Good stuff