missionCommands: change Group.

[ADHS]

Hello.

I was wondering if:

once we have set menus/options for a group,
if we can change the receipient group, so:
the menus to be visible to the new one
without having to reconstruct the menus/options again.

Thank you

[TEMPEST.114]

It’s very fast and not much of a hot to remake the menus, personally I don’t think you need to worry about reconstructing them, but to answer your first question, I see no way to ‘move’ them wholesale from one group to another without removing them from the first group and reconstructing on the second. 
 

I do this all the time and there is no real hit for doing it. 

Edited November 23, 2022 by Elphaba

[ADHS]

4 hours ago, Elphaba said:

I do this all the time and there is no real hot for doing it. 

Hello.
This is why i am asking. Sure i can do it by a similar way as you said.
But, if indeed there is a shortcut to do it more efficient, why not to
choose this instead the long way ?

[cfrag]

6 hours ago, ADHS said:

once we have set menus/options for a group,
if we can change the receipient group, so:
the menus to be visible to the new one
without having to reconstruct the menus/options again.

This seems rather unlikely. You may try and construct the 'path' (as referenced here and here) and then try and assign that table as command to other groups. However, since the "path" table you have received does not contain (or rather, is not documented if and how it contains) any callback- nor parameter-info, you'll have to re-do all addCommand() invocations with their correct settings anyway, so the invoked callback knows which group it came from. If the callback doesn't need to know that information, it usually shouldn't have been targeted at individual groups anyway, and made available to all. 

I think it's a result of the 'design' chosen by ED for these commands; I agree that it has a definite clunky 'bolted-on' feeling, and it does not integrate well with missions (a properly designed menu architecture would probably deliver any menu choices as game events - but I digress). Let's be happy that they are available at all, and hope for unit-individual menus at some point in the future. Clunky or not, mission commands do expand missions greatly

 

[ADHS]

9 minutes ago, cfrag said:

not contain (or rather, is not documented if and how it contains) any callback- nor parameter-info,

Hello and thank you for your reply cfrag. (i always appreciate your comments in details)

I will study your guideline(s) and i'll report back any findings.
Sure we've given enough, but there is more hidden in there. Some people know but they are not talking.
Thank you

Edited November 23, 2022 by ADHS

[ADHS]

Hello.
I've managed to get the required result with
a custom short function full of variables.
My knowliedge doesn't allow me to know the ONE
and single core group.ID variable so to avoid 40 lines of code.

Edited December 1, 2022 by ADHS