User Tools

Site Tools




31 Clone Manager

This is not part of the template, but a concept to follow if need be.

If you want the application itself (i.e. the or the UI Manager to load a number of clones, the suggested or preferred way is to create a Clone Manager DQMH module. As this comes - in our experience - with more or less project-specific requirements, we have not looked into creating a generic Clone Manager but rather build application-specific modules.

With only a few changes, any cloneable module supports the following suggested architecture:

Clone Manager

The Clone Manager module can…

  • have its own .ini file, like other modules, to tell it which and how many clones to launch
    • each clone is identified by a clone name
    • the clone name is defined in the manager's .ini file
    • the clone name is handed over to each clone at startup
  • manage a registry of clones
  • contain multiple subpanels to display several clones in parallel
    • manage clone-to-subpanel allocations in the registry
Loading a number of clones from a clone manager module


The Clone modules…

  • need a control on their front panel so the clone name can be supplied during start
  • have a shared .ini file
    • one section per clone instance (identified by the clone name)
  • read their own configuration from the corresponding section in the .ini file
The features a string control for the clone name
code/dqmh/hse-application-template/clone-manager.txt · Last modified: 2020/01/07 17:20 by joerg.hampel