Patent Description:
Devices today (e.g., computing devices) typically support a variety of different input techniques. For instance, a particular device may receive input from a user via a keyboard, a mouse, voice input, touch input (e.g., to a touchscreen), and so forth. One particularly intuitive input technique enables a user to utilize a touch instrument (e.g., a pen, a stylus, a finger, and so forth) to provide freehand input to a touch-sensing functionality such as a touchscreen. The freehand input may be converted to a corresponding visual representation on a display, such as for taking notes, for creating and editing an electronic document, and so forth. <CIT>) discloses a system for recognizing handwritten characters that are written at least partially over the top of one another on a touch-based surface of a computing device. In an example, a touch-based input relating to a sequence of strokes is received. A corresponding graphical representation of a first subset of the sequence of strokes is displayed on an output device of the computing device. A confidence level is determined, the confidence level indicating that a first character approximately matches the first subset of the sequence of strokes, wherein the confidence level is of at least a first confidence threshold. The display of the graphical representation of the first subset of the sequence of strokes is adjusted based on the confidence level. For instance, the graphical representation is faded. Then, the first character is provided for processing by an application executing on the computing device when the confidence level is of at least a second confidence threshold, wherein the application is designed to process characters from touch-based input. <CIT>) discloses an apparatus for executing a handwriting recognition engine automatically without requiring user selection of a handwriting recognition application to start the handwriting recognition engine. In an example, it receives input from a touch-enabled display. The input is displayed on the display. The apparatus determines whether the input indicates a character, and automatically stores the character responsive to a determination that the input indicates a character. If this is the case, in an example, a memo application is launched, and a memo file is displayed. <CIT> discloses a system for processing electronic ink that receives electronic ink input, converts the input to machine-generated objects, and renders the objects such that their size substantially corresponds to the input's original size. In examples, to enable quick and easy identification of recognizer errors, a user may select one or more words, which will cause the system to display the original ink corresponding to the selected word(s). For example, such a system also may display alternative words generated by the recognizer corresponding to the selected original ink and allow the user to select one of the alternatives to make corrections in the recognized text.

Several aspects of the invention provide techniques as set forth in the accompanying claims.

In accordance with one or more aspects, a digital input is received by a digital input system, the receiving including collecting input data for the digital input that describes the digital input. The input data for the digital input is provided, by the digital input system, to a host application as the digital input is received. An indication of one or more operations that the host application performed on the input data is received from the host application, and the digital input system controls, as the digital input is received, a display of data based at least in part on the operated-on input data.

In accordance with one or more aspects, a computing device includes an input data collection module, an input manager, and a data display module. The input data collection module comprises instructions configured to collect input data for a digital input that is input to the computing device. The input manager comprises instructions configured to provide the input data to a host application as the digital input is received, and to receive from the host application an indication of the digital input as operated on by the host application. The data display module comprises instructions configured to communicate with the input manager and to display data based on the digital input as operated on by the host application.

Entities represented in the figures may be indicative of one or more entities and thus reference may be made interchangeably to single or plural forms of the entities in the discussion.

Controlling digital input is discussed herein. A computing device includes a digital input system that provides digital input functionality for the computing device. The digital input system can be implemented as part of an application, as a standalone application that provides digital input support to other applications (referred to herein as host applications), or combinations thereof. Digital inputs may be provided in various ways, such as using a pen (e.g., an active pen, a passive pen, and so forth), a stylus, a finger, and so forth. The digital inputs discussed herein are provided by movement of an input device (e.g., stylus, pen, finger, mouse, etc.) in a freehand manner and thus can also be referred to as freehand digital inputs. The digital input system provides functionality allowing applications to receive digital inputs from a user of the computing device, store received digital inputs, and control the display of data based on the digital inputs.

Various different types of digital inputs can be supported by the digital input system. In one or more embodiments, the digital input system supports digital ink that can be displayed on a display device. Generally, digital ink refers to freehand input to a touch-sensing device such as a touchscreen, which is interpreted by the computing device as digital ink (or simply "ink"). Additionally or alternatively, the digital input system supports other types of digital inputs, such as digital input to erase or delete a portion of data previously input, digital input to control a direction of movement (e.g., a route or path for a vehicle to take, a route or path for a game), and so forth.

The digital input system receives digital input from a user and analyzes the digital input to collect input data for the digital input. This input data refers to various information describing the digital input, such as the coordinates on the input device where the digital input occurred and pressure information indicating an amount of pressure applied at each of those coordinates for the digital input. A digital input refers to the movement of the input device (e.g., a pen, stylus, finger, etc.) along an input surface from a beginning location (e.g., where the input device is brought into contact with the input surface) to an ending location (e.g., where the input device is pulled away from the input surface).

As the digital input is received, the input data is made available to a host application if the host application desires the input data. The host application can then act or operate on the input data in any of a variety of different manners, and return the input data (optionally modified) to the digital input system. The digital input system then proceeds to control the display of data based on the operated-on input data. This controlling of the display of data can be, for example, displaying digital ink corresponding to the input data, erasing data based on the input data, determining movement of an object based on the input data, and so forth. For example, the host application can change the input data, such as changing the coordinates where the digital input occurred (e.g., to keep the digital input along a straight edge), and return the changed input data to the digital input system (e.g., for display). By way of another example, the host application can create new input data for a new digital input (e.g., that mirrors the digital input) and provide the new input data to the digital input system. The digital input system can then control or manipulate data based on both the digital input and the new digital input (e.g., by displaying both the new input data as well as the input data received as part of the digital input). By way of another example, the host application can create new input data for a new digital input (e.g., that projects the digital input onto a different screen or display) and provide the new input data to the digital input system (e.g., which displays both the new input data as well as the input data received as part of the digital input).

Thus, the host application can act upon the digital input as the input is being received. The techniques discussed herein allow, for example, the host application to ensure that the input data reflects digital input along a ruler, protractor, or other edge, providing smooth digital input rather than wobbly or wiggly lines as might be drawn freehand by the user. The techniques discussed herein also allow, for example, a mirror image for the digital input to be created (e.g., the other half of a heart being drawn by the user) and/or to have a duplicate of the digital input displayed on a remote display (e.g., another screen or display device that the computing device implementing the digital input system is projecting the digital input to).

The techniques discussed herein provide a robust and user friendly experience with digital inputs. Various different host applications can leverage the digital input system to support digital inputs. The host application is able to act upon the digital input as the digital input is being made - the host application need not wait for a digital input to be completed to act upon the digital input. Thus, the digital input is acted upon in real time as the digital input is made (e.g., as the user draws a digital input, the digital input is mirrored, the digital input is modified so as to be smooth along a straight edge, etc.).

<FIG> illustrates an example environment <NUM> in which the controlling digital input discussed herein can be used. The environment <NUM> includes a computing device <NUM> that can be embodied as any suitable device such as, by way of example, a desktop computer, a server computer, a laptop or netbook computer, a mobile device (e.g., a tablet or phablet device, a cellular or other wireless phone (e.g., a smartphone), a notepad computer, a mobile station), a wearable device (e.g., eyeglasses, head-mounted display, watch, bracelet), an entertainment device (e.g., an entertainment appliance, a set-top box communicatively coupled to a display device, a game console), an Internet of Things (IoT) device (e.g., objects or things with software, firmware, and/or hardware to allow communication with other devices), a television or other display device, an automotive computer, and so forth. Thus, the computing device <NUM> may range from a full resource device with substantial memory and processor resources (e.g., personal computers, game consoles) to a low-resource device with limited memory and/or processing resources (e.g., traditional set-top boxes, hand-held game consoles).

The computing device <NUM> includes a variety of different functionalities that enable various activities and tasks to be performed. For instance, the computing device <NUM> includes an operating system <NUM>, multiple applications <NUM> (also referred to herein as host applications), and a communication module <NUM>. Generally, the operating system <NUM> is representative of functionality for abstracting various system components of the computing device <NUM>, such as hardware, kernel-level modules and services, and so forth. The operating system <NUM>, for instance, can abstract various components of the computing device <NUM> to the applications <NUM> to enable interaction between the components and the applications <NUM>.

The applications <NUM> represent functionalities for performing different tasks via the computing device <NUM>. Examples of the applications <NUM> include a word processing application, an information gathering and/or note taking application, a spreadsheet application, a web browser, a gaming application, and so forth. The applications <NUM> may be installed locally on the computing device <NUM> to be executed via a local runtime environment, and/or may represent portals to remote functionality, such as cloud-based services, web apps, and so forth. Thus, the applications <NUM> may take a variety of forms, such as locally-executed code, portals to remotely hosted services, and so forth.

The communication module <NUM> is representative of functionality for enabling the computing device <NUM> to communicate over wired and/or wireless connections. For instance, the communication module <NUM> represents hardware and logic for communication via a variety of different wired and/or wireless technologies and protocols.

The computing device <NUM> further includes a display device <NUM>, input mechanisms <NUM>, and a digital input system <NUM>. The display device <NUM> generally represents functionality for visual output for the computing device <NUM>. Additionally, the display device <NUM> optionally represents functionality for receiving various types of input, such as touch input, pen input, and so forth. The input mechanisms <NUM> generally represent different functionalities for receiving input to the computing device <NUM>. Examples of the input mechanisms <NUM> include gesture-sensitive sensors and devices (e.g., such as touch-based sensors and movement-tracking sensors (e.g., camera-based)), a mouse, a keyboard, a stylus, a touch pad, accelerometers, a microphone with accompanying voice recognition software, and so forth. The input mechanisms <NUM> may be separate or integral with the display <NUM>; integral examples include gesture-sensitive displays with integrated touch-sensitive or motion-sensitive sensors. The input mechanisms <NUM> optionally include a pen digitizer <NUM> and/or touch input devices <NUM>. The pen digitizer <NUM> represents functionality for converting various types of input to the display device <NUM> and/or the touch input devices <NUM> into digital data that can be used by the computing device <NUM> in various ways, such as for generating digital ink. The touch input devices <NUM> represent functionality for providing touch input separately from the display <NUM>.

Although reference is made herein to the display device <NUM> receiving various types of input such as touch input or pen input, alternatively the display device <NUM> may not receive such input. Rather, a separate input device (e.g., a touchpad) implemented as a touch input device <NUM> can receive such input. Additionally or alternatively, the display device <NUM> may not receive such input, but a pen (such as pen <NUM>) can be implemented as a touch input device <NUM>, and the pen provides an indication of the input rather than the input being sensed by the display device <NUM>.

According to various implementations, the digital input system <NUM> represents functionality for performing various aspects of the techniques for controlling digital input discussed herein. Various functionalities of the digital input system <NUM> are discussed herein. In one or more embodiments, the digital input system <NUM> is implemented as an application <NUM> (or as part of the operating system <NUM>) that provides digital input support to other applications <NUM> (or programs of the operating system <NUM>). The digital input system <NUM> optionally includes an application programming interface (API) allowing the applications <NUM> or other programs to interact with the functionality provided by the digital input system <NUM>. Alternatively, the digital input system <NUM> can be implemented in an application <NUM> and provide digital input support for that application <NUM> but not for other applications <NUM>. Alternatively, the digital input system <NUM> can be implemented as a combination thereof. For example, some functionality of the digital input system <NUM> can be implemented in an application <NUM> (or as part of the operating system <NUM>) that provides digital input support to other applications <NUM> or programs, and other functionality of the digital input system <NUM> can be implemented in the individual applications <NUM> to which the digital input system <NUM> provides support.

The environment <NUM> further includes a pen <NUM>, which is representative of an input device for providing input to the display device <NUM>. Generally, the pen <NUM> is in a form factor of a traditional pen but includes functionality for interacting with the display device <NUM> and other functionality of the computing device <NUM>. In at least some implementations, the pen <NUM> is an active pen that includes electronic components for interacting with the computing device <NUM>. The pen <NUM>, for instance, includes a battery that can provide power to internal components of the pen <NUM>. Alternatively or additionally, the pen <NUM> may include a magnet or other functionality that supports hover detection over the display device <NUM>. This is not intended to be limiting, however, and in at least some implementations the pen <NUM> may be passive, e.g., a stylus without internal electronics.

Digital input can be provided by the user using the pen <NUM>. Additionally or alternatively, digital input can be provided by the user using other input mechanisms, such as the user's finger, a stylus, and so forth.

In one or more embodiments, the digital input system <NUM> maintains the digital input in a vector format. Various different vector formats can be used, such as a Scalable Vector Graphics (SVG) format. Thus, in contrast to systems that maintain digital input in a bitmap format, the individual digital inputs (optionally as modified by an application <NUM> as discussed in more detail below) are maintained in a vector format. The digital inputs can optionally be saved by the computing device <NUM>. The digital inputs can be stored in a digital input store (e.g., a storage device local to the computing device <NUM> and/or accessed via a network) by the digital input system <NUM> and/or the applications <NUM>. The digital inputs can be saved in various different types of files, such as an Ink Serialized Format (ISF) file, an eXtensible Markup Language (XML) file, a HyperText Markup Language (HTML) file, and so forth.

<FIG> illustrates an example system <NUM> including a host application and digital input system in accordance with one or more embodiments. <FIG> is discussed with reference to elements of <FIG>. The digital input system <NUM> includes an input data collection module <NUM>, an input manager <NUM>, and a data display module <NUM>. The digital input system <NUM> communicates with an input operations module <NUM> of the host application <NUM>, which performs various operations based on the input data as discussed in more detail below.

The input data collection module <NUM> collects input data for digital inputs (e.g., to the computing device <NUM>). A digital input is described using various information referred to as input data (also referred to as digital input data). In one or more embodiments, the input data includes a set of coordinates and optionally pressure applied at each coordinate. The coordinates can be in various coordinate systems, such as a <NUM>-dimensional Cartesian coordinate system, a polar coordinate system, and so forth. The pressure or force can be measured in various units, such as pascals. The coordinates and optionally pressure can be sensed by various sensors of the touch input devices <NUM> (e.g., sensors in the display device <NUM>, sensors in the pen <NUM>, and so forth). The input data can additionally or alternatively include other data, such as an angle or tilt of the input device, a shape of the input device (e.g., in contact with a touchscreen), and so forth.

The coordinates included in the input data are a set or series of coordinates that identify the location of the input mechanism at particular times as the digital input is being provided by the user. These particular times can be regular or irregular intervals (e.g., every <NUM> milliseconds). The coordinates are detected or sensed by the pen digitizer <NUM> or a touch input device <NUM>, such as by the display device <NUM>, by the pen <NUM>, and so forth. Using the example of the digital ink input of "Ink" in <FIG>, the ink stroke data for the digital ink input is the coordinates that identify the location of the input mechanism as the letter "I" is written, as the letter "n" is written, and as the letter "k" is written. In one or more embodiments, as used herein an input refers to the movement of the input device from being first sensed as providing input (e.g., touching a touchscreen device or a "pen down" event) through the input device no longer being sensed as providing input (e.g., the input device being lifted away from the touchscreen device or a "pen up" event). In situations in which the digital input is digital ink, the input can also be referred to as a digital ink stroke, and the input data can also be referred to as digital ink stroke data.

The input manager <NUM> determines the appropriate manner to control or manipulate data displayed by the computing device <NUM>. This data displayed by the computing device <NUM> can be data showing the digital input (e.g., digital ink that is input by the user), or other data that is shown and manipulated based on the digital input (e.g., erasing of previously input digital ink, display of an icon or character, etc.). The data displayed is based on the both the digital input that is input and one or more operations performed on the input data by the input operations module <NUM>.

The input manager <NUM> receives the input data from the input data collection module <NUM> and notifies the input operations module <NUM> of the received input data. In one or more embodiments, the input operations module <NUM> registers with the input manager <NUM> to receive particular events regarding digital input, such as when an input begins, when an input ends, input data collected during the input, and so forth. Whenever one of these registered-for events occurs, the input manager <NUM> notifies the input operations module <NUM> of the input data at the time the event occurs. This notification can be performed in various manners, such as by invoking an API method or callback function of the input operations module <NUM>.

Additionally or alternatively, the input operations module <NUM> can be notified of input data in other manners. For example, the input manager <NUM> can notify the input operations module (e.g., by invoking an API method or callback function of the input operations module <NUM>) of collected input data regardless of which (if any) events the input operations module <NUM> has registered for. By way of another example, the input manager <NUM> can issue a message (e.g., via a messaging system of the operating system <NUM>) indicating the input data collected, and input operations module <NUM> can choose whether to receive such messages (or choose to receive all such messages and then determine what, if any, action to take on the messages).

The input operations module <NUM> operates on the input data, and provides an indication to the input manager <NUM> of the operated-on input data. This indication can be a change to the input data received from the input manager <NUM> and/or additional input data to be used by the input manager <NUM>.

The input operations module <NUM> operates on the input data provided by the input manager <NUM>. The input operations module <NUM> can operate on the input data in a variety of different manners, such as modifying the input data, generating additional input data, and so forth. The manner in which the input operations module <NUM> operates on the input data can vary based on the desires of the developer of the host application <NUM> and/or the user of the host application <NUM>.

In one or more embodiments, the input operations module <NUM> modifies the input data based on a stencil. Various different stencils can be used, such as a ruler, a protractor, a circle, a French curve, and so forth. A "soft" stencil is used (and optionally displayed) by the host application <NUM>, the soft stencil referring to a stencil that is generated and displayed by the host application <NUM> (or other program running on the computing device <NUM>) in contrast to a physical stencil available to a user of the host application <NUM>. The soft stencils can be available from the host application <NUM>, the digital input system <NUM>, and/or other programs of the computing device <NUM>. For example, a library of soft stencils can be maintained and the user of the host application <NUM> can select a desired soft stencil to use for the digital input.

Freehand digital input is often wiggly or wobbly rather than a straight line, and the soft stencil allows the user to generate digital input that conforms to the shape of the edge of the stencil rather than the wiggly or wobbly digital input. For example, the stencil can be a ruler, and the input operations module <NUM> modifies the input data so that the input data indicates locations (e.g., coordinates) along the edge of the ruler. By way of another example, the stencil can be a ruler that is used as a mask, so that digital input in an area where the stencil is displayed is masked (and thus is not displayed by the digital input system <NUM>) but digital input in an area where the stencil is not displayed is not masked (and thus is displayed by the digital input system <NUM>).

Additionally or alternatively, the input data can be modified in various other manners. For example, the data indicating pressure applied by the input device can be changed, an angle or tilt of the input device can be changed, a shape of the input device (e.g., in contact with a touchscreen) can be changed, and so forth.

In one or more embodiments, the input operations module <NUM> generates additional input data. This additional input data can be, for example, input data that mirrors the digital input about one or more axes or lines (e.g., a vertical axis or a horizontal axis). For example, the user may desire to draw a heart shape and provide digital input that is the right half of the heart shape. The input operations module <NUM> generates additional input data that corresponds to the input data for the right half of the heart shape and generates additional input data for the left half of the heart shaped.

Additionally or alternatively, this additional input data can be input data that corresponds to the input data of the digital input but is relative to a different one or more lines (or axes) input or selected by the user. For example, the user may desire to draw a first straight line and have a second straight line drawn perpendicular to the first straight line. The input operations module <NUM> generates additional input data that corresponds to the input data for the first straight line, but is a second straight line perpendicular to the first straight line (e.g., beginning where the first straight line begins or at some other location specified by the user).

Additionally or alternatively, this additional input data can be input data that is for one or more additional displays. For example, the host application <NUM> may facilitate projection of data from the computing device <NUM> to another display (e.g., the computing device <NUM> may be a tablet or smartphone, and the host application <NUM> may facilitate projection of data from the tablet or smartphone to a larger television or monitor). In this situation, the additional input data is additional input data indicating data to be displayed on one or more additional displays in addition to (or rather than) the data to be displayed on a display device of the computing device <NUM>.

The input operations module <NUM> provides the operated-on input data to the input manager <NUM>. The input manager <NUM> receives the operated-on input data from the input operations module <NUM> and determines how to control the display of the digital input based on the operated-on input data. This determination is based at least in part on the operated-on input data received from the input operations module <NUM>. In situations in which the input operations module <NUM> modifies the input data, the input manager <NUM> controls display of data based on the operated-on input data (the modified input data) rather than the input data received from the input data collection module <NUM>. In situations in which additional input data is generated by the input operations module <NUM>, the input manager <NUM> controls display of data based on the additional input data rather than (or alternatively in addition to) the input data received from the input data collection module <NUM>. The input manager <NUM> treats the additional input data it receives from the input operations module <NUM> as if it were any other digital input (e.g., as if the additional input data were received from an input device rather than having been generated by the input operations module <NUM>).

The input manager <NUM> communicates with the data display module <NUM> to display data based on the digital input as appropriate. The data display module <NUM> displays data as indicated by the input manager <NUM>, and can display data on a single display, multiple displays, and so forth. Thus, the data displayed by the data display module <NUM> reflects the input data as operated on by the input operations module <NUM>.

It should be noted that the input data that is operated on by the input operations module <NUM> can be managed in different manners. In one or more embodiments, the input manager <NUM> provides or otherwise makes available to the input operations module <NUM> a copy of the collected input data. The input operations module <NUM> operates on the copy and then the input manager <NUM> updates the collected input data to incorporate any modifications made to the input data by the input operations module <NUM> (optionally maintaining a backup copy or record of the un-modified input data for later use if desired). Alternatively, the input manager <NUM> can provide the collected input data to the input operations module <NUM>, allowing the input operations module <NUM> to modify the collected input data rather than a copy of the collected input data.

In one or more embodiments, as part of generating additional input data, the input operations module <NUM> optionally provides additional instruction or information regarding the additional input data to the input manager <NUM>. This additional instruction or information can specify, for example, whether to render the additional input data immediately or after some delay, which of multiple instances of data display module <NUM> to have display the additional input data, and so forth.

It should be noted that the data display module <NUM> can display data based on the digital input in various manners, and that new data is not necessarily displayed. For example, the digital input can be to erase at least part of a previous input (e.g., erase previously input digital ink), including erasing previous input as modified by the input operations module <NUM>. The digital input system <NUM> also supports various additional operations on digital inputs and treats digital inputs that have been operated on by the input operations module <NUM> as if they were any other digital inputs, including saving the input data, allowing the digital input (e.g., digital ink) to be copied and/or pasted, and so forth.

<FIG> illustrate examples of controlling digital input using the techniques discussed herein in accordance with one or more embodiments. <FIG> are discussed with reference to elements of <FIG> and <FIG>.

<FIG> illustrates an example <NUM> in which digital ink is generated along the edge of a stencil. In the example <NUM>, a user desires to input digital ink that is an arc along the edge of a soft stencil <NUM>. A pen <NUM> is used to provide a digital input on a touchscreen display <NUM>, but due to the wiggly or wobbly nature of the freehand input with the pen <NUM> without alteration the digital ink input by the user would be a wiggly or wobbly arc rather than a smoothly drawn arc along the edge of the soft stencil <NUM>. The input operations module <NUM> modifies the digital input from the pen <NUM>, modifying the input data so that the modified input data is a smooth arc along the edge of the stencil <NUM>. The input manager <NUM> uses this modified input data to have the data display module <NUM> display the smooth arc <NUM>.

<FIG> illustrates an example <NUM> in which digital ink is generated and a stencil is used to mask part of the digital input. In the example <NUM>, a user desires to input digital ink that is freeform digital ink that is not displayed in the area in which a soft stencil <NUM> is located. A pen <NUM> is used to provide a digital input on a touchscreen display <NUM>, and the input operations module <NUM> modifies the digital input from the pen <NUM> so that input data for the digital input at locations (e.g., coordinates) at which the soft stencil <NUM> is present (e.g., overlaps the input data) is not displayed. The input operations module <NUM> can separate the digital input into multiple different digital inputs, can delete or otherwise drop the input data for locations at which the soft stencil <NUM> is present, or modify the input data to include an indicator to the input manager <NUM> that the input data for the locations at which the soft stencil <NUM> is present is not to be displayed. The input manager <NUM> uses this modified input data to have the data display module <NUM> generate the digital ink <NUM>, which is the freeform digital input provided by the user masked by the soft stencil <NUM>.

<FIG> illustrates an example <NUM> in which a digital input is used to erase data. In the example <NUM>, a user desires to erase data along a straight line from previously input digital ink <NUM>. A pen <NUM> is used to provide a digital input on a touchscreen display <NUM>, but due to the wiggly or wobbly nature of the freehand input with the pen <NUM> without alteration the digital input by the user would be a wiggly or wobbly line rather than a smoothly drawn straight line. The input operations module <NUM> modifies the digital input from the pen <NUM>, modifying the input data so that the modified input data is a smooth straight line along the edge of a straight edge soft stencil (not shown). The input manager <NUM> uses this modified input data to have the data display module <NUM> erase a smooth straight line <NUM> from the previously input digital ink <NUM>.

<FIG> illustrates an example <NUM> in which a digital input is used to set a route. In the example <NUM>, a user desires to set a route along a straight line from a starting location <NUM> to a destination location <NUM>. A pen <NUM> is used to provide a digital input on a touchscreen display <NUM>, but due to the wiggly or wobbly nature of the freehand input with the pen <NUM> without alteration the digital input by the user would be a wiggly or wobbly line rather than a smoothly drawn straight line. The input operations module <NUM> modifies the digital input from the pen <NUM>, modifying the input data so that the modified input data is a smooth straight line along the edge of a straight edge soft stencil (not shown). This modified input data is used to generate a smooth straight line <NUM> from the starting location <NUM> to the destination location <NUM>. The input manager <NUM> optionally uses this modified input data to have the data display module <NUM> draw the line <NUM>. Additionally or alternatively, the host application <NUM> can use the modified input data to generate the route along the smooth straight line <NUM>, and need not have the line <NUM> displayed. The route can be used for various different purposes as desired by the host application <NUM>, such as to move icons or characters in a game, to set a path for a vehicle (e.g., a drone), and so forth.

<FIG> illustrates an example <NUM> in which additional digital ink is generated. In the example <NUM>, a user desires to input digital ink and have additional digital ink generated that is a mirror along of the input digital ink. A pen <NUM> is used to provide a digital input on a touchscreen display <NUM>. The input operations module <NUM> generates additional input data that is a mirror of the input data for the input digital ink along an axis <NUM> (e.g., which can be input or otherwise selected by the user). The input operations module <NUM> provides the additional input data to the input manager <NUM>, which uses the input data for the digital input provided by the user to have the display module <NUM> display the digital input <NUM> and uses the additional input data to have the display module <NUM> display an additional line <NUM> that mirrors the digital input <NUM> about the axis <NUM>. The input data is provided to the input operations module <NUM> as the input data is received by the input manager <NUM>, and the additional input data is returned to the input manager <NUM> as the input data is operated on. Thus, the additional input data can be used to generate and display the additional line <NUM> contemporaneously with the collected input data being used to generate and display the digital input <NUM>.

<FIG> illustrates an example <NUM> in which additional digital ink is generated. In the example <NUM>, a user desires to input digital ink and have additional digital ink generated that is displayed on an additional display device. A pen <NUM> is used to provide a digital input on a touchscreen display <NUM>. The input operations module <NUM> generates additional input data that is the same as (e.g., a duplicate of) the input data but uses the additional input data to project the digital input onto a display for a different display device, and provides the additional input data to the input manager <NUM>. The input manager <NUM> uses the input data for the digital input provided by the user to have the display module <NUM> display the digital input <NUM> on the display <NUM>. The input manager <NUM> uses the additional input data to have the display module <NUM> display an additional line <NUM> on an additional display <NUM>. The additional line <NUM> can be displayed on the additional display <NUM> in various different manners. In one or more embodiments, the digital input system <NUM> includes multiple data display modules <NUM>, one for each display device on which digital inputs are displayed (e.g., one data display module for the display <NUM>, and one data display module for the additional display <NUM>). These multiple data display modules can be, for example, different instances of the data display module <NUM> within a process, or different instances of the data display module <NUM> in different processes. In such situations, the input manager <NUM> communicates with both of the data display modules to display the input data on the display <NUM> as line <NUM> and the additional input data on the display <NUM> as line <NUM>. The input data is provided to the input operations module <NUM> as the input data is received by the input manager <NUM>, and the additional input data is returned to the input manager <NUM> as the input data is operated on. Thus, the additional input data can be used to generate and display the additional line <NUM> contemporaneously with the collected input data being used to generate and display the digital input <NUM>.

Additionally or alternatively, the input operations module <NUM> generates additional input data that is based on the input data but is not the same as (e.g., is not a duplicate of) the input data. For example, the additional input data can be a mirror of the input data (analogous to the discussion above regarding <FIG>).

Returning to <FIG>, in one or more embodiments the input operations module <NUM> and the input manager <NUM> are implemented at least in part in software or firmware, and at least part of the input operations module <NUM> is executed in a same thread as the input manager <NUM>. This allows, for example, modifications to the input data to be made as the input data is received, with little or no user-perceivable delay between moving the input device and the modified input data being displayed. In one or more embodiments, the notification of the events and the modifications of the input data are performed synchronously - the input manager <NUM> does not proceed with having the data display module <NUM> change the display (e.g., display a portion of an input digital ink stroke) until the input operations module <NUM> has had the opportunity to operate on the input data.

It should be noted that not all of the input operations module <NUM> need be implemented in the same thread as the input manager <NUM>. In one or more embodiments, portions of the input operations module <NUM> that are more time sensitive (e.g., to provide a modification to the digital input as the digital input is received) are performed in the same thread as the input manager <NUM>. Other portions of the input operations module <NUM>, such as portions that generate additional input data, can be performed in a different thread than the input manager <NUM>. This may result in some lag in the input manager <NUM> acting on the additional input data, but that lag may not be noticeable to a user (e.g., the user may not notice a quarter or half second lag in displaying digital ink on an additional display).

In one or more embodiments, the input data is provided to the input operations module <NUM> as discussed above, and the most recently sent input data can be operated on by the input operations module <NUM>. This allows the operations on the input data to be reflected by the digital input system <NUM> as the digital input is being received. Additionally or alternatively, the input operations module <NUM> can operate on a larger portion of an input rather than just the most recently sent input data, such as the entire digital input. The input data to be operated on can be provided to the input operations module <NUM> when such operation is desired, or alternatively the input operations module <NUM> can maintain the input data as it is sent to the input operations module <NUM>. In situations in which a larger portion of the input is operated on, the input operations module <NUM> provides the operated-on input data to the input manager <NUM> to display the larger portion of the digital input as operated on.

Operating on a larger portion of an input allows various different behavior. For example, the user can select (e.g., by providing various different inputs, such as wiggling the input device) to have the input data toggle between being operated on and not being operated on (e.g., so that the input can toggle between being freehand input and smooth input along the edge of a stencil). By way of another example, the user can select (e.g., providing various different inputs, such as by wiggling the input device) to have the input data be operated on to be animated, such as shaking or wiggling like a snake or wet noodle.

Additionally, in one or more embodiments, the input operations module <NUM> can separate an input into multiple digital inputs. As discussed above, a digital input can refer to the movement of the input device or object from being first sensed as providing input (e.g., touching a touchscreen device or a "pen down" event) through the input device or object no longer being sensed as providing input (e.g., the input device being lifted away from the touchscreen device or a "pen up" event). The input operations module <NUM> can separate a digital input into multiple digital inputs even though the input device or object continues to be sensed as providing input (e.g., is touching the touchscreen device). For example, referring again to <FIG>, the user provides input using the input device <NUM>, and the illustrated input is a freeform line that passes over the soft stencil <NUM>. The input device <NUM> remains sensed as providing input (e.g., as touching the touchscreen display <NUM>), but the input operations module <NUM> separates the digital input as multiple digital inputs (e.g., two digital inputs on the left-hand side of the soft stencil <NUM>, and two digital inputs on the right-hand side of the soft stencil <NUM>) rather than a single digital input. A digital input is thus able to be completed mid-input and a new digital input started (at the time of the mid-input completion or at a later time). In situations in which the digital input is digital ink, digital ink is thus able to be completed mid-stroke and a new digital ink stroke started (at the time of the mid-stroke completion or at a later time). The input operations module <NUM> notifies the input manager <NUM> of this separation of the digital input into multiple digital inputs. This notification can take various forms, such as modifying the input data to include an indication that a digital input has ended or begun, sending commands to (e.g., invoking API methods exposed by) the input manager <NUM> indicating that a digital input has ended or begun, and so forth.

<FIG> is a flowchart illustrating an example process <NUM> for implementing the controlling digital input in accordance with one or more embodiments. Process <NUM> can be implemented in software, firmware, hardware, or combinations thereof. Acts of process <NUM> illustrated on the left-hand side of <FIG> are carried out by a digital input system, such as the digital input system <NUM> of <FIG> or <FIG>. Acts of process <NUM> illustrated on the right-hand side of <FIG> are carried out by a host application, such as a host application <NUM> of <FIG> or <FIG>. Process <NUM> is shown as a set of acts and is not limited to the order shown for performing the operations of the various acts. Process <NUM> is an example process for implementing the controlling digital input; additional discussions of implementing the controlling digital input are included herein with reference to different figures.

In process <NUM>, a digital input is received by the digital input system (act <NUM>). The received digital input includes input data for the digital input. The digital input can be input directly to an application and provided to the digital input system, or can be provided to the digital input system that receives the digital input on behalf of the application.

The received input data is provided to a host application (act <NUM>). The host application is, for example, an application that has registered to receive from the digital input system events or messages regarding input data.

The host application receives the captured input data from the digital input system (act <NUM>) and performs one or more operations on the received input data (act <NUM>). These one or more operations can include modifying the input data and/or generating additional input data as discussed above.

An indication of the operated-on input data is provided to the digital input system (act <NUM>). The indication can take various forms as discussed above. For example, the indication can be the modified input data and/or additional input data generated by the host application.

The digital input system receives the indication of the operated-on input data (act <NUM>) and controls display of data based at least in part on the operated-on input data (act <NUM>). This controlling of the display of data can take various forms based on the operated-on input data, such as displaying modified input data, displaying the additional input data as well as the input data collected in act <NUM>, erasing or not displaying the input data, erasing (including point erase) of a modified stroke, and so forth. Additionally or alternatively, various other operations can also be performed, such as saving the data (e.g., the modified input data, the additional input data as well as the input data collected in act <NUM>) and loading the saved data back in later, selecting the data (e.g., the modified input data, the additional input data as well as the input data collected in act <NUM>) for copy/paste operations, and so forth.

The techniques discussed herein thus support various usage scenarios. Digital inputs can be intercepted and changed by the host application prior to the effect of the change being displayed (e.g., prior to any changes in digital ink being displayed). Any aspect of the input data can be changed, including and not limited to coordinates of the input, data reflecting pressure applied by the input device, tilt and/or twist of the input device and so forth. The digital input can also be completed mid-input and a new digital input started, allowing the digital input (and, for example, displayed digital ink) to stop at the edge of a stencil. The host application can also operate on digital input after a display has been changed based on the digital input, allowing the digital input to be modified after a display has been changed based on the digital input (e.g., changing digital ink after the digital ink has been displayed). Replay of a digital input is also supported, allowing the digital input to be mirrored, duplicated, remotely displayed, and so forth. The host application can also operate on the digital input as the digital input is received, allowing, for example, digital ink as operated on by the host application to appear to "flow" from the tip of the input device.

Although particular functionality is discussed herein with reference to particular modules, it should be noted that the functionality of individual modules discussed herein can be separated into multiple modules, and/or at least some functionality of multiple modules can be combined into a single module. Additionally, a particular module discussed herein as performing an action includes that particular module itself performing the action, or alternatively that particular module invoking or otherwise accessing another component or module that performs the action (or performs the action in conjunction with that particular module). Thus, a particular module performing an action includes that particular module itself performing the action and/or another module invoked or otherwise accessed by that particular module performing the action.

<FIG> illustrates an example system generally at <NUM> that includes an example computing device <NUM> that is representative of one or more systems and/or devices that may implement the various techniques described herein. The computing device <NUM> may be, for example, a server of a service provider, a device associated with a client (e.g., a client device), an on-chip system, and/or any other suitable computing device or computing system.

The example computing device <NUM> as illustrated includes a processing system <NUM>, one or more computer-readable media <NUM>, and one or more I/O Interfaces <NUM> that are communicatively coupled, one to another. Although not shown, the computing device <NUM> may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.

The processing system <NUM> is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system <NUM> is illustrated as including hardware elements <NUM> that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements <NUM> are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.

The computer-readable media <NUM> is illustrated as including memory/storage <NUM>. The memory/storage <NUM> represents memory/storage capacity associated with one or more computer-readable media. The memory/storage <NUM> may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage <NUM> may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media <NUM> may be configured in a variety of other ways as further described below.

The one or more input/output interface(s) <NUM> are representative of functionality to allow a user to enter commands and information to computing device <NUM>, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone (e.g., for voice inputs), a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non-visible wavelengths such as infrared frequencies to detect movement that does not involve touch as gestures), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile-response device, and so forth. Thus, the computing device <NUM> may be configured in a variety of ways as further described below to support user interaction.

The computing device <NUM> also includes a digital input system <NUM>. The digital input system <NUM> provides various functionality supporting controlling digital input as discussed above. The digital input system <NUM> can be, for example, the digital input system <NUM> of <FIG> or <FIG>.

Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms "module," "functionality," and "component" as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of computing platforms having a variety of processors.

"Computer-readable storage media" refers to media and/or devices that enable persistent storage of information and/or storage that is tangible, in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media refers to non-signal bearing media. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.

"Computer-readable signal media" refers to a signal-bearing medium that is configured to transmit instructions to the hardware of the computing device <NUM>, such as via a network. Signal media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Signal media also include any information delivery media. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.

As previously described, the hardware elements <NUM> and computer-readable media <NUM> are representative of instructions, modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein. Hardware elements may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware devices. In this context, a hardware element may operate as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element as well as a hardware device utilized to store instructions for execution, e.g., the computer-readable storage media described previously.

Combinations of the foregoing may also be employed to implement various techniques and modules described herein. Accordingly, software, hardware, or program modules and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements <NUM>. The computing device <NUM> may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of modules as a module that is executable by the computing device <NUM> as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements <NUM> of the processing system. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices <NUM> and/or processing systems <NUM>) to implement techniques, modules, and examples described herein.

As further illustrated in <FIG>, the example system <NUM> enables ubiquitous environments for a seamless user experience when running applications on a personal computer (PC), a television device, and/or a mobile device. Services and applications run substantially similar in all three environments for a common user experience when transitioning from one device to the next while utilizing an application, playing a video game, watching a video, and so on.

In the example system <NUM>, multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one or more embodiments, the central computing device may be a cloud of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link.

In one or more embodiments, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one or more embodiments, a class of target devices is created and experiences are tailored to the generic class of devices. A class of devices may be defined by physical features, types of usage, or other common characteristics of the devices.

In various implementations, the computing device <NUM> may assume a variety of different configurations, such as for computer <NUM>, mobile <NUM>, and television <NUM> uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device <NUM> may be configured according to one or more of the different device classes. For instance, the computing device <NUM> may be implemented as the computer <NUM> class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.

The computing device <NUM> may also be implemented as the mobile <NUM> class of device that includes mobile devices, such as a mobile phone, portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device <NUM> may also be implemented as the television <NUM> class of device that includes devices having or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, gaming consoles, and so on.

The techniques described herein may be supported by these various configurations of the computing device <NUM> and are not limited to the specific examples of the techniques described herein. This functionality may also be implemented all or in part through use of a distributed system, such as over a "cloud" <NUM> via a platform <NUM> as described below.

The platform <NUM> may abstract resources and functions to connect the computing device <NUM> with other computing devices. The platform <NUM> may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources <NUM> that are implemented via the platform <NUM>. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system <NUM>. For example, the functionality may be implemented in part on the computing device <NUM> as well as via the platform <NUM> that abstracts the functionality of the cloud <NUM>.

Claim 1:
A method (<NUM>) comprising:
receiving (<NUM>), by a digital input system (<NUM>) , a digital input, the digital input being provided by a user to input mechanism (<NUM>), wherein the input mechanism comprises a touch input device (<NUM>), the receiving (<NUM>) including collecting input data for the digital input, the input data describing the digital input, wherein the digital input includes a set or series of coordinates that identify the location of the input mechanism at particular times as the digital input is being provided by the user;
providing (<NUM>), by the digital input system (<NUM>) , the input data for the digital input to a host application (<NUM>) as the digital input is received;
receiving (<NUM>), from the host application (<NUM>), an indication of one or more operations the host application (<NUM>) performed on the input data via an input operations module (<NUM>) wherein the operations modify the input data;
separating, via the input operations module (<NUM>), the digital input into multiple digital inputs wherein the separating is one of the one or more operations;
notifying, via an input manager (<NUM>), of the separation of the digital input into multiple digital inputs, wherein notifying relates to an event;
controlling, by the digital input system as the digital input is received, a display of data based at least in part on the operated-on input data, thereby forming modified input data; and
displaying of the modified input data as the digital input is received wherein the notification of the event and the modifications of the input data are performed synchronously.