 Name
Name of the Context inside the Knowledge.
This name can be used to retrieve the Context (instance) in case user wants to stop the processing or modify some parameters from source code.
|
|
 Knowledge
Name of the Knowledge the Context belongs to. Read only value.
|
|
 Entry Point
Use this button to access the Entry Point window (can also be opened from the diagram using double click on the Entry Point symbol).
|
|
 Exit Point
Use this button to access the Exit Point window (can also be opened from the diagram using double click on the Exit Point symbol).
|
If grayed out, that means the Point is not defined.
|
|
|
 Cycling
Check this to enable the runtime cycling of the Context (meaning, the Rules part).
The frequency list provided is according to the RTC base definition (a Context cannot cycle faster than the RTC).
If you need a user defined frequency not listed, take the highest frequency and add your own frequency divider code.
|
|
 Throw Event
When the Context is over (and if Perform mode is not Nothing), an event can be raised.
Click here to set (or unset) the event.
|
|
 Rules
List of all the rules defined in the context.
Click on each of them to edit them.
|
|
 Properties
Display the property window of the selected Rule in the list (7).
|
|
 Delete
Delete the selected Rule of the list (7).
|
|
 Definitions
Put here all the includes and structures that might be needed by the code of the Rules.
Definition part is put in the generated header file.
|
|
 Declarations
Add here all the variables needed into the Context to be used by the Rules.
They will not generate interface so, needless to use //&& here.
|
|
 Initialization
This part will be used at different phases of the simulation.
Use the RESET part to initialize your variables.
|
Refer to the Developer Guide for more details on system phases/events.
|
|
|
 Methods
Put here the methods defined in the Declaration part (if any). Leave it empty otherwise.
|
|
 Help
Any description of the Context can be put here and will be used for the automatic document generation (see Make Documents)
|
|