This release brings support of map themes, layer styles, custom variables and print layouts in the **UsabILIty Hub Toppings**.
Improvements
UsabILIty Hub passing metaconfig to ili2db
ili2db configurations are defined in the *metaconfiguration file*.
ini
[ch.ehi.ili2db]
defaultSrsCode = 2056
smart2Inheritance = true
strokeArcs = false
importTid = true
ili2db will be called like this:
ili2db --metaConfig ilidata:metconfigId --schemaimport
Some parameters are automatically set in the background when ili2db is called by the Model Baker (like `--coalesceCatalogueRef --createEnumTabs --createNumChecks --createUnique --createFk --createFkIdx --coalesceMultiSurface --coalesceMultiLine --coalesceMultiPoint --coalesceArray --beautifyEnumDispName --createGeomIdx --createMetaInfo --expandMultilingual --createTypeConstraint --createEnumTabsWithId --createTidCol --importTid`), and others can be configured by the user in the input mask of the Model Baker (like `--smart1Inheritance`/`--smart2Inheritance`, `--createBasketCol`, `--strokeArcs`, `--iliMetaAttrs` (for `ini`/`toml`), `--preScript` and `--postScript` or `--models`). In addition, the relevant *metaconfiguration file* is passed to ili2db. But parameters passed directly to ili2db ***override*** the configurations of the passed *metaconfiguration file*.
The Model Baker reads the ili2db parameters from the *metaconfiguration file*. The parameters that can be set via the input mask of the Model Baker are loaded from the *metaconfiguration file* into the input mask. The user can now customize them. The Model Baker now passes the *metaconfiguration file* and the parameters from the input mask (whether customized or not) to ili2db. So if the parameters were listed in the *metaconfiguration file* but then disabled in the input mask, they will be passed to ili2db as `false`.
Changes are marked visually in the input mask for *ili2db Options*:
![grafik](https://user-images.githubusercontent.com/28384354/206726583-3299b193-01da-4a35-814b-182b2d6285ab.png)
The parameters set by the Model Baker in the background are still set. But they can be overridden in the *metaconfiguration file*. However, if in the *metaconfiguration file* such parameters are not mentioned, then they are also not overridden with `false`.
Exception is the setting to consider ***only*** the *metaconfiguration file*. If this is set, then only the parameters configured in the *metaconfiguration file* should be set and no others (Exception from the exception is `--models` and `--sqlEnableNull` on "Run withouth constraints"):
ini
[CONFIGURATION]
qgis.modelbaker.metaConfigParamsOnly = True
When this parameter is set the *Advanced Options* and *CRS* settings are disabled in the input mask.