Touch Tab Enhance

8/14/2019 Touch Tab Enhance

1/17

Developer Enhancements toWindows for Touch and Tablet

November 5, 2008

Abstract

Tablet and touch enhancements in Windows 7 offer exciting newopportunities to create hardware and devices that stand above the

competition. This paper describes the new tablet and touch featuresin the Windows 7 operating system and the Windows Server 2008R2 operating system.

This information applies for the following operating systems:Windows 7Windows Server 2008 R2

For the latest information, see:

http://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspx
http://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspxhttp://www.microsoft.com/whdc/device/input/touch_tab_enhance.mspx


2/17

- 2

Disclaimer: This is a preliminary document and may be changed substantially prior to final commercialrelease of the software described herein.

The information contained in this document represents the current view of Microsoft Corporation on theissues discussed as of the date of publication. Because Microsoft must respond to changing marketconditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannotguarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS,IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights undercopyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, ortransmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), orfor any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rightscovering subject matter in this document. Except as expressly provided in any written license agreementfrom Microsoft, the furnishing of this document does not give you any license to these patents, trademarks,copyrights, or other intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mailaddresses, logos, people, places and events depicted herein are fictitious, and no association with any realcompany, organization, product, domain name, email address, logo, person, place or event is intended orshould be inferred.

2008 Microsoft Corporation. All rights reserved.

Microsoft, MSDN, Windows, Windows Server, and Silverlight are either registered trademarks or trademarksof Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respectiveowners.



3/17

- 3

Document History

Date ChangeNovember 5,2008

First publication

Contents

Introduction........................................................................................4The Math Input Control.......................................................................4

Creating the Math Input Control......................................................5Include Headers and Libraries for the Math Input Control...........5Declare and Initialize the Control Pointer.....................................5Show the Control.........................................................................6

Customizing the Math Input Control................................................6Changing the Displayed Buttons..................................................6Changing the Control Caption......................................................8Changing the Control's Preview-Area Size...................................8

Multitouch for Windows 7...................................................................9Creating Custom Dictionaries for Handwriting Recognition..............10

Compiling a Word List....................................................................10Explanation of Options...............................................................11Defaults.....................................................................................12Examples...................................................................................12

Installing a Compiled Custom Dictionary.......................................12Running HwrReg.exe in Check/Install Mode...............................13Running HwrReg.exe in List/Remove Mode................................13

General Notes on Custom Dictionaries..........................................14Server-Side Recognition....................................................................15



4/17

Introduction - 4

Introduction

The Windows 7 and Windows Server 2008 R2 will introduce mathinput control, custom dictionaries, and multitouch support toWindows operating systems. These features will enhance tablet

functionality and will enable new applications that support practicalscenarios for end users:

Math input control will allow input of math formulas and functionsfrom handwritten text.

To improve text recognition, Windows 7 and WindowsServer 2008 R2 will support custom dictionaries, so thatadministrators can directly enable support for word lists.

Multitouch will support input from multiple touch sources throughnew window messages, plus a gesture-recognition API thatsupports panning, zooming, and rotating.

Windows Server 2008 R2 will support server-side recognition of forminput and will also support custom dictionaries for server-siderecognition. With the addition of these features, developers andadministrators will be able to create and customize powerfulapplications that support handwriting recognition from the serverside.

Introduction 2008 Microsoft Corporation. All rights reserved.


5/17

The Math Input Control - 5

The Math Input Control

The Windows 7 operating system will support math input from themath input panel (MIP), the new math-specific equivalent of the textinput panel. Many applicationseven legacy applicationswill beable to take advantage of the MIP without modification, because

users will be able to directly trigger this input application fromWindows 7. The following figure shows one scenario of usage for themath input control, in which a user takes notes, inks them into apen-enabled document, and then copies them into anotherapplication as symbolic input.

The math input control will let developers integrate the functionalityof the MIP much more directly within their applications. Compared todata input with traditional methodssuch as browsing throughsymbol menus or memorizing keyboard shortcutsentering data byusing the math input control is much more intuitive and natural. Withits well-implemented integration into applications, users shouldnotice the improved experience that math input control provides.

Developing applications that take advantage of the math inputcontrol is very easy in Windows 7. This section gives a few examplesof typical tasks that Windows 7 developers may want to performwhen integrating the math input control into their applications.

Creating the Math Input ControlIn this section, you will learn how to create the math input controlfrom application code. This creation procedure is typically performedwhen the programmer expects a user to enter formulaic data.

To create the math input control

1. Include the headers and libraries for the math input control.

2. Declare and initialize the control pointer.

The Math Input Control 2008 Microsoft Corporation. All rights reserved.


6/17


3. Show the control.

Include Headers and Libraries for the Math Input Control

Place the following at the top of code that uses the math inputcontrol:

// includes for implementation

#include "micaut.h"

#include "micaut_i.c"

This code will add support for the math input control to yourapplication.

Declare and Initialize the Control Pointer

After you have included the headers for your control, you can declarethe control pointer and initialize it with a call to the CoInitializefunction. This call creates a handle to the math input controlinterface. The following code can be placed in a class or as a global

variable in your application's implementation:CComPtr g_spMIC; // Math Input Control

The following code shows how to call CoInitialize on the controlpointer.

HRESULT hr = CoInitialize(NULL);

hr = g_spMIC.CoCreateInstance(CLSID_MathInputControl);

After you call CoInitialize on the control pointer, you have areference to the control and can access the control's methods. Forexample, you could enable the extended set of controls as shown inthe following example:

hr = g_spMIC->EnableExtendedButtons(VARIANT_TRUE);

Show the Control

The control does not automatically appear after you create it. Toshow the control, call the Show method on the control referencethat you created in the previous step. The following codedemonstrates how the Show method can be called:

hr = g_spMIC->Show();

http://c/sd/Client/Main/tablet/tablet/imathinputcontrol_show.xmlhttp://c/sd/Client/Main/tablet/tablet/imathinputcontrol_show.xmlhttp://c/sd/Client/Main/tablet/tablet/imathinputcontrol_show.xmlhttp://c/sd/Client/Main/tablet/tablet/imathinputcontrol_show.xml


7/17


After the control shows, it resembles the following figure.

Note that the extended set of buttons is enabled, so that Redo andUndo are available.

Customizing the Math Input Control

This section explains three ways of customizing the math inputcontrol's appearance to better suit your application:

Changing the displayed buttons.

Changing the control caption.

Changing the control's preview-area size.

Changing the Displayed ButtonsYou can change the buttons that appear on the math input control sothat the control has extended functionality or appears smaller on thescreen. Enabling the extended button set shows the Redo and Undobuttons. The following code shows how to enable the extendedbutton set:

void CMath_Input_Control_testDlg::OnBnClickedToggleBtns()

{

static bool enabled = true;

HRESULT hr = S_OK;

hr = g_spMIC->Hide();if(!enabled){

if (SUCCEEDED(hr)){

hr = g_spMIC->EnableExtendedButtons(VARIANT_TRUE);

enabled = true;

}

}else{

if (SUCCEEDED(hr)){

hr = g_spMIC->EnableExtendedButtons(VARIANT_FALSE);



8/17


enabled = false;

}

}

if (SUCCEEDED(hr)){

hr = g_spMIC->Show();

}}

The following figure shows the control with the extended set ofbuttons.

The following figure shows the control without the extended set ofbuttons.



9/17


Changing the Control Caption

You can change the control caption for the math input control, to setthe caption on the math input control's window. The following codeshows how to set the caption:

void CMath_Input_Control_testDlg::OnBnClickedSetCaption()

{

g_spMIC->Hide();

CComBSTR cap1(L"Some Caption Text");

g_spMIC->SetCaptionText((BSTR)cap1);

g_spMIC->Show();

}

The following figure shows the control after the caption has been set.

Changing the Control's Preview-Area Size

You can customize the math input control so that the controlexplicitly sets its preview-area size. This creates a larger area inwhich the math formulas appear. The following code shows how toset the preview area size:

void CMath_Input_Control_testDlg::OnBnClickedSetPreviewAreaSize()

{

LONG height = 200;

HRESULT hr = S_OK;

hr = g_spMIC->SetPreviewHeight(height);

}



10/17


The following figures show a control with differently sized previewareas.

Multitouch for Windows 7

New hardware and API elements in the Windows 7 operating systemwill allow applications to receive multitouch input. This ability lets anapplication detect and respond to multiple simultaneous touch pointson the applications visible surface. Functionality for this feature in

Windows 7 will be provided by a new set of dedicated windowmessages that report touch-down, touch-up, and touch-moveactions. The new messages report action and position of touchpoints, with unique identification of simultaneous touch points.

The messages will be generated by pen or touch raw-inputprocessing, which is currently performed by the Tablet platform'sWindows Ink Service Platform Tablet Input Subsystem (WISPTIS)process and which will be delivered to a target application.

Multitouch for Windows 7 2008 Microsoft Corporation. All rights reserved.


11/17

Multitouch for Windows 7 - 11

In addition to the new input messages, multitouch gesture messageswill be added to the existing list of window messages. Messagingsupport for multitouch and multitouch gestures will function throughnew window messages. Those messages will be sent or posted bythe Tablet WISPTIS process to appropriate application windows whenuser input is recognized as a gesture. Dedicated API functions

encapsulate the details for creation and consumption of thesemessages. This is done so that the information that is associatedwith the message can change in the future without requiringdevelopers to update applications that already consume thismessage.

By applying the new multitouch functionality that will be madeavailable in Windows 7, developers can create applications that fallinto the following three tiers of specialization:

Applications in the first tier have no optimized support formultitouch. These applications will use generic handlers forgesture input and will translate those messages into windowautomation.

Applications in the second tier have some optimization forspecific messages. For example, these applications will use thecenter point of a pinch or zoom gesture, rather than zoom directlyto the center of a picture.

Applications in the third tier are full multitouch applications.These applications will be designed specifically for use only onmultitouch hardware, for example, a multitouch game wheremultitouch gestures and multiple input points are used tomanipulate objects on screen.

The Touch and Tablet folder in the WinHEC media kit contains acompiled Help (.chm) file with more information about this newfunctionality. This .chm file discusses multitouch development andindicates the API elements that are new for multitouch support.

Creating Custom Dictionaries for Handwriting Recognition

In Windows 7 and Windows Server 2008 R2, the accuracy ofhandwriting recognition can be significantly improved by usingcustom dictionaries. These dictionaries supplement or replacesystem dictionaries that are used for handwriting.

Note that custom dictionaries can be installed for a language only if

the handwriting recognizer for that language is installed.

Setting up a custom dictionary for handwriting has the following twosteps:

Compile a word list. The compilation creates a compiled custom-dictionary (.hwrdict) file.

Install the compiled custom dictionary.

Creating Custom Dictionaries for Handwriting Recognition 2008 Microsoft Corporation. All rights reserved.


12/17

Creating Custom Dictionaries for Handwriting Recognition - 12

Compiling a Word List

The word list to be compiled must be in plain-text format and shouldbe saved by using a Unicode encoding. Other encodings will notwork. Each line of the text file is taken as a single entry in thedictionary. Multiword unitsentries that contain one or more spaces

are allowed. Spaces at the beginning or end of a line are ignored.A custom dictionary is compiled from a command line. To compile adictionary, open a command window, navigate to the folder thatcontains the word list, and then run HwrComp.exe with the desiredcommand-line options.

The following code shows the usage syntax for the command-lineoptions:

Usage: hwrcomp [-lang ] [-type ]

[-comment ]

[-o ]

Explanation of Options

-lang The specified locale name is assigned to the compiled custom-dictionary file. The argument has the formlanguage-REGION. An example of this is en-US, which signifiesthe English language in the United States region. For examples ofthis form, see Locale Identifier Constants and Strings in theMSDN library.

-type The option argument is a single-string concatenation of

the resource's useas either the main word list (PRIMARY) or asa supplement to the main word list (SECONDARY)followed bythe actual word-list name to which the resource is applied (suchas DICTIONARYor SURNAME).

Possible type values include the following:

PRIMARY-CITYNAME-LIST

PRIMARY-COUNTRYNAME-LIST

PRIMARY-COUNTRYSHORTNAME-LIST

PRIMARY-DICTIONARY

PRIMARY-GIVENNAME-LIST

PRIMARY-STATEORPROVINCE-LIST

PRIMARY-STREETNAME-LIST

PRIMARY-SURNAME-LIST

SECONDARY-CITYNAME-LIST

SECONDARY-COUNTRYNAME-LIST

SECONDARY-COUNTRYSHORTNAME-LIST

http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137


13/17


SECONDARY-DICTIONARY

SECONDARY-EMAILSMTP-LIST

SECONDARY-EMAILUSERNAME-LIST

SECONDARY-GIVENNAME-LIST

SECONDARY-STATEORPROVINCE-LIST SECONDARY-STREETNAME-LIST

SECONDARY-SURNAME-LIST

SECONDARY-URL-LIST

If a type value starts with the PRIMARYprefix, the compileddictionary, once installed, replaces the system dictionary. ThePRIMARY-DICTIONARYvalue represents the main systemdictionary for the given language. Note that replacing a systemdictionary does nothing to the original system-dictionary contentbecause the replacement is in effect only until the custom

dictionary is removed.If a type value starts with the SECONDARYprefix, the compileddictionary supplements the system dictionary without replacingit.

-commentThe specified comment is compiled into the dictionary file. Thecomment must be a single string that does not exceed 64characters.

-oOutput is written to the file name that is specified by.

If this option is missing, the output file name is derived from theoriginal input file name, with the input-file extension replaced by.hwrdict.

Defaults

If no parameters are specified, the default option values are thefollowing:

-lang-type SECONDARY-

DICTIONARY

Examples

The following command compiles the mylist1.txt input file, appliesthe default option values, and creates the mylist1.hwrdict outputfile:

hwrcomp mylist1.txt



14/17


In contrast, the following command compilesmylist1.txt intomyrsrc1.hwrdict, but assigns English (US) (en-US) as the languageand SECONDARY-DICTIONARYas the type:

hwrcomp lang en-US type SECONDARY-DICTIONARY o myrsrc1 mylist1.txt

Installing a Compiled Custom Dictionary

HwrComp.exe creates an .hwrdict file, which is in a binary formatthat a handwriting recognizer can use. This file can be installed onany computer that is running Windows 7 or Windows Server 2008 R2that supports handwriting recognition. A dictionary is installed eitherfor just the current user or for all users on a machine.

A compiled custom-dictionary file can be installed from thecommand line by using the HwrReg.exe tool. This tool is useful if youwant to override configuration values that either are compiled intothe file or are the default values. You can run HwrReg.exein

check/install mode and in list/remove mode.

Running HwrReg.exe in Check/Install Mode

This mode is for custom dictionary files that have not yet beeninstalled. The following command shows the usage syntax for thecommand-line options:

Usage: hwrreg [-check]

[-lang ]

[-scope {all|me}]

[-noprompt]


-checkThe dictionary file is verified without being installed. The checkoption displays the files comment, plus the registrationinformation that would be used to install the file. This option isuseful for verifying registration information before the installationis performed.

If this option is missing, HwrReg.exe installs the customdictionary.

-lang The specified locale name is applied to the custom dictionary.This effectively ignores the locale name that is specified duringcompilation with HwrComp.exe. The argument hasthe form language-REGION. For examples of this form, seeLocale Identifier Constants and Strings in the MSDN library.

If this option is missing, the language specified duringcompilation is used.

http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137


15/17


-scope {all|me}The custom dictionary is installed either for all users (scope all)or for just the current user (-scope me). Installing with scopeall requires the command to be run in an elevated commandprompt; otherwise, an error code is returned.

If this option is missing, the installation is scoped to just thecurrent user.

-nopromptHwrReg.exe does not prompt for confirmation. This can be usefulwhen you are running hwrReg.exe from a script.

Example

The following example installs the custom dictionary myrsrc1.hwrdictfor language Danish (Denmark) (da-DK), with the default scope of

just the current user:

hwrreg lang da-DK myrsrc1.hwrdict

Running HwrReg.exe in List/Remove Mode

This mode either lists or removes installed custom dictionaries. Thefollowing shows the usage syntax for the command-line options:

Usage: hwrreg [-lang ]

[-scope {all|me}]

[-type ]

-list | -remove


-lang

The dictionaries that are registered for only this locale name arelisted or removed. The argument has the formlanguage-REGION. For examples of this form, see LocaleIdentifier Constants and Strings in the MSDN library.

If this option is missing, dictionaries for all languages are listed orremoved.

-scope {all|me}Dictionaries are listed or removed either for all users (-scope all)or for just the current user (-scope me). Running with scope allrequires the command to be run in an elevated commandprompt; otherwise, an error code is returned.

If this option is missing, the listing or removal is scoped to justthe current user.

-type This option lists or removes only dictionaries that are registeredwith the specified type.

If this option is missing, all dictionaries type are listed orremoved.

http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137http://go.microsoft.com/fwlink/?LinkId=129137


16/17


-listThis option lists all installed dictionaries that match the otheroptions.

If this option is missing, the remove option must be specified.

-remove

This option prompts for removal of any dictionary that matchesthe other options.

If this option is missing, the option list must be specified.

Examples

The following command lists dictionaries that have languageEnglish (US) (en-US) and type PRIMARY-DICTIONARYand thatare installed for just the current user:

hwrreg list lang en-US type PRIMARY-DICTIONARY

Similarly, the following command removes dictionaries that match

the same criteria:hwrreg remove lang en-US type PRIMARY-DICTIONARY

General Notes on Custom Dictionaries

If you install two custom dictionaries that have the same type,language, and scope, the second installation overwrites the first.

If you install two custom dictionaries with the same type andlanguage, but with different scopesone for all users and one forthe current userthe dictionary installed for the current usertakes precedence and the dictionary that was installed for allusers is ignored.

The only way to specify a nondefault type is at compilation timeby using the hwrcomp program.

Only files that are compiled with HwrComp.exe should beregistered. Forcing registration of any other file may disable orotherwise disrupt handwriting recognition.

The type that corresponds to the main system dictionary(PRIMARY-DICTIONARY) comprises several other types.Installing a custom dictionary of another type (such as PRIMARY-COUNTRYNAME-LIST) affects handwriting recognition in all

contexts. Custom dictionaries in Windows 7 and Windows Server 2008 R2

are incompatible with the approach to customization that isoutlined in Creating Portable Encoded Custom Dictionaries ThatImprove Handwriting Recognition Results in the MSDN library. Ifyou used that approach, we strongly encourage you to reinstallyour word list as a custom dictionary for Windows 7 or WindowsServer 2008 R2.

http://go.microsoft.com/fwlink/?LinkId=129140http://go.microsoft.com/fwlink/?LinkId=129140http://go.microsoft.com/fwlink/?LinkId=129140http://go.microsoft.com/fwlink/?LinkId=129140http://go.microsoft.com/fwlink/?LinkId=129140http://go.microsoft.com/fwlink/?LinkId=129140http://go.microsoft.com/fwlink/?LinkId=129140http://go.microsoft.com/fwlink/?LinkId=129140


17/17


Custom dictionaries in Windows Server 2008 R2 can be installedonly for the entire machine (-scope all).

Server-Side Recognition

The Windows Server 2008 R2 operating system supports server-side

recognition. Server-side recognition lets a server recognize contentthat is typed into a Microsoft Silverlight form. This is especiallyuseful when users on a network will be specifying terms that areinterpreted by using a custom dictionary. For example, if you had amedical application that queried a server database for patientnames, those names could be added to another database that wouldbe cross-referenced when it performs searches from a handwrittenSilverlight form.

Windows Server 2008 R2 will include an example applicationSilverLiveSearchto demonstrate server-side recognition.

Server-Side Recognition 2008 Microsoft Corporation. All rights reserved.

Touch Tab Enhance

Documents

Transcript of Touch Tab Enhance