User manual
Table Of Contents
- Cover
- Title Page
- Table of Contents
- List of Tables
- List of Figures
- Preface
- Software Installation
- U.S. Export ControlLaws Compliance
- Publication Updates
- Symbols Used in This Document
- Safety
- Quick Start
- Description
- Operation
- Special Topics
- Host Interface
- Calibration and Warranty
- Appendix A: Specifications
- Index
FieldMaxII-TO User Manual
44
cFM2Listener class and IFM2Listener interface—An
object class that dispatches meter USB connect/discon-
nect and data event notifications to the application code.
Notifications are permitted by means of a user-imple-
mented callback object that is passed to this object. It
implements the IFM2Listener interface. One
cFM2Listener object is needed to manage all meters with
which the program will communicate.
cFM2ScanUSBForChange class—An object class that is
the engine for capturing meter USB connect and discon-
nect status changes. The cFM2Listener object is passed
to this object to provide a means of sending USB
connection status changes to the application code via the
listener. One cFM2ScanUSBForChange object is needed
to manage all meters with which the program will
communicate.
cFM2ScanForData class—An object class that is the
engine for capturing meter data transmissions. One
cFM2ScanForData object is needed to manage all meters
with which the program will communicate.
cFM2Notify class—A callback object that implements
the IFM2DeviceEvents interface. The application code is
responsible for providing the code and instantiating this
object (that is, implementing the class and instantiating
the class object). All status change events and data trans-
missions are channeled through this object to the appli-
cation code. One cFM2Notify object is needed for all
meters with which the program will communicate.
cFM2Device class—An object class that abstracts
configuration and status access to a meter. Configuration
is accessed by calling any of the numerous
cFM2Device.<parameter>Command() methods. Status