PRIMER 22.1
Example
Example
The figures below show the effect of recursive deletion. The entities selected by PRIMER with (left column) and without (right column) recursion are shown. In this example the user selected one part to be deleted.
- will sketch each of the entities that are to be deleted. ( may not be available for all entity types.)
- will quit the delete operation making no changes to the model.
- The user can toggle each of the entities using the and toggles so that they will be deleted or left as required.
- executes the deletion using the above rules and reports to the user the number of entities that have been deleted - see the lower pair of figures.
|
DELETE_RECURSIVE ON
|
DELETE_RECURSIVE OFF
|
|
|
| The left figure shows that recursive deletion has found a number of elements, nodes etc. |
Without recursion PRIMER finds the entities shown on the
right(ie the part only).
|
|
|
| Following the part and its associated data have been deleted on the left, since recursive deletion has picked up all the subordinate items. |
On the right nothing has been deleted since the part is"locked"
by its elements.
|