Make MFD maps configurable in the MAS Part Module

[MOARdV]

All of the MFDs use a hard-coded IMAGE node to display the Kerbin map. What I should have done is make it configurable in the Avionics System Part Module so it's simple to patch for JNSQ / GPP / other planet packs.

I'll need to sort out just how that would look. Or maybe it would be a key/value pair based on the planet name? Like

map=Kerbin,ASET/ASET_Props/Instruments/ASET_IMP/map_Kerbin_sat
map=Mun, ...
etc

I'm not sure how well Module Manager would do with token matching a string containing a comma, though.

[theonegalen]

Ooh, yeah

[MOARdV]

Can I take it one step further and have a specialized MAP_IMAGE node for the MFD? IMAGE requires a static name, but a MAP_IMAGE or, generalized to DYNAMIC_IMAGE, could allow the referenced texture to change. Then I can add a function like fc.GetMapImageName(string celestialName) that could update when the SoI changes (or the player selects the name to view). Add a map=default, name to the config, and there'd be a fallback option for when there is no map to correspond to the celestial.

[StoneBlue]

MOARdV, you mention a "generalized DYNAMIC_IMAGE" module...
A use case for making something wider than just for maps, for example, is the clipboard prop.
It is interactive, in that, it has a couple triggered colliders, for "Next/Prev" page... So it has a texture, using the ASET Jebsen charts...
You can flip thru different pages of the texture, to have interactive, in-game access to the "document"
I could think of a "tablet" prop you could pic up, and do the same with... Basically flip thru different "pages" (ie textures)...

[Sheepdog2142]

Did this ever get implemented?