omron — .NET Control object

Screens and Graphics Configuring Events The Events tab provides a grid with the following fields: Configuration Dialog – Events Tab • Event : List all events available from the ActiveX object. • Parameters : The tags configured in this field are associated with the parameters of the event of the corresponding ActiveX object. If the event does not support any parameter, the fixed text is displayed in the Parameters field. Otherwise, you can type the tags associated with the parameters of the ActiveX object. When the event has more than one parameter, you can type one tag for each parameter, separating them by a comma (,). For example, TagA , TagB , TagC .

When the event is generated, either the value of the tags are written to the parameters of the event (input parameters), or the parameter values are written to the tags (output parameters). Tip: When you click the Browse button ( ), it will display the list of parameters supported by the event, allowing you to associate one tag with each parameter. • Script : The script configured in this field will be executed when the event is triggered by the ActiveX control. Tip: When you click the Browse button ( ), it will display a dialog with the complete script associated with the event. The main dialog displays only the expression configured in the first line of the script.

.NET CONTROL OBJECT .NET Components are designed according to the Microsoft .NET Framework, which is a standard for modular programming technologies. Because IWS is a .NET container, you can configure and run .NET Components in your project screens. The actual functions of a .NET Component are contained within a .NET Control object, which provides the configuration dialogs. .NET Components include the following interfaces: • Properties : Variables whose values can be read and/or written for your project (e.g., Object Color, FileName, URL, and so forth) • Methods :

Functions from the .NET Component that can be triggered by your project (e.g., open a dialog, execute a calculation, and so forth) • Events : Internal messages that can trigger the execution of expressions in your project (e.g., Mouse_Click, Download_Completed, and so forth) The properties, methods and events supported by each .NET Component vary according to the component's implementation. Caution: When using .NET Components in your project, make sure that the target system (runtime station) can support the same components and that they are properly installed and registered.

Your project includes links to the .NET Components; however, the installation of these components on the target system must be done separately. Furthermore, when .NET Components are used on screens open in remote Thin Clients, the .NET Components must also be manually installed on the Thin Client stations. The Microsoft Windows operating system installs a large selection of components by default, but additional components are offered by Page 196 InduSoft Web Studio