手写开发通用接口标准文档资源-CSDN文库

Wintab

Tablet

需积分: 22 168 浏览量 2018-04-12 10:15:50 上传评论收藏 344KB PDF 举报

资源推荐

资源详情

资源评论

file:///C/Users/sqqdf/Desktop/Wintab_v140.html[2017/8/18 16:24:33]

Wacom Technology Corp.

Wintab Interface Specification 1.4:

16-bit and 32-bit API Reference

Revised October, 2010

This specification was developed in response to a perceived need for a standardized programming interface to digitizing tablets, three

dimensional position sensors, and other pointing devices by a group of leading digitizer manufacturers and applications developers. The

availability of drivers that support the features of the specification will simplify the process of developing Windows application programs that

incorporate absolute coordinate input, and enhance the acceptance of advanced pointing devices among users.

This specification is intended to be an open standard, and as such the text and information contained herein may be freely used, copied, or

distributed without compensation or licensing restrictions.

Address questions and comments to:

Wacom Technology Corporation

1311 SE Cardinal Court

Vancouver, WA 98683

USA Tel: ++1-360-896-9833

For Wintab programming developer support questions, send email to: developer@wacom.com

For Wintab samples and documentation, visit: http://us.wacom.com/en/developerrelations/windows

Ø For general questions regarding Wacom tablet usage, visit: http://www.wacom.com and search for "Product Support".

Contents

1. BACKGROUND INFORMATION

1.1. FEATURES OF DIGITIZERS

1.2. THE WINDOWS ENVIRONMENT

2. DESIGN GOALS

2.1. USER CONTROL

2.2. EASE OF PROGRAMMING

2.3. TABLET SHARING

2.4. TABLET FEATURE SUPPORT

3. DESIGN CONCEPTS

3.1. DEVICE CONVENTIONS

3.2. DEVICE INFORMATION

3.3. TABLET CONTEXTS

3.4. EVENT PACKETS

file:///C/Users/sqqdf/Desktop/Wintab_v140.html[2017/8/18 16:24:33]

7.2.2.

Information Categories and Indices (1.1 modified)

7.3. CONTEXT DATA STRUCTURES

7.3.1. LOGCONTEXT (1.1 modified)

7.4. EVENT DATA STRUCTURES

7.4.1. PACKET (1.1 modified)

7.4.2. ORIENTATION

7.4.3. ROTATION (1.1)

APPENDIX A. USING PKTDEF.H

APPENDIX B. EXTENSION DEFINITIONS (1.4 MODIFIED)

B.1. EXTENSIONS PROGRAMMING

Extensions Programming Notes

B.2. OUT OF BOUNDS TRACKING

OBT Programming

Information Category

Turning OBT On and Off

B.5. CURSOR MASK

CSRMASK Programming

Information Category

B.6. EXTENDED BUTTON MASKS

XBTNMASK Programming

Information Category

B.7. EXPRESS KEYS EXTENSION (1.4 MODIFIED)

B.8. TOUCH STRIPS AND TOUCH RINGS EXTENSIONS (1.4 MODIFIED)

B.9. EXTENSION STRUCTURES (1.4 MODIFIED)

EXPKEYSDATA structure

SLIDERDATA structure

EXTPROPERTY structure

APPENDIX C. ADDITIONAL FEATURES (1.4 MODIFIED)

C.1. ERASER

C.2. TILT

C.3. DUAL TRACK

C.4. UNIQUE ID

C.5. AIRBRUSH FINGERWHEEL

C.6. 4D MOUSE ROTATION

C.7. 4D MOUSE THUMBWHEEL

1. BACKGROUND INFORMATION

This document describes a programming interface for using digitizing tablets and other advanced pointing devices with Microsoft Windows

Version 3.0 and above. The design presented here is based on the input of numerous professionals from the pointing device manufacturing and

Windows software development industries.

In this document, the words "tablet" and "digitizer" are used interchangeably to mean all absolute pointing or digitizing devices that can be

made to work with this interface. The definition is not limited to devices that use a physical tablet. In fact, this specification can support

devices that combine relative and absolute pointing as well as purely relative devices.

The following sections describe features of tablets and of the Windows environment that helped motivate the design.

1.1. Features of Digitizers

Digitizing tablets present several problems to device interface authors.

· Many tablets have a very high report rate.

file:///C/Users/sqqdf/Desktop/Wintab_v140.html[2017/8/18 16:24:33]

· Many tablets have many configurable features and types of input information.

· Tablets often control the system cursor, provide additional digitizing input, and provide template or macro functions.

1.2. The Windows Environment

Programming for tablets in the Windows environment presents additional problems.

· Multitasking means multiple applications may have to share the tablet.

· The tablet must also be able to control the system cursor and/or the pen (in Pen Windows).

· The tablet must work with legacy applications, and with applications written to take advantage of tablet services.

· The tablet driver must add minimal speed and memory overhead, so as many applications as possible can run as efficiently as

possible.

· The user should be able to control how applications use the tablet. The user interface must be efficient, consistent, and

customizable.

2. DESIGN GOALS

While the tablet interface design must address the technical problems stated above, it must also be useful to the programmers who will

write tablet programs, and ultimately, to the tablet users. Four design goals will help clarify these needs, and provide some criteria for

evaluating the interface specification. The goals are user control, ease of programming, tablet sharing, and tablet feature support.

2.1. User Control

The user should be able to use and control the tablet in as natural and easy a manner as possible. The user's preferences should take

precedence over application requests, where possible.

Here are questions to ask when thinking about user control as a design goal:

· Can the user understand how applications use the tablet?

· Is the interface for controlling tablet functions natural and unobtrusive?

· Is the user allowed to change things that help to customize the work environment, but prevented from changing things over

which applications must have control?

2.2. Ease of Programming

Programming is easiest when the amount of knowledge and effort required matches the task at hand. Writing simple programs should

require only a few lines of code and a minimal understanding of the environment. On the other hand, more advanced features and

functions should be available to those who need them. The interface should accommodate three kinds of programmers: those who wish to

write simple tablet programs, programmers who wish to write complex applications that take full advantage of tablet capabilities, and

programmers who wish to provide tablet device control features. In addition, the interface should accommodate programmers in as many

different programming languages, situations, and environments as possible.

Questions to ask when thinking about ease of programming include:

· How hard is it to learn the interface and write a simple program that uses tablet input?

· Can programmers of complex applications control the features they need?

· Are more powerful tablet device control features available?

· Can the interface be used in different programming environments?

· Is the interface logical, consistent, and robust?

2.3. Tablet Sharing

file:///C/Users/sqqdf/Desktop/Wintab_v140.html[2017/8/18 16:24:33]

In the Windows environment, multiple applications that use the tablet may be running at once. Each application will require different services.

Applications must be able to get the services they need without getting in each others' way.

Questions to ask when thinking about tablet sharing include:

· Can tablet applications use the tablet features they need, independent of other applications?

· Does the interface prevent a rogue application from "hijacking" the tablet, or causing deadlocks?

· Does the sharing architecture promote efficiency?

2.4. Tablet Feature Support

The interface gives standard access to as many features as possible, while leaving room for future extensions and vendor-specific

customizations. Applications should be able to get the tablet information and services they want, just the way they want them. Users

should be able to use the tablet to set up an efficient, comfortable work environment.

Questions to ask when thinking about tablet feature support include:

· Does the interface provide the features applications need? Are any commonly available features not supported?

· Does the interface provide what users need? Is anything missing?

· Are future extensions possible and fairly easy?

· Are vendor-specific extensions possible?

3. DESIGN CONCEPTS

The proposed interface design depends on several fundamental concepts. Devices and cursor types describe physical hardware configurations.

The interface publishes read-only information through a single information interface. Applications interact with the interface by setting up

tablet contexts and consuming event packets. Applications may assume interface and hardware control functions by becoming tablet

managers. The interface provides explicit support for future extensions.

3.1. Device Conventions

The interface provides access to one or more devices that produce pointing input. Devices supported by this interface have some common

characteristics. The device must define an absolute or relative coordinate space in at least two dimensions for which it can return position

data. The device must have a pointing apparatus or method (such as a stylus, or a finger touching a touch pad), called the cursor, that

defines the current position. The cursor must be able to return at least one bit of additional state (via a button, touching a digitizing

surface, etc.).

Devices may have multiple cursor types that have different physical configurations, or that have different numbers of buttons, or return

auxiliary information, such as pressure information. Cursor types may also describe different optional hardware configurations.

The interface defines a standard orientation for reporting device native coordinates. When the user is viewing the device in its normal

position, the coordinate origin will be at the lower left of the device. The coordinate system will be right-handed, that is, the positive x axis

points from left to right, and the positive y axis points either upward or away from the user. The z axis, if supported, points either toward

the user or upward. For devices that lay flat on a table top, the x-y plane will be horizontal and the z axis will point upward. For devices

that are oriented vertically (for example, a touch screen on a conventional display), the x-y plane will be vertical, and the z axis will point

toward the user.

3.2. Device Information

Any program can get descriptive information about the tablet via the WTInfo function. The interface specifies certain information that

剩余52页未读，继续阅读

评论收藏

内容反馈

sqqdftb

粉丝: 0
资源: 5

手写开发通用接口标准文档

api接口文档模板

科大讯飞手写识别接口对接

uWintab：用于Unity的Wintab API插件

数位板压力测试

汉王手写板web开发

汉包手写板接口包

手写板支持的笔式交互界面的研究与应用

c#手写笔记文档 适用于c#实战开发

扫描卡纳达语文档中的自动偏斜检测和校正：任何无噪声手写扫描文档的偏斜检测和自动线对齐-matlab开发

用于线多边形提取的多维 Seamcarve：提取手写文档中以任何方向书写的检测基线周围的多边形。-matlab开发

一个基于canvas开发,封装于Vue组件的通用手写签名板

汉王创艺掌门系列手写屏 开发文档与示例

NTKO文档在线编辑控件独立安装包4.0.6.5(适合TA2009\2010\2011版本)

NTKO文档在线编辑控件4.0.1.2

NTKO OFFICE痕迹保留文档控件.rar

iWeb Office2000[Domino版]

非常不错的手写输入法源码

非常简单的手写板JS

restful 接口开发规范（RESTfulAPIdesignguide）

汉王开发文档

JS实现的手写输入

AT89C51设计LCD1602显示DS1302实时日历时钟毕业论文文档+软件源码.rar

iWebOffice2003(PHP OCX版)

C#微软培训资料

MFC Windows程序设计(第2版修订版)--源代码

MFC Windows程序设计(第2版修订版)--详细书签版2卷

WINCE6.0 m蒙恬手写输入法解决方案（蒙恬输入法+sipapi）

简单手写字符识别（简单web界面手写）

VBTablet - a WinTab Tablet API wrapper-开源

最新资源

c#手写笔记文档适用于c#实战开发

汉王创艺掌门系列手写屏开发文档与示例