LonWorks-Temperature-Sensor.rar_lonworks_lonwork学习

================================================================================ Plug-in Framework Project : TemperatureSensor_03 Generated on 01 February 2002 ================================================================================ The LNS(tm) Device Plug-in Wizard has created this plug-in application for you. This plug-in software is a fully functioning LNS device plug-in. You may customize this plug-in to tailor it to your device and further simplify device installation for your users. The only required change to the code generated by the plug-in wizard is to delete MsgBox() function calls in the ProcessLonMarkObjectCommand() and ProcessDeviceCommand() functions within fMain.frm. These MsgBox() calls identify where you can start adding your customization code. The following comments describe the code generated by the plug-in wizard and identify functions that you can customize. Functions that require changes if you add any controls that are not added by the plug-in wizard are identified. Refer to the LNS Plug-In Programmer's Guide for more details about customizing the code generated by the wizard. Search for "TO DO:" to find possible changes. <-- fHidden.frm --> This form is an invisible container for the ActiveX Common Dialog control, that is used to select the XIF file. This feature is used by the RegisterSupportedCommands function if an appropriate DeviceTemplate is not found within the current network database. * This module is complete and does not require changes. <-- fMain.frm --> The fMain form is where most of the wizard-defined and user-defined action takes place. The form contains: 1 Tabbed Dialog Control 6.0 (SP5). This control accommodates the elements used by the monitoring and control feature provided by the plug-in. N text control(s): When generating a user interface with the user interface editor, a text control is added for each network variable and configuration property, grouped in tabs according to your selection in the user interface editor. Apply and Cancel buttons. An EchLog control: This is an ActiveX control named EchLog, similar to a ListBox. The EchLog control is used to record all user and system events. An EchStsBar control: This is an ActiveX control named EchStsBar, similar to a standard status bar. EchStsBar displays the device name, the device's state, the functional blocks, and status and alarm information for each functional block. Device Template Label. The device template label displays the name of the LNS device template the plug-in software applies to. The Wizard generates the following code: ProcessLonMarkObjectCommand or ProcessDeviceCommand: Handlers to process a command that applies to a functional block (LcaLonMarkObject), or an entire device (LcaAppDevice), respectively. The default implementation contains code to perform a complete resource rile look-up to adjust the scope of the implemented functional blocks. It also contains pre-defined code to set the device template label and to initialize the device. Also contains a MsgBox() function call, reminding you that these handlers are subject to review and enhancement; at a minimum, you must remove the MsgBox() function calls. * TO DO: You can add code to enhance the plug-in functionality and to tailor the plug-in software to meet the requirements of your device and its intended user. txtNvi_KeyPress and txtCp_KeyPress event handlers: These event handlers mark changes in the relevant text controls when using the wizard-generated user-interface. The plug-in code tries to commit pending changes when Apply is clicked. * TO DO: You must add similar handlers for any controls that you add to the interface and were therefore not added by the plug-in wizard. You must add code for your controls to commit pending changes from within the Apply handler. cmdApply_Click and cmdCancel_Click: Commit or cancel the changes pending in the altered text controls. * TO DO: Add your Apply and Cancel methods if you add any controls that are not added by the plug-in wizard. For example, you may add controls for monitoring and control network variable fields or configuration property fields. EnableMonitor: Initialize monitoring for network variables and configuration properties. * This code is complete and does not normally require changes. smnuMonitor_Click: Menu handler to control monitoring of network variables and configuration properties. * This code is complete and does not normally require changes. EnableControls: Prepares the text controls that are used for monitoring. * TO DO: Add your own code if you add any controls that are not added by the plug-in wizard. tabData_Click: This click handler is being activated when the tab page changes, and ensures that only items on the currently visible tab page are monitored. * TO DO: Modify this code if you wish to permanently monitor any network variables. Be sure to manage your network bandwidth utilization if you permanently enable monitoring on many network variables. SelectActiveTab: Set the active tab during start-up. The plug-in attempts to set the tab to the most appropriate page. In case all network variables and configuration properties that belong to a single functional block are hosted on the same tab page, the plug-in will then automatically select this page whenever it receives a command associated with the relevant functional block. It might start with the incorrect page if the network variable or configuration property that belong to one functional block are being spread across multiple tab pages. * TO DO: You can modify the code if the wrong tab is selected when you have multiple tab pages with network variables and configuration properties from the same functional block. DrfLookUp: Function to set the functional block scope using the LNS LonMark Objects Mode property. * This code is complete and does not normally require changes. lcaOS_OnNvUpdateError: Log errors for monitored network variables. * This code is complete and does not normally require changes. lcaOS_OnNetworkVariableUpdate: Calls your update handler. * This code is complete and does not normally require changes. NetworkVariableUpdateReceived: This is a default implementation of an update handler that displays the new values in simple text controls. * TO DO: Changes are not required, but you can customize the code and user interface to your specifics needs. InitDevice: Used to determine the device state. Also collects initial values for items being monitored. * TO DO: Changes are not required, but you can add your own, device-specific, initialization code here, if any. SetDevTemplateLabel: Set the caption for the Device Template label. * This code is complete and does not require changes. ReadInitValues: Adjust formatting options for network variables and configuration properties, and retrieve initial values for configuration properties. * TO DO: Changes are not required, but you can modify the code as needed for a different format or for using custom controls. <-- fProgress.frm --> The form fProgress.frm is a pop up dialog to show status or progress during the plug-in methods. You should show this progress screen for any function that requires a noticeable execution time such as, for example, downloading an application image to a LonWorks device. * TO DO: Changes are not required, but you can customize this form with your logo or progress icon. <-- fRegisterPlugIn.frm --> This is the interface provided for the plug-in when it runs as a standalone executable, offering a simple user interfac