1.263

Publishing a live version is not permitted if it contains locked components. In the past, this restriction was only noted in a console traceback, with no visible feedback in the user interface. Users now see a clear error message after clicking Set public.

After renaming the application from “LoCo” to “SCALE.sdm”, some areas of the user interface (i.e. tooltips, error messages, UI elements) still displayed the old name. Such occurrences were updated to reflect the current wording.

The sanitize_for_filename method is used to sanitize component filenames during export or assembly. Previously, only a strict mode was available, which filtered out non-ascii characters, for example Japanese and Chinese characters. A new permissive mode was added, which only removes characters that are invalid in file names: [<>:"/\\|?*].

In the past, drop-down menus, such as the widget preset drop-down, could intermittently become unresponsive for the duration of the current session, requiring a client refresh to restore functionality. This has been fixed.

In the past, if a user right-clicked on a tab and selected Duplicate tab from the context menu, then the currently active tab was always duplicated, regardless of which tab the context menu was opened on. For example, if Pool A was the active tab and the user duplicated Pool B, then a new tab for Pool A was incorrectly opened. This has been fixed. The duplicated tab now always corresponds to the tab on which the action was invoked.

In the past, when editing multiple components simultaneously, a history comment entered for one component was propagated to the other selected components. However, upon closing the editor, the propagated history comments for the other components were discarded. This has been fixed.

In the past, a new pool version was generated when performing certain actions on run configurations, e.g. activating the checkbox Save on run configuration or changing the local assembly directory in the Properties view. This has been fixed. In public pool versions, settings that would trigger automatic pool version creation are now read-only and cannot be modified.

In the past, if multiple single run configurations were selected for local or remote assembly and the Save on this run configuration option was only enabled for some of the run configurations, then an error appeared and the assembly was aborted. This has been fixed. Each run configuration is now assembled according to its own individual settings.

In the past, if a user selected multiple run configurations and clicked “Load all properties” in the Properties view, then the properties continued to load, even if the user changed their mind and selected different run configurations before the loading completed. This has been fixed. Loading is now cancelled immediately when the selection changes.

In the past, if a user grouped run configurations by scenario and no scenarios were configured, then all of the run configurations were hidden and there was no way to reset the grouping. This has been fixed. A placeholder group labelled -- is now displayed when no scenarios are configured.

In the past, when a run configuration was selected and the user switched to a pool version that did not contain that run configuration, the sort index column in the new grid displayed an indefinitely spinning loading icon. This has been fixed. The column now correctly displays a value or an error state.

In the past, when setting user metadata for multiple components in the Properties view (multi-select), the user metadata was not always saved for all of the selected components. This has been fixed.

In the past, users could add or change attachments on objects, e.g. components in another user’s private pool version, even when they only had read access. This has been fixed. Attachment actions are now only available on objects for which the user has write permissions.

In the past, when copying a parameter table from a read-only sub-pool and pasting it into a different pool, the client attempted to create the entry in the source sub-pool instead of the user-selected destination group. Because the user lacked write access to the source pool, the action failed with an error. This has been fixed. The pasted parameter table is now created in the correct destination group.