Searching/Deleting Unused Processes/Methods/Runnables
You cannot search for unused processes/methods/runnables in the entire project context in the same way as for unused elements. Instead, proceed as follows:
Do one of the following:
Generate code for your project.
Click
Compile generated Code.Start an experiment (
).Rebuild (
) the project.
Note
Build (
) can also work, but beware: if the component does not need to be regenerated, then no WBdl2 and WSm80 warnings will occur. Information, warning and error messages are displayed in the Messages tab of the ASCET monitor window. Unused processes/methods/runnables are indicated by the following messages:
Location in
monitorMessage
No.Message text
processes
<process> node
WBdl2
process "<process name>" (using specification) is not defined
methods
<method> node
WBdl2
method "<method name>" (using <*> specification) is not defined
Global Analysis
nodeIMdl93
method <method name> not used in this project
triggers in
state machines<trigger> node
WSm80
trigger "<method name>" not defined
Global Analysis
nodeIMdl93
method <trigger name> not used in this project
runnables
<runnable> node
WBdl2
runnable "<runnable name>" (using <*> specification) is not defined
To delete an unused process/method/runnable, proceed as follows:
In the ASCET monitor window, double-click a warning message with number WBdl2.
In case of a method, you can also double-click an information message with number IMdl93.
The parent component of the process/method/runnable opens. The process/method/runnable mentioned in the message is selected in the Outline tab.
Right-click the process/method/runnable and select Delete from the context menu.
To delete an unused state machine trigger, proceed as follows:
In the ASCET monitor window, double-click a warning message with number WSm80.
The parent state machine of the trigger opens.
- In the state machine editor, Outline tab, select the trigger mentioned in the warning message.
- Right-click the trigger and select Delete from the context menu.
See also
