1.262

New placeholders were added inside the top-level MULTI_RUN_SETTINGS bucket of the assembly context:

• MULTI_RUN_SETTINGS.DISCRIMINATOR_ATTRIBUTES — The names of the attributes that discriminate sub-runs of the multi-run configuration.
• MULTI_RUN_SETTINGS.DISCRIMINATOR_VARIATION — The concrete attribute : value mapping that identifies the specific sub-run.
• MULTI_RUN_SETTINGS.DISCRIMINATOR_VARIATIONS — The complete list of all attribute : value combinations available for the parent multi-run configuration in the current pool version (i.e. the full list of all sibling sub-runs).

RunContext.is_multi can also be used to check whether a run configuration is a multi-run configuration. If the run is not a sub-run of a multi-run configuration, MULTI_RUN_SETTINGS will be None and all three properties will return None.

In the past, obsolete warnings were inconsistent between single and multi-run configurations:

• A single run configuration using a parameter set from an obsolete parameter group correctly showed an obsolete warning and was blocked from assembly.
• The same run configuration used as a child inside a multi-run configuration showed no warning, and assembly of the multi-run failed with an error.

This has been fixed. Now, whenever a component group is tagged as obsolete, any run configuration using its content shows an obsolete warning and is blocked from assembly.

In the past, users could not select individual components/files in the component grid by left-clicking. This issue only affected clients on hardware with touch displays and/or on remote desktop solutions with support for such hardware. Range selection (Shift + click) was not affected. This has been fixed. A single left-click now selects the target row and updates the selection highlighting accordingly.

When a component’s type is changed, snippets that are not supported by the new type will now remain visible. For example, if component X has snippets A, B, C and component Y supports snippets D, E, then after changing the component type from X to Y:

• Snippets D and E will be visible. The user can modify them as needed (e.g. edit, copy, delete, etc).
• Snippets A, B, and C will remain visible in read-only mode. The user can copy or delete them as needed.

When a component is copied and pasted into a pool that does not support its type, the component is listed in an unassigned group. Changing the component to a supported type activates the Apply button. In the past, clicking Apply caused an error to occur and the action to fail. This has been fixed.

In the past, activating the Show only assigned attributes option in the new component grid (while also having a run configuration selected) caused attributes from the run configuration to be displayed, even if they were not set on any components in the pool version. This has been fixed. The option now only considers attributes assigned to components. For clarity, the option has also been renamed to Show only component attributes.

In the past, the Sort column sometimes failed to finish computing its value, leaving the loading icon spinning indefinitely for some components. This has been fixed, and sort values now compute and display correctly.

Note: This fix relates to the new component grid, which is still under development and disabled by default. It can be enabled by starting the client with --feature new_component_grid.

In the past, right-clicking a component and selecting Edit with… incorrectly triggered an “Unwritten changes” pop-up in the edit window. This has been fixed, and the warning no longer appears on every edit operation.

In the past, the post-edit script created a preview.mvz file, however the client generated a transparent preview.png from it, which appeared empty in the Preview tab. This has been fixed, and preview screenshots are now generated correctly.

This fix relates to the External Applications area of the Settings. In the past, clicking the “+” button created a new entry in the backend, but the UI did not refresh, so no new row was displayed until the Settings area was closed and reopened. This made it look like the action had failed. This has been fixed, and new entries now appear immediately.