Multi-device pairing and combined display

Description

BACKGROUND

Computing devices, such as personal computers, laptop computers, tabletop computers, entertainment devices, and the like increasingly offer more functions and features which can make it difficult for a user to navigate and select application commands that are relevant to a function the user wants to initiate on a device. The traditional techniques to interact with computing devices, such as a mouse, keyboard, and other input devices, may become less efficient as the functions and features of computing devices continues to increase. A challenge that continues to face designers of these devices is how to incorporate interaction techniques that are not only intuitive, but allow a user to easily and quickly interact with the many functions and features of a computing device.

SUMMARY

This summary is provided to introduce simplified concepts of multi-screen gestures. The simplified concepts are further described below in the Detailed Description. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

Embodiments of a multi-screen dual tap gesture are described. In various embodiments, a first tap input to a displayed object is recognized at a first screen of a multi-screen system. A second tap input to the displayed object is recognized at a second screen of the multi-screen system, and the second tap input is recognized approximately when the first tap input is recognized. A dual tap gesture can then be determined from the recognized first and second tap inputs. In other embodiments, a single input that contacts both the first and second screens at approximately the same time may be recognized and determined as a dual-tap gesture input. In embodiments, the dual tap gesture can be used to expand or pocket a displayed object. The displayed object can be expanded for full-screen display on the first and second screens when the dual tap gesture is determined while the displayed object is pocketed, or the displayed object can be pocketed when the dual tap gesture is determined while the displayed object is displayed full-screen on the first and second screens.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of multi-screen gestures are described with reference to the following drawings. The same numbers are used throughout the drawings to reference like features and components:

FIG. 1 illustrates an environment of a multi-screen system that can implement various embodiments of multi-screen gestures.

FIG. 2 illustrates an example system with multiple devices that can implement various embodiments of multi-screen gestures for a seamless user experience in ubiquitous environments.

FIG. 3 illustrates an example of multi-screen pinch and expand gestures on a multi-screen system.

FIG. 4 illustrates example method(s) for multi-screen pinch and expand gestures in accordance with one or more embodiments.

FIG. 5 illustrates an example of a multi-screen pinch-to-pocket gesture on a multi-screen system.

FIG. 6 illustrates example method(s) for a multi-screen pinch-to-pocket gesture in accordance with one or more embodiments.

FIG. 7 illustrates an example of a multi-screen dual tap gesture on a multi-screen system.

FIG. 8 illustrates example method(s) for a multi-screen dual tap gesture in accordance with one or more embodiments.

FIG. 9 illustrates an example of a multi-screen hold and tap gesture on a multi-screen system.

FIG. 10 illustrates example method(s) for a multi-screen hold and tap gesture in accordance with one or more embodiments.

FIG. 11 illustrates an example of a multi-screen hold and drag gesture on a multi-screen system.

FIG. 12 illustrates example method(s) for a multi-screen hold and drag gesture in accordance with one or more embodiments.

FIG. 13 illustrates an example of a multi-screen hold and page-flip gesture on a multi-screen system.

FIG. 14 illustrates example method(s) for a multi-screen hold and page-flip gesture in accordance with one or more embodiments.

FIG. 15 illustrates an example of a multi-screen bookmark hold gesture on a multi-screen system.

FIG. 16 illustrates example method(s) for a multi-screen bookmark hold gesture in accordance with one or more embodiments.

FIG. 17 illustrates an example of a multi-screen object-hold and page-change gesture on a multi-screen system.

FIG. 18 illustrates example method(s) for a multi-screen object-hold and page-change gesture in accordance with one or more embodiments.

FIG. 19 illustrates an example of a multi-screen synchronous slide gesture on a multi-screen system.

FIG. 20 illustrates example method(s) for a multi-screen synchronous slide gesture in accordance with one or more embodiments.

FIG. 21 illustrates components of an example device that can implement various embodiments of multi-screen gestures.

DETAILED DESCRIPTION

Embodiments of multi-screen gestures provide that a user of one or more computing devices in a multi-screen system can provide inputs at more than one screen of the system to initiate computing device functions. In various embodiments of multi-screen gestures, a multi-screen system includes two or more screens that may be implemented as independent devices, or integrated into a single, multi-screen device. A user can input any type of various inputs or combinations of inputs, such as select, hold, motion, touch, and/or tap inputs that are recognized at multiple screens of a multi-screen system or multi-screen device. A multi-screen gesture can then be recognized from a combination of the various inputs to initiate a computing device function. Accordingly, the multi-screen gestures provide that the user can provide the various inputs to a multi-screen system or device in an intuitive manner, rather than by conventional techniques used to input commands to a computer device.

In various embodiments, multi-screen gestures can be implemented by a computer device having multiple screens. Alternatively, multi-screen gestures can be implemented by a multi-screen system of two or more screens that may not be physically connected or integrated into a single device, but rather are communicatively linked such as via a data or network connection. A multi-screen system can include multiple, independent slate or handheld devices that may automatically discover one another, are explicitly paired by a user, or are otherwise positioned in temporary physical proximity.

In various embodiments of multi-screen gestures, a multi-screen pinch gesture can be used to condense a displayed object on multiple screens of a multi-screen system or device. Alternatively, a multi-screen expand gesture can be used to expand a displayed object for display on multiple screens of the multi-screen system or device. Multi-screen pinch and expand gestures may also semantically zoom through different levels of an information architecture associated with a display, object, and/or application. A multi-screen pinch-to-pocket gesture can be used to pocket a displayed object, such as to save the displayed object as a thumbnail image under a bezel of a multi-screen system or device.

A multi-screen dual tap gesture can be used to expand or pocket a displayed object that is displayed on multiple screens of a multi-screen system or device. For example, a displayed object can be expanded for full-screen display on first and second screens when a dual tap gesture is determined while the displayed object is pocketed. Alternatively, a displayed object can be pocketed when a dual tap gesture is determined while the displayed object is displayed full-screen on the first and second screens.

A multi-screen hold and tap gesture can be used to move and/or copy a displayed object from one displayed location to another, such as to move or copy an object onto a journal page, or incorporate the object into a notebook. A multi-screen hold and drag gesture can be used to maintain a display of a first part of a displayed object on one screen and drag a second part of the displayed object that is displayed on another screen to pocket the second part of the displayed object for a split-screen view. Alternatively, a hold and drag gesture can be used to maintain a display of a first part of the displayed object on one screen and drag a pocketed second part of the displayed object to expand the display on another screen.

A multi-screen hold and page-flip gesture can be used to select a journal page that is displayed on one screen and flip journal pages to display two additional or new journal pages, much like flipping pages in a book. The journal pages are flipped in a direction of the selected journal page to display the two new journal pages, much like flipping pages forward or backward in a book. Alternatively, a hold and page-flip gesture can be used to maintain the display of a journal page that is displayed on one screen and flip journal pages to display a different journal page on another screen. Non-consecutive journal pages can then be displayed side-by-side, which for a book, would involve tearing a page out of the book to place it in a non-consecutive page order to view it side-by-side with another page.

A multi-screen bookmark hold gesture can be used to bookmark a journal page at a location of a hold input to the journal page on a screen, and additional journal pages can be flipped for viewing while the bookmark is maintained for the journal page. A bookmark hold gesture mimics the action of a reader holding a thumb or finger between pages to save a place in a book while flipping through other pages of the book. Additionally, a bookmark is a selectable link back to the journal page, and a selection input of the bookmark flips back to display the journal page on the screen. A multi-screen object-hold and page-change gesture can be used to move and/or copy a displayed object from one display location to another, such as to incorporate a displayed object for display on a journal page. Additionally, a relative display position can be maintained when a displayed object is moved or copied from one display location to another.

A multi-screen synchronous slide gesture can be used to move a displayed object from one screen for display on another screen, replace displayed objects on the device screens with different displayed objects, move displayed objects to reveal a workspace on the device screens, and/or cycle through one or more workspaces (e.g., applications, interfaces, etc.) that are displayed on the system or device screens. A synchronous slide gesture may also be used to navigate to additional views, or reassign a current view to a different screen. Additionally, different applications or workspaces can be kept on a stack and cycled through, forward and back, with synchronous slide gestures.

While features and concepts of the described systems and methods for a multi-screen gestures can be implemented in any number of different environments, systems, and/or various configurations, embodiments of a multi-screen gestures are described in the context of the following example systems and environments.

FIG. 1 illustrates an environment 100 in an example implementation that is operable to employ multi-screen gesture techniques. The illustrated environment 100 includes an example of a computing device 102 that may be configured in a variety of ways, such as any type of multi-screen computer or device. For example, the computing device 102 may be configured as a computer (e.g., a laptop computer, notebook computer, tablet PC, tabletop computer, and so on), a mobile station, an entertainment appliance, a gaming device, and so forth as further described with reference to FIG. 2. The computing device 102 may also be implemented with software that causes the computing device 102 to perform one or more operations.

In this example environment 100, the computing device 102 is a multi-screen device that includes a first screen 104 and a second screen 106, which can each be implemented as any type of display device, display system, and/or touch-screen. The first and second screens can display any type of background or desktop, as well as user interfaces and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The first and second screens can also display journal pages, such as any type of notebook, periodical, book, paper, a single page, and the like in an electronic form.

The computing device 102 includes a gesture module 108 that is representative of functionality to determine gestures and cause operations to be performed that correspond to the gestures. The computing device also includes an input recognition system 110 implemented to recognize various inputs or combinations of inputs, such as a select input, hold input, motion input, touch input, tap input, and the like. The input recognition system 110 may include any type of input detection features to distinguish the various types of inputs, such as sensors, light sensing pixels, touch sensors, cameras, and/or a natural user interface that interprets user interactions, gestures, inputs, and motions. In implementations, the input recognition system 110 can detect motion inputs at the first or second screens from discernable variables, such as from a direction variable (e.g., right-to-left or vice-versa); from start region position variables (e.g., left1, top1, right1, bottom1) and end region position variables (e.g., left2, top2, right2, bottom2); and/or from a motion rate variable (e.g., a particular number of pixels per second).

The input recognition system 110 recognizes the various types of inputs, and the gesture module 108 identifies or determines a multi-screen gesture from the recognized inputs. For example, the input recognition system 110 can recognize a first input at the first screen 104, such as a touch input 112, and recognize a second input at the second screen 106, such as a select input 114. The gesture module 108 can then determine a type of multi-screen gesture from the recognized touch and select inputs. An input at the first or second screen may also be recognized as including attributes (e.g., movement, a selection point, etc.) that differentiate one type of input from another input as recognized by the input recognition system 110. This differentiation may then serve as a basis to identify or determine a motion input from a touch input, and consequently an operation that is to be performed based on a determination of the corresponding gesture. In implementations, the computing device 102 may include a gestures database that includes various determinable representations of gestures, inputs, and/or motions from which the gesture module 108 can determine or identify a multi-screen gesture.

The computing device 102 can also be implemented to recognize and differentiate between the various inputs, such as a touch input and a stylus input. The differentiation may be performed in a variety of ways, such as by recognizing the size of a finger input versus the size of a stylus input. Differentiation may also be performed through use of a camera to distinguish a touch input (e.g., holding up one or more fingers), a stylus input (e.g., holding two fingers together to indicate a point), or an input via a natural user interface (NUI). A variety of other techniques for distinguishing the various types of inputs are contemplated.

A variety of different types of inputs may be recognized by the input recognition system 110, and a variety of different gestures may be determined by the gesture module 108, such a gestures that are recognized as a single type of input as well as gestures involving multiple types of inputs. Accordingly, the gesture module 108 of computing device 102 may include a bimodal input module 116 that is representative of functionality to recognize inputs and identify or determine gestures involving bimodal inputs. The gesture module 108 may support a variety of different gesture techniques by recognizing and leveraging different types of inputs through use of the bimodal input module 116. For instance, the bimodal input module 116 may be configured to recognize a stylus as a writing tool, whereas touch is employed to manipulate objects displayed on the first or second screen. It should be noted that by differentiating between the various types of inputs, the number of gestures that are made possible by each of these inputs alone is also increased.

Accordingly, the gesture module 108 can support a variety of different multi-screen gestures 118, both bimodal and otherwise. Examples of the multi-screen gestures 118 described herein include pinch and expand gestures 120, a pinch-to-pocket gesture 122, a dual tap gesture 124, a hold and tap gesture 126, a hold and drag gesture 128, a hold and page-flip gesture 130, a bookmark hold gesture 132, an object-hold and page-change gesture 134, and a synchronous slide gesture 136. Each of these different multi-screen gestures is described in a corresponding section in the following discussion. Although each multi-screen gesture is described in a different section, it should be readily apparent that the features of these gestures may be combined and/or separated to support additional gestures. Therefore, the description is not limited to these examples. Additionally, although the following discussion may describe specific examples of select, hold, motion, touch, and tap inputs, the various types of inputs may be switched in different instances (e.g., a touch input may be used as a select input, and vice versa) and/or both inputs may be provided with the same input without departing from the spirit and scope thereof.

The illustrated environment 100 also includes an example of a multi-screen system 138 that includes two (or more) devices that each have a screen, such as a first device 140 that has a screen 142, and a second device 144 that has a screen 146. The screens are not physically connected or integrated into a single device, but rather are communicatively linked such as via a data or network connection. A multi-screen system can include multiple, independent slate or handheld devices that may automatically discover one another, are explicitly paired by a user, or are otherwise positioned in temporary physical proximity. In an implementation, a multi-screen system may also include a multi-screen device. The first device 140 and the second device 144 of the multi-screen system 138 can each be configured as described with reference to computing device 102 in any form of a computer (e.g., a laptop computer, notebook computer, tablet PC, tabletop computer, and so on), a mobile station, an entertainment appliance, a gaming device, and so forth.

FIG. 2 illustrates an example system 200 that includes the computing device 102 as described with reference to FIG. 1. The example system 200 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 200, 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 embodiment, the central computing device is a “cloud” server farm, which comprises one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link. In one embodiment, 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 embodiment, 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 102 may assume a variety of different configurations, such as for computer 202, mobile 204, and television 206 uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device 102 may be configured according to one or more of the different device classes. For instance, the computing device 102 may be implemented as the computer 202 class of a device that includes a personal computer, desktop computer, a multi-screen tabletop computer, laptop computer, netbook, and so on. The computing device 102 may also be implemented as the mobile 204 class of device that includes mobile devices, such as a mobile phone, portable music player, portable gaming device, a tablet computer, a multi-screen tablet computer, and so on. The computing device 102 may also be implemented as the television 206 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 102 and are not limited to the specific examples of multi-screen gestures described in the following sections.

The cloud 208 includes and/or is representative of a platform 210 for server-based services 212. The platform 210 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 208. The server-based services 212 may include applications and/or data that can be utilized while all or most of the computer processing is executed on servers that are remote from the computing device 102. Server-based services can be provided as a service over the Internet and/or through a subscriber network, such as a cellular or WiFi network.

The platform 210 may abstract resources and functions to connect the computing device 102 with other computing devices. The platform 210 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the server-based services 212 that are implemented via the platform 210. Accordingly, in an interconnected device embodiment, implementation of functionality of the gesture module 108 may be distributed throughout the system 200. For example, the gesture module 108 may be implemented in part on the computing device 102 as well as via the platform 210 that abstracts the functionality of the cloud 208.

Further, the functionality may be supported by the computing device 102 in any one or more of the configurations. For example, the multi-screen gesture techniques supported by the gesture module 108 and the input recognition system 110 may be recognized using track pad functionality in the computer 202 configuration, touch-screen functionality in the mobile 204 configuration, and/or recognized by a camera as part of a natural user interface (NUI) that does not involve contact with a specific input device in the television 206 configuration. Further, performance of the operations to detect and recognize the inputs to identify or determine a particular multi-screen gesture may be distributed throughout the system 200, such as by the computing device 102 and/or the server-based services 212 supported by the platform 210 of the cloud 208.

In addition to the following sections that describe the various multi-screen gestures, example methods are also described with reference to respective figures in accordance with various embodiments of multi-screen gestures. Generally, any of the functions, methods, procedures, components, and modules described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. A software implementation represents program code that performs specified tasks when executed by a computer processor. The example methods may be described in the general context of computer-executable instructions, which can include software, applications, routines, programs, objects, components, data structures, procedures, modules, functions, and the like. The program code can be stored in one or more computer-readable memory devices, both local and/or remote to a computer processor. The methods may also be practiced in a distributed computing environment by multiple computer devices. Further, the features described herein are platform-independent and can be implemented on a variety of computing platforms having a variety of processors.

Multi-Screen Pinch and Expand Gestures

FIG. 3 illustrates examples 300 of multi-screen pinch and expand gestures on a multi-screen system 302, which in these examples, is shown as a two-screen device. The multi-screen system 302 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 302 includes a first screen 304 and a second screen 306, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 302 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of multi-screen pinch and expand gestures can be implemented by a multi-screen system having more than two screens.

A multi-screen pinch gesture can be used to condense a displayed object on multiple screens of a multi-screen system. Alternatively, a multi-screen expand gesture can be used to expand a displayed object for display on multiple screens of the multi-screen system. In the first view 308 of the multi-screen system 302, a first journal page 310 is displayed on the first screen 304, and a second journal page 312 is displayed on the second screen 306. The input recognition system 110 is implemented to recognize a first input 314 at the first screen 304, where the first input also includes a first motion input 316. The input recognition system 110 can also recognize a second input 318 at the second screen 306, where the second input also includes a second motion input 320, and the second input is recognized approximately when the first input is recognized.

The gesture module 108 is implemented to determine the multi-screen pinch gesture from the motion inputs 316, 320 that are associated with the recognized first and second inputs 314, 318. The pinch gesture can be identified as a cross-screen combination of the first and second motion inputs that are effective to condense the displayed journal pages 310, 312. In an implementation, the input recognition system 110 can recognize that a distance between the first and second inputs changes (e.g., decreases) with the motion inputs. The change in distance may also have minimum distance thresholds. The gesture module 108 can then determine the pinch gesture from a decrease in the distance between the first and second inputs.

In some embodiments, a multi-screen pinch gesture is determined when the gesture motion inputs are recognized within a defined zone or region proximate the edge shared by the screens, such as a bezel that separates the first and second screens on the multi-screen device. The zone or region proximate the bezel can be defined as a minimum distance from the edge or bounding rectangle where a pinch gesture is recognized. In other embodiments, segments of a pinch gesture may be incrementally recognized, such as when a pinch gesture is composed of: approximate synchronous inputs (e.g., finger-touch-contacts) on adjacent edges; the first input 314 holds while the second motion input 320 slides toward the bezel (e.g., one finger holding while the other finger slides toward the common edge); or approximate synchronous lifts of both fingers resulting in a composite pinch gesture. Additionally, a user can input expand and pinch gestures in opposite directions back and forth between the gesture states until lifting the first and second inputs. Similar to a double-tap gesture on a user interface, applications can subscribe to a composite high-level pinch and/or expand gesture that includes some or all of the gesture segments.

The second view 322 of the multi-screen system 302 illustrates a transition of the journal pages 310, 312 being condensed from an original position 324 in a direction 326 in response to the pinch gesture. The third view 328 of the multi-screen system 302 illustrates the journal pages 310, 312 condensed for display. The pinch gesture gives the appearance of zooming-out when a displayed object is condensed. In this example, the pinch gesture condenses the journal pages, zooming-out to a virtual desktop 330 on the multi-screen system 302. The virtual desktop 330 may be used as a space to navigate to other journals or books, drag displayed objects between journal pages, or leave reminders such as posted notes and to-do lists that are visible for quick access outside of any particular individual notebook, e-book, journal, or document. Alternate navigable views may include: an organizational view of thumbnail images of multiple pages of a notebook (e.g., a “light table view”); a minimized or shrunken-down version of the current notebook with multiple pages, page tabs, and/or bookmarks protruding from the notebook, and a surround similar to the virtual desktop 330 (e.g., a “butterfly view”); a “library view” across multiple books and/or journals; or a home screen.

From the third view 328, a multi-screen expand gesture can be used to return to the full-screen view of the journal pages, such as shown in the first view 308. The gesture module 108 is also implemented to determine the multi-screen expand gesture that can be identified as a cross-screen combination of motion inputs that are effective to expand the journal pages 310, 312 from the condensed display shown in the third view 328 of the multi-screen system. In an implementation, the input recognition system 110 can recognize that a distance between inputs changes (e.g., increases) with motion inputs. The gesture module 108 can then determine the expand gesture from an increase in the distance between inputs. A transition from the third view 328 back to the first view 308 of the multi-screen system 302 illustrates that the journal pages 310, 312 are expanded for full-screen display on the first and second screens. The expand gesture gives the appearance of zooming-in when a displayed object is expanded.

It should be noted that the representations of the first and second inputs, as well as the indications of motion directions, are merely illustrative for discussion purposes and may or may not appear on the screens of the multi-screen system when described embodiments are implemented. Additionally, any description herein of an input or motion at one screen that may correlate to another input or motion at another screen is applicable to either the first or second screens of the multi-screen system. Additionally, a three-, four-, or five-finger multi-screen pinch or expand gesture that spans two or more screens is also contemplated, as are two-handed stretch and squeeze gestures that may be recognized and determined from multiple finger and/or contact inputs.

FIG. 4 illustrates example method(s) 400 of multi-screen pinch and expand gestures. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 402, a first input is recognized at a first screen of a multi-screen system, the first input including a first motion input. For example, the input recognition system 110 recognizes the first input 314 at the first screen 304 of the multi-screen system 302, the first input including the first motion input 316. At block 404, a second input is recognized at a second screen of the multi-screen system, the second input including a second motion input. For example, the input recognition system 110 also recognizes the second input 318 at the second screen 306, the second input including the second motion input 320, and the second input being recognized approximately when the first input is recognized. Alternatively or in addition, the first input 314 at the first screen 304 may initiate a time-out (e.g., 500 ms) with the input recognition system 110 after which the first input is processed for other single screen gestures if the second input is not provided.

At block 406, a change in distance between the first and second inputs is recognized based on the first and second motion inputs. For example, the input recognition system 110 recognizes that a distance between the first and second inputs 314, 318 changes (e.g., increases or decreases) with the motion inputs. At block 408, a determination is made as to whether the distance change between the first and second inputs is a decrease in the distance.

If the distance decreases between the first and second inputs (i.e., “yes” from block 408), then at block 410, a pinch gesture is determined, which gives the appearance of zooming-out when a displayed object is condensed. For example, the gesture module 108 determines the pinch gesture based on the first and second motion inputs that decrease the distance between the first and second inputs. The pinch gesture can be identified as a cross-screen combination of the first and second motion inputs that are effective to condense a displayed object, such as the displayed journal pages 310, 312. The pinch gesture gives the appearance of zooming-out when a displayed object is condensed.

If the distance increases between the first and second inputs (i.e., “no” from block 408), then at block 412, an expand gesture is determined, which gives the appearance of zooming-in when a displayed object is expanded. For example, the gesture module 108 determines the expand gesture based on the first and second motion inputs that increase the distance between the first and second inputs. The expand gesture can be identified as a cross-screen combination of the first and second motion inputs that are effective to expand a displayed object, such as when the displayed journal pages 310, 312 are expanded for full-screen display on the first and second screens of the multi-screen system 302.

Multi-Screen Pinch-to-Pocket Gesture

FIG. 5 illustrates examples 500 of a multi-screen pinch-to-pocket gesture on a multi-screen system 502, which in these examples, is shown as a two-screen device. The multi-screen system 502 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 502 includes a first screen 504 and a second screen 506, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 502 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen pinch-to-pocket gesture can be implemented by a multi-screen system having more than two screens.

A multi-screen pinch-to-pocket gesture can be used to pocket a displayed object, such as to save the displayed object as a thumbnail image under a bezel of a multi-screen system. In the first view 508 of the multi-screen system 502, a first journal page 510 is displayed on the first screen 504, and a second journal page 512 is displayed on the second screen 506. The input recognition system 110 is implemented to recognize a first motion input 514 to a first screen region 516 at the first screen 504, where the first motion input is recognized when the first journal page 510 is selected. The input recognition system 110 can also recognize a second motion input 518 to a second screen region 520 at the second screen 506, where the second motion input is recognized when the second journal page 512 is selected. The first screen region 516 of the first screen 504 and the second screen region 520 of the second screen 504 are shown in a second view 522 of the multi-screen system 502.

The gesture module 108 is implemented to determine the pinch-to-pocket gesture from the recognized motion inputs 514, 518. The pinch-to-pocket gesture can be identified as a cross-screen combination of the first and second motion inputs that are effective to condense the displayed journal pages 510, 512 within the first and second screen regions 516, 520 and pocket the journal pages proximate a bezel 524 that separates the first and second screens. Optionally, the gesture module 108 may also determine the pinch-to-pocket gesture from the first and second motion inputs 514, 518 that decrease a distance between a first input to the journal page 510 on the first screen 504 and a second input to the second journal page 512 on the second screen 506.

The second view 522 of the multi-screen system 502 illustrates a transition of the journal pages 510, 512 being condensed from an original position 526 in a direction 528 in response to the pinch-to-pocket gesture. The third view 530 of the multi-screen system 502 illustrates the displayed object (e.g., the journal pages) pocketed proximate the bezel 524 and saved as a thumbnail image 532 for display. In this example, more of the virtual desktop 534 is displayed, and any of the other displayed objects on the desktop are accessible while the journal pages are pocketed as the thumbnail image 532. In another example, a displayed object 536 (e.g., shown displayed as a sketch of the text “zeal” on the computing device 102 in FIG. 1) is pocketed under the bezel 524 of the multi-screen system 502.

When displayed objects are pocketed to display the virtual desktop 534 for access to the many other displayed objects, a user can interleave multiple tasks in multiple journals or application views, and then easily return to the pocketed items. Additionally, a pocketed item can be dropped onto a notebook or journal page of an open notebook to incorporate the item in the context of other work and notations.

In various embodiments, a multi-screen pinch-to-pocket gesture may be used as a general mechanism for multi-tasking between different working sets of screen views and/or applications. For example, if a Web browser is displayed on the first screen 504 and a journal page is displayed on the second screen 506, then a user can pinch-to-pocket that pairing of screen views. A user may also pinch-to-pocket multiple screen views, in which case the set of pocketed views along the bezel 524 of the device appear as a taskbar from which the user can alternate between different applications and views.

In embodiments, the thumbnail image 532 of the journal pages is saved to a visual clip-board when pocketed. Additionally, the thumbnail image 532 may be displayed on the first and/or second screens as a selectable link to the journal pages when the displayed object is pocketed. From this third view 530, the input recognition system 110 can recognize a select input that the gesture module 108 determines as a tap gesture on the thumbnail image 532 that is effective to expand the journal pages 510, 512 for display on the first and second screens, such as shown in the first view 508 of the multi-screen system 502.

It should be noted that the representations of the first and second inputs and the indications of the motion directions, as well as the screen regions, are merely illustrative for discussion purposes and may or may not appear on the screens of the multi-screen system when described embodiments are implemented. Additionally, any description herein of an input or motion at one screen that may correlate to another input or motion at another screen is applicable to either the first or second screens of the multi-screen system.

FIG. 6 illustrates example method(s) 600 of a multi-screen pinch-to-pocket gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 602, a first motion input to a first screen region is recognized at a first screen of a multi-screen system, the first motion input being recognized to select a displayed object. For example, the input recognition system 110 recognizes the first motion input 514 to the first screen region 516 at the first screen 504, and the first motion input is recognized when the first journal page 510 is selected. At block 604, a second motion input to a second screen region is recognized at a second screen of the multi-screen system, the second motion input being recognized to select the displayed object. For example, the input recognition system 110 also recognizes the second motion input 518 to the second screen region 520 at the second screen 506, and the second motion input is recognized when the second journal page 512 is selected.

At block 606, a pinch-to-pocket gesture is determined from the recognized first and second motion inputs within the respective first and second screen regions. For example, the gesture module 108 determines the pinch-to-pocket gesture from the recognized motion inputs 514, 518. The pinch-to-pocket gesture can be identified as a cross-screen combination of the first and second motion inputs that are effective to condense the displayed journal pages 510, 512 within the first and second screen regions 516, 520 and pocket the journal pages proximate the bezel 524 that separates the first and second screens. Alternatively or in addition, the pinch-to-pocket gesture is determined from the first and second motion inputs that decrease a distance between a first input to the first journal page 510 on the first screen and a second input to the second journal page 512 on the second screen.

At block 608, the displayed object is pocketed proximate a bezel of the multi-screen system that separates the first and second screens. For example, the journal pages 510, 512 (e.g., the displayed object) are pocketed proximate the bezel 524 and saved as a thumbnail image 532 for display. In an embodiment, the thumbnail image 532 is a selectable link to the journal pages pocketed and/or the displayed object is saved to a visual clip-board.

At block 610, a select input is recognized as a tap gesture on the displayed object that is pocketed and, at block 612, the displayed object is expanded for display on the first and second screens in response to the tap gesture. For example, the input recognition system 110 recognizes a select input that the gesture module 108 determines as a tap gesture on the thumbnail image 532 that is effective to expand the journal pages 510, 512 for display on the first and second screens of the multi-screen system 502.

Multi-Screen Dual Tap Gesture

FIG. 7 illustrates examples 700 of a multi-screen dual tap gesture on a multi-screen system 702, which in these examples, is shown as a two-screen device. The multi-screen system 702 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 702 includes a first screen 704 and a second screen 706, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 702 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen dual tap gesture can be implemented by a multi-screen system having more than two screens.

A multi-screen dual tap gesture can be used to expand or pocket a displayed object that is displayed on multiple screens of a multi-screen system. For example, a displayed object can be expanded for full-screen display on first and second screens when a dual tap gesture is determined while the displayed object is pocketed. Alternatively, a displayed object can be pocketed when a dual tap gesture is determined while the displayed object is displayed full-screen on the first and second screens.

In the first view 708 of the multi-screen system 702, a first journal page 710 is displayed on the first screen 704, and a second journal page 712 is displayed on the second screen 706. The input recognition system 110 is implemented to recognize a first tap input 714 to the first journal page 710 at the first screen 704. The input recognition system 110 can also recognize a second tap input 716 to the second journal page 712 at the second screen 706, where the second tap input is recognized approximately when the first tap input is recognized.

Alternatively, a single input (e.g., with a finger, thumb, palm, etc.) may contact both the first and second screens at approximately the same time to initiate a dual-tap gesture input. For example, the multi-screen device may have little or no spine, housing, or bezel between the screens, in which case a single input can contact both screens together. Further, a multi-screen system with two (or more) independent screens may be positioned such that a thumb or finger between the screens (e.g., like a finger placed between pages in a book) makes contact with both screens.

The gesture module 108 is implemented to determine the multi-screen dual tap gesture from the recognized tap inputs 714, 716. The dual tap gesture can be identified as a cross-screen combination of the first and second tap inputs. The second view 718 of the multi-screen system 702 illustrates that the dual tap gesture is effective to pocket the journal pages as a thumbnail image 720 proximate a bezel 722 of the multi-screen system that separates the first and second screens. In this example, the virtual desktop 724 is displayed, and any of the other displayed objects on the desktop are accessible while the journal pages are pocketed as the thumbnail image 720.

The second view 718 of the multi-screen system 702 also illustrates that a dual tap gesture is effective to expand a displayed object for display on the first and second screens of the multi-screen system. For example, the input recognition system 110 is implemented to recognize a first tap input 726 to the thumbnail image 720 at the first screen 704, and recognize a second tap input 728 to the thumbnail image 720 at the second screen 706, where the second tap input is recognized approximately when the first tap input is recognized. The gesture module 108 can then determine the multi-screen dual tap gesture from the recognized tap inputs 726, 728, and the dual tap gesture effective to expand the journal pages 710, 712 for display on the first and second screens as shown in the first view 708 of the multi-screen system 702.

The third view 730 of the multi-screen system 702 illustrates a split-screen view that includes a first part of the displayed object being displayed full-screen on the first screen and a second part of the displayed object being displayed condensed on the second screen. For example, the first journal page 710 is displayed full-screen on the first screen 704, and the second journal page 712 is pocketed for display on the second screen 706. In an implementation, the input recognition system 110 can recognize a single select input to one of the journal pages 710, 712 on one of the first or second screens, such as one of the tap inputs 726, 728 shown in the second view 718 of the multi-screen system 702. The single tap input is effective to initiate the split-screen view of the journal pages, such as shown in the third view 730 of the multi-screen system 702.

It should be noted that the representations of the first and second inputs are merely illustrative for discussion purposes and may or may not appear on the screens of the multi-screen system when described embodiments are implemented. Additionally, any description herein of an input or motion at one screen that may correlate to another input or motion at another screen is applicable to either the first or second screens of the multi-screen system.

FIG. 8 illustrates example method(s) 800 of a multi-screen dual tap gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 802, a first tap input to a displayed object is recognized at a first screen of a multi-screen system. For example, the input recognition system 110 recognizes the first tap input 714 to the first journal page 710 at the first screen 704. At block 804, a second tap input to the displayed object is recognized at a second screen of the multi-screen system, the second tap input being recognized approximately when the first tap input is recognized. For example, the input recognition system 110 also recognizes the second tap input 716 to the second journal page 712 at the second screen 706, and the second tap input is recognized approximately when the first tap input is recognized.

At block 806, a dual tap gesture is determined from the recognized first and second tap inputs. For example, the gesture module 108 determines the multi-screen dual tap gesture from the recognized tap inputs 714, 716. The dual tap gesture can be identified as a cross-screen combination of the first and second tap inputs, and the dual tap gesture is effective to expand or pocket a displayed object that is displayed on the first and second screens of the multi-screen system 702. Alternatively, a single input (e.g., with a finger, thumb, palm, etc.) that contacts both the first and second screens at approximately the same time may be recognized and determined as a dual-tap gesture input. In embodiments, a displayed object can be expanded for full-screen display on the first and second screens when a dual tap gesture is determined while the displayed object is pocketed. Alternatively, a displayed object can be pocketed when a dual tap gesture is determined while the displayed object is displayed full-screen on the first and second screens.

At block 808, a single select input to the displayed object is recognized on one of the first or second screens effective to initiate a split-screen view of the displayed object. For example, the input recognition system 110 recognizes a single select input to one of the journal pages 710, 712 on one of the first or second screens, such as one of the tap inputs 726, 728 shown in the second view 718 of the multi-screen system 702. The single tap input is effective to initiate the split-screen view of the journal pages, such as shown in the third view 730 of the multi-screen system 702.

Multi-Screen Hold and Tap Gesture

FIG. 9 illustrates examples 900 of a multi-screen hold and tap gesture on a multi-screen system 902, which in these examples, is shown as a two-screen device. The multi-screen system 902 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 902 includes a first screen 904 and a second screen 906, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 902 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen hold and tap gesture can be implemented by a multi-screen system having more than two screens.

A multi-screen hold and tap gesture can be used to move and/or copy a displayed object from one displayed location to another, such as to move or copy an object onto a journal page, or incorporate the object into a notebook. In various embodiments, general functionality may include: a hold input to a command on one screen and a tap input on the other screen to apply the command on the other screen; a hold input to a parameter value (e.g., a color, brush thickness, image effect, filter, and the like) and a tap input on the other screen to apply the parameter value to an object displayed on the other screen; and/or a hold input to a tag, category, or other metadata, and a tap input to apply the feature to an object displayed on the other screen. In one example, a journal or notebook may include custom stickers that may be viewed on a page of the journal or notebook. A sticker can be held on one page (e.g., as displayed on one screen) and then tapped to apply the sticker at the tap location on another page (e.g., on the other screen). The stickers may have specific semantics attached to them, such as “Expense”, “To-do”, “Personal”, “Recipe”, or the like, and a sticker can be utilized to tag content to facilitate subsequent search and organization.

In the first view 908 of the multi-screen system 902, a journal page 910 is displayed on the first screen 904, and various objects, such as displayed object 912, are displayed on the virtual desktop 914 on the second screen 906. The input recognition system 110 is implemented to recognize a hold input 916 at the second screen 906, where the hold input is recognized when held to select the displayed object 912 on the second screen 906. The input recognition system 110 can also recognize a tap input 918 at the first screen 904, where the tap input is recognized while the displayed object 912 is selected on the second screen 906.

The gesture module 108 is implemented to determine the multi-screen hold and tap gesture from the recognized hold and tap inputs 916, 918. The hold and tap gesture can be identified as a cross-screen combination of the hold and tap inputs, and the gesture is effective to move the displayed object 912 from a displayed location on the second screen 906 to a tap input location for display on the first screen 904, as indicated at 920. The second view 922 of the multi-screen system 902 illustrates that the dual tap gesture is effective to move the displayed object 912 from the displayed location 924 on the second screen 906 and incorporate the displayed object 912 for display on the journal page 910 that is displayed at the tap input location 926 on the first screen 904. The third view 928 of the multi-screen system 902 illustrates that the dual tap gesture is effective to copy the displayed object 912 to generate an object copy 930, and initiate a display of the object copy 930 at a tap input location 932 on the first screen 904.

In other embodiments of a multi-screen hold and tap gesture, the input recognition system 110 can recognize the tap input 918 to an additional displayed object (e.g., the journal page 910) on the first screen 904, and the hold and tap gesture is then effective to correlate the displayed object 912 with the additional displayed object (e.g., correlate the displayed object 912 with the journal page 910). Additionally, a displayed object may represent a function, and the hold and tap gesture is effective to apply the function of the displayed object to an additional displayed object at a tap input location on first or second screen of the multi-screen system 902.

It should be noted that the representations of the hold and tap inputs are merely illustrative for discussion purposes and may or may not appear on the screens of the multi-screen system when described embodiments are implemented. Additionally, any description herein of an input or motion at one screen that may correlate to another input or motion at another screen is applicable to either the first or second screens of the multi-screen system.

FIG. 10 illustrates example method(s) 1000 of a multi-screen hold and tap gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 1002, a hold input is recognized at a first screen of a multi-screen system, the hold input being recognized when held to select a displayed object on the first screen. For example, the input recognition system 110 recognizes the hold input 916 at screen 906, and the hold input is recognized when held to select the displayed object 912 on screen 906. At block 1004, a tap input is recognized at a second screen of the multi-screen system, the tap input being recognized while the displayed object is selected. For example, the input recognition system 110 also recognizes the tap input 918 at screen 904, and the tap input is recognized while the displayed object 912 is selected on screen 906. In an embodiment, the tap input may be recognized as a tap input to an additional displayed object on the second screen, and the hold and tap gesture is effective to correlate the displayed object with the additional displayed object.

At block 1006, a hold and tap gesture is determined from the recognized hold and tap inputs. For example, the gesture module 108 determines the multi-screen hold and tap gesture from the recognized hold and tap inputs 916, 918, and the hold and tap gesture can be identified as a cross-screen combination of the hold and tap inputs. In various embodiments, the hold and tap gesture is effective to move the displayed object from a displayed location on the first screen to a tap input location for display on the second screen (at block 1008); incorporate the displayed object for display on a journal page that is displayed at a tap input location on the second screen (at block 1010); copy the displayed object to generate an object copy, and display the object copy at a tap input location on the second screen (at block 1012); and/or apply a function of the displayed object to an additional displayed object at a tap input location on the second screen (at block 1014).

Multi-Screen Hold and Drag Gesture

FIG. 11 illustrates examples 1100 of a multi-screen hold and drag gesture on a multi-screen system 1102, which in these examples, is shown as a two-screen device. The multi-screen system 1102 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 1102 includes a first screen 1104 and a second screen 1106, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 1102 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen hold and drag gesture can be implemented by a multi-screen system having more than two screens.

A multi-screen hold and drag gesture can be used to maintain a display of a first part of a displayed object on one screen and drag a second part of the displayed object that is displayed on another screen to pocket the second part of the displayed object for a split-screen view. Alternatively, a hold and drag gesture can be used to maintain a display of a first part of the displayed object on one screen and drag a pocketed second part of the displayed object to expand the display on another screen. The direction of a dragging gesture may also be determined based on different semantics (e.g., motion up, down, towards the bezel, away from the bezel, etc.). For the multi-screen hold and drag gesture, four to eight cardinal directions can be defined for different actions.

In the first view 1108 of the multi-screen system 1102, a first journal page 1110 is displayed on the first screen 1104, and a second journal page 1112 is displayed on the second screen 1106. The input recognition system 110 is implemented to recognize a hold input 1114 at the first screen 1104, where the hold input is recognized when held in place. The input recognition system 110 can also recognize a motion input 1116 at the second screen 1106, where the motion input is recognized to select a displayed object (e.g., the journal page 1112) while the hold input remains in place.

The gesture module 108 is implemented to determine the multi-screen hold and drag gesture from the recognized hold and motion inputs 1114, 1116. The hold and drag gesture can be identified as a cross-screen combination of the hold and motion inputs, and the gesture is effective to maintain the display of the first journal page 1110 on the first screen 1104 and drag the second journal page 1112 that is displayed on the second screen 1106 to pocket the second journal page for a split-screen view of the journal pages. The second view 1118 of the multi-screen system 1102 illustrates that the first journal page 1110 is maintained for display on the first screen 1104, and the second journal page 1112 is pocketed proximate the bezel 1120 of the multi-screen system on the second screen 1106 for a split-screen view of the journal pages in response to the hold and drag gesture. In an embodiment, the second journal page 1112 is pocketed as a thumbnail image, which may also be a selectable link to the second journal page 1112.

The third view 1122 of the multi-screen system 1102 illustrates a multi-screen hold and drag gesture can be used to maintain a display of a first part of a displayed object on one screen and drag a pocketed second part of the displayed object to expand the display on another screen, or initiate a multi-screen display of the displayed object. For example, the input recognition system 110 can recognize a hold input 1124 at the first screen 1104, where the hold input is recognized when held in place. The input recognition system 110 can also recognize a motion input 1126 at the second screen 1106, where the motion input is recognized to select the second journal page 1112 when the journal page is pocketed (e.g., the journal page 1112 as shown in the second view 1118) while the hold input remains in place (e.g., to hold the first journal page 1110). The gesture module 108 can determine a multi-screen hold and drag gesture from the recognized hold and motion inputs 1124, 1126, effective to expand the pocketed second journal page 1112 in a direction 1128 for display on the second screen 1106.

It should be noted that the representations of the hold and motion inputs are merely illustrative for discussion purposes and may or may not appear on the screens of the multi-screen system when described embodiments are implemented. Additionally, any description herein of an input or motion at one screen that may correlate to another input or motion at another screen is applicable to either the first or second screens of the multi-screen system.

FIG. 12 illustrates example method(s) 1200 of a multi-screen hold and drag gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 1202, a hold input is recognized at a first screen of a multi-screen system, the hold input being recognized when held in place. For example, the input recognition system 110 recognizes the hold input 1114 at the first screen 1104, where the hold input is recognized when held in place. At block 1204, a motion input is recognized at a second screen of the multi-screen system, the motion input being recognized to select a displayed object while the hold input remains in place. For example, the input recognition system 110 also recognizes the motion input 1116 at the second screen 1106, where the motion input is recognized to select the second journal page 1112 while the hold input remains in place.

At block 1206, a hold and drag gesture is determined from the recognized hold and motion inputs. For example, the gesture module 108 determines the multi-screen hold and drag gesture from the recognized hold and motion inputs 1114, 1116. The hold and drag gesture can be identified as a cross-screen combination of the hold and motion inputs. In various embodiments, the hold and drag gesture is effective to maintain a display of a first part of the displayed object on the first screen and drag a second part of the displayed object that is displayed on the second screen to pocket the second part of the displayed object for a split-screen view (at block 1208); maintain a display of a first part of the displayed object on the first screen and drag a pocketed second part of the displayed object to expand the display on the second screen (at block 1210); maintain a display of the displayed object on the first screen and expand the display of the displayed object onto the second screen (at block 1212); and/or initiate a multi-screen display of the displayed object (at block 1214).

Multi-Screen Hold and Pace-Flip Gesture

FIG. 13 illustrates examples 1300 of a multi-screen hold and page-flip gesture on a multi-screen system 1302, which in these examples, is shown as a two-screen device. The multi-screen system 1302 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 1302 includes a first screen 1304 and a second screen 1306, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 1302 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen hold and page-flip gesture can be implemented by a multi-screen system having more than two screens.

In the first view 1308 of the multi-screen system 1302, a first journal page 1310 is displayed on the first screen 1304, and a second journal page 1312 is displayed on the second screen 1306. The input recognition system 110 is implemented to recognize a hold input 1314 at the first screen 1304, where the hold input is recognized when held to select the journal page 1310 that is displayed on the first screen 1304. The input recognition system 110 can also recognize a motion input 1316 at the second screen 1306, where the motion input is recognized while the hold input remains in place.

The gesture module 108 is implemented to determine the multi-screen hold and page-flip gesture from the recognized hold and motion inputs 1314, 1316. The hold and page-flip gesture can be identified as a cross-screen combination of the hold and motion inputs, which in various embodiments may include: hold and drag inputs on opposite screens with one or two input devices (e.g., one finger, or two fingers); and/or a hold input and a drag input across the bezel onto the opposite screen. The hold and page-flip gesture is effective to select the journal page 1310 on the first screen 1304 while one or more additional journal pages are flipped for display. The second view 1318 of the multi-screen system 1302 illustrates that two additional journal pages 1320, 1322 have been page-flipped for display on the respective first and second screens 1304, 1306. Alternatively, the third view 1324 of the multi-screen system 1302 illustrates that the display of journal page 1310 is maintained on the first screen 1304 and a non-consecutive journal page 1322 has been page-flipped for display side-by-side on the second screen 1306.

FIG. 14 illustrates example method(s) 1400 of a multi-screen hold and page-flip gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 1402, a hold input is recognized at a first screen of a multi-screen system, the hold input being recognized when held to select a journal page that is displayed on the first screen. For example, the input recognition system 110 recognizes the hold input 1314 at the first screen 1304, and the hold input is recognized when held to select the journal page 1310 that is displayed on the first screen 1304. At block 1404, a motion input is recognized at a second screen of the multi-screen system, the motion input being recognized while the hold input remains in place. For example, the input recognition system 110 also recognizes the motion input 1316 at the second screen 1306, and the motion input is recognized while the hold input remains in place.

At block 1406, a hold and page-flip gesture is determined from the recognized hold and motion inputs, and effective to select the journal page while additional journal pages are flipped for display. For example, the gesture module 108 determines the multi-screen hold and page-flip gesture from the recognized hold and motion inputs 1314, 1316. The hold and page-flip gesture is identified as a cross-screen combination of the hold and motion inputs. In various embodiments, the hold and page-flip gesture is effective to select the journal page that is displayed on the first screen and flip journal pages (optionally in a direction of the selected journal page) to display two additional journal pages, one each displayed on the first and second screens (at block 1408); maintain the display of the journal page that is displayed on the first screen and flip journal pages to display a different journal page on the second screen (at block 1410); and/or maintain the display of the journal page that is displayed on the first screen and flip journal pages to display a non-consecutive journal page on the second screen side-by-side with first journal page (at block 1412).

In an embodiment, a hold and page-flip gesture is configurable to select the journal page that is displayed on the first screen and flip journal pages to display two additional journal pages, one each displayed on the first and second screens (as described with reference to block 1408), or to maintain the display of the journal page that is displayed on the first screen and flip the journal pages to display a different journal page on the second screen (as described with reference to blocks 1410 and 1412).

Multi-Screen Bookmark Hold Gesture

FIG. 15 illustrates examples 1500 of a multi-screen bookmark hold gesture on a multi-screen system 1502, which in these examples, is shown as a two-screen device. The multi-screen system 1502 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 1502 includes a first screen 1504 and a second screen 1506, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 1502 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen bookmark hold gesture can be implemented by a multi-screen system having more than two screens.

In the first view 1508 of the multi-screen system 1502, a first journal page 1510 is displayed on the first screen 1504, and a second journal page 1512 is displayed on the second screen 1506. The first journal page 1510 is displayed over a journal page 1514 that is bookmarked. The input recognition system 110 is implemented to recognize a hold input 1516 at the first screen 1504, where the hold input is recognized when held in place proximate an edge of the journal page 1514 that is bookmarked on the first screen 1504. The input recognition system 110 can also recognize a motion input 1518 at the second screen 1506, where the motion input is recognized while the hold input remains in place. In an embodiment, the motion input 1518 is recognized at the second screen 1506 along an outer edge of the journal page 1512, and the motion input is effective to flip journal pages at 1520 while the bookmark is maintained for the journal page 1514 on the first screen 1504.

The gesture module 108 is implemented to determine the multi-screen bookmark hold gesture from the recognized hold and motion inputs 1516, 1518. The bookmark hold gesture can be identified as a cross-screen combination of the hold and motion inputs, and the gesture is effective to bookmark journal page 1514 at a location of the hold input 1516 on the first screen 1504. In embodiments, a bookmark identifier 1522 is displayed to identify the journal page 1514 that is bookmarked and the location of the bookmark on the first screen. In this example, the bookmark identifier 1522 is a partial display of the journal page 1514 that is bookmarked. A bookmark and/or bookmark identifier is a selectable link to the journal page 1514 that is bookmarked on the first screen 1504, and the input recognition system 110 can recognize a selection input of the bookmark effective to flip back and display the journal page 1514 on the first screen.

The second view 1524 of the multi-screen system 1502 illustrates an alternate hold input 1526, such as when a user may hold a two-screen device with one hand while also bookmarking the journal page 1510 on the first screen 1504. The input recognition system 110 is implemented to recognize the hold input 1526 at the first screen 1504, and also recognize a motion input 1528 at the second screen 1506, where the motion input is recognized while the hold input remains in place. In an embodiment, the motion input 1528 is recognized at the second screen 1506 and is effective to flip the journal pages while the bookmark is maintained. In an implementation, the input recognition system 110 can recognize a bookmark hold gesture in defined regions, such as a region where a user is likely to both hold the device and bookmark a page. Alternatively or in addition, the multi-screen system 1502 may be implemented to sense the orientation of the screens, such that page bookmarking automatically adapts to the manner in which a user holds the device.

The third view 1530 of the multi-screen system 1502 illustrates that a hold input from which a bookmark is determined can include a slide motion input 1532 proximate a corner of the journal page 1514. The slide motion input 1532 can be recognized as a progression of motion to initiate the hold input, and the slide motion input can be determined to bookmark the journal page 1514 at the corner. The bookmark is maintained on the first screen 1504 for the journal page 1514 while other journal pages are flipped for viewing at 1534. In embodiments, there are various techniques that can be implemented to distinguish between: holding a page to temporarily save a position; explicitly “dog-earing” a page with a bookmark; or flipping back to a page denoted by a temporary hold or bookmark. In an embodiment, a hold input can be recognized to implicitly temporarily save a page position. Then a user can simply lift the input to discard the temporary bookmark or alternatively, provide the slide motion input to flip back to a saved page position. In another embodiment, if the slide motion input is initiated at approximately a same time as the hold input, then the page dog-ear bookmark can be created. In another embodiment, a dog-ear bookmark may only be recognized at defined locations around the boundary of a journal page (e.g., at the corners of the page), whereas the implicit temporary page hold can be implemented for a larger area or region.

FIG. 16 illustrates example method(s) 1600 of a multi-screen bookmark hold gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 1602, a hold input is recognized at a first screen of a multi-screen system, the hold input being recognized when held in place proximate an edge of a journal page that is displayed on the first screen. For example, the input recognition system 110 recognizes the hold input 1516 at the first screen 1504, and the hold input is recognized when held in place proximate an edge of the journal page 1514 that is bookmarked on the first screen 1504. The hold input can include the slide motion input 1532 proximate a corner of the journal page 1514. The input recognition system 110 recognizes the slide motion input as a progression of motion to initiate the hold input, and the gesture module 108 determines the bookmark hold gesture from the slide motion input to bookmark the journal page.

At block 1604, a motion input is recognized at a second screen of the multi-screen system, the motion input being recognized while the hold input remains in place. For example, input recognition system 110 also recognizes the motion input 1518 at the second screen 1506, and the motion input is recognized while the hold input remains in place. The input recognition system 110 can recognize the motion input along an outer edge of an opposite journal page that is displayed on the second screen 1506, and the motion input is effective to flip journal pages while the bookmark is maintained for the journal page 1514 on the first screen 1504.

At block 1606, a bookmark hold gesture is determined from the recognized hold and motion inputs, the bookmark hold gesture effective to bookmark the journal page at a location of the hold input on the first screen. For example, the gesture module 108 determines the multi-screen bookmark hold gesture from the recognized hold and motion inputs 1516, 1518. The bookmark hold gesture can be identified as a cross-screen combination of the hold and motion inputs. A bookmark and/or bookmark identifier is a selectable link to a journal page that is bookmarked on the first screen 1504, and the input recognition system 110 recognizes a selection input of the bookmark effective to flip back and display the journal page on the first screen.

At block 1608, display a bookmark identifier to identify the journal page that is bookmarked and the location of the bookmark on the first screen. For example, a bookmark identifier 1522 is displayed to identify the journal page 1514 that is bookmarked and the location of the bookmark on the first screen. In an implementation, the bookmark identifier 1522 can be a partial display of the journal page itself that is bookmarked.

Multi-Screen Object-Hold and Pate-Change Gesture

FIG. 17 illustrates examples 1700 of a multi-screen object-hold and page-change gesture on a multi-screen system 1702, which in these examples, is shown as a two-screen device. The multi-screen system 1702 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 1702 includes a first screen 1704 and a second screen 1706, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 1702 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen object-hold and page-change gesture can be implemented by a multi-screen system having more than two screens.

A multi-screen object-hold and page-change gesture can be used to move and/or copy a displayed object (or objects) from one display location to another, such as to incorporate a displayed object for display on a journal page. Additionally, a relative display position can be maintained when a displayed object is moved or copied from one display location to another. This can also include a selection of multiple objects that are selected with tap-selection inputs to a series of objects in succession, and then a hold input holds the selection while a motion input is recognized to change journal pages. This gesture can then be determined to move and/or copy all of the held objects to a new journal page that is displayed, while maintaining their relative display position and/or the relative spatial relationship between the objects. Alternatively or in addition, this gesture can include selections of objects that start on one page, then are held while journal pages are flipped, and additional objects from other pages are selected to be added to the selection of objects and carried along with the group.

In the first view 1708 of the multi-screen system 1702, a first journal page 1710 is displayed on the first screen 1704, and a second journal page 1712 is displayed on the second screen 1706. The input recognition system 110 is implemented to recognize a hold input 1714 at the first screen 1704, where the hold input is recognized when held to select a displayed object 1716 on the first screen 1704. The input recognition system 110 can also recognize a motion input 1718 at the second screen 1706, where the motion input is recognized while the displayed object 1716 is selected and the motion input effective to change journal pages at 1720. When the journal pages are changed at 1720, a subsequent journal page 1722 is revealed for display. In an embodiment, the motion input 1518 is recognized at the second screen 1506 along an outer edge of the journal page 1512, and the motion input is effective to flip journal pages at 1520 while the bookmark is maintained for the journal page 1514 on the first screen 1504.

The gesture module 108 is implemented to determine the multi-screen object-hold and page-change gesture from the recognized hold and motion inputs 1714, 1718. The object-hold and page-change gesture can be identified as a cross-screen combination of the hold and motion inputs, and the gesture is effective to move or copy the displayed object 1716 for display on a currently displayed journal page. The second view 1724 of the multi-screen system 1702 illustrates that the displayed object 1716 is moved from journal page 1710 (e.g., or copied from journal page 1710) for display on a currently displayed journal page 1726, which is displayed on the first screen 1704. The displayed object 1716 remains selected while journal pages are changed. The input recognition system 110 can then recognize that the displayed object 1716 is released from the hold input, and the object-hold and page-change gesture is effective to move or copy the displayed object for display on a currently displayed journal page. Additionally, a relative display position of the displayed object can be maintained when the displayed object is moved or copied from one display location to another.

FIG. 18 illustrates example method(s) 1800 of a multi-screen object-hold and page-change gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 1802, a hold input is recognized at a first screen of a multi-screen system, the hold input being recognized when held to select a displayed object on the first screen. For example, the input recognition system 110 recognizes the hold input 1714 at the first screen 1704, and the hold input is recognized when held to select the displayed object 1716 on the first screen 1704. At block 1804, a motion input is recognized at a second screen of the multi-screen system, the motion input being recognized while the displayed object is selected and the motion input effective to change one or more journal pages. For example, the input recognition system 110 also recognizes the motion input 1718 at the second screen 1706, the motion input being recognized while the displayed object 1716 is selected and the motion input effective to change journal pages at 1720.

At block 1806, an object-hold and page-change gesture is determined from the recognized hold and motion inputs. For example, the gesture module 108 determines the multi-screen object-hold and page-change gesture from the recognized hold and motion inputs 1714, 1718. The object-hold and page-change gesture can be identified as a cross-screen combination of the hold and motion inputs. In an embodiment, the object-hold and page-change gesture is effective to initiate a copy and paste function to copy the displayed object 1716 for display on a currently displayed journal page 1726.

At block 1808, the displayed object is recognized when released from the hold input, and the object-hold and page-change gesture effective to move and/or copy the displayed object for display on a currently displayed journal page. For example, the input recognition system 110 recognizes when the displayed object 1716 is released from the hold input, and the object-hold and page-change gesture is effective to move or copy the displayed object for display on a currently displayed journal page. The second view 1724 of the multi-screen system 1702 illustrates that the displayed object 1716 is moved from journal page 1710 (e.g., or copied from journal page 1710) for display on a currently displayed journal page 1726, which is displayed on the first screen 1704. Additionally, a relative display position of the displayed object is maintained when the displayed object is moved or copied from one display location to another. An object-hold and page-change gesture may also be effective to select multiple displayed objects that are moved and/or copied as a group from one display location to another.

Multi-Screen Synchronous Slide Gesture

FIG. 19 illustrates examples 1900 of a multi-screen synchronous slide gesture on a multi-screen system 1902, which in these examples, is shown as a two-screen device. The multi-screen system 1902 may be implemented as any of the various devices described with reference to FIGS. 1 and 2. In this example, the multi-screen system 1902 includes a first screen 1904 and a second screen 1906, each implemented to display any type of user interface and various displayable objects (e.g., any type of pictures, images, graphics, text, notes, sketches, drawings, selectable controls, user interface elements, etc.). The screens can also display journal pages, such as any type of notebook, periodical, book, paper, single page, and the like in an electronic form. The multi-screen system 1902 can include a gesture module 108 and an input recognition system 110, as described with reference to the computing device 102 shown in FIG. 1, and may also be implemented with any combination of components as described with reference to the example device shown in FIG. 21. Although the examples are illustrated and described with reference to the two-screen device, embodiments of a multi-screen synchronous slide gesture can be implemented by a multi-screen system having more than two screens.

A multi-screen synchronous slide gesture can be used to move a displayed object from one screen for display on another screen, replace displayed objects on the system screens with different displayed objects, move displayed objects to reveal a workspace on the system screens, and/or cycle through one or more workspaces (e.g., applications, interfaces, etc.) that are displayed on the system screens. A synchronous slide gesture may also be used to navigate to additional views, or reassign a current view to a different screen. Additionally, different applications or workspaces can be kept on a stack and cycled through, forward and back, with synchronous slide gestures.

In the first view 1908 of the multi-screen system 1902, a journal page 1910 is displayed as being moved from the first screen 1904 for display on the second screen 1906. The input recognition system 110 is implemented to recognize a first motion input 1912 at the first screen 1904 when the first motion input moves in a particular direction across the first screen. The input recognition system 110 can also recognize a second motion input 1914 at the second screen 1906 when the second motion input moves in the particular direction across the second screen and approximately when the first motion input is recognized.

The gesture module 108 is implemented to determine the multi-screen synchronous slide gesture from the recognized motion inputs 1912, 1914. The synchronous slide gesture can be identified as a cross-screen combination of the motion inputs, and the gesture is effective to move the journal page 1910 from display on the first screen 1904 to display on the second screen 1906.

In the second view 1916 of the multi-screen system 1902, the first journal page 1910 that is displayed on the first screen 1904 and a second journal page 1918 that is displayed on the second screen 1906 are illustrated as being replaced with different journal pages. The input recognition system 110 can recognize a first motion input 1920 at the first screen 1904 when the first motion input moves in a particular direction across the first screen. The input recognition system 110 can also recognize a second motion input 1922 at the second screen 1906 when the second motion input moves in the particular direction across the second screen and approximately when the first motion input is recognized. The gesture module 108 can determine the multi-screen synchronous slide gesture from the recognized motion inputs 1920, 1922. As shown in the third view 1924 of the multi-screen system 1902, the synchronous slide gesture is effective to move and/or replace the journal pages 1910, 1918 with different journal pages 1926, 1928 for display on the system screens.

It should be noted that the various representations of the motion inputs are merely illustrative for discussion purposes and may or may not appear on the screens of the multi-screen system when described embodiments are implemented. Additionally, any description herein of an input or motion at one screen that may correlate to another input or motion at another screen is applicable to either the first or second screens of the multi-screen system.

FIG. 20 illustrates example method(s) 2000 of a multi-screen synchronous slide gesture. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternate method.

At block 2002, a first motion input is recognized at a first screen of a multi-screen system when moving in a particular direction across the first screen. For example, the input recognition system 110 recognizes the first motion input 1912 at the first screen 1904 when the first motion input moves in a particular direction across the first screen. At block 2004, a second motion input is recognized at a second screen of the multi-screen system when moving in the particular direction across the second screen and approximately when the first motion input is recognized. For example, the input recognition system 110 also recognizes the second motion input 1914 at the second screen 1906 when the second motion input moves in the particular direction across the second screen and approximately when the first motion input is recognized.

At block 2006, a synchronous slide gesture is determined from the recognized first and second motion inputs. For example, the gesture module 108 determines the multi-screen synchronous slide gesture from the recognized motion inputs 1912, 1914. The synchronous slide gesture is identified as a cross-screen combination of the first and second motion inputs. In various embodiments, the synchronous slide gesture is effective to move a displayed object from display on the first screen to display on the second screen (at block 2008); replace one or more displayed objects on the first and second screens with different displayed objects (at block 2010); move one or more displayed objects and reveal a workspace on the first and second screens (at block 2012); cycle through one or more workspaces that are displayed on the first and second screens (at block 2014); and/or replace one or more applications on the first and second screens with different applications (at block 2016).

FIG. 21 illustrates various components of an example device 2100 that can be implemented as any type of portable and/or computing device as described with reference to FIGS. 1 and 2 to implement embodiments of multi-screen gestures. In embodiments, device 2100 can be implemented as any one or combination of a wired and/or wireless device, a multi-screen device, as any form of television client device (e.g., television set-top box, digital video recorder (DVR), etc.), consumer device, computer device, server device, portable computer device, user device, communication device, video processing and/or rendering device, appliance device, gaming device, electronic device, and/or as any other type of device. Device 2100 may also be associated with a user (i.e., a person) and/or an entity that operates the device such that a device describes logical devices that include users, software, firmware, and/or a combination of devices.

Device 2100 includes communication devices 2102 that enable wired and/or wireless communication of device data 2104 (e.g., received data, data that is being received, data scheduled for broadcast, data packets of the data, etc.). The device data 2104 or other device content can include configuration settings of the device, media content stored on the device, and/or information associated with a user of the device. Media content stored on device 2100 can include any type of audio, video, and/or image data. Device 2100 includes one or more data inputs 2106 via which any type of data, media content, and/or inputs can be received, such as user-selectable inputs, messages, music, television media content, recorded video content, and any other type of audio, video, and/or image data received from any content and/or data source.

Device 2100 also includes communication interfaces 2108 that can be implemented as any one or more of a serial and/or parallel interface, a wireless interface, any type of network interface, a modem, and as any other type of communication interface. The communication interfaces 2108 provide a connection and/or communication links between device 2100 and a communication network by which other electronic, computing, and communication devices communicate data with device 2100.

Device 2100 includes one or more processors 2110 (e.g., any of microprocessors, controllers, and the like) which process various computer-executable instructions to control the operation of device 2100 and to implement embodiments of multi-screen gestures. Alternatively or in addition, device 2100 can be implemented with any one or combination of hardware, firmware, or fixed logic circuitry that is implemented in connection with processing and control circuits which are generally identified at 2112. Although not shown, device 2100 can include a system bus or data transfer system that couples the various components within the device. 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.

Device 2100 also includes computer-readable media 2114, such as one or more memory components, examples of which include random access memory (RAM), non-volatile memory (e.g., any one or more of a read-only memory (ROM), flash memory, EPROM, EEPROM, etc.), and a disk storage device. A disk storage device may be implemented as any type of magnetic or optical storage device, such as a hard disk drive, a recordable and/or rewriteable compact disc (CD), any type of a digital versatile disc (DVD), and the like. Device 2100 can also include a mass storage media device 2116.

Computer-readable media 2114 provides data storage mechanisms to store the device data 2104, as well as various device applications 2118 and any other types of information and/or data related to operational aspects of device 2100. For example, an operating system 2120 can be maintained as a computer application with the computer-readable media 2114 and executed on processors 2110. The device applications 2118 can include a device manager (e.g., a control application, software application, signal processing and control module, code that is native to a particular device, a hardware abstraction layer for a particular device, etc.).

The device applications 2118 also include any system components or modules to implement embodiments of multi-screen gestures. In this example, the device applications 2118 can include interface applications 2122 and a gesture module 2124, such as when device 2100 is implemented as a multi-screen device. The interface applications 2122 and the gesture module 2124 are shown as software modules and/or computer applications. Alternatively or in addition, the interface applications 2122 and/or the gesture module 2124 can be implemented as hardware, software, firmware, or any combination thereof.

Device 2100 includes an input recognition system 2126 implemented to recognize various inputs or combinations of inputs, such as a select input, hold input, motion input, touch input, tap input, and the like. The input recognition system 2126 may include any type of input detection features to distinguish the various types of inputs, such as sensors, light sensing pixels, touch sensors, cameras, and/or a natural user interface that interprets user interactions, gestures, inputs, and motions.

Device 2100 also includes an audio and/or video rendering system 2128 that generates and provides audio data to an audio system 2130 and/or generates and provides display data to a display system 2132. The audio system 2130 and/or the display system 2132 can include any devices that process, display, and/or otherwise render audio, display, and image data. Display data and audio signals can be communicated from device 2100 to an audio device and/or to a display device via an RF (radio frequency) link, S-video link, composite video link, component video link, DVI (digital video interface), analog audio connection, or other similar communication link. In an embodiment, the audio system 2130 and/or the display system 2132 are implemented as external components to device 2100. Alternatively, the audio system 2130 and/or the display system 2132 are implemented as integrated components of example device 2100.

Although embodiments of multi-screen gestures have been described in language specific to features and/or methods, it is to be understood that the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of the multi-screen gestures.

Claims

1. A computer-implemented method, comprising: recognizing a first input gesture with an input recognition system as a request to initiate a pairing of a first mobile device with a second mobile device, wherein the first input gesture is a first touch gesture received via a first device touchscreen of the first mobile device and a second device touchscreen of the second mobile device;pairing the first mobile device with at least the second mobile device based on the first input gesture;enabling a cross-screen display of an interface on the first device touchscreen and on the at least second device touchscreen, the first mobile device and the second mobile devices positioned proximate to each other forming a combined display from the respective first and second device touchscreens;recognizing a second input gesture with the input recognition system as a request to display a split-screen view of a displayed object, wherein the second input gesture is a second touch gesture received via the first device touchscreen of the first mobile device and the second device touchscreen of the second mobile device; andin response to the recognition of the second input gesture, displaying the split-screen view, wherein the split-screen view includes a full-screen display of first part of the displayed object on the first device touchscreen and non-full screen display of a second part of the displayed object on the second device touchscreen.
2. The method as recited in claim 1, further comprising: displaying a first part of the interface on the first device touchscreen; anddisplaying a second part of the interface on the second device touchscreen.
3. The method as recited in claim 1, further comprising: pairing at least one additional mobile device with the first mobile device and the second mobile device, each of the at least one additional mobile devices having a device touchscreen, whereinthe cross-screen display of the interface on the respective device touchscreens of the paired first, second, and at least one additional mobile device forms the combined display.
4. The method as recited in claim 1, wherein said recognizing the first input gesture includes recognizing proximity of the first mobile device with the second mobile device.
5. The method as recited in claim 1, wherein said recognizing the first input gesture includes recognition of an input from at least one sensor.
6. The method as recited in claim 1, wherein said recognizing the first input gesture includes recognition of a voice-activated input.
7. The method as recited in claim 1, wherein: recognizing the first input gesture includes recognition of a portion of the first input gesture at the first mobile device with an instance of the input recognition system and recognition of another portion of the input at the second mobile device with another instance of the input recognition system.
8. A system, comprising: a first mobile device having a first device touchscreen;at least a second mobile device having a second device touchscreen, housing bezels of the respective first and second mobile devices positioned proximate to each other to form a combined display from the first and second device touchscreens; andwherein the first mobile device is configured to: recognize a first input gesture as an request to initiate pairing of the first mobile device with the second mobile device and wherein the first input gesture is a touch gesture received via at least the first device touchscreen and the second device touchscreen;pair the first mobile device with at least the second mobile device in response to the first input gesture;enable a cross-screen display of an interface on the first device touchscreen and on the at least second device touchscreen;recognize a second input gesture as a request to display a split-screen view of an object, wherein the second input gesture is a second touch gesture received via at least the first device touchscreen and the second device touchscreen; andin response to the recognition of the second input gesture, display the split-screen view, wherein the split-screen view includes a full-screen display of first part of the object on the first device touchscreen and non-full screen display of a second part of the object on the second device touchscreen.
9. The system as recited in claim 8, wherein: a first part of the interface is displayed on the first device touchscreen; anda second part of the interface is displayed on the second device touchscreen.
10. The system as recited in claim 8, wherein the interface is a gaming application interface that is displayable cross-screen on the first and second device touchscreens.
11. The system as recited in claim 8, further comprising: additional mobile devices each having a device touchscreen; andwherein the additional mobile devices are positioned proximate the first and second mobile devices to form the combined display from the respective device touchscreens.
12. The system as recited in claim 8, wherein: the additional mobile devices include a third mobile device having a third device touchscreen and a fourth mobile device having a fourth device touchscreen; anda first part of the interface is displayed on the first device touchscreen, a second part of the interface is displayed on the second device touchscreen, a third part of the interface is displayed on the third device touchscreen, and a fourth part of the interface is displayed on the fourth device touchscreen.
13. The system as recited in claim 8, wherein the first mobile device is also configured to recognize proximity of the first mobile device with the second mobile device.
14. The system as recited in claim 8, wherein the first mobile device is also configured to recognize sensor input.
15. The system as recited in claim 8, wherein the first mobile device is also configured to recognize a voice-activated input.
16. The system as recited in claim 8, wherein: the first mobile device is also configured to recognize a portion of the first input gesture; andthe second mobile device is configured to recognize another portion of the first input gesture.
17. A first mobile device, comprising: a memory and a processor, wherein the memory and the processor are respectively configured to store and execute instructions for causing the first mobile device to perform operations, the operations comprising: recognizing a first input gesture with an input recognition system as a request to initiate a pairing of the first mobile device with a second mobile device, wherein the first input gesture is a touch gesture received via a first device touchscreen of the first mobile device and a second device touchscreen of the second mobile device;pairing the first mobile device with the second mobile device based on the first input gesture, the first mobile device having a first device touchscreen and the second mobile device having a second device touchscreen; andenabling a cross-screen display of an interface on the first device touchscreen and on the second device touchscreen, the first mobile device and the second mobile device positioned proximate to each other forming a combined display from the respective first and second device touchscreens;recognizing a second input gesture with the input recognition system as a request to display a split-screen view of an object, wherein the second input gesture is a second touch gesture received via the first device touchscreen of the first mobile device and the second device touchscreen of the second mobile device; andin response to the recognition of the second input gesture, displaying the split-screen view, wherein the split-screen view includes a full-screen display of first part of the object on the first device touchscreen and non-full screen display of a second part of the object on the second device touchscreen.
18. The first mobile device as recited in claim 17, wherein the input recognition system also recognizes at least one of: proximity of the first mobile device with the second mobile device;a sensor input; ora voice-activated input.
19. The first mobile device as recited in claim 17, wherein the operations further comprise: displaying a first part of the interface on the first device touchscreen; anddisplaying a second part of the interface on the second device touchscreen.
20. The first mobile device as recited in claim 17, wherein the operations further comprise: pairing a third mobile device with the first mobile device and the second mobile devices, the third mobile device having a third device touchscreen, whereinthe cross-screen display of the interface is on the first device touchscreen, on the second device touchscreen, and on the third device touchscreen.

RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patent application Ser. No. 12/713,096 filed Feb. 25, 2010 entitled “Multi-Screen Dual Tap Gesture”, the disclosure of which is incorporated by reference herein in its entirety.

US Referenced Citations (434)

Number	Name	Date	Kind
4686332	Greanias et al.	Aug 1987	A
4843538	Lane et al.	Jun 1989	A
4868912	Doering	Sep 1989	A
5231578	Levin et al.	Jul 1993	A
5237647	Roberts et al.	Aug 1993	A
5252951	Tannenbaum et al.	Oct 1993	A
5351995	Booker et al.	Oct 1994	A
5404458	Zetts	Apr 1995	A
5463725	Henckel et al.	Oct 1995	A
5491783	Douglas et al.	Feb 1996	A
5496974	Akebi et al.	Mar 1996	A
5497776	Yamazaki et al.	Mar 1996	A
5511148	Wellner	Apr 1996	A
5555369	Menendez et al.	Sep 1996	A
5596697	Foster et al.	Jan 1997	A
5661773	Swerdloff et al.	Aug 1997	A
5664128	Bauer	Sep 1997	A
5664133	Malamud et al.	Sep 1997	A
5694150	Sigona et al.	Dec 1997	A
5696915	Johnston et al.	Dec 1997	A
5731813	O'Rourke et al.	Mar 1998	A
5761485	Munyan	Jun 1998	A
5777596	Herbert	Jul 1998	A
5817019	Kawashima	Oct 1998	A
5821930	Hansen	Oct 1998	A
5838889	Booker et al.	Nov 1998	A
5898434	Small et al.	Apr 1999	A
5943052	Allen	Aug 1999	A
5969720	Lisle et al.	Oct 1999	A
6029214	Dorfman et al.	Feb 2000	A
6037937	Beaton et al.	Mar 2000	A
6061061	Conrad et al.	May 2000	A
6072476	Harada et al.	Jun 2000	A
6097392	Leyerle	Aug 2000	A
6115724	Booker et al.	Sep 2000	A
6167439	Levine et al.	Dec 2000	A
6208331	Singh	Mar 2001	B1
6239798	Ludolph et al.	May 2001	B1
6246395	Goyins	Jun 2001	B1
6266050	Oh et al.	Jul 2001	B1
6278443	Amro et al.	Aug 2001	B1
6310610	Beaton et al.	Oct 2001	B1
6340979	Beaton et al.	Jan 2002	B1
6396523	Segal et al.	May 2002	B1
6459424	Resman	Oct 2002	B1
6507352	Cohen et al.	Jan 2003	B1
6525749	Moran et al.	Feb 2003	B1
6545669	Kinawi et al.	Apr 2003	B1
6831631	Chuang	Dec 2004	B2
6859909	Lerner et al.	Feb 2005	B1
6920619	Milekic	Jul 2005	B1
6948173	Isom	Sep 2005	B1
6957233	Beezer et al.	Oct 2005	B1
7023427	Kraus et al.	Apr 2006	B2
7053887	Kraus et al.	May 2006	B2
7231609	Baudisch	Jun 2007	B2
7295191	Kraus et al.	Nov 2007	B2
7302650	Allyn et al.	Nov 2007	B1
7338224	Jones et al.	Mar 2008	B2
7339580	Westerman et al.	Mar 2008	B2
7454717	Hinckley et al.	Nov 2008	B2
7479949	Jobs et al.	Jan 2009	B2
7506269	Lang	Mar 2009	B2
7532196	Hinckley	May 2009	B2
7561146	Hotelling	Jul 2009	B1
7636071	O'Gorman	Dec 2009	B2
7636898	Takahashi	Dec 2009	B2
7643012	Kim et al.	Jan 2010	B2
7656393	King et al.	Feb 2010	B2
7676767	Hofmeister et al.	Mar 2010	B2
7760187	Kennedy	Jul 2010	B2
7765486	Jaeger	Jul 2010	B2
7821780	Choy	Oct 2010	B2
7847789	Kolmykov-Zotov et al.	Dec 2010	B2
D631043	Kell	Jan 2011	S
7898529	Fitzmaurice et al.	Mar 2011	B2
7956847	Christie	Jun 2011	B2
8018440	Townsend et al.	Sep 2011	B2
8102858	Rahim et al.	Jan 2012	B1
8122384	Partridge et al.	Feb 2012	B2
8169418	Birkler	May 2012	B2
8181122	Davidson	May 2012	B2
8201109	Van Os et al.	Jun 2012	B2
8212788	Lam	Jul 2012	B2
8239785	Hinckley	Aug 2012	B2
8261213	Hinckley	Sep 2012	B2
8274482	Kim et al.	Sep 2012	B2
8284170	Bernstein	Oct 2012	B2
8289289	Rimon et al.	Oct 2012	B2
8294669	Partridge et al.	Oct 2012	B2
8294686	Townsend et al.	Oct 2012	B2
8327295	Ikeda et al.	Dec 2012	B2
8335996	Davidson et al.	Dec 2012	B2
8345008	Lee et al.	Jan 2013	B2
8373660	Pallakoff	Feb 2013	B2
8395600	Kawashima et al.	Mar 2013	B2
8407606	Davidson et al.	Mar 2013	B1
8473870	Hinckley et al.	Jun 2013	B2
8477114	Miller et al.	Jul 2013	B2
8539384	Hinckley et al.	Sep 2013	B2
8581864	Miyazawa et al.	Nov 2013	B2
8587526	Engelhardt et al.	Nov 2013	B2
8640047	Mouton et al.	Jan 2014	B2
8643628	Eriksson et al.	Feb 2014	B1
8659570	Townsend et al.	Feb 2014	B2
8707174	Hinckley et al.	Apr 2014	B2
8751970	Hinckley et al.	Jun 2014	B2
8788967	Davidson et al.	Jul 2014	B2
8799827	Hinckley et al.	Aug 2014	B2
8810533	Chen	Aug 2014	B2
8836648	Wilairat	Sep 2014	B2
8836659	Chen et al.	Sep 2014	B2
9047009	King	Jun 2015	B2
9075522	Hinckley et al.	Jul 2015	B2
9256342	Davidson	Feb 2016	B2
9261964	Townsend et al.	Feb 2016	B2
9274682	Hinckley et al.	Mar 2016	B2
9310994	Hinckley et al.	Apr 2016	B2
9367205	Hinckley et al.	Jun 2016	B2
9411498	Hinckley et al.	Aug 2016	B2
9411504	Hinckley et al.	Aug 2016	B2
9454304	Hinckley et al.	Sep 2016	B2
20010012000	Eberhard	Aug 2001	A1
20010035860	Segal et al.	Nov 2001	A1
20010047263	Smith et al.	Nov 2001	A1
20020060701	Naughton et al.	May 2002	A1
20020097229	Rose et al.	Jul 2002	A1
20020101457	Lang	Aug 2002	A1
20020116421	Fox et al.	Aug 2002	A1
20030016253	Aoki et al.	Jan 2003	A1
20030067451	Tagg et al.	Apr 2003	A1
20030095095	Pihlaja	May 2003	A1
20030098858	Perski et al.	May 2003	A1
20030142081	Iizuka et al.	Jul 2003	A1
20030179541	Sullivan	Sep 2003	A1
20030231219	Leung	Dec 2003	A1
20040001048	Kraus et al.	Jan 2004	A1
20040117782	Lo	Jun 2004	A1
20040150664	Baudisch	Aug 2004	A1
20040155871	Perski et al.	Aug 2004	A1
20040175764	Nishiyama et al.	Sep 2004	A1
20040190754	Sakagami et al.	Sep 2004	A1
20040205669	Hoidahl	Oct 2004	A1
20040236741	Burstrom et al.	Nov 2004	A1
20040236774	Baird et al.	Nov 2004	A1
20040255254	Weingart et al.	Dec 2004	A1
20050012723	Pallakoff	Jan 2005	A1
20050017957	Yi	Jan 2005	A1
20050017959	Kraus et al.	Jan 2005	A1
20050052432	Kraus et al.	Mar 2005	A1
20050076300	Martinez	Apr 2005	A1
20050101864	Zheng et al.	May 2005	A1
20050129314	Chen	Jun 2005	A1
20050162402	Watanachote	Jul 2005	A1
20050177796	Takahashi	Aug 2005	A1
20050184973	Lum et al.	Aug 2005	A1
20050189154	Perski et al.	Sep 2005	A1
20050198592	Keely et al.	Sep 2005	A1
20060001650	Robbins et al.	Jan 2006	A1
20060010371	Shur et al.	Jan 2006	A1
20060012580	Perski et al.	Jan 2006	A1
20060012581	Haim et al.	Jan 2006	A1
20060022955	Kennedy	Feb 2006	A1
20060026521	Hotelling et al.	Feb 2006	A1
20060026535	Hotelling et al.	Feb 2006	A1
20060026536	Hotelling et al.	Feb 2006	A1
20060031786	Hillis et al.	Feb 2006	A1
20060071912	Hill et al.	Apr 2006	A1
20060092177	Blasko	May 2006	A1
20060093219	Gounares et al.	May 2006	A1
20060101354	Hashimoto et al.	May 2006	A1
20060109252	Kolmykov-Zotov et al.	May 2006	A1
20060112335	Hofmeister et al.	May 2006	A1
20060161870	Hotelling et al.	Jul 2006	A1
20060197750	Kerr et al.	Sep 2006	A1
20060197753	Hotelling	Sep 2006	A1
20060197963	Royal et al.	Sep 2006	A1
20060238517	King et al.	Oct 2006	A1
20060238520	Westerman et al.	Oct 2006	A1
20060262105	Smith et al.	Nov 2006	A1
20060262188	Elyada et al.	Nov 2006	A1
20060267955	Hino	Nov 2006	A1
20060284852	Hofmeister et al.	Dec 2006	A1
20070043744	Carro	Feb 2007	A1
20070050726	Wakai et al.	Mar 2007	A1
20070061755	Taboada et al.	Mar 2007	A1
20070063987	Sato et al.	Mar 2007	A1
20070075976	Kun et al.	Apr 2007	A1
20070097096	Rosenberg	May 2007	A1
20070106939	Qassoudi	May 2007	A1
20070109274	Reynolds	May 2007	A1
20070120762	O'Gorman	May 2007	A1
20070146337	Ording et al.	Jun 2007	A1
20070146347	Rosenberg	Jun 2007	A1
20070150496	Feinsmith	Jun 2007	A1
20070152976	Townsend et al.	Jul 2007	A1
20070168890	Zhao et al.	Jul 2007	A1
20070171211	Perski et al.	Jul 2007	A1
20070236468	Tuli	Oct 2007	A1
20070242056	Engelhardt et al.	Oct 2007	A1
20070262951	Huie et al.	Nov 2007	A1
20080001924	de los Reyes et al.	Jan 2008	A1
20080005703	Radivojevic et al.	Jan 2008	A1
20080036743	Westerman et al.	Feb 2008	A1
20080040692	Sunday et al.	Feb 2008	A1
20080042978	Perez-Noguera	Feb 2008	A1
20080046425	Perski	Feb 2008	A1
20080052945	Matas et al.	Mar 2008	A1
20080059914	Allyn et al.	Mar 2008	A1
20080062141	Chandhri	Mar 2008	A1
20080065720	Brodersen et al.	Mar 2008	A1
20080074402	Cornish et al.	Mar 2008	A1
20080082903	McCurdy et al.	Apr 2008	A1
20080084400	Rosenberg	Apr 2008	A1
20080094371	Forstall et al.	Apr 2008	A1
20080164982	Andrews et al.	Jul 2008	A1
20080165141	Christie	Jul 2008	A1
20080165255	Christie et al.	Jul 2008	A1
20080168382	Louch et al.	Jul 2008	A1
20080168396	Matas et al.	Jul 2008	A1
20080168403	Westerman et al.	Jul 2008	A1
20080180404	Han et al.	Jul 2008	A1
20080211766	Westerman et al.	Sep 2008	A1
20080211778	Ording et al.	Sep 2008	A1
20080216125	Li	Sep 2008	A1
20080218494	Perski et al.	Sep 2008	A1
20080229192	Gear et al.	Sep 2008	A1
20080231635	Saund	Sep 2008	A1
20080249682	Wisniewski et al.	Oct 2008	A1
20080278455	Atkins et al.	Nov 2008	A1
20080278481	Arcas et al.	Nov 2008	A1
20080303798	Matsudate et al.	Dec 2008	A1
20090019188	Mattice et al.	Jan 2009	A1
20090033632	Szolyga et al.	Feb 2009	A1
20090054107	Feland, III et al.	Feb 2009	A1
20090058830	Herz	Mar 2009	A1
20090059730	Lyons et al.	Mar 2009	A1
20090064012	Tremblay	Mar 2009	A1
20090074255	Holm	Mar 2009	A1
20090077501	Partridge et al.	Mar 2009	A1
20090079699	Sun	Mar 2009	A1
20090089739	Mollicone et al.	Apr 2009	A1
20090094562	Jeong et al.	Apr 2009	A1
20090096758	Hotelling et al.	Apr 2009	A1
20090117943	Lee et al.	May 2009	A1
20090128505	Partridge et al.	May 2009	A1
20090132256	Geldbach	May 2009	A1
20090138830	Borgaonkar et al.	May 2009	A1
20090143141	Wells et al.	Jun 2009	A1
20090153289	Hope et al.	Jun 2009	A1
20090153438	Miller et al.	Jun 2009	A1
20090167696	Griffin	Jul 2009	A1
20090167702	Nurmi	Jul 2009	A1
20090174679	Westerman	Jul 2009	A1
20090184921	Scott et al.	Jul 2009	A1
20090193366	Davidson	Jul 2009	A1
20090217211	Hildreth et al.	Aug 2009	A1
20090249236	Westerman et al.	Oct 2009	A1
20090249247	Tseng et al.	Oct 2009	A1
20090251432	Wang et al.	Oct 2009	A1
20090251434	Rimon et al.	Oct 2009	A1
20090256857	Davidson et al.	Oct 2009	A1
20090276701	Nurmi	Nov 2009	A1
20090278806	Duarte et al.	Nov 2009	A1
20090282332	Porat	Nov 2009	A1
20090284478	De la Torre Baltierra et al.	Nov 2009	A1
20090284488	Sip	Nov 2009	A1
20090292989	Matthews et al.	Nov 2009	A1
20090295753	King et al.	Dec 2009	A1
20090307589	Inose et al.	Dec 2009	A1
20090309846	Trachtenberg et al.	Dec 2009	A1
20090319893	Pihlaja	Dec 2009	A1
20090320070	Inoguchi	Dec 2009	A1
20090327963	Mouilleseaux et al.	Dec 2009	A1
20090327975	Stedman	Dec 2009	A1
20100013768	Leung	Jan 2010	A1
20100013792	Fukushima	Jan 2010	A1
20100016049	Shirakawa et al.	Jan 2010	A1
20100020025	Lemort et al.	Jan 2010	A1
20100039392	Pratt et al.	Feb 2010	A1
20100042827	Pratt et al.	Feb 2010	A1
20100045705	Vertegaal et al.	Feb 2010	A1
20100050076	Roth	Feb 2010	A1
20100051355	Yang	Mar 2010	A1
20100053103	No et al.	Mar 2010	A1
20100053861	Kim et al.	Mar 2010	A1
20100058182	Jung	Mar 2010	A1
20100060607	Ludwig	Mar 2010	A1
20100066667	MacDougall et al.	Mar 2010	A1
20100066694	Jonsdottir	Mar 2010	A1
20100066698	Seo	Mar 2010	A1
20100079392	Chiang et al.	Apr 2010	A1
20100081475	Chiang et al.	Apr 2010	A1
20100083154	Takeshita	Apr 2010	A1
20100083190	Roberts et al.	Apr 2010	A1
20100088641	Choi	Apr 2010	A1
20100090971	Choi et al.	Apr 2010	A1
20100097338	Miyashita et al.	Apr 2010	A1
20100103136	Ono et al.	Apr 2010	A1
20100105443	Vaisanen	Apr 2010	A1
20100107067	Vaisanen	Apr 2010	A1
20100110019	Ozias et al.	May 2010	A1
20100113148	Haltovsky	May 2010	A1
20100115455	Kim	May 2010	A1
20100123675	Ippel	May 2010	A1
20100134415	Iwase et al.	Jun 2010	A1
20100134424	Brisebois et al.	Jun 2010	A1
20100137027	Kim	Jun 2010	A1
20100144283	Curcio	Jun 2010	A1
20100149109	Elias	Jun 2010	A1
20100164878	Bestle et al.	Jul 2010	A1
20100164959	Brown et al.	Jul 2010	A1
20100169813	Chang	Jul 2010	A1
20100182247	Petschnigg et al.	Jul 2010	A1
20100182264	Hahn et al.	Jul 2010	A1
20100188371	Lowles et al.	Jul 2010	A1
20100201634	Coddington	Aug 2010	A1
20100213040	Yeh et al.	Aug 2010	A1
20100217428	Strong et al.	Aug 2010	A1
20100220900	Orsley	Sep 2010	A1
20100241973	Whiddett	Sep 2010	A1
20100245242	Wu et al.	Sep 2010	A1
20100245263	Parada, Jr. et al.	Sep 2010	A1
20100251112	Hinckley et al.	Sep 2010	A1
20100251189	Jaeger	Sep 2010	A1
20100262928	Abbott	Oct 2010	A1
20100283748	Hsieh et al.	Nov 2010	A1
20100295795	Wilairat	Nov 2010	A1
20100295802	Lee	Nov 2010	A1
20100298033	Lee	Nov 2010	A1
20100302172	Wilairat	Dec 2010	A1
20100302712	Zednicek et al.	Dec 2010	A1
20100306702	Warner	Dec 2010	A1
20100313124	Privault et al.	Dec 2010	A1
20100321326	Grunthaner et al.	Dec 2010	A1
20110012841	Lin	Jan 2011	A1
20110018821	Kii	Jan 2011	A1
20110041096	Larco et al.	Feb 2011	A1
20110043472	Hada	Feb 2011	A1
20110050594	Kim et al.	Mar 2011	A1
20110055729	Mason et al.	Mar 2011	A1
20110055753	Horodezky et al.	Mar 2011	A1
20110072036	Agsen et al.	Mar 2011	A1
20110107220	Perlman	May 2011	A1
20110115735	Lev et al.	May 2011	A1
20110117526	Wigdor et al.	May 2011	A1
20110126094	Horodezky et al.	May 2011	A1
20110143769	Jones et al.	Jun 2011	A1
20110159915	Yano et al.	Jun 2011	A1
20110164042	Chaudhri	Jul 2011	A1
20110167092	Subramaniam et al.	Jul 2011	A1
20110167336	Aitken et al.	Jul 2011	A1
20110167391	Momeyer et al.	Jul 2011	A1
20110169749	Ganey et al.	Jul 2011	A1
20110181524	Hinckley et al.	Jul 2011	A1
20110185299	Hinckley et al.	Jul 2011	A1
20110185300	Hinckley et al.	Jul 2011	A1
20110185318	Hinckley et al.	Jul 2011	A1
20110185320	Hinckley et al.	Jul 2011	A1
20110191704	Hinckley et al.	Aug 2011	A1
20110191718	Hinckley et al.	Aug 2011	A1
20110191719	Hinckley et al.	Aug 2011	A1
20110199386	Dharwada et al.	Aug 2011	A1
20110205163	Hinckley et al.	Aug 2011	A1
20110209039	Hinckley et al.	Aug 2011	A1
20110209057	Hinckley et al.	Aug 2011	A1
20110209058	Hinckley et al.	Aug 2011	A1
20110209088	Hinckley et al.	Aug 2011	A1
20110209089	Hinckley et al.	Aug 2011	A1
20110209093	Hinckley et al.	Aug 2011	A1
20110209097	Hinckley et al.	Aug 2011	A1
20110209098	Hinckley et al.	Aug 2011	A1
20110209099	Hinckley et al.	Aug 2011	A1
20110209100	Hinckley et al.	Aug 2011	A1
20110209101	Hinckley et al.	Aug 2011	A1
20110209102	Hinckley et al.	Aug 2011	A1
20110209103	Hinckley et al.	Aug 2011	A1
20110209104	Hinckley et al.	Aug 2011	A1
20110231796	Vigil	Sep 2011	A1
20110242039	Kalis et al.	Oct 2011	A1
20110242138	Tribble	Oct 2011	A1
20110261058	Luo	Oct 2011	A1
20110291948	Stewart et al.	Dec 2011	A1
20110291964	Chambers et al.	Dec 2011	A1
20110310459	Gates et al.	Dec 2011	A1
20120001861	Townsend et al.	Jan 2012	A1
20120075194	Ferren	Mar 2012	A1
20120084705	Lee et al.	Apr 2012	A1
20120096411	Nash	Apr 2012	A1
20120113007	Koch et al.	May 2012	A1
20120131454	Shah	May 2012	A1
20120154303	Lazaridis et al.	Jun 2012	A1
20120158629	Hinckley et al.	Jun 2012	A1
20120212445	Heikkinen et al.	Aug 2012	A1
20120236026	Hinckley et al.	Sep 2012	A1
20120262407	Hinckley et al.	Oct 2012	A1
20120287076	Dao et al.	Nov 2012	A1
20120304133	Nan et al.	Nov 2012	A1
20120306788	Chen et al.	Dec 2012	A1
20120311476	Campbell	Dec 2012	A1
20120324384	Cohen et al.	Dec 2012	A1
20130038564	Ho	Feb 2013	A1
20130044070	Townsend et al.	Feb 2013	A1
20130063891	Martisauskas	Mar 2013	A1
20130088434	Masuda et al.	Apr 2013	A1
20130093691	Moosavi	Apr 2013	A1
20130117715	Williams et al.	May 2013	A1
20130121492	Vacon	May 2013	A1
20130154999	Guard	Jun 2013	A1
20130181902	Hinckley et al.	Jul 2013	A1
20130222287	Bae et al.	Aug 2013	A1
20130265269	Sharma et al.	Oct 2013	A1
20130271447	Setlur et al.	Oct 2013	A1
20130275914	Zhuo	Oct 2013	A1
20130300668	Churikov et al.	Nov 2013	A1
20130335453	Lim et al.	Dec 2013	A1
20140022183	Ayoub et al.	Jan 2014	A1
20140033134	Pimmel et al.	Jan 2014	A1
20140043265	Chang et al.	Feb 2014	A1
20140043277	Saukko et al.	Feb 2014	A1
20140092041	Ih	Apr 2014	A1
20140111462	Townsend et al.	Apr 2014	A1
20140132551	Bathiche	May 2014	A1
20140192019	Fukushima	Jul 2014	A1
20140195957	Bang	Jul 2014	A1
20140258880	Holm	Sep 2014	A1
20140289668	Mavrody	Sep 2014	A1
20140293145	Jones et al.	Oct 2014	A1
20140337791	Agnetta et al.	Nov 2014	A1
20150042588	Park	Feb 2015	A1
20150145797	Corrion	May 2015	A1
20150160849	Weiss et al.	Jun 2015	A1
20150261362	King	Sep 2015	A1
20150261364	Cady et al.	Sep 2015	A1

Foreign Referenced Citations (63)

Number	Date	Country
1326564	Dec 2001	CN
1578430	Feb 2005	CN
1704888	Dec 2005	CN
1766824	May 2006	CN
1921671	Feb 2007	CN
1936799	Mar 2007	CN
101198925	Jun 2008	CN
101356493	Jan 2009	CN
201181467	Jan 2009	CN
101404687	Apr 2009	CN
101410781	Apr 2009	CN
101432677	May 2009	CN
101482790	Jul 2009	CN
101496404	Jul 2009	CN
201298220	Aug 2009	CN
101551728	Oct 2009	CN
101566865	Oct 2009	CN
101576789	Nov 2009	CN
101609383	Dec 2009	CN
101627361	Jan 2010	CN
101636711	Jan 2010	CN
101866263	Oct 2010	CN
1942401	Jul 2008	EP
2081107	Jul 2009	EP
2148268	Jan 2010	EP
2466442	Jun 2012	EP
2560088	Feb 2013	EP
2634678	Sep 2013	EP
6282368	Oct 1994	JP
7281810	Oct 1995	JP
2001265523	Sep 2001	JP
2001290585	Oct 2001	JP
2002055753	Feb 2002	JP
2003140802	May 2003	JP
2003195998	Jul 2003	JP
2005004690	Jan 2005	JP
2005026834	Jan 2005	JP
2005122271	May 2005	JP
2005149279	Jun 2005	JP
2007078144	Mar 2007	JP
2007240964	Sep 2007	JP
2008033945	Feb 2008	JP
3143462	Jul 2008	JP
2008532185	Aug 2008	JP
2008217742	Sep 2008	JP
2008305087	Dec 2008	JP
2009026769	Feb 2009	JP
2009097724	Apr 2009	JP
2010019643	Jan 2010	JP
2010026834	Feb 2010	JP
2010250465	Nov 2010	JP
20090013927	Feb 2009	KR
102009008850	Aug 2009	KR
20090106755	Oct 2009	KR
200921478	May 2009	TW
200947297	Nov 2009	TW
200951783	Dec 2009	TW
WO-9928812	Jan 1999	WO
WO-2009086628	Jul 2009	WO
WO-2009137419	Nov 2009	WO
2010008088	Jan 2010	WO
WO-2011106467	Sep 2011	WO
WO-2011106468	Sep 2011	WO

Non-Patent Literature Citations (287)

Entry
“Office Action Issued in European Patent Application No. 11748027.7”, dated Oct. 26, 2017, 4 Pages.
“Search Report Issued in European Patent Application No. 11748026.9”, dated Dec. 4, 2012, 3 Pages.
“Office Action Issued in European Patent Application No. 11748028.5”, dated Nov. 9, 2017, 2 Pages.
“Office Action Issued in European Patent Application No. 11748029.3”, dated Oct. 26, 2017, 4 Pages.
“Search Report Issued in European Patent Application No. 11748029.3”, dated Nov. 30, 2012, 3 Pages.
“Office Action Issued in Chinese Patent Application No. 201180011035.X”, dated May 5, 2014, 12 Pages.
“Office Action Issued in Japanese Patent Application No. 2012-555124”, dated Mar. 2, 2015, 4 Pages.
“3M Touch Systems, Inc. Announces Shipment of Dispersive Signal Technology Product”, Datasheet, 3M Corporation, retrieved from <http://solutions.3m.com/wps/porta1/3M/en_US/TouchSystems/TouchScreen/Informatio/Media/PressReleases/Archive/?PC_7_RJH9U52300FA602N 9RSR991OI3000000_assetId=1114287537178<, Sep. 6, 2005, 3 pages.
“3M TouchWare TM Software for Windows User Guide”, In White Paper of 3M Touch Systems—Retrieved at: <<http://multimedia.3m.com/mws/mediawebserver?6666660Zjcf6IVs6EVs66SS0LCOrrrrQ->>, Aug. 9, 2013, 65 pages.
“AccuScribe Touchscreens”, Datasheet, Elo TouchSystem, Aug. 2005, 2 pages.
“Advisory Action”, U.S. Appl. No. 12/695,842, dated Mar. 28, 2016, 3 pages.
“Advisory Action”, U.S. Appl. No. 12/695,842, dated May 12, 2015, 3 pages.
“Advisory Action”, U.S. Appl. No. 12/709,376, dated Dec. 19, 2013, 2 pages.
“Apple Unibody MacBook Pro #MB991LL/A 2.53 GHz Intel Core 2 Duo”, Retrieved from: <http://www.themacstore.com/parts/show/c-nmb3-mb991ll_a> on Nov. 10, 2009, 2009, 12 pages.
“Decision on Reexamination”, CN Application No. 201110046519.X, dated May 28, 2015, 9 Pages.
“Dell and Windows 7—The Wait Is Over”, Retrieved from: <http://content.dell.com/us/en/corp/d/press-releases/2009-10-22-Dell-and-Windows-7.aspx> on Nov. 10, 2009, Oct. 22, 2009, 2 pages.
“Ex Parte Mewherter, PTAB precedential decision”, U.S. Appl. No. 10/685,192, dated May 8, 2013, 22 pages.
“Final Office Action”, U.S. Appl. No. 12/472,699, dated Jul. 29, 2013, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/472,699, dated Feb. 15, 2012, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/695,842, dated Feb. 2, 2016, 10 pages.
“Final Office Action”, U.S. Appl. No. 12/695,842, dated Feb. 12, 2015, 20 pages.
“Final Office Action”, U.S. Appl. No. 12/695,842, dated Dec. 2, 2013, 17 pages.
“Final Office Action”, U.S. Appl. No. 12/695,937, dated Apr. 2, 2015, 14 pages.
“Final Office Action”, U.S. Appl. No. 12/695,937, dated Nov. 10, 2014, 13 pages.
“Final Office Action”, U.S. Appl. No. 12/695,937, dated Jul. 26, 2012, 13 pages.
“Final Office Action”, U.S. Appl. No. 12/695,976, dated Jul. 23, 2014, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/695,976, dated Aug. 5, 2015, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/695,976, dated Nov. 21, 2012, 10 pages.
“Final Office Action”, U.S. Appl. No. 12/695,976, dated Nov. 27, 2015, 11 pages.
“Final Office Action”, U.S. Appl. No. 12/700,357, dated Apr. 15, 2016, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/700,357, dated Aug. 31, 2015, 14 pages.
“Final Office Action”, U.S. Appl. No. 12/700,357, dated Oct. 24, 2012, 13 pages.
“Final Office Action”, U.S. Appl. No. 12/700,357, dated Nov. 20, 2014, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/700,460, dated Aug. 28, 2012, 26 pages.
“Final Office Action”, U.S. Appl. No. 12/700,510, dated Feb. 3, 2015, 28 pages.
“Final Office Action”, U.S. Appl. No. 12/700,510, dated Mar. 14, 2016, 36 pages.
“Final Office Action”, U.S. Appl. No. 12/700,510, dated Oct. 10, 2012, 23 pages.
“Final Office Action”, U.S. Appl. No. 12/709,204, dated Jan. 12, 2015, 29 pages.
“Final Office Action”, U.S. Appl. No. 12/709,204, dated Apr. 11, 2014, 24 pages.
“Final Office Action”, U.S. Appl. No. 12/709,204, dated Sep. 12, 2013, 24 pages.
“Final Office Action”, U.S. Appl. No. 12/709,204, dated Oct. 3, 2012, 24 pages.
“Final Office Action”, U.S. Appl. No. 12/709,245, dated Mar. 15, 2013, 16 pages.
“Final Office Action”, U.S. Appl. No. 12/709,245, dated Jan. 6, 2012, 13 pages.
“Final Office Action”, U.S. Appl. No. 12/709,245, dated Nov. 14, 2014, 6 pages.
“Final Office Action”, U.S. Appl. No. 12/709,282, dated May 9, 2014, 17 pages.
“Final Office Action”, U.S. Appl. No. 12/709,282, dated Aug. 24, 2015, 24 pages.
“Final Office Action”, U.S. Appl. No. 12/709,282, dated Dec. 24, 2012, 11 pages.
“Final Office Action”, U.S. Appl. No. 12/709,282, dated Jul. 16, 2013, 11 pages.
“Final Office Action”, U.S. Appl. No. 12/709,301, dated Jan. 7, 2013, 14 pages.
“Final Office Action”, U.S. Appl. No. 12/709,301, dated Sep. 3, 2013, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/709,301, dated Mar. 1, 2012, 11 pages.
“Final Office Action”, U.S. Appl. No. 12/709,348, dated Jan. 7, 2013, 15 pages.
“Final Office Action”, U.S. Appl. No. 12/709,348, dated Sep. 12, 2013, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/709,348, dated Feb. 17, 2012, 13 pages.
“Final Office Action”, U.S. Appl. No. 12/709,376, dated Sep. 10, 2013, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/709,376, dated Nov. 8, 2012, 20 pages.
“Final Office Action”, U.S. Appl. No. 12/709,376, dated Mar. 30, 2012, 16 pages.
“Final Office Action”, U.S. Appl. No. 12/713,053, dated Aug. 17, 2012, 10 pages.
“Final Office Action”, U.S. Appl. No. 12/713,081, dated May 9, 2012, 19 pages.
“Final Office Action”, U.S. Appl. No. 12/713,096, dated Feb. 15, 2013, 7 pages.
“Final Office Action”, U.S. Appl. No. 12/713,110, dated Jan. 17, 2013, 10 pages.
“Final Office Action”, U.S. Appl. No. 12/713,113, dated Aug. 5, 2015, 26 pages.
“Final Office Action”, U.S. Appl. No. 12/713,113, dated Oct. 8, 2013, 21 pages.
“Final Office Action”, U.S. Appl. No. 12/713,113, dated Oct. 8, 2014, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/713,113, dated Jun. 4, 2012, 18 pages.
“Final Office Action”, U.S. Appl. No. 12/713,118, dated Oct. 26, 2012, 10 pages.
“Final Office Action”, U.S. Appl. No. 12/713,127, dated Jul. 31, 2015, 19 pages.
“Final Office Action”, U.S. Appl. No. 12/713,127, dated Aug. 14, 2014, 15 pages.
“Final Office Action”, U.S. Appl. No. 12/713,127, dated Jun. 6, 2012, 18 pages.
“Final Office Action”, U.S. Appl. No. 12/713,130, dated Jun. 29, 2012, 8 pages.
“Final Office Action”, U.S. Appl. No. 12/713,133, dated May 20, 2013, 10 pages.
“Final Office Action”, U.S. Appl. No. 12/713,133, dated Jul. 2, 2012, 8 pages.
“Final Office Action”, U.S. Appl. No. 13/484,075, dated Feb. 4, 2015, 12 pages.
“Final Office Action”, U.S. Appl. No. 13/484,075, May 21, 2013, 10 pages.
“Final Office Action”, U.S. Appl. No. 13/484,075, dated Jul. 16, 2015, 10 pages.
“Final Office Action”, U.S. Appl. No. 13/484,075, dated dated Nov. 10, 2015, 11 pages.
“Foreign Office Action”, CN Application No. 201110050852.8, dated Nov. 1, 2013, 8 Pages.
“Foreign Notice of Allowance”, CN Application No. 201110046510.9, dated Feb. 12, 2015, 6 Pages.
“Foreign Notice of Allowance”, CN Application No. 201110050506.X, dated Nov. 2, 2014, 4 Pages.
“Foreign Notice of Allowance”, CN Application No. 201180009579.2, dated Mar. 7, 2016, 4 Pages.
“Foreign Notice of Allowance”, CN Application No. 201180010769.6, dated Apr. 30, 2015, 4 Pages.
“Foreign Notice of Allowance”, CN Application No. 201180011039.8, dated Jan. 13, 2016, 4 Pages.
“Foreign Notice of Allowance”, JP Application No. 2012-555062, dated Mar. 3, 2015, 4 Pages.
“Foreign Office Action”, CN Application No. 201180010692.2, dated Mar. 28, 2016, 7 Pages.
“Foreign Office Action”, CN Application No. 201110044285.5, dated Apr. 24, 2013, 8 pages.
“Foreign Office Action”, CN Application No. 201110044285.5, dated Jun. 20, 2012, 12 pages.
“Foreign Office Action”, CN Application No. 201110044285.5, dated Jan. 4, 2013, 13 pages.
“Foreign Office Action”, CN Application No. 201110046510.9, dated Feb. 12, 2014, 9 Pages.
“Foreign Office Action”, CN Application No. 201110046510.9, dated Jul. 25, 2014, 11 Pages.
“Foreign Office Action”, CN Application No. 201110046510.9, dated May 31, 2013, 11 pages.
“Foreign Office Action”, CN Application No. 201110046519.X, dated Mar. 19, 2013, 12 pages.
“Foreign Office Action”, CN Application No. 201110046519.X, dated Apr. 1, 2016, 13 pages.
“Foreign Office Action”, CN Application No. 201110046519.X, dated Sep. 21, 2015, 16 Pages.
“Foreign Office Action”, CN Application No. 201110046519.X, dated Aug. 2, 2012, 13 pages.
“Foreign Office Action”, CN Application No. 201110046519.X, dated Aug. 6, 2013, 11 pages.
“Foreign Office Action”, CN Application No. 201110046529.3, dated Feb. 4, 2013, 9 pages.
“Foreign Office Action”, CN Application No. 201110046529.3, dated Aug. 16, 2012, 14 pages.
“Foreign Office Action”, CN Application No. 201110046529.3, dated Aug. 6, 2013, 11 pages.
“Foreign Office Action”, CN Application No. 201110050499.3, dated Nov. 27, 2012, 8 pages.
“Foreign Office Action”, CN Application No. 201110050499.3, dated Aug. 3, 2012, 8 pages.
“Foreign Office Action”, CN Application No. 201110050506.X, dated Apr. 2, 2013, 11 pages.
“Foreign Office Action”, CN Application No. 201110050506.X, dated Feb. 26, 2014, 6 pages.
“Foreign Office Action”, CN Application No. 201110050508.9, dated Mar. 7, 2013, 8 pages.
“Foreign Office Action”, CN Application No. 201110050508.9, dated Aug. 3, 2012, 8 pages.
“Foreign Office Action”, CN Application No. 201110050852.8, dated Mar. 26, 2013, 11 pages.
“Foreign Office Action”, CN Application No. 201180007100.1, dated May 15, 2015, 20 Pages.
“Foreign Office Action”, CN Application No. 201180007100.1, dated Sep. 10, 2014, 22 pages.
“Foreign Office Action”, CN Application No. 201180009579.2, dated Apr. 21, 2015, 16 Pages.
“Foreign Office Action”, CN Application No. 201180009579.2, dated Sep. 6, 2015, 19 pages.
“Foreign Office Action”, CN Application No. 201180009579.2, dated Nov. 4, 2014, 16 pages.
“Foreign Office Action”, CN Application No. 201180009635.2, dated Jul. 28, 2014, 13 pages.
“Foreign Office Action”, CN Application No. 201180010692.2, dated Mar. 10, 2015, 9 Pages.
“Foreign Office Action”, CN Application No. 201180010692.2, dated Jun. 26, 2014, 13 pages.
“Foreign Office Action”, CN Application No. 201180010692.2, dated Sep. 15, 2015, 10 Pages.
“Foreign Office Action”, CN Application No. 201180010769.6, dated Sep. 3, 2014, 12 Pages.
“Foreign Office Action”, CN Application No. 201180011020.3, dated Jan. 15, 2015, 9 Pages.
“Foreign Office Action”, CN Application No. 201180011020.3, dated May 4, 2014, 12 Pages.
“Foreign Office Action”, CN Application No. 201180011039.8, dated Feb. 17, 2015, 17 Pages.
“Foreign Office Action”, CN Application No. 201180011039.8, dated Jun. 5, 2014, 16 Pages.
“Foreign Office Action”, CN Application No. 201180011039.8, dated Sep. 6, 2015, 7 pages.
“Foreign Office Action”, EP Application No. 11737428.0, dated Nov. 18, 2013, 4 pages.
“Foreign Office Action”, EP Application No. 11745193.0, dated Jun. 10, 2016, 6 pages.
“Foreign Office Action”, EP Application No. 11747907.1, dated Jan. 28, 2013, 5 pages.
“Foreign Office Action”, EP Application No. 11748026.9, dated Jan. 16, 2013, 5 pages.
“Foreign Office Action”, EP Application No. 11748027.7, dated Jan. 18, 2013, 5 pages.
“Foreign Office Action”, EP Application No. 11748028.5, dated Jan. 28, 2013, 5 pages.
“Foreign Office Action”, EP Application No. 11748029.3, dated Jan. 16, 2013, 5 pages.
“Foreign Office Action”, JP Application No. 2012-554008, dated Jun. 25, 2015, 13 pages.
“Foreign Office Action”, JP Application No. 2012-554008, dated Nov. 25, 2014, 7 pages.
“In touch with new opportunities—Dispersive Signal Technology”, DataSheet, NXT, 2005, 1 page.
“International Search Report and Written Opinion”, Application No. PCT/US2011/025132, dated Oct. 26, 2011, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/025131, dated Oct. 31, 2011, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/020413, dated Apr. 8, 2013, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2015/019811, dated Jul. 8, 2015, 11 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/025973, dated Oct. 27, 2011, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US/2011025972, dated Sep. 30, 2011, 14 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/025575, dated Sep. 30, 2011, 14 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/025971, dated Oct. 31, 2011, 15 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2014/067804, dated Jul. 24, 2015, 19 Pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/020417, dated Oct. 20, 2011, 8 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/025974, dated Oct. 26, 2011, 8 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/020412, dated Aug. 31, 2011, 9 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/020410, dated Sep. 27, 2011, 9 pages.
“iQuery & Css Example—Dropdown Menu”, DesignReviver, Retrieved from: <http://designreviver.com/tutorials/jquery-css-example-dropdown-menu/> on Nov. 22, 2011, Oct. 7, 2008, 30 pages.
“New MS Courier Leak Details Multi-Touch Interface”, Retrieved from: <http://www.electronista.com/articles/09/11/04/courier.gestures.ui.explained/> on Nov. 10, 2009, Nov. 4, 2009, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/472,699, dated Mar. 28, 2013, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/472,699, dated Oct. 23, 2013, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/472,699, dated Sep. 12, 2011, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,842, dated May 22, 2013, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,842, dated Aug. 13, 2015, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,842, dated Aug. 18, 2014, 21 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,842, dated Oct. 3, 2012, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,937, dated May 7, 2014, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,937, dated Apr. 25, 2012, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,976, dated Mar. 25, 2015, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/695,976, dated Sep. 11, 2012, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,357, dated Apr. 2, 2015, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,357, dated Jun. 26, 2014, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,357, dated Dec. 16, 2015, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,357, dated Jul. 2, 2012, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,460, dated Jan. 13, 2012, 21 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,510, dated Jun. 12, 2014, 26 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,510, dated Aug. 28, 2015, 34 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/700,510, dated Feb. 7, 2012, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,204, dated May 7, 2015, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,204, dated Jun. 6, 2013, 27 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,204, dated Aug. 13, 2014, 25 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,204, dated Nov. 20, 2013, 31 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,204, dated May 10, 2012, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,245, dated Mar. 20, 2014, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,245, dated May 30, 2013, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,245, dated Nov. 30, 2011, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,245, dated Mar. 21, 2012, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,282, dated Jan. 29, 2015, 22 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,282, dated Feb. 28, 2013, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,282, dated May 10, 2016, 22 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,282, dated Oct. 10, 2013, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,282, dated Apr. 12, 2012, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated Jan. 16, 2015, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated May 14, 2013, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated May 23, 2014, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated Jul. 14, 2015, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated Oct. 24, 2013, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated Nov. 19, 2015, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated Nov. 28, 2011, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,301, dated Sep. 13, 2012, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,348, dated Apr. 25, 2013, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,348, dated Dec. 20, 2013, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,348, dated Dec. 7, 2011, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,348, dated Aug. 2, 2012, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,376, dated May 23, 2013, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,376, dated Jan. 23, 2012, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/709,376, dated Aug. 17, 2012, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,053, dated Nov. 23, 2012, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,053, dated Feb. 3, 2012, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,081, dated Nov. 29, 2012, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,081, dated Dec. 23, 2011, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,096, dated Jan. 30, 2014, 23 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,096, dated Dec. 30, 2015, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,096, dated Jun. 26, 2013, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,096, dated Jun. 6, 2012, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,110, dated May 3, 2013, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,110, dated Jun. 21, 2012, 21 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,113, dated Feb. 12, 2015, 24 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,113, dated Apr. 23, 2013, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,113, dated Jun. 4, 2014, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,113, dated Dec. 22, 2011, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,118, dated Jan. 29, 2015, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,118, dated Jun. 8, 2012, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,127, dated Jan. 31, 2014, 21 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,127, dated Mar. 26, 2015, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,127, dated Dec. 27, 2011, 22 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,130, dated Jan. 16, 2013, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,130, dated Jan. 23, 2012, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,133, dated Jan. 14, 2013, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,133, dated Jan. 31, 2012, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/713,133, dated Dec. 10, 2013, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/484,075, dated Jan. 15, 2013, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/484,075, dated Apr. 29, 2015, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/484,075, dated Sep. 5, 2014, 11 pages.
“Notice of Allowance”, U.S. Appl. No. 12/472,699, dated May 2, 2014, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 12/695,064, dated Mar. 28, 2012, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 12/695,842, dated Apr. 8, 2016, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 12/695,959, dated Apr. 17, 2012, 13 pages.
“Notice of Allowance”, U.S. Appl. No. 12/700,357, dated Aug. 4, 2016, 16 pages.
“Notice of Allowance”, U.S. Appl. No. 12/709,204, dated Sep. 25, 2015, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 12/709,245, dated Jan. 30, 2015, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 12/709,245, dated Apr. 28, 2015, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 12/709,301, dated Feb. 24, 2016, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 12/709,301, dated Sep. 8, 2015, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 12/709,376, dated Mar. 17, 2014, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,053, dated Jun. 7, 2013, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,096, dated Jan. 9, 2015, 14 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,096, dated May 20, 2016, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,096, dated Aug. 29, 2014, 14 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,110, dated Dec. 4, 2013, 13 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,118, dated Mar. 5, 2015, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,130, dated Feb. 19, 2013, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 12/713,133, dated Jan. 17, 2014, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 13/484,075, dated Mar. 31, 2016, 17 pages.
“Search Report”, TW Application No. 099142890, dated Jun. 30, 2015, 1 page.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/713,096, dated Nov. 4, 2014, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/713,118, dated Mar. 19, 2015, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/713,133, dated Feb. 3, 2014, 2 pages.
“Supplementary European Search Report”, EP Application No. 11737428.0, dated Nov. 13, 2004, 3 pages.
“Supplementary European Search Report”, EP Application No. 11747907.1, dated Nov. 7, 2012, 3 pages.
“Supplementary European Search Report”, EP Application No. 11748027.7, dated Nov. 29, 2012, 3 pages.
“Supplementary European Search Report”, EP Application No. 11748028.5, dated Nov. 7, 2012, 3 pages.
“Touch Screen is available in .36-50.8 mm thickness”, ThomasNet Industrial News Room, Jul. 29, 2003, 2 pages.
“TouchSystems—Innovation Touch Screen Solution”, Retrieved from <http://www.touchsystems.com/article.aspx?id=16> on Aug. 30, 2012, Aug. 14, 2012, 1 page.
“UI Guidelines Version 2.1”, Retrieved from: http://na.blackberry.com/eng/deliverables/6622/BlackBerry_Smartphones-US.pdf., 76 Pages.
Appleinsider,“Special Report: Apple's Touch-Sensitive iPod Ambitions Disclosed in Filing”, Retrieved from: <http://www.appleinsider.com/articles/06/10/26/special_report_apples_touch_sensitive_ipod_ambitions_disclosed_in_filing.html> on Nov. 11, 2009, Oct. 26, 2006, 10 pages.
Boudreaux,“Touch Patterns: Chapter 6—Programming the iPhone User Experience”, retrieved from <http://oreilly.com/iphone/excerpts/iphone-programming-user/touch-patterns.html> on Oct. 25, 2011, 12 pages.
Brandl,“Combining and Measuring the Benefits of Bimanual Pen and Direct-Touch Interaction on Horizontal Interfaces”, Retrieved from: <http://www.merl.com/papers/docs/TR2008-054.pdf> on Nov. 5, 2009, Mitsubishi Electric Research Laboratories, May 2008, 10 pages.
Daniels,“Brave New World”, Retrieved from: <http://bookseller-association.blogspot.com/2009_03_01_archive.html> on Nov. 10, 2009, Mar. 2009, 54 pages.
Elliott,“First Dell, Then HP: What's Next for N-trig's Multitouch Screen Technology”, Retrieved from: <http://news.cnet.com/8301-17938_105-10107886-1.html> on Nov. 11, 2009, Nov. 25, 2008, 5 pages.
Emigh,“Lenovo Launches Windows 7 ThinkPads with Multitouch and Outdoor Screens”, Retrieved from: <http://www.betanews.com/article/Lenovo-launches-Windows-7-ThinkPads-with-multitouch-and-outdoor-screens/1253017166> on Nov. 11, 2009, Sep. 15, 2009, 3 pages.
Findlater,“Personalized Input: Improving Ten-Finger Touchscreen Typing through Automatic Adaptation”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Available at <http://terpconnect.umd.edu/˜leahkf/pubs/CHI2012-findlater-PersonalizedTyping.pdf>, May 5, 2012, 10 pages.
Fonseca,“New Apple Patent Hints at Touch Enabled Bezels for Future Devices”, Retrieved from: <http://vr-zone.com/articles/new-apple-patent-hints-at-touch-enabled-bezels-for-future-devices/42928.html?utm_source=rss&utm_medium=rss&utm_campaign=new-apple-patent-hints-at-touch-enabled-bezels-for-future-devices> Jan. 31, 2014, Jul. 3, 2013, 6 Pages.
Goel,“GripSense: Using Built-In Sensors to Detect Hand Posture and Pressure on Commodity Mobile Phones”, Proceedings of the 25th Annual ACM Symposium on User Interface Software and Technology, Oct. 7, 2012, pp. 545-554.
Gross,“Stretch-A-Sketch: A Dynamic Diagrammer”, IEEE Symposium on Visual Languages, Available at <http://depts.washington.edu/dmachine/PAPER/VL94/vl.html>, Oct. 1994, 11 pages.
Hinckley,“Codex: A Dual Screen Tablet Computer”, Conference on Human Factors in Computing Systems, Apr. 9, 2009, 10 pages.
Hinckley,“Sensor Synaesthesia: Touch in Motion, and Motion in Touch”, CHI 2011, May 7-12, 2011, available at <http://research.microsoft.com/en-us/um/people/kenh/papers/touch-motion-camera-ready-final.pdf>, May 7, 2011, 10 pages.
Hinckley,“Stitching: Pen Gestures that Span Multiple Displays”, CHI 2004, Available at <http://www.cs.cornell.edu/˜francois/Papers/2004-Hinckley-AVI04-Stitching.>, 2004, pp. 1-8.
Hirche,“Adaptive Interface for Text Input on Large-Scale Interactive Surfaces”, 3rd IEEE International Workshop on Horizontal Interactive Human Computer System, Oct. 1, 2008, pp. 153-156.
Hotelling,“Multi-functional hand-held device”, U.S. Appl. No. 60/658,777, filed Mar. 4, 2015, 117 pages.
Hotelling,“Multi-functional hand-held device”, U.S. Appl. No. 60/663,345, filed Mar. 16, 2005, 76 pages.
Kim,“Hand Grip Pattern Recognition for Mobile User Interfaces”, Interaction Lab / Samsung Advanced Institute of Technology, Available at <http://www.alice.org/stage3/pubs/uistsensing.pdf>, 2006, pp. 1789-1794.
Krazit,“Has Apple Found the Magic Touch?”, Retrieved from: <http://news.cnet.com/8301-13579_3-9879471-37.html> on Nov. 10, 2009, Feb. 26, 2008, 2 pages.
Lee,“The TypeWay iPad app is an adaptive on-screen keyboard”, Retrieved from <http://www.ubergizmo.com/2012/02/the-typeway-ipad-app-is-an-adaptive-on-screen-keyboard/> on Mar. 7, 2013, Feb. 1, 2012, 2 pages.
Maxwell,“Writing drivers for common touch-screen interface hardware”, Industrial Control Design Line, Jun. 15, 2005, 9 pages.
Minsky,“Manipulating Simulated Objects with Real-world Gestures using a Force and Position Sensitive Screen”, Computer Graphics, vol. 18, No. 3, Available at <http://delivery.acm.org/10.1145/810000/808598/p195-minsky.pdf?key1=808598&key2=2244955521&coll=GUIDE&dl=GUIDE&CFID=57828830&CFTOKEN=43421964>, Jul. 1984, pp. 195-203.
Moore,“TypeWay Adaptive Keyboard for iPad Review”, Retrieved from <http://www.technologytell.com/apple/89378/typeway-adaptive-keyboard-for-ipad-review/> on Mar. 6, 2013, Feb. 5, 2012, 10 pages.
Nordgren,“Development of a Touch Screen Interface for Scania Interactor”, Master's Thesis in C—Available at <http://www.cs.umu.se/education/examina/Rapporter/PederNordgren.pdf>omputing Science, UMEA University, Apr. 10, 2007, pp. 1-59.
Olwal,“Rubbing and Tapping for Precise and Rapid Selection on Touch-Screen Displays”, Conference on Human Factors in Computing Systems, Available at <http://www.csc.kth.se/˜alx/projects/research/rubbing/olwal_rubbing_tapping_chi_2008.pdf>, Apr. 2008, 10 pages.
Panzarino,“Apple's iPad Mini Should have a Widescreen Display”, Retrieved from <http://thenextweb.com/apple/2012/08/15/what-ipad-mini-169-instead-43/> on Aug. 29, 2012, Aug. 15, 2012, 6 pages.
Pierce,“Toolspaces and Glances: Storing, Accessing, and Retrieving Objects in 3D Desktop Applications”, 1999 Symposium on Interactive 3D Graphics, Available at <http://delivery.acm.org/10.1145/310000/300545/p163-pierce.pdf?key1=300545&key2=8792497521&coll=GUIDE&dl=GUIDE&CFID=61004073& CFTOKEN=28819248>, Apr. 1999, pp. 163-168.
Roth,“Bezel Swipe: Conflict-Free Scrolling and Multiple Selection on Mobile Touch Screen Devices”, CHI 2009, Available at <http://www.volkerroth.com/download/Roth2009a.pdf>, Apr. 2009, 4 pages.
Roudaut,“Leaf Menus: Linear Menus with Stroke Shortcuts for Small Handheld Devices”, Proceedings of the 12th IFIP TC 13 International Conference on Human-Computer Interaction: Part I, Aug. 2009, 4 pages.
Saini,“Designing of a Virtual System with Fingerprint Security by considering many Security Threats”, International Journal of Computer Applications, vol. 3—No. 2, available at <http://www.ijcaonline.org/volume3/number2/pxc387995.pdf>, Jun. 2010, pp. 25-31.
Sajid,“Microsoft Patent a Futuristic Virtual Multitouch Keyboard”, Retrieved from <http://thetechnopath.com/microsoft-patent-futuristic-virtual-multitouch-keyboard/857/> on Mar. 6, 2013, Sep. 27, 2009, 8 pages.
Sax,“LiquidKeyboard: An Ergonomic, Adaptive QWERTY Keyboard for Touchscreens and Surfaces”, ICDS 2011, The Fifth International Conference on Digital Society, Feb. 23, 2011, 6 pages.
Serrano,“Bezel-Tap Gestures: Quick Activation of Commands from Sleep Mode on Tablets”, n Proceedings of the SIGCHI Conference on Human Factors in IComputing Systems, Apr. 27, 2013, 10 pages.
T.,“Smartphone displays need a bezel. Here's why”, Retrieved from <http://www.phonearena.com/news/Smartphone-displays-need-a-bezel.-Heres- why_id27670> on Aug. 29, 2012, Mar. 12, 2012, 4 pages.
Vallerio,“Energy-Efficient Graphical User Interface Design”, Retrieved from: <http://www.cc.gatech.edu/classes/AY2007/cs7470_fall/zhong-energy-efficient-user- interface.pdf>, Jun. 10, 2004, pp. 1-13.
Vigil,“Methods for Controlling a Floating Cursor on a Multi-touch Mobile Phone or Tablet in Conjunction with Selection Gestures and Content Gestures”, U.S. Appl. No. 61/304,972, Feb. 16, 2010, 54 pages.
Yee,“Two-Handed Interaction on a Tablet Display”, Retrieved from: <http://zesty.ca/tht/yee-tht-chi2004-short.pdf>, Conference on Human Factors in. Computing Systems, Apr. 2004, 4 pages.

Related Publications (1)

	Number	Date	Country
	20170010848 A1	Jan 2017	US

Continuations (1)

	Number	Date	Country
Parent	12713096	Feb 2010	US
Child	15276500		US

Multi-device pairing and combined display

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Term Extension

Abstract