Sensor definition
TODO: finish
Starting the method sensor definition
The method sensor definition process starts when a user presses the 'Add'-Button positioned in the top part. After that the bottom part folds out and the size of the top part will decrease. That means, the top part makes place available to the bottom part which is used to configure the method sensor.
Define a method sensor definition
The above picture shows the bottom part for the definition of a method sensor. Currently there are two sections available: Basic and Description. The division into sections allows additions in future versions which can be integrated as new sections.
The content of the second section Description should explain itself. The Basic-section contains a lot of settings (as you can see in the above picture) which will be explained in more detail:
- package/class/method: they describe the method you want to monitor. It's possible to use wild cards instead of define concrete names. Look at these pages for getting more information about the wild card usage: description and examples.
- sensors: The list contains the method sensors which will monitor the defined method. The following small dialog is used to add method sensor to the list:
- interface/superclass: Defines if the flag will be used. For more information about the flags see the description and the examples
- visibility: Only methods with the selected modifier will be monitored. The check boxes can be fold in and out.
- signature: This area can be fold in and out. If 'ignore signature' is unchecked, the parameter amount is defined by the number of list entries. The parameter order of the signature relates to the order of the list entries. Examples: List entries: none => method(); List entries: int, *, *Service => method(int, *, *Service)
TODO: complete this part
During the definition process 3 ways of assistance are provided to the user.
- Auto-completion (description)
- Code Library Content Viewer (description)
- use available definition (description)
