[WIP](New Version Jun 28/15) ModActions: Control mods via action groups.

[wasml]

Had a chance to play with this a little and noticed that the ModActs button duplicates on revert to VAB.

Checked Areo surfaces, Command, Stock Engines, Docking Node - Noticed limits weren't check in the Stock Engine module Not sure you really need to check - even if this did work - if the user wants to cheat no reason to stop them.

A few thoughts - not sure how feasible they are but I'll throw them out here.

Pre-populate ModActs list for non-input actions (or even input required actions and use a default) instead of having the user re-add for each piece. In other words the "Control from here" would be already filled in for all docking ports. The user can always delete it if they want.

Or

Have persistent lists for each type of module instead of each part. Ex: If I setup a list of thrust limits for one engine it would still be there for the second, third and fourth engine. I realize that some users may want a per part setup but my preference would be to do this by part type.

Follow on thoughts - pre-populate the list with the last used list for that type of part

Save these lists in a config file that can be saved and copied so when the mod is updated the config can be copied over to the new folder.

Thoughts on UI (only a minor issue (if that) for first time users)

When user selects a part with no ModAct actions and then clicks the Mod Act "Click to Select" button display something to indicate it's a non supported part.

Suggested mod to add: GPOSpeedFuelPump.

Three fields - pump level, Pump On/Off, Balance On/Off

Thanks for this mod!

------Edit------

To expand on the events to get multiple ModAct buttons.

I created a craft and assigned some ModActs to a few actions.

Sent the craft to the pad and exercised the actions.

Hit escape and "Revert to VAB"

I repeated this on the same craft a few times and noticed the multiple buttons showing up. It looked like one new button each time I reverted to the VAB.

Edited July 1, 2015 by wasml
added info

[Diazo]

@wasml: Thanks for all the feedback.

The ModActs button appearing a second time of revert is a simple fix, I just forgot a line of code.

On getting actions across multiple parts, would the ability to copy the actions from part to part work?

It's just that I foresee issues in trying to save configs like you are asking, notably around the fact that different players are going to want the save/loading of the configs to work differently and I can't accomodate everyone.

Copying actions from one part to another is much more straightfoward, but it does require setting up the part to copy from once per vessel. Thoughts?

I'll add GPOSpeedFuelPump to the list.

D.

[wasml]

For actions across multiple parts I was just throwing ideas out there after going through the SAS, engine and areo surfaces and setting up and testing all the options - lots of clicking there. The copy from one part to another does sound useful.

"I'll add GPOSpeedFuelPump to the list." - thank you.

[Cheesecake]

Hey Diazo

Can you integrate your Landing AID Mod?

[Diazo]

This mod is now in official release.

Release thread here.

This includes support for GPOSpeedFuelPump and my Landing Aid mod as requested.

D.

[Cheesecake]

Thank you.

[bepsy3d]

Hi!

I don't know if this discussion is till active... but I'll ask anyway.

Will this mod allow me also to set via action group, the SAS ship direction prograde - retrograde - ecc? 

That would actually be great! 

Edited December 6, 2016 by bepsy3d

[Diazo]

This specific thread is dead because all discussion has moved to the release thread;

That can be found here.

And yes, you can set SAS direction via action group, as long and the ship supports it. So you still need a high enough level pilot or probe core along for it to work.

D.