Searching/Deleting Unused Methods/Triggers

You cannot search for unused methods (including actions in separate diagrams) and triggers in the state machine and its sub-components in the same way as for unused elements. Instead, proceed as follows:

Do one of the following:

Click Generate Code.
Click Compile generated Code.
Start an experiment ().

Information, warning and error messages are displayed in the Messages tab of the ASCET monitor window. Unused methods/triggers are indicated by the following messages:

	Location in monitor	Message No.	Message text
methods	<method> node	WBdl2	method "method name" (using <*> = Block Diagram or ESDL specification) is not defined
methods	Global Analysis node	IMdl93	method <method name> not used in this project
triggers in state machines	<trigger> node	WSm80	trigger "method name" not defined
triggers in state machines	Global Analysis node	IMdl93	method <trigger name> not used in this project

To delete an unused method, proceed as follows:
1. In the ASCET monitor window, double-click a warning message with number WBdl2.
  You can also double-click an information message with number IMdl93.
  The parent component of the method opens. The method mentioned in the message is selected in the Outline tab.
2. Right-click the method and select Delete from the context menu.
To delete an unused trigger, proceed as follows:
1. In the ASCET monitor window, double-click a warning message with number WSm80.
  The parent state machine of the trigger opens.
2. In the state machine editor, Outline tab, select the trigger mentioned in the warning message.
3. Right-click the trigger and select Delete from the context menu.