1.244

Users can now right-click on a component in the grid and select/deselect the option Show components recursively from the context menu. This setting is also stored in the widget preset.

•  : The components will be displayed recursively. That means, when a user selects a pool version or a group, all of the components in that group and in all of the contained subgroups will be displayed as a flat list in the grid.
•  : Then components will be displayed non-recursively. That means, the user will only see the components explicitly contained in the selected group. The components in contained subgroups will be filtered out. In some cases this might lead to an empty grid or to fewer components being displayed than expected.

Note: This feature relates to the new component grid, which is still being developed and which is deactivated by default. Currently, the new grid is only used if it is specifically activated with the command --feature new_component_grid while starting the client.

Note: In the past, the component grid always showed the components of a group recursively.

• Computing this information from older data can become very expensive. Only activate this column if necessary and deactivate it when no longer needed.
• The original file name is loaded from the database. This is only available for newer components.
• This feature relates to the new component grid, which is still being developed and which is deactivated by default. Currently, the new grid is only used if it is specifically activated with the command --feature new_component_grid while starting the client.

This feature relates to the Repair local storage pop-up window, which can be accessed by clicking on the red   icon, or by using the repair option in the command line interface. This pop-up window now includes a new function called Repair local database. This action might be necessary, e.g. if the database is malformed or if there is still an “NFS lock” on the database, which prevents it from being opened. The pop-up window gives users three options for repairing the local database:

• Copy: Creates a copy of the existing database and thus attempts to remove any file system locks that may prevent the software from opening.
• Repair: Dumps the database to the file system and reinitializes it from the dumped data.
• Re-checkout: This is the most drastic action. It discards the local database entirely, and initiates a fresh setup of the desktop client.

This improvement relates to the Tags column in the grid. In the past, this column displayed the name of the tag, e.g. “reference” or “status”. This has been improved. The column now displays the tag’s color and letter. This visual aid helps users recognize the tag more quickly.

Note: This improvement relates to the new component grid, which is still being developed and which is deactivated by default. Currently, the new grid is only used if it is specifically activated with the command --feature new_component_grid while starting the client.

This fix relates to sub-components that have been grouped together into a multi component. Specifically, this fix relates to the information that is displayed in the Properties view after having selected a sub-component in the grid. In the past, it was possible to change the path of the sub-component in the Basic information section. However, doing so caused the sub-component to break. The file path has therefore been disabled for sub-components. It can no longer be changed, since all sub-components of a multi component must be in the same group.

This fix relates to exclusive tags. In the past, if a user deleted the tag configuration in the menu Admin > Model > Tags, then the exclusive tag was still visible on the pool/tree where it was set. Furthermore, users were not able to remove the exclusive tag via the context menu. This behavior has been fixed.

This fix relates to the Edit with tab, which appears when editing a component. In the past, the Apply button remained deactivated, even after the user had edited the component and entered a history comment. This behavior has been fixed.