[FEATURE] allow unregistration of modules

Thomas Schön wrote:

General question: 
the modules that are loaded by the application template are stopped when the application shuts down. So, if loaded it remains loaded till the end.

My project uses the HSE Application Template as a framework for executing several different test scenarios. It uses a few modules for common functionality which is needed continuously and this fits to the application template. The common modules are started by startup.

Where I have issues is that - after startup when the application is already running -  I start module-A for testing A. This test can be executed for any number of DUTs. Then module-A shall be stopped and module-B is started for testing B and so on.
The Data Cluster of the UI Manager still has module-A in its Module Paths array which causes errors.

As a test, I added a request to the UI Manager to remove the path of the module that was stopped. This is now gone by the update. No worries about that, I knew that it will happen. It was a test and I thought that using the System Message would be the better way of doing so.
But with the next update this will be deleted too.

Do you have plans of supporting the start-stop scenario for arbitrary modules?
If not, what could be the best workaround?
Thomas

This is how we set a new module:

For UI Manager and Event Manager:

• create new request "unset modules" which takes an array of Module Paths and remove them from the Module Paths on the shift register.