What about making it a setting item, which could then easily be pushed/popped from the player UI settings menu

Subject: Re:  Digital Input plugin should only appear on transporters

That would be fine.  In fact, preferred.

(Though it would be nice for plugins to be able to be added to  
settings, I was thinking that the Rescan plugin should probably  
appear in settings just tonight.)

It could be done.  the addMenu feature does allow something, but we'd need to adjust the settings module to be more of a plugin itself,. adding to the home menu hash instead of being it's own fixed structure.  My only thought lately is that the server is including a lot of plugins that it confuses the line where plugins were more of a third party thing.  When users upgrade, they don't have that mindset to check plugins for incompatiblities, possibly because they think of them as being just part of the server.

My other idea for making the home menu an OPML navigable via the xmlbrowser would also make this kind of thing easier. I just have far less of an idea of how to write that, then I would about adding settings or refactoring the settings mode.

I'm making a very simple INPUT.Select module, which expects a list of items, where only one in the list is selectable and shown with the checkbox overlay.  All functions are hard coded, with PLAY and ADD acting as actions to set the change.  

What I'm missing from fixing this specific issue is a way to read the current state.  From the plugin, it doesn't appear that there is one.  How do we know what the current setting is?

Created attachment 1388 [details]
digial input in settings

adds core strings, player pref (w/ default), and a checkboxOverlay handled UI for Transporter.

Fixed in change 8756