Previous steps showed basic Management functionalities as well as Simulink functionalities for MODULES :
This step 0h deals with module removal.
User versions vU are not devoted to be maintained as they are temporary versions, (contrary to capitalized versions, see step 6).
Then, user may delete some old transient user versions :
First, select at least one version to make the Delete button enabled and press Delete :
Then a rank 2 appears, asking the user to confirm the deletion :
The acknowledgment message says that module has been saved in the Recyclebin folder :
At this placement on the hard drive, a zip file is saved containing the just deleted module.
This file is in fact an export of the module. Export functionality is part of the Community functionalities explained in step 6.
To know how to recover this file, go specifically to this step 6.
Remark : before deletion, MTX checks that module is not in use. If it's the case (for example the library of a module is used), MTX says that the module is not free and can not proceed the requested deletion process.
Several deletions are possible at once by selecting several versions :
After deletion, these modules are available in the Recyclebin folder as export files (see step 6) :
Modules can be selected discontinuously using the Ctrl key :
A row is selected as soon as one column or several columns of this row are selected, i.e. cell in blue.
For example, these selections all select the second row :
Classical combination 'Ctrl + A' select all the elements :
There is a Sort functionality :
At the first level, there are possibilities :
Sort by
Only
Sort by enables sort by :
versions : rows are sorted by versions
origin : rows are sorted by their origin version. Origin version comes from Capitalization process, explained in Step 6 : Community functionalitites
who : rows are sorted regarding who created the module
when : rows are sorted regarding when the module has been created
Only enables to list only :
Capi : only capitalized versions are listed. Capitalied version comes from Capitalization process, explained in Step 6 : Community functionalitites
User : only user versions are listed, i.e. vU versions
All : both Capi and User versions are listed
Current parameter of the sort is available in the tip of the Sort button :
Next step 0i explaine the modules copy capability.