03 FAQ
Which versions of DQMH are supported?
See the Upgrade Instructions page for more details.
Are there any limitations to the naming of DQMH modules?
In order to avoid conflicts and collisions, DQMH module naming needs to comply with the following limitations:
HSE-* | DQMH module names may not start with the HSE- prefix (reserved for internal and commercial modules) |
|---|---|
Event Manager | reserved for framework |
Navigation | reserved for framework |
UI Manager | reserved for framework |
DB_CONNECTOR | reserved for libraries |
GenNet-Server | reserved for libraries |
GenNet-Client | reserved for libraries |
Are there any limitations to the naming of DQMH events?
DQMH modules implementing the HSE Flavour ship with the following events:
Configure | Request |
|---|---|
Prepare | Request |
Request UI Display | Request |
System Message | Broadcast |
Module Is Ready | Broadcast |
Is there an existing way of adapting the template to launch a cloneable starting module?
There is not. The reason for this is that there’s no good way at the moment to publish the clone id, and without that, I don’t see how that would be useful.
For all the projects we’ve done that needed something like that, we created a “Management” module that did the launching and registration of clones and their IDs. See Clone Manager for more information.
The application can't load my DQMH modules!
For DQMH modules to be compatible with our application template (i.e. for the application template to be able to load modules, and for all the features of the UI Framework to work out right), these modules need to adhere to our HSE DQMH Flavour.
You can find more information on saving existing modules as templates as well as creating new modules from templates in Delacor's DQMH Online Help.