OLE for Retail POS API指南：OPOS-APG-Rel.1.1

5星 · 超过95%的资源需积分: 9 10 浏览量更新于2024-07-23 1 收藏 767KB PDF 举报

"此资源是关于OPoS API 110的参考文档，适用于POS系统开发。文档名为《OLE for Retail POS Application Guide - Rel. 1.1》，由Microsoft、NCR、Epson、Post Software International等公司联合编撰，旨在为零售领域的Windows 95、Windows NT或其它支持OLE的32位操作系统下的POS应用编程提供指导。" OPoS（Open Point of Sale）API 110是一个接口标准，它允许软件开发者创建与不同硬件设备交互的零售点（POS）应用程序。这个标准基于微软的OLE（Object Linking and Embedding，对象链接和嵌入）技术，使得在Windows环境下，软件可以无缝集成各种POS设备，如打印机、扫描枪、现金抽屉等。《OLE for Retail POS Application Guide》是这个标准的重要参考资料，其中包含了详细的API接口说明和使用指南。文档的第1.1版本发布于1996年4月22日，提供了关于如何在Windows 95和Windows NT系统上，以及其他支持OLE的32位操作系统中利用OLE for Retail POS进行应用开发的信息。开发者可以通过访问微软官方网站上的“Industry Solutions / Retail / Technologies”页面获取最新的修订版文档。此文档的内容可能涵盖了以下关键知识点： 1. OLE for Retail POS的基本概念和架构，解释了如何通过OLE技术实现硬件设备的集成。 2. API接口详解，包括各种设备类别的方法、属性和事件，如Cash Drawer的Open方法、Scanner的ScanData事件等。 3. 设备控制和数据交换的示例代码，帮助开发者理解如何在实际项目中应用这些接口。 4. 设备状态管理，如错误处理机制、设备检测和自动配置。 5. 开发流程和最佳实践，指导开发者如何有效地设计和测试POS应用程序。该文档还提醒读者，其中的信息可能会随时更新，建议定期检查微软网站以获取最新信息。同时，文档的版权分别归NCR Corporation、Microsoft Corporation、Post Software International和Seiko Epson Corporation所有，任何使用都需遵守版权规定。通过理解和掌握OPoS API 110及其应用指南，开发者可以构建出高效、稳定且兼容性强的POS系统，提高零售业务的运营效率。

16 OLE for Retail POS Application Guide Introduction

Document: OLE for Retail POS Application Guide - Rel. 1.1

Filename: OPOS-APG-(Rel-1.1).doc Author: crm/NCR

Page: 16 of 330

♦ Continue – Use only if the locus is InputWithData. This response

acknowledges the error and directs the Control to continue processing. The

Control remains in the error state, and will fire additional data events as

directed by the DataEventEnabled property. When all input has been

fired and the DataEventEnabled property is again set to TRUE, then

another ErrorEvent is fired with locus “InputNoData.”

“Continue” is the default response when the locus is “InputNoData.”

The Control ensures that while the application is processing an ErrorEvent, it

will not fire any other ErrorEvents.

OLE for Retail POS Controls Device Sharing Model 17

Document: OLE for Retail POS Application Guide - Rel. 1.1

Filename: OPOS-APG-(Rel-1.1).doc Author: crm/NCR

Page: 17 of 330

Device Sharing Model

The OLE for Retail POS device sharing model supports devices that are to be used

exclusively by one application

at a time, as well as devices that may be partially or

fully shared by multiple applications. (See “When Methods and Properties May Be

Accessed”, page 11, for other details.)

Exclusive-Use Devices

The most common device type is called an “exclusive-use device.” An example is

the POS printer. Due to physical or operational characteristics, this device can only

be used by one application at a time. The application must call the Claim method

to gain exclusive access to the device before most methods, properties, or events are

legal. Until the device is claimed, calling methods or setting properties cause an

OPOS_E_NOTCLAIMED error, and events are not fired to the application.

Should two closely cooperating applications want to treat an exclusive-use device in

a shared manner, then one application may claim the device for a short sequence of

operations, then release it so that the other application may use it.

When the Claim method is called again, settable device characteristics are restored

to their condition at Release. Examples of restored characteristics are the line

display’s brightness, the MSR’s tracks to read, and the printer’s characters per line.

State characteristics are not restored, such as the printer’s sensor properties.

Instead, these are updated to their current values.

Sharable Devices

Some devices are “sharable devices.” An example is the keylock. A sharable

device allows multiple applications to call its methods and access its properties.

Also, it may fire its events to all applications that have opened it. A sharable device

may still limit access to some methods or properties to an application that has

claimed it, or may fire some events only to this application.

One might argue that all devices should be defined as sharable to allow

This document assumes that an application consists of only one process. Multi-process

applications are possible to create but uncommon. Technically, device sharing is

performed on a process basis. However, with single-process applications we can view

sharing as application-level.

Note

OLE for Retail POS Controls Input Model 19

Document: OLE for Retail POS Application Guide - Rel. 1.1

Filename: OPOS-APG-(Rel-1.1).doc Author: crm/NCR

Page: 19 of 330

Input Model

The OLE for Retail POS input model supports event-driven input. When the

application is ready to receive input from the device, it sets the DataEventEnabled

property to TRUE. Then, when input is received (usually as a result of a hardware

interrupt), the Control generates a DataEvent. This event may include input status

information through a numeric parameter. The Control places the input data plus

other information as needed into device specific-specific properties just before the

event is fired.

Just before firing this event, OPOS disables further data events by setting the

DataEventEnabled property to FALSE. This causes buffering of further input

data by OPOS while the application processes the current input and associated

properties. When the application has finished the current input and is ready for

more data, it reenables events by setting DataEventEnabled to TRUE.

If the input device is an exclusive-use device, the application must both claim and

enable the device before the device begins reading input.

For sharable input devices, one or more applications must open and enable the

device before the device begins reading input. An application must call the Claim

method to request exclusive access to the device before OPOS will send data to it

using the DataEvent. If event-driven input is received, but no application has

claimed the device, then the input is buffered until an application Claims the device

(and the DataEventEnabled property is TRUE). This behavior allows orderly

sharing of the device between multiple applications, effectively passing the input

focus between them.

If OPOS encounters an error while gathering or processing event-driven input, then

it will fire an ErrorEvent to alert the application of the error condition. This event

is not fired until the DataEventEnabled property is TRUE, so that orderly

application sequencing occurs. Error events are fired with one or both of the

following loci:

剩余329页未读，继续阅读

cjtan2014

粉丝: 0
资源: 1

OLE for Retail POS API指南：OPOS-APG-Rel.1.1

OPOS开发源码pos machine industry to international standards, the source for the development of source OPOS control objects can be used directly

OPOS Assemblies for .NET

OPOS sample for 88IV

EPSON OPOS

VB.zip_EPSON OPOS 下载_OPOS开发_Opos vb_epson_opos

EPOSN OPOS ADK

EPSON OPOS手册

OPOS 1.9 安装目录

EPSON OPOS打印驱动

EPSON OPOS ADK PDF

最新资源