CCOs are implemented as ActiveX controls (OCX files) that can be used by any programming language that supports COM (Component Object Model), such as Visual Basic, C#, or C++. Each CCO corresponds to a device class defined by OPOS, such as POSPrinter, LineDisplay, or Scanner. A CCO exposes a set of properties, methods, and events that allow the application to control the device and receive notifications from it. For example, the POSPrinter CCO has properties such as CharacterSet, FontTypeface, and MapMode; methods such as PrintNormal, CutPaper, and RotatePrint; and events such as StatusUpdateEvent, ErrorEvent, and DirectIOEvent.
The current version of CCOs is 1.14.001, which was released in February 2015. This version supports all OPOS APIs from Release 1.01 through Release 1.14.1. The 1.14.001 CCOs can be used with applications built against previous CCO releases, beginning with the 1.6 CCOs. No rebuild is needed. This version contains several bug fixes and enhancements, such as adding OPOS Release 1.14.1 API support for Electronic Value Reader Writer (EVWR) device class, correcting memory leak and potential buffer overrun issues, updating license information, and digitally signing the CCOs, OPOS for .NET assemblies, and Windows Installer (.MSI) files.
Version 1.13 18 of CCOs was an earlier release that was available in December 2013. This version supported all OPOS APIs from Release 1.01 through Release 1.13. The 1.13 18 CCOs could be used with applications built against previous CCO releases, beginning with the 1.6 CCOs. This version contained several bug fixes and enhancements, such as adding OPOS Release 1.13 API support for Biometrics (BIO) device class, correcting an issue with Open method for some devices, updating license information, and digitally signing the CCOs and Windows Installer (.MSI) files.
CCOs are widely used by POS developers and vendors to create cross-platform and cross-device applications that can run on various operating systems and hardware configurations. CCOs provide a consistent and easy-to-use interface for accessing POS devices, while hiding the complexity and diversity of device drivers and protocols. CCOs also enable interoperability and compatibility among different POS products and systems.
References:
[MCS: OPOS Common Control Objects - Current Version]
[OPOS library v1.14 is not working as expected with x64 build of .net - Stack Overflow]
[Opos Common Control Objects Version 1.13 18 - OpenSea]
a7a7d27f09