US 8,239,785 B2Grant
Edge gestures
Issue Date:2012-08-07
•10 Claims
•39 Drawing Sheets
Abstract
Techniques involving gestures and other functionality are described. In one or more implementations, the techniques describe gestures that are usable to provide inputs to a computing device. A variety of different gestures are contemplated, including bimodal gestures (e.g., using more than one type of input) and single modal gestures. Additionally, the gesture techniques may be configured to leverage these different input types to increase the amount of gestures that are made available to initiate operations of a computing device.
Metadata
Assignee
- Microsoft Corporation
Inventors
- Kenneth P. Hinckley
- Koji Yatani
- Georg F. Petschnigg
Application Information
Application Number:US 12/695,064
Filing Date:2010-01-27
Priority Date:2010-01-27
Art Unit:2172
Classifications
IPC:
G06F3/01G06F3/048
Patent Drawings (39 sheets)
Description
Background
[0001] The amount of functionality that is available from computing devices is ever increasing, such as from mobile devices, game consoles, televisions, set-top boxes, personal computers, and so on. However, traditional techniques that were employed to interact with the computing devices may become less efficient as the amount of functionality increases.
[0002] For example, inclusion of additional functions in a menu may add additional levels to the menu as well as additional choices at each of the levels. Consequently, the addition of these functions in the menu may frustrate users by the sheer number of choices of functions and thereby result in decreased utilization of both the additional functions as well as the device itself that employs the functions. Thus, traditional techniques that were used to access the functions may limit the usefulness of the functions to a user of the computing device.
Summary
[0003] Techniques involving gestures and other functionality are described. In one or more implementations, the techniques describe gestures that are usable to provide inputs to a computing device. A variety of different gestures are contemplated, including bimodal gestures (e.g., using more than one type of input) and single modal gestures. Additionally, the gesture techniques may be configured to leverage these different input types to increase the amount of gestures that are made available to initiate operations of a computing device.
[0004] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Brief Description of the Drawings
[0005] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.
[0006] FIG. 1 is an illustration of an environment in an example implementation that is operable to employ gesture techniques.
[0007] FIG. 2 illustrates an example system 200 showing the gesture module 104 and bimodal input module 114 of FIG. 1 as being implemented using in an environment where multiple devices are interconnected through a central computing device.
[0008] FIG. 3 is an illustration of an example implementation in which stages of a copy gesture of FIG. 1 are shown as being input through interaction with the computing device.
[0009] FIG. 4 is a flow diagram depicting a procedure in an example implementation of a copy gesture in accordance with one or more embodiments.
[0010] FIG. 5 is an illustration of an example implementation in which stages of a staple gesture of FIG. 1 are shown as being input through interaction with the computing device.
[0011] FIG. 6 is a flow diagram depicting a procedure in an example implementation of a staple gesture in accordance with one or more embodiments.
[0012] FIG. 7 is an illustration of an example implementation in which stages of a cut gesture of FIG. 1 are shown as being input through interaction with the computing device.
[0013] FIG. 8 is a flow diagram depicting a procedure in an example implementation of a cut gesture in accordance with one or more embodiments.
[0014] FIG. 9 is an illustration of an example implementation in which stages of a punch-out gesture of FIG. 1 are shown as being input through interaction with the computing device.
[0015] FIG. 10 is a flow diagram depicting a procedure in an example implementation of a punch-out gesture in accordance with one or more embodiments.
[0016] FIG. 11 is an illustration of an example implementation in which a combination of a cut gesture and a punch-out gesture of FIG. 1 are shown as being input in conjunction with the computing device.
[0017] FIG. 12 is an illustration of an example implementation in which stages of a rip gesture of FIG. 1 are shown as being input through interaction with the computing device.
[0018] FIG. 13 is a flow diagram that depicts a procedure in an example implementation of a rip gesture in accordance with one or more embodiments.
[0019] FIG. 14 is an illustration of an example implementation in which stages of an edge gesture of FIG. 1 are shown as being input through interaction with the computing device to draw a line.
[0020] FIG. 15 is a flow diagram depicting a procedure in an example implementation of an edge gesture in accordance with one or more embodiments.
[0021] FIG. 16 is a flow diagram depicting a procedure in an example implementation of an edge gesture in accordance with one or more embodiments.
[0022] FIG. 17 is an illustration of an example implementation in which stages of an edge gesture of FIG. 1 are shown as being input through interaction with the computing device to cut along a line.
[0023] FIG. 18 is a flow diagram that depicts a procedure in an example implementation of an edge gesture to perform a cut in accordance with one or more embodiments.
[0024] FIG. 19 is an illustration of an example implementation in which stages of a stamp gesture of FIG. 1 are shown as being input in conjunction with the computing device.
[0025] FIG. 20 is a flow diagram that depicts a procedure in an example implementation of a stamp gesture in accordance with one or more embodiments.
[0026] FIG. 21 is an illustration of an example implementation in which stages of a brush gesture of FIG. 1 are shown as being input through interaction with the computing device.
[0027] FIG. 22 is a flow diagram that depicts a procedure in an example implementation of a brush gesture in accordance with one or more embodiments.
[0028] FIG. 23 is an illustration of an example implementation in which stages of a carbon-copy gesture of FIG. 1 are shown as being input through interaction with a computing device.
[0029] FIG. 24 is an illustration of an example implementation in which stages of a carbon-copy gesture of FIG. 1 are shown as being input in conjunction with the computing device.
[0030] FIG. 25 is a flow diagram that depicts a procedure in an example implementation of a carbon-copy gesture in accordance with one or more embodiments.
[0031] FIG. 26 is an illustration of an example implementation in which stages of a fill gesture of FIG. 1 are shown as being input in conjunction with the computing device.
[0032] FIG. 27 is a flow diagram that depicts a procedure in an example implementation of a fill gesture in accordance with one or more embodiments.
[0033] FIG. 28 is an illustration of an example implementation in which stages of a cross-reference gesture of FIG. 1 are shown as being input in conjunction with the computing device.
[0034] FIG. 29 is an illustration of an example implementation in which stages of a gesture are shown to access metadata associated with the image using the fill gesture of FIG. 28 .
[0035] FIG. 30 is a flow diagram that depicts a procedure in an example implementation of the cross-reference gesture of FIG. 1 in accordance with one or more embodiments.
[0036] FIG. 31 is an illustration of an example implementation in which stages of a link gesture of FIG. 1 are shown as being input in conjunction with the computing device.
[0037] FIG. 32 is a flow diagram that depicts a procedure in an example implementation of a link gesture in accordance with one or more embodiments.
[0038] FIG. 33 is an illustration of an example implementation in which stages of the link gesture of FIG. 1 are shown as being input in conjunction with the computing device.
[0039] FIG. 34 is a flow diagram that depicts a procedure in an example implementation of a link gesture in accordance with one or more embodiments.
[0040] FIG. 35 depicts an example implementation showing techniques for contextual spatial multiplexing.
[0041] FIG. 36 is a flow diagram that depicts a procedure in an example implementation in which identification of whether an input is a stylus or touch input is used to identify an operation to be performed in conjunction with a user interface.
[0042] FIG. 37 is a flow diagram that depicts another procedure in an example implementation in which identification of whether an input is a stylus or touch input is used to identify an operation to be performed in conjunction with a user interface.
[0043] FIG. 38 illustrates various components of an example device that can be implemented as any type of portable and/or computer device as described with reference to FIGS. 1-37 to implement embodiments of the gesture techniques described herein.
Detailed Description
[0044] Overview
[0045] Conventional techniques that were used to access functions of a computing device may become less efficient when expanded to access an ever increasing number of functions. Therefore, these conventional techniques may result in user frustration regarding the additional functions and may result in decreased user satisfaction with a computing device having those additional functions. For example, use of a traditional menu may force a user to navigate through multiple levels and selections at each of the levels to locate a desired function, which may be both time consuming and frustrating for the user.
[0046] Techniques involving gestures are described. In the following discussion, a variety of different implementations are described that involve gestures to initiate functions of a computing device. In this way, a user may readily access the functions in an efficient and intuitive manner without encountering the complexities involved using conventional access techniques. For example, in one or more implementations a gesture involves a bimodal input to signify the gesture, such as through direct manual input using touch (e.g., a finger of a user's hand) and a stylus (e.g., a pointed input device such as a pen). Through recognition of which input is a touch input versus a stylus input and vice versa, a variety of different gestures may be supported. Further discussion of this and other implementations that do and do not involve bimodal inputs may be found in the following sections.
[0047] In the following discussion, an example environment is first described that is operable to employ the gesture techniques described herein. Example illustrations of gestures and procedures involving the gestures are then described, which may be employed in the example environment as well as in other environments. Accordingly, the example environment is not limited to performing the example gestures and procedures. Likewise, the example procedures and gestures are not limited to implementation in the example environment.
[0048] Example Environment
[0049] FIG. 1 is an illustration of an environment 100 in an example implementation that is operable to employ gesture techniques. The illustrated environment 100 includes an example of a computing device 102 that may be configured in a variety of ways. For example, the computing device 102 may be configured as a traditional computer (e.g., a desktop personal computer, laptop computer, and so on), a mobile station, an entertainment appliance, a set-top box communicatively coupled to a television, a wireless phone, a netbook, a game console, and so forth as further described in relation to FIG. 2 . Thus, the computing device 102 may range from full resource devices with substantial memory and processor resources (e.g., personal computers, game consoles) to a low-resource device with limited memory and/or processing resources (e.g., traditional set-top boxes, hand-held game consoles). The computing device 102 may also relate to software that causes the computing device 102 to perform one or more operations.
[0050] The computing device 102 is illustrated as including a gesture module 104. The gesture module 104 is representative of functionality to identify gestures and cause operations to be performed that correspond to the gestures. The gestures may be identified by the gesture module 104 in a variety of different ways. For example, the gesture module 104 may be configured to recognize a touch input, such as a finger of a user's hand 106 as proximal to a display device 108 of the computing device 102 using touchscreen functionality.
[0051] The touch input may also be recognized as including attributes (e.g., movement, selection point, etc.) that are usable to differentiate the touch input from other touch inputs recognized by the gesture module 104. This differentiation may then serve as a basis to identify a gesture from the touch inputs and consequently an operation that is to be performed based on identification of the gesture.
[0052] For example, a finger of the user's hand 106 is illustrated as selecting 110 an image 112 displayed by the display device 108. Selection 110 of the image 112 and subsequent movement of the finger of the user's hand 106 may be recognized by the gesture module 104. The gesture module 104 may then identify this recognized movement as indicating a “drag and drop” operation to change a location of the image 112 to a point in the display at which the finger of the user's hand 106 was lifted away from the display device 108. Thus, recognition of the touch input that describes selection of the image, movement of the selection point to another location, and then lifting of the finger of the user's hand 106 may be used to identify a gesture (e.g., drag-and-drop gesture) that is to initiate the drag-and-drop operation.
[0053] A variety of different types of gestures may be recognized by the gesture module 104, such a gestures that are recognized from a single type of input (e.g., touch gestures such as the previously described drag-and-drop gesture) as well as gestures involving multiple types of inputs. As illustrated in FIG. 1 , for instance, the gesture module 104 is illustrated as including a bimodal input module 114 that is representative of functionality to recognize inputs and identify gestures involving bimodal inputs.
[0054] For example, the computing device 102 may be configured to detect and differentiate between a touch input (e.g., provided by one or more fingers of the user's hand 106) and a stylus input (e.g., provided by a stylus 116). The differentiation may be performed in a variety of ways, such as by detecting an amount of the display device 108 that is contacted by the finger of the user's hand 106 versus an amount of the display device 108 that is contacted by the stylus 116. Differentiation may also be performed through use of a camera to distinguish a touch input (e.g., holding up one or more fingers) from a stylus input (e.g., holding two fingers together to indicate a point) in a natural user interface (NUI). A variety of other example techniques for distinguishing touch and stylus inputs are contemplated, further discussion of which may be found in relation to FIG. 38 .
[0055] Thus, the gesture module 104 may support a variety of different gesture techniques by recognizing and leveraging a division between stylus and touch inputs through use of the bimodal input module 114. For instance, the bimodal input module 114 may be configured to recognize the stylus as a writing tool, whereas touch is employed to manipulate objects displayed by the display device 108. Consequently, the combination of touch and stylus inputs may serve as a basis to indicate a variety of different gestures. For instance, primitives of touch (e.g., tap, hold, two-finger hold, grab, cross, pinch, hand or finger postures, and so on) and stylus (e.g., tap, hold-and-drag-off, drag-into, cross, stroke) may be composed to create a space of intuitive and semantically rich gestures. It should be noted that by differentiating between stylus and touch inputs, the number of gestures that are made possible by each of these inputs alone is also increased. For example, although the movements may be the same, different gestures (or different parameters to analogous commands) may be indicated using touch inputs versus stylus inputs.
[0056] Accordingly, the gesture module 104 may support a variety of different gestures, both bimodal and otherwise. Examples of gestures described herein include a copy gesture 118, a staple gesture 120, a cut gesture 122, a punch-out gesture 124, a rip gesture 126, an edge gesture 128, a stamp gesture 130, a brush gesture 132, a carbon-copy gesture 134, a fill gesture 136, a cross-reference gesture 138, and a link gesture 140. Each of these different gestures is described in a corresponding section in the following discussion. Although different sections are used, 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.
[0057] Additionally, although the following discussion may describe specific examples of touch and stylus inputs, in instances the types of inputs may be switched (e.g., touch may be used to replace stylus and vice versa) and even removed (e.g., both inputs may be provided using touch or a stylus) without departing from the spirit and scope thereof. Further, although in instances in the following discussion the gestures are illustrated as being input using touchscreen functionality, the gestures may be input using a variety of different techniques by a variety of different devices, further discussion of which may be found in relation to the following figure.
[0058] FIG. 2 illustrates an example system 200 showing the gesture module 104 and bimodal input module 114 of FIG. 1 as being implemented using in an environment where 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 or the Internet or other means. In one embodiment, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to the 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 device is created and experiences are tailored to the generic class of devices. A class of device may be defined by physical features or usage or other common characteristics of the devices.
[0059] For example, as previously described the computing device 102 may assume a variety of different configurations, such as for mobile 202, computer 204, and television 206 uses. Each of these configurations has a generally corresponding screen size and thus the computing device 102 may be configured accordingly to one or more of these device classes in this example system 200. For instance, the computing device 102 may assume the mobile 202 class of device which includes mobile phones, portable music players, game devices, and so on. The computing device 102 may also assume a computer 204 class of device that includes personal computers, laptop computers, netbooks, and so on. The television 206 configuration includes configurations of devices that involve display on a generally larger screen in a casual environment, e.g., televisions, set-top boxes, game consoles, and so on. Thus, the techniques described herein may be supported by these various configurations of the computing device 102 and are not limited to the specific examples described in the following sections.
[0060] The cloud 208 is illustrated as including a platform 210 for web services 212. The platform 210 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 208 and thus may act as a “cloud operating system.” For example, the platform 210 may abstract resources 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 web services 212 that are implemented via the platform 210. A variety of other examples are also contemplated, such as load balancing of servers in a server farm, protection against malicious parties (e.g., spam, viruses, and other malware), and so on. Thus, web services 212 and other functionality may be supported without the functionality “having to know” the particulars of the supporting hardware, software, and network resources.
[0061] Accordingly, in an interconnected device embodiment, implementation of functionality of the gesture module 104 (and the bimodal input module 114) may be distributed throughout the system 200. For example, the gesture module 104 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.
[0062] Further, the functionality may be supported by the computing device 102 regardless of the configuration. For example, the gesture techniques supported by the gesture module 104 may be detected using touchscreen functionality in the mobile 202 configuration, track pad functionality of the computer 204 configuration, detected by a camera as part of support of a natural user interface (NUI) that does not involve contact with a specific input device in the television 206 example, and so on. Further, performance of the operations to detect and recognize the inputs to identify a particular gesture may be distributed throughout the system 200, such as by the computing device 102 and/or the web services 212 supported by the platform 210 of the cloud 208. Further discussion of the gestures supported by the gesture module 104 may be found in relation to the following sections.
[0063] Generally, any of the functions described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms “module,” “functionality,” and “logic” as used herein generally represent software, firmware, hardware, or a combination thereof. In the case of a software implementation, the module, functionality, or logic represents program code that performs specified tasks when executed on a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer readable memory devices. The features of the gesture techniques described below are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.
[0064] Copy Gesture
[0065] FIG. 3 is an illustration of an example implementation 300 in which stages of the copy gesture 118 of FIG. 1 are shown as being input through interaction with the computing device 102. The copy gesture 118 is illustrated in FIG. 3 using first, second, and third stages 302, 304, 306. In the first stage 302, an image 308 is displayed by the display device 108 of the computing device 102. The image 308 is further illustrated as being selected 310 using a finger of the user's hand 106. For example, the finger of the user's hand 106 may be placed and held within a boundary of image 308. This touch input may therefore be recognized by the gesture module 104 of the computing device 102 as a touch input to select the image 308. Although selection with the user's finger has been described, other touch inputs are also contemplated without departing from the spirit and scope thereof.
[0066] In the second stage 304, the image 308 is still selected using the finger of the user's hand 106, although in other embodiments the image 308 may remain in a selected state even after the finger of the user's hand 106 is lifted away from the image 308. While the image 308 is selected, the stylus 116 is used to provide a stylus input that includes placement of the stylus within the boundary of the image 308 and then subsequent movement of the stylus outside the boundary of the image 308. This movement is illustrated in the second stage 304 using a phantom line and a circle indicating the initial point of interaction with the image 308 by the stylus 116. Responsive to the touch and stylus inputs, the computing device 102 (through the gesture module 104) causes a copy 312 of the image 308 to be displayed by the display device 108. The copy 312 in this example follows the movement of the stylus 116 at the initial point of interaction with the image 308. In other words, the initial point of interaction of the stylus 116 with the image 308 is used as a continuing point for manipulation of the copy 312 such that the copy 312 follows movement of the stylus. In an implementation, the copy 312 of the image 308 is displayed once the movement of the stylus 116 crosses a boundary of the image 308, although other implementations are also contemplated, such as movement that has passed a threshold distance, recognition of the touch and stylus inputs as indicating the copy gesture 118, and so on. For example, if a boundary edge of an image lies beyond a maximum allowed stroke distance from a starting point of the stylus, crossing of this maximum allowed stroke distance may instead trigger initiation of the copy gesture. In another example, if a boundary edge of an image is closer than a minimum allowed stroke distance, movement of the stylus beyond the minimum allowed stroke distance likewise replaces crossing of the image boundary itself. In a further example, movement velocity may be employed rather than distance threshold, e.g. moving the pen “fast” for a copy gesture versus slow for a carbon copy gesture. In a further example, pressure at the initiation of the movement may be employed, e.g., pressing relatively “hard” on the pen for a copy gesture.
[0067] In the third stage 306, the stylus 116 is illustrated as having moved further away from the image 308. In the illustrated implementation, the opacity of the copy 312 increases the further the copy 312 is moved, an example of which may be noticed by comparison of the second and third stages 304, 306 that is shown using grayscale. Once the stylus 116 is removed from the display device 108, the copy 312 is displayed at that location on the display device 108 as being fully opaque, e.g., is a “true copy” of the image 308. In an implementation, another copy may be created by repeating the stylus 116 movement while the image 308 is selected, e.g., using the finger of the user's hand 106. For example, if the finger of the user's hand 106 remains on the image 308 (thereby selecting the image), each subsequent movement of the stylus from within the boundary of the image 308 to outside the boundary may cause another copy of the image 308 to be created. In an implementation, the copy is not considered to be fully realized until the copy becomes fully opaque. That is, lifting the stylus (or moving the stylus back to a distance less than the copy creation threshold) while the image remains semi-transparent may cancel the copy operation in this implementation.
[0068] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the copy gesture 118, the gesture may be performed using touch or stylus inputs alone, or a physical keyboard, mouse, or bezel button may be held down in lieu of continuing a touch input on the display device, and so on. In some embodiments, ink annotations or other objects completely or partially overlapping, proximal to, previously selected, or otherwise associated with the selected image may also be considered as part of the “image” and copied as well.
[0069] FIG. 4 is a flow diagram that depicts a procedure 400 in an example implementation of a copy gesture 118 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 300 of FIG. 3 .
[0070] A first input is recognized as selecting an object displayed by a display device (block 402). For example, a touch input provided using a finger of a user's hand 106 may be recognized by the gesture module 104 as selecting an image 308 displayed by the display device 108 of the computing device 102.
[0071] A second input is recognized as movement from within the bounds of the object to outside the bounds of the object, the movement recognized as occurring while the object is selected (block 404). Continuing with the previous example, a stylus 116 may be used to provide an input describing movement from a point within the image 308 to outside a boundary of the image 308 as shown in the second stage 304 of FIG. 3 . Accordingly, the gesture module 104 may recognize this movement from a stylus input detected using touchscreen functionality of the display device 108. In an implementation, the first and second inputs are input and detected concurrently using the computing device 102.
[0072] A copy gesture is identified from the recognized first and second inputs, the copy gesture effective to cause a display of a copy of the object to follow subsequent movement of a source of the second input (block 406). Through recognition of the first and second inputs, the gesture module 104 may identify a corresponding copy gesture 118 to be indicated using those inputs. In response, the gesture module 104 may cause a copy 312 of the image 308 to be displayed by the display device 108 and follow subsequent movement of the stylus 116 across the display device 108. In this way, the copy 312 of the image 308 may be created and moved in an intuitive manner. Additional copies may also be made using these techniques.
[0073] For example, a third input is recognized as movement from within the bounds of the object to outside the bounds of the object, the movement recognized as occurring while the object is selected by the first input (block 408). Thus, in this example the object (e.g., the image 308) is still selected using the finger of the user's hand 106 (or other touch input). Another stylus input may then be received that involves movement from within the image 308 to outside the bounds of the image 308. Accordingly, a second copy gesture is identified from the recognized first and third inputs, the copy gesture effective to cause a display of a second copy of the object to follow subsequent movement of a source of the third input (block 410).
[0074] Continuing with the previous example, the second copy may follow the subsequent movement of the stylus 116. Although this example described continued selection of the image 308 using the finger of the user's hand 106, selection may continue even when the selection of the object is not continued using the source, e.g., the finger of the user's hand. For example, the image 308 may be placed in a “selected state” such that continued contact by the finger of the user's hand 106 is not needed to keep the image 308 selected. Again, it should be noted that although a specific example was described in the copy gesture 118 above using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the input, and so on.
[0075] Staple Gesture
[0076] FIG. 5 is an illustration of an example implementation 500 in which stages of the staple gesture 120 of FIG. 1 are shown as being input in conjunction with the computing device 102. The staple gesture 120 is illustrated in FIG. 5 using first, second, and third stages 502, 504, 506. In the first stage 502, first, second, third, and fourth images 508, 510, 512, 514 are displayed by the display device 108 of the computing device 102. A user's hands are shown in phantom as selecting the first and second images 508, 510 using touch inputs, such as by “tapping” on the images using the user's hands.
[0077] In the second stage 504, the first and second images 508, 510 are shown as being in a selected state through the use of a phantom border around the images, although other techniques may also be employed. A finger of the user's hand 106 is further illustrated in the second stage 504 as holding the fourth image 514, such as by placing the finger of the user's hand 106 in the proximity of the fourth image 514 and keeping it there, e.g., for at least a predetermined amount of time.
[0078] While the fourth image 514 is being held by the finger of the user's hand 106, the stylus 116 may be used to “tap” within the bounds of the fourth image 514. Accordingly, the gesture module 104 (and the bimodal input module 114) may identify a staple gesture 120 from these inputs, e.g., the selection of the first and second images 508, 510, the hold of the fourth image 514, and the tap of the fourth image 514 using the stylus 116.
[0079] Responsive to the identification of the staple gesture 120, the gesture module 104 may arrange the first, second, and fourth images 508, 510, 514 into a collated display. For example, the first and second images 508, 510 may be displayed in the order selected as beneath the held object (e.g., the fourth image 514) by the display device 108. Additionally, an indication 516 may be displayed to indicate that the first, second, and fourth images 508, 510, 514 are stapled together. In an embodiment, the indication 516 may be removed by holding the fourth image 514 and swiping the stylus 116 over the indication to “remove the staple.”
[0080] This gesture may be repeated to add additional items to the collated display, e.g., selection of the third image 512 and then tapping the fourth image 514 using the stylus 116 while the fourth image 514 is being held. In another example, a book may be formed through use of the staple gesture 120 to collate collections of already stapled material. Further, the collated collection of objects may be manipulated as a group, such as to resize, move, rotate, and so on, further discussion of which may be found in relation to the following figure. Performing a staple gesture on top of a stack that is already stapled may toggle the stack between collated and un-collated states (with the gesture module 104 remembering the original relative spatial relationship between the items collated), may add a cover sheet or book binding (cover) to a stack, and so on.
[0081] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the staple gesture 120, the gesture may be performed using touch or stylus inputs alone, and so on.
[0082] FIG. 6 is a flow diagram that depicts a procedure 600 in an example implementation of a staple gesture in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 500 of FIG. 5 .
[0083] A first input is recognized as selecting a first object displayed by a display device (block 602). The first object may be selected in a variety of ways. For example, the first image 508 may be tapped by a finger of the user's hand 106, a stylus 116, use of a cursor control device, and so on.
[0084] A second input is recognized as provided subsequent to the first input and as a hold of a second object displayed by the display device (block 604). A third input is also recognized as a tap of the second object during the hold of the second object (block 606). Continuing with the previous example, a finger of the user's hand 106 may be placed and held within the boundary of the fourth image 514 while the stylus 116 is tapped within the boundary of the fourth image 514. Additionally, these inputs may be received after selection of the first image 508, e.g., using a touch input.
[0085] A staple gesture is identified from the first, second, and third inputs, the staple gesture effective to cause a collated display of the first object as beneath the second object (block 608). The gesture module 104 may identify the staple gesture 120 from the first, second, and third inputs. Responsive to this identification, the gesture module 104 may cause one or more objects selected by the first input to be arranged beneath the object that is being held as described by the second input. An example of this is shown in the third stage 506 of the system 500 of FIG. 5 . In an implementation, the one or more objects that are selected via the first input are arranged beneath the second input in an order that corresponds to an order in which the one or more objects were selected. In other words, the order of selection of the one or more objects is used as a basis to arrange the objects in the collated display. The collated display of the objects, as stapled together, may be leveraged in a variety of ways.
[0086] For instance, a fourth input is recognized as involving selection of the collated display (block 610). A gesture is identified from the fourth input that is effective to change an appearance of the collated display (block 612). For example, the gesture may involve resizing the collated display, moving the collated display, rotating the collated display, minimizing the collated display, and so on. Thus, the stapled group of objects may be manipulated as a group in an efficient and intuitive manner by a user.
[0087] The staple gesture may also be repeated to add additional objects to the collated display of a stapled group of objects, further collate groups of already collated objects, and so on. For instance, a second staple gesture is identified that is effective to cause a collated display of a third object as beneath a fourth object (block 614). A third staple gesture is then identified that is effective to cause a collated display of the first, second, third, and fourth objects (block 616). In this way, a user may form a “book” of objects by repeating the staple gesture 120. Again, it should be noted that although a specific example was described regarding the staple gesture 120 above using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the input, and so on.
[0088] Cut Gesture
[0089] FIG. 7 is an illustration of an example implementation 700 in which stages of the cut gesture 122 of FIG. 1 are shown as being input through interaction with the computing device 102. The cut gesture 122 is illustrated in FIG. 7 using first, second, and third stages 702, 704, 706. In the first stage 702, an image 708 is displayed by the display device 108 of the computing device 102. A finger of the user's hand 106 is illustrated as selecting the image 708 in the first stage 702.
[0090] In the second stage 704, a stylus input is received that describes movement 710 of the stylus 116 at least twice across one or more boundaries of the image 708 while the image 708 is selected. This movement 708 is illustrated through use of a dashed line in the second stage 704 that begins outside the image 708, passes through a first boundary of the image 708, proceeds through at least a portion of the image 708, and passes through another boundary of the image 708, thereby leaving the confines of the image 708.
[0091] Responsive to these inputs (e.g., the touch input to select the image 708 and the stylus input defining the movement), the gesture module 104 may identify the cut gesture 122. Accordingly, as shown in the third stage 706, the gesture module 104 may cause the image 708 to be displayed in at least two portions 712, 714 in accordance with the indicated movement 710 of the stylus 116. In an implementation, the portions are displaced slightly in the display by the gesture module 104 to better indicate the cut. Although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the cut gesture 122, the gesture may be performed using touch or stylus inputs alone, and so on.
[0092] FIG. 8 is a flow diagram that depicts a procedure 800 in an example implementation of a cut gesture in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 700 of FIG. 7 .
[0093] A first input is recognized as selecting an object displayed by a display device (block 802). For example, the image 708 may be tapped by a finger of the user's hand 106, a stylus 116, use of a cursor control device, and so on. In the illustrated implementation, a finger of the user's hand 106 is illustrated as selecting the image 708.
[0094] A second input is recognized as movement at least twice across one or more boundaries of the object, the movement recognized as occurring while the object is selected (block 804). The movement may be input in a variety of ways. For example, the movement 710 may involve uninterrupted contact of the stylus 116 with the display device 108 of the computing device 102 that crosses boundaries (e.g., edges) of the image 708 at least twice. Additionally, although the movement 710 is illustrated as beginning “outside” the image 708, the movement may also begin within the bounds of the image 708 and then cross at least two boundaries to indicate the cut in this example. Further, the stylus movement may also include multiple strokes (e.g., overlapping) that collectively cross the boundaries. Multiple strokes drawn in this manner may be recognized by the module as together since the hold of the image (e.g., the touch input) clearly indicates that these strokes belong together. To realize this, the first (partial) stroke may put the selection in a special state such that additional strokes are permitted without invoking other gestures (e.g., the copy gesture) until the “phrase” of multiple stroke inputs has completed.
[0095] A cut gesture is identified from the recognized first and second inputs, the cut gesture effective to cause a display of the object to appear as cut along the movement of the second input across the display of the object (block 806). Upon identification of the cut gesture 122 by the computing device 102, for instance, the gesture module 104 may cause one or more portions of the image 106 to appear displaced from an initial location and to have a boundary that corresponds at least partially to the movement 710 of the stylus 116. Furthermore, the initial and final portions of the pen stroke (outside of the image boundary) may initially be seen as ordinary “ink” strokes by the gesture module 104, but during or subsequent to the cut operation, these ink traces may be removed from the display device so as not to leave marks as a result of performing the cut gesture.
[0096] It should be realized that each subsequent crossing of a boundary of the object (e.g., the image 708) may be identified as another cut gesture. Therefore, each pair of crossings of the border of the image 708 may be identified by the gesture module 104 as a cut. In this way, multiple cuts may be performed while the image 708 is selected, e.g., while the finger of the user's hand 106 is still placed within the image 708. Again, it should be noted that although a specific example was described in the cut gesture 122 above using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the input, and so on.
[0097] Punch-out Gesture
[0098] FIG. 9 is an illustration of an example implementation 900 in which stages of the punch-out gesture 124 of FIG. 1 are shown as being input through interaction with the computing device 102. The punch-out gesture 124 is illustrated in FIG. 9 using first, second, and third stages 902, 904, 906. In the first stage 902, an image 908 is illustrated as being selected using a finger of a user's hand 106, although other implementations are also contemplated as previously described.
[0099] While the image 908 is selected (e.g., in a selected state), a second input is received that approximates self-intersecting movement 910 within the image 908. For example, the movement 910 is illustrated in the second stage 904 as being input using the stylus 116. The stylus input that describes the movement 910 in illustrated example details an oval shown through the use of dashed lines on the image 908. In an implementation, the gesture module 104 may provide such a display (e.g., during or upon completion of the self-intersecting movement) to serve as a visual cue to the user. Additionally, the gesture module 104 may use a threshold to identify when the movement is sufficiently close to approximate the self-intersecting movement. In an implementation, the gesture module 104 incorporates a threshold size for the movement, e.g., to limit punch outs below the threshold size such as at a pixel level.
[0100] At the second stage 904, the gesture module 104 has recognized that the movement 910 is self intersecting. While the image 908 is still selected (e.g., the finger of the user's hand 106 remains within the image 908), another input is received that involves a tap within the self intersecting movement 910. For example, the stylus 116 that was used to detail the self intersecting movement 910 may then be used to tap within the self intersecting movement, e.g., the dashed oval as illustrated in the second stage 904. From these inputs, the gesture module 104 may identify the punch-out gesture 124. In another implementation, the tap may be performed “outside” the approximated self-intersecting movement to remove that portion of the image. Thus, the “tap” may be used to indicate which portion of the image is to be retained and which is to be removed.
[0101] Accordingly, as illustrated in the third stage 906, a portion of the image 908 that was within the self intersecting movement 910 is punched out (e.g., removed) from the image 908, thereby leaving a hole 912 in the image 908. In the illustrated implementation, the portion of the image 908 that was punched out is no longer displayed by the display device 108, although other implementations are also contemplated. For example, the punched out portion may be minimized and displayed within the hole 912 in the image 908, may be displayed proximal to the image 908, and so on. Subsequent taps while the image is still held (selected) may produce additional punch-outs with the same shape as the first—thus the operation may define a paper-punch shape and the user may then repeatedly apply it to punch additional holes in the image, other images, the canvas in the background, and so forth.
[0102] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the punch-out gesture 124, the gesture may be performed using touch or stylus inputs alone, and so on.
[0103] FIG. 10 is a flow diagram that depicts a procedure 1000 in an example implementation of a punch-out gesture in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 900 of FIG. 9 .
[0104] A first input is recognized as selecting an object displayed by a display device (block 1002). For example, the image 708 may be tapped by a finger of the user's hand 106, a stylus 116, through use of a cursor control device, and so on.
[0105] A second input is recognized as self-intersecting movement within the object (block 1004). For example, the self-intersecting movement may be input as a continuous movement that crosses itself. A variety of shapes and sizes of self-intersecting movement are contemplated and as such this movement is not limited to the example illustrated movement 910 of FIG. 9 . In an implementation, the second input also includes a tap within an area defined by the movement as previously described in relation to FIG. 9 . However, other implementations are also contemplated, e.g., the portion within the self-intersecting movement 910 may “drop out” without the tap of the stylus 116.
[0106] A punch-out gesture is identified from the recognized first and second inputs, the punch-out gesture effective to cause a display of the object to appear as if the self-intersecting movement caused a hole in the object (block 1006). Continuing with the previous example, the hole 912 may be displayed by the gesture module 104 upon identification of the punch-out gesture 124. Again, it should be noted that although a specific example was described in which the punch-out gesture 124 was input using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on. Additionally, as previously described functionality of the gestures may be combined into a single gesture, an example of which is shown in the following figure.
[0107] FIG. 11 is an illustration of an example implementation 1100 in which a combination of a cut gesture 122 and a punch-out gesture 124 of FIG. 1 are shown as being input in conjunction with the computing device 102. The cut and punch-out gestures 122, 124 are illustrated through use of first and second stages 1102, 1104. In the first stage 1102, an image 1106 is illustrated as being selected using a finger of a user's hand 106. Movement 1108 of a stylus 116 is also illustrated through use of a dash line as before. In this case, however, the movement 1108 passes through two boundaries of the image 1106 and is self-intersecting within the image 1106.
[0108] In the second stage 1104, the image 1106 is cut along the described movement 1108 of the stylus 116. As with the cut gesture 122, portions 1110, 1112, 1114 are slightly displaced to show “where” the image 1106 was cut. Additionally, a portion of the movement 1108 is identified as self-intersecting and is therefore “punched out” of the image 1106. In this instance, however, the portion 1110 that is punched out is displayed proximal to the other portions 1112, 1114 of the image 1106. It should be readily apparent that this is but one of a variety of different examples of composing of gestures and that a variety of different combinations of the gestures described herein are contemplated without departing from the spirit and scope thereof.
[0109] Rip Gesture
[0110] FIG. 12 is an illustration of an example implementation 1200 in which stages of the rip gesture 126 of FIG. 1 are shown as being input through interaction with the computing device 102. The rip gesture 126 is illustrated in FIG. 12 using first and second stages 1202, 1204. In the first stage 1202, an image 1206 is displayed by a display device 108 of the computing device 102. First and second fingers of the user's hand 106 and first and second fingers of the user's other hand 1208 are illustrated as selecting the image 1206. For example, the first and second fingers of the user's hand 106 may be used to indicate a first point 1210 and the first and second finger of the user's other hand 1208 may be used to indicate a second point 1212.
[0111] Movement is recognized by the gesture module 104 in which the first and second inputs have moved away from each other. In the illustrated implementation, this movement 1214, 1216 describes an arc much like a motion that would be used to rip physical paper. Accordingly, the gesture module 104 may identify a rip gesture 126 from these inputs.
[0112] The second stage 1204 shows a result of the rip gesture 126. In this example, the image 1206 is ripped to form first and second portions 1218, 1220. Additionally, a rip 1222 is formed between the first and second points 1210, 1212 of the image that is generally perpendicular to the described movement of the fingers of the user's hands 106, 1208 away from each other. In the illustrated example, the rip 1222 is displayed as having a jagged edge which differs from the clean edge of the cut gesture 122, although a clean edge is also contemplated in other implementations, e.g., to rip along a perforated line in an image displayed by the display device 108. As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the rip gesture 126, the gesture may be performed using touch or stylus inputs alone, and so on.
[0113] FIG. 13 is a flow diagram that depicts a procedure 1300 in an example implementation of a rip gesture 126 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 1200 of FIG. 12 .
[0114] A first input is recognized as selecting a first point of an object displayed by a display device (block 1302). A second input is recognized as selecting a second point of the object (block 1304). For example, the finger of the user's hand 106 may select the first point 1210 and a finger from the user's other hand 1208 may select the second point of the image 1206.
[0115] Movement is recognized of the first and second inputs as moving away from each other (block 1306). For example, the movement may contain a vector component that indicates that the first and second inputs (and thus sources of the first and second inputs) are moving and/or have moved apart. Accordingly, a rip gesture is identified from the recognized first and second inputs, the rip gesture effective to cause a display of the object to appear as ripped between the first and second points (block 1308). As shown in FIG. 12 , for instance, the rip 1222 may be formed at a general midpoint between the first and second points 1210, 1212 and run perpendicular to a straight line connecting the first and second points 1210, 1212 if so drawn. Yet again, it should be noted that although a specific example was described in which the rip gesture 126 was input using touch inputs, those inputs may be switched to stylus input, multiple input types may be used (e.g., touch and stylus), and so on.
[0116] Edge Gesture
[0117] FIG. 14 is an illustration of an example implementation 1400 in which stages of the edge gesture 128 of FIG. 1 are shown as being input in conjunction with the computing device 102 to draw a line. The edge gesture 128 is illustrated in FIG. 14 using first, second, and third stages 1402, 1404, 1406. At the first stage 1402, an image 1408 is selected using two points of contact. For example, first and second fingers of the user's hand 106 may be used to select the image 1408, although other examples are also contemplated. By using two-points of contact as opposed to one, the gesture module 104 may differentiate between an increased number of gestures, although it should be readily apparent that a single point of contact is also contemplated in this example.
[0118] In the second stage 1404, the two points of contact from the user's hand 106 are used to move and rotate the image 1408 from the initial location in the first stage 1402 to the new location illustrated in the second stage 1404. The stylus 116 is also illustrated as moving proximal to an edge 1410 of the image 1408. Accordingly, the gesture module 104 identifies the edge gesture 128 from these inputs and causes a line 1412 to be displayed as shown in the third stage 1406.
[0119] In the illustrated example, the line 1412 is displayed as proximal to where the edge 1410 of the image 1408 was located when the movement of the stylus 116 occurred. Thus, in this example the edge 1410 of the image 1408 acts as a straight edge to draw a corresponding line 1412 that is straight. In an implementation, the line 1412 may be continue to follow the edge 1410 even when proceeding past the corner of the image 1408. In this way, the line 1412 may be drawn as having a length that is greater that the length of the edge 1410.
[0120] Additionally, identification of the edge gesture 128 may cause output of an indication 1414 of where the line is to be drawn, an example of which is shown in the second stage 1404. The gesture module 104, for instance, may output the indication 1414 to give the user an idea of where the line 1412 is to be drawn in relation to the edge 1410. In this way, the user may adjust a location of the image 1408 to further refine where the line is to be drawn without actually drawing the line 1412. A variety of other examples are also contemplated without departing from the spirit and scope thereof.
[0121] In an implementation, the line 1412 has different characteristics depending on what is to be displayed beneath the line 1412, i.e., what the line is to be drawn upon. The line 1412, for instance, may be configured for display when drawn over a background of a user interface but not displayed when drawn over another image. Additionally, the image 1408 may be displayed as partially transparent when used as a part of the edge gesture 128 such that a user may view what is beneath the image 1408 and thus made better aware of a context in which the line 1412 is to be drawn. Further, although the edge 1410 is illustrated as straight in this example, the edge may take a variety of configurations, e.g., a French curve, circle, oval, wave, following the cut, torn, or punched-out edges from our previous example gestures, and so on. For instance, a user may select from a variety of preconfigured edges to perform the edge gesture 128 (such as from a menu, a template displayed in a side area of the display device 108, and so on). Accordingly, in such configurations the line drawn proximal to the edges may follow curves and other features of the edge.
[0122] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the edge gesture 128, the gesture may be performed using touch or stylus inputs alone, and so on. For example, in some embodiments where finger painting or color-smudging are supported using touch inputs, these touch inputs also conform to the edge(s) thus formed. Other tools, such as an airbrush, can also be snapped to the edge, to produce a hard edge along the constraint line, and a soft edge on the underlying surface.
[0123] FIG. 15 is a flow diagram that depicts a procedure 1500 in an example implementation of the edge gesture 128 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 1400 of FIG. 14 .
[0124] A first input is recognized as selecting an object displayed by a display device (block 1502). As described above, the first input may be recognized as a touch input involving two points of contact on a display of an object, e.g., the image 1408. Although referenced as “points of contact,” it should be readily apparent that actual contact is not required, e.g., the points of contact may be signified “in the air” using a natural user interface (NUI) and detected using a camera. Therefore, the points of contact may refer to an indication of an intent to indicate contact, and not limited to actual contact itself.
[0125] A second input is recognized as movement along an edge of the object, the movement recognized as occurring while the object is selected (block 1504). Continuing with the previous example, a stylus input may be recognized that was input as proximal to and following a displayed edge 1410 of the image 1408 using the stylus 116.
[0126] The gesture is identified from the recognized first and second inputs, the gesture effective to cause display of a line as drawn proximal to the edge and as following movement described by the second input (block 1506). The gesture module 104 may recognize the edge gesture 128 from these inputs. The edge gesture 128 is operable to cause a line to be displayed that corresponds to the recognized movement as well as to follow subsequent movement of the stylus 116. As previously noted, the line drawn using the edge gesture 128 is not limited to a straight line and rather may follow any desirable edge shape without departing from the spirit and scope thereof. Likewise multiple pen strokes may be drawn in succession along the same or different edges of a selected object.
[0127] FIG. 16 is a flow diagram that depicts a procedure 1600 in an example implementation of the edge gesture 128 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 1400 of FIG. 14 .
[0128] A first input is recognized as selecting an object displayed by a display device using a plurality of touch inputs (block 1602). As described in relation to FIG. 14 , the first input may be recognized as a touch input involving two points of contact on a display of an object, e.g., the image 1408.
[0129] A second input is recognized as describing movement of a stylus along an edge of the object, the movement recognized as occurring while the object is selected (block 1604). In this example, the input is a type of stylus input that is recognized as being input as proximal to and following a displayed edge 1410 of the image 1408 using the stylus 116.
[0130] A gesture is identified from the recognized first and second inputs, the gesture effective to cause the edge of the object to act as a template such that a line drawn proximal to the edge as indicated by the stylus input is displayed as following the edge of the object (block 1606). Thus, in this example, the edges of the object (e.g., image 1408) act as guide to cause display of a line responsive to identification of the edge gesture 128.
[0131] FIG. 17 is an illustration of an example implementation 1700 in which stages of the edge gesture 128 of FIG. 1 are shown as being input in conjunction with the computing device 102 to cut along a line. The edge gesture 128 is illustrated in FIG. 17 using first, second, and third stages 1702, 1704, 1706. At the first stage 1702, a first image 1708 is selected using two points of contact. For example, first and second fingers of the user's hand 106 may be used to select the image 1708, although other examples are also contemplated.
[0132] In the second stage 1704, the two points of contact from the user's hand 106 are used to move the first image 1708 from the initial location in the first stage 1702 to the new location illustrated in the second stage 1704 as positioned “over” a second image 1710. Additionally, the first image 1708 is illustrated as partially transparent (e.g., using grayscale) such that at least a portion of the second image 1710 that is positioned beneath the first image 1708 may be viewed. In this way, the user may adjust a location of the image 1708 to further refine where the cut is to occur.
[0133] The stylus 116 is illustrated as moving proximal to an edge 1712 of the first image 1708 along in indication 1712 of a “cut line.” Accordingly, the gesture module 104 identifies the edge gesture 128 from these inputs, a result of which is shown in the third stage 1706. In an implementation, the object to be cut is also selected (e.g., via a tap) to indicate what is to be cut. The selection of the edge and cut/drawn objects may be performed in any order.
[0134] As shown in the third stage 1706, the first image 1708 has been moved away from the second image 1710, e.g., using a drag and drop gesture to move the image 1708 back to the previous location. Additionally, the second image 1710 is displayed as cut into first and second portions 1714, 1716 along where the edge of the first image 1708 was positioned in the second stage 1704, i.e., along the indication 1712. Thus, in this example the edge of the first image 1708 may be used as a template to perform the cut, rather than performing a “freehand” cut as previously described for the cut gesture 122.
[0135] In an implementation, the cut performed by the edge gesture 128 has different characteristics depending on where the cut is to be performed. For example, the cut may be used to cut objects displayed in a user interface but not a background of the user interface. Additionally, although the edge is illustrated as straight in this example, the edge may take a variety of configurations, e.g., a French curve, circle, oval, wave, and so on. For instance, a user may select from a variety of preconfigured edges to perform cut using the edge gesture 128 (such as from a menu, a template displayed in a side area of the display device 108, and so on). Accordingly, in such configurations the cut may follow curves and other features of a corresponding edge. Likewise, a tearing gesture may be performed with a finger to create a torn edge that follows the template.
[0136] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the edge gesture 128, the gesture may be performed using touch or stylus inputs alone, and so on.
[0137] FIG. 18 is a flow diagram that depicts a procedure 1800 in an example implementation of the edge gesture 128 to perform a cut in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 1700 of FIG. 17 .
[0138] A first input is recognized as selecting an object displayed by a display device (block 1802). A second input is recognized as movement along an edge of the object, the movement recognized as occurring while the object is selected (block 1804). As before, a stylus input may be recognized that was input as proximal to and following a displayed edge of the image 1708 using the stylus 116 while the image 1708 is selected, e.g., using one or more fingers of the user's hand 106.
[0139] The gesture is identified from the recognized first and second inputs, the gesture is effective to cause display of a cut as being proximal to the edge and as following movement described by the second input (block 1806). The gesture module 104 may recognize the edge gesture 128 from these inputs. The edge gesture 128 is operable to cause a cut to be displayed that corresponds to the recognized movement as well as to follow subsequent movement of the stylus 116. For example, portions 1714, 1716 of the image 1710 may be displayed as slightly displaced to show “where” the cut occurred. As previously noted, the cut is not limited to a straight line and rather may follow any desirable edge shape without departing from the spirit and scope thereof.
[0140] Again, it should be noted that although the specific examples of FIGS. 14-18 were described in which the edge gesture 128 was input using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on.
[0141] Stamp Gesture
[0142] FIG. 19 is an illustration of an example implementation 1900 in which stages of the stamp gesture 130 of FIG. 1 are shown as being input in conjunction with the computing device 102. The stamp gesture 130 is illustrated in FIG. 19 using first, second, and third stages 1902, 1904, 1906. In the first stage 1902, an image 1908 is selected using a finger of the user's hand 106, although other implementations are also contemplated, e.g., selection using multiple points of contact, a cursor control device, and so on as previously described.
[0143] In the second stage 1904, the stylus 116 is used to indicate first and second locations 1910, 1912 in a user interface displayed by the display device 108 of the computing device 102. For example, the stylus 116 may be used to “tap” the display device 108 at those locations. In this example, the first and second locations 1910, 1912 are located “outside” the bounds of the image 1908. However, it should be readily apparent that other examples are contemplated. For instance, once the first location has fallen outside the bounds of the image, a “stamping phrase” may be established, and therefore subsequent taps may fall within the bounds of the image with introducing ambiguity with respect to other gestures, e.g., the staple gesture.
[0144] Responsive to these inputs, the gesture module 104 identifies the stamp gesture 130 and causes first and second copies 1914, 1916 to be displayed at the first and second locations 1910, 1912, respectively. In an implementation, the first and second copies 1914, 1916 of the image 1908 are displayed to give an appearance that the image 1908 was used similar to a rubber stamp to stamp the copies 1914, 1916 onto a background of the user interface. A variety of techniques may be used to give the rubber stamp appearance, such as granularity, use of one or more colors, and so on. Furthermore the stylus tap pressure and stylus tilt angles (azimuth, elevation, and roll, where available) may be used to weight the resulting ink impression, determine the stamp's image orientation, determine a direction of smudging or blurring effects, introduce a gradient of light to dark ink in the resulting image, and so on. Likewise, for touch inputs there may also be corresponding properties of contact area and orientation of the touch input. Additionally, successive stamp gestures 130 may be used to create successively lighter copies of the image 1908 in response to successive taps that are performed outside the boundary of the image 1908, optionally down to a minimum lightness threshold. An example of this is illustrated as the second copy 1916 of the image 1908 being displayed as lighter than the first copy 1914 of the image 1908 in the second stage 1904 through the use of grayscale. Other lightening techniques are also contemplated, such as use of contrast, brightness, and so on. The user may also “refresh the ink” or change the color or effect(s) produced by a stamp by engaging a color picker, color icons, effect icons, or the like during a stamping phrase.
[0145] In the third stage 1906, the image 1908 is displayed as rotated when compared with the image 1908 in the first and second stages 1902, 1904. Accordingly, in this example a third stamp gesture 130 causes a display of a third copy 1918 as having an orientation that matches the orientation of the image 1908, e.g., rotated. A variety of other examples are also contemplated, such as to manipulate a size, color, texture, view angle, and so on of the copies 1914-1918 of the image 1908. As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the stamp gesture 130 (e.g., the image 1908 may be held using the stylus 116 and the locations of where the stamp is to be made using a touch input), the gesture may be performed using touch or stylus inputs alone, and so on.
[0146] FIG. 20 is a flow diagram that depicts a procedure 2000 in an example implementation of a stamp gesture 130 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the system 1900 of FIG. 19 .
[0147] A first input is recognized as selecting an object displayed by a display device (block 2002). For example, the image 1908 may be selected using one or more fingers of the user's hand 106, a stylus 116, use of a cursor control device, and so on. Accordingly, the first input describes this selection.
[0148] A second input is recognized as indicating a first location in a user interface outside a boundary of the object and as occurring while the object is selected (block 2004). For example, the second input may be recognized by the gesture module 104 as a stylus input that describes a tap of the stylus 116 in the first location 1910 in a user interface displayed by a display device 108 of the computing device 102. Additionally, the first location may occur outside a boundary of the image 1908.
[0149] A first stamp gesture is identified from the recognized first and second inputs, the first stamp gesture effective to cause a display of a copy of the object at the first location in the user interface (block 2006). Continuing with the previous example, the gesture module 104 may cause a first copy 1914 of the image 1908 to be displayed at the first location 1910. The copy 1914 of the image 1908 may be configured in a variety of different ways, such as to appear as if the image 1908 was used as a rubber stamp to create the copy 1914.
[0150] Additionally, the stamp may be initiated and placed in the user interface in a variety of ways. For example, the stylus 116 may “tap down” on the display device 108 to indicate an initially desired location, e.g., the second location 1912. If the stylus 116 is moved while still indicating desired interaction with the user interface (e.g., placed proximal to a user interface output by the display device 108), the second copy 1916 may follow the movement of the stylus 116. Once the stylus 116 indicates a final placement, e.g., through lifting the stylus 116 away from the display device 108, the copy may remain at that location, motion blur/smudging may be applied to the resulting stamp that follows the path prescribed by the stylus, and so on. Additional copies (e.g., stamps) may also be made, an example of which is described as follows.
[0151] A third input is recognized as indicating a second location in the user interface outside the boundary of the object and as occurring while the object is selected (block 2008). A second stamp gesture is identified from the recognized first and third inputs, the second stamp gesture effective to cause a display of the second copy of the object at the second location in the user interface, the second copy being lighter than the first copy (block 2010). Continuing yet again with the previous example, the gesture module 104 may cause a second copy 1916 of the image 1908 to be displayed at the second location 1912. In an implementation, successive implementation of the stamp gesture 130 causes successfully lighter copies to be displayed by the display device 108, an example of which is shown using successively lighter shades of gray in the example implementation 1900 of FIG. 19 . Additionally, different semantics may be employed by the gesture module 104 depending on “what” is going to be stamped. For instance, the gesture module 104 may permit the copy (e.g., the stamp) to appear on a background but not on icons or other images displayed by the display device 108, may limit the copies to being implemented in data that may be manipulated by a user, and so on.
[0152] For example, in an embodiment an icon from a toolbar may be selected (e.g., held) and then instances of the icon may be “stamped” onto a user interface, e.g., shapes in a drawing program. A variety of other examples are also contemplated. Again, it should be noted that although a specific example was described in which the stamp gesture 130 was input using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on.
[0153] Brush Gesture
[0154] FIG. 21 is an illustration of an example implementation 2100 in which stages of the brush gesture 132 of FIG. 1 are shown as being input through interaction with the computing device 102. The brush gesture 132 is illustrated in FIG. 21 using first, second, and third stages 2102, 2104, 2106. In the first stage 2102, an image 2108 is displayed in a user interface by the display device 108 of the computing device 102. The image 2108 in this example is a photo of a city skyline having a plurality of buildings.
[0155] In the second stage 2104, a touch input is used to both select the image 2108 and to select a particular point 2110 in the image 2108, which is illustrated as being performed using a finger of the user's hand 106. The stylus 116 in this example is also illustrated as providing a stylus input that describes one or more lines that are “brushed” by the stylus 116 outside the borders of the image 2108. For example, the stylus 116 may make a series of zigzagging lines that begin at a location 2112 outside the boundary of the image 2108 in the user interface, a combination of lines taken together, a single line over a threshold distance, and so on. The gesture module 104 may then identify these inputs as the brush gesture 132. At this point, the gesture module 104 may consider these inputs to have initiated a brushing phrase, such that subsequent lines below a threshold distance are permitted.
[0156] Upon identification of the brush gesture 132, the gesture module 104 may use a bitmap of the image 2108 as fill for the lines drawn by the stylus 116. Additionally, in an implementation the fill is taken from corresponding lines of the image 2108 beginning at the particular point 2110 in the image 2108 indicated by the touch input, e.g., the finger of the user's hand 106, although other viewport mappings of the source image to the resulting brush strokes are contemplated within the scope thereof, such as by using properties of the source object, e.g., texture and so on. A result of these lines is illustrated as a portion 2114 of the image 2108 copied using the brush strokes of the stylus 116.
[0157] In an implementation, the opacity of the lines that are drawn by the stylus 116 increases as additional lines are drawn over a given area. As illustrated in the third stage 2106, for instance, the stylus 116 may draw back over the portion 2114 copied from the image 2108 to increase the opacity of the portion 2114. This is illustrated in the third stage 2106 by increasing the darkness of the portion 2114 as compared to the darkness of the portion 2114 illustrated in the second stage 2104 of the example implementation 2100.
[0158] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the brush gesture 132, the brush gesture 132 may be performed using touch or stylus inputs alone, and so on.
[0159] FIG. 22 is a flow diagram that depicts a procedure 2200 in an example implementation of a brush gesture 132 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 2100 of FIG. 21 .
[0160] A first input is recognized as selecting an object displayed by a display device (block 2202). For example, the image 2108 may be selected using a touch input, a stylus input, through use of a cursor control device, and so on. In the illustrated implementation, a finger of the user's hand 106 is illustrated as selecting the image 2108 to provide the touch input.
[0161] A second input is recognized as a line drawn outside the bounds of the object, the line recognized as being drawn while the object is selected (block 2204). For example, the second input may be a stylus input that describes one or more lines drawn outside the boundary of the image 2108 in a user interface.
[0162] A brush gesture is identified from the recognized first and second inputs, the brush gesture effective to cause a display of the line being drawn as a copy of a corresponding line of the object (block 2206). Continuing with the previous example, the gesture module 104 may identify the brush gesture from the inputs and therefore use the image 2108 that was selected via the first input as fill for the lines described by the second input. For instance, the brush gesture may be effective to cause a copy of a corresponding line of the object beginning at a point in the object selected by the first input (block 2208). As shown in the second stage 2104 of FIG. 21 , the touch input may select a particular point 2110 which may be used as a starting point to provide fill for the lines drawn by the stylus beginning at a point 2112 that is outside the image 2108. Although indication of a starting point for fill to be used for the brush gesture 132 by the touch input was described, a variety of other implementations are also contemplated. For example, the fill point for each brush gesture 132 may be set at a predefined location in the image 2108, such as a top-left corner of the image 2108, center of the image 2108, and so on.
[0163] Additionally, the brush gesture may be effective to cause copying of a corresponding plurality of lines from the object as having a matching spatial relationship to a plurality of lines of the second input (block 2210). In this example, the lines described by the stylus input are taken from corresponding portions of the image and preserve a spatial relationship of the image 2108. Further, continued selection of the image 2108 may cause lines drawn elsewhere in the user interface displayed by the display device 108 to preserve this relationship until an input is received that this is no longer desired, such as by lifting a finger of the user's hand 106 away from the display device. Therefore, even if the stylus 116 is lifted from the display device 108 and placed elsewhere on the device 108 to draw additional lines, the fill used for those additional lines in this embodiment maintains the same spatial relation from the image 2108 as the previous set of lines. A variety of other examples are also contemplated, such as to begin the fill process again using the point 2110 indicated by the touch input as a starting point. Again, it should be noted that although a specific example was described in which the brush gesture 132 was input using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on.
[0164] Carbon-Copy Gesture
[0165] FIG. 23 is an illustration of an example implementation 2300 in which stages of the carbon-copy gesture 134 of FIG. 1 are shown as being input through interaction with the computing device 102. The carbon-copy gesture 134 is illustrated in FIG. 23 using first, second, and third stages 2302, 2304, 2306. In the first stage 2302, an image 2308 is displayed in a user interface by the display device 108 of the computing device 102. Like the image 2108 of FIG. 21 , the image 2308 in this example is a photo of a city skyline having a plurality of buildings. The image 2308 is selected in the first stage 2302 using a touch input, e.g., a finger of the user's hand 106, and moved to a new location in the user interface as illustrated in the second stage 2304.
[0166] In the second stage 2304, the stylus 116 in this example is also illustrated as providing a stylus input that describes one or more lines that are “rubbed” by the stylus 116 within the borders of the image 2308. For example, the stylus 116 may make a series of zigzagging lines that begin at a location 2310 within the boundary of the image 2308 in the user interface, a single line above a threshold length may be used, and so on as previously described. The gesture module 104 may then identify these inputs (e.g., the selection and rubbing) as the carbon-copy gesture 134.
[0167] Upon identification of the carbon-copy gesture 134, the gesture module 104 may use a bitmap of the image 2308, texture of the image, and so on as fill for the lines drawn by the stylus 116. Additionally, these lines may be implemented to be drawn “through” the image 2308 such that the lines are displayed beneath the image 2308. Therefore, once the image 2308 is moved away as shown in the third stage 2306, a portion 2312 of the image 2308 that is copied to the user interface is shown, e.g., drawn on a background of the user interface. In an implementation, the overlying image may be displayed as semi-transparent state to allow a user to see both the overlying and underlying images. Thus, like the brush gesture 132, the carbon-copy gesture 134 may be used to copy portions of the image 2308 indicated by the lines drawn by the stylus 116. Likewise, the image 2308 may be used as fill for the portion 2312 in a variety of ways, such as use as a bitmap to make a “true” copy, use of one or more colors that may be user specified, and so on. Although this example implementation 2400 showed the carbon-copy gesture 134 as being implemented to “deposit” the portion 2312 onto a background of a user interface, the carbon-copy gesture 134 may also be implemented to “rub up” a portion of the image 2308, an example of which is shown in the next figure.
[0168] FIG. 24 is an illustration of an example implementation 2400 in which stages of the carbon-copy gesture 134 of FIG. 1 are shown as being input in conjunction with the computing device 102. Like FIG. 23 , the carbon-copy gesture 134 is illustrated in FIG. 24 using first, second, and third stages 2402, 2404, 2406. In the first stage 2402, an image 2408 is displayed in a user interface by the display device 108 of the computing device 102. Additionally, another object 2410 is also illustrated in the user interface, which in this instance is shown as a blank document for clarity of the discussion, although other objects are also contemplated. The object 2410 is selected in the first stage 2402 using a touch input, e.g., a finger of the user's hand 106, and moved to a new location in the user interface (as illustrated in the second stage 2404) as positioned over the image 2408, such as through use of a drag and drop gesture.
[0169] In the second stage 2404, the stylus 116 in this example is illustrated as providing a stylus input that describes one or more lines that are “rubbed” by the stylus 116 within the borders of the object 2410 and the image 2408. For example, the stylus 116 may make a series of zigzagging lines that begin at a location within the boundary of the object 2410 that is over the image 2408 in the user interface. The gesture module 104 may then identify these inputs (e.g., the selection, position of the object 2410 in relation to the image 2408, and rubbing) as the carbon-copy gesture 134.
[0170] Upon identification of the carbon-copy gesture 134, the gesture module 104 may use a bitmap of the image 2408 as fill for the lines drawn by the stylus 116. Additionally, these lines may be implemented to be “rubbed through” onto the object 2410 such that the lines are displayed as a portion 2412 within the object 2410. Therefore, once the object 2410 is moved away as shown in the third stage 2406, the portion 2412 of the image 2408 remains with the object 2410. Thus, like the brush gesture 132 in the previous example implementation 2300 of the carbon-copy gesture 134, the carbon copy gesture 134 of this example implementation 2400 may be used to copy portions of the image 2408 indicated by the lines drawn using a stylus 116. Likewise, the image 2408 may be used as fill for the portion 2412 in a variety of ways, such as use as a bitmap to make a “true” copy, use of one or more colors that may be user specified, and so on.
[0171] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the carbon-copy gesture 134, the gesture may be performed using touch or stylus inputs alone, and so on.
[0172] FIG. 25 is a flow diagram that depicts a procedure 2500 in an example implementation of a carbon-copy gesture 134 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementations 2300, 2400 of FIGS. 23 and 24 , respectively.
[0173] A first input is recognized as selecting an object displayed by a display device (block 2502). For example, the image 2308 may be tapped by a finger of the user's hand 106, a stylus 116, through use of a cursor control device, and so on. In the illustrated implementation of FIG. 23 , a finger of the user's hand 106 is illustrated as selecting the image 2408. In the illustrated implementation of FIG. 24 , the image 2408 is selected through positioning of the object 2410 “over” the image 2408 using a touch input. A variety of other examples are also contemplated.
[0174] A second input is recognized as a line that is drawn while the object is selected (block 2504). The second input, for instance, may describe a line drawn outside the bounds of the object as shown in FIG. 23 . In another instance, the second input may describe a line drawn within the bounds of the object as shown in FIG. 24 .
[0175] A carbon-copy gesture is identified from the recognized first and second inputs, the carbon-copy gesture effect to cause display of a copy of portions of the object (block 2506). Continuing with the previous instances, the carbon copy gesture 134 may work to deposit portions of the object 2308 as shown in FIG. 23 or receive portions of the object 2408 onto another object 2410 as shown in FIG. 24 . It should be noted that although a specific example was described in which the carbon-copy gesture 134 was input using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on.
[0176] Fill Gesture
[0177] FIG. 26 is an illustration of an example implementation 2600 in which stages of the fill gesture 136 of FIG. 1 are shown as being input in conjunction with the computing device 102. The fill gesture 136 is illustrated in FIG. 26 using first, second, and third stages 2602, 2604, 2606. In the first stage 2602, an image 2608 is displayed in a user interface by the display device 108 of the computing device 102, which may be performed by one or more of the ways previously or subsequently described.
[0178] In the second stage 2604, a frame 2612 is illustrated as being drawn using the stylus 116 having a rectangular shape that is defined through motion 2614 of the stylus 116. For example, the stylus 116 may be placed against the display device 108 and dragged to form the frame 2612. Although a frame 2612 having a rectangular shape is shown, a variety of different shapes may be employed as well as a variety of techniques employed to make them, e.g., circular, freehand, and so on.
[0179] The fill gesture 136 is then recognized from the inputs, an example of a result of which is shown in the third stage 2606. Upon identification of the fill gesture 136, the gesture module 104 may use the selected image 2608 to fill the frame 2612, thereby forming another image 2616. The fill may be provided in a variety of ways, such as stretched to fit the aspect ratio of the frame 2612 as illustrated in the third stage 2606, repeated in the original aspect ratio until the frame 2612 is filled, repeated in the original aspect ratio but cropped to fit, and so on. Although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the fill gesture 136, the fill gesture 136 may be performed using touch or stylus inputs alone, and so on.
[0180] FIG. 27 is a flow diagram that depicts a procedure 2700 in an example implementation of a fill gesture in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 2600 of FIG. 26 .
[0181] A first input is recognized as selecting an object displayed by a display device (block 2702). A second input is recognized as a frame drawn outside a boundary of the object, the frame recognized as being drawn while the object is selected (block 2704). The frame may be drawn in a variety of ways, such as freehand using the stylus 116 or touch input to form a self-intersecting line, selection of a preconfigured frame, through drag-and-drop to specify a size for the frame, and so on.
[0182] A fill gesture is identified from the first and second inputs, the fill gesture effective to use the object for fill in the frame (block 2706). Upon identification of the fill gesture 136, the gesture module 104 may use the object selected using the first input to fill the frame recognized from the second input. The fill may be performed in a variety of ways, such as a stretch to fill an aspect ratio of the frame 2612, repetition of the image 2608 within the frame 2612, shrinking the image 2608, use of the image 2608 as a bitmap, and so on. Further, it should be noted that although a specific example was described in which the fill gesture 136 was input using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on.
[0183] Cross-reference Gesture
[0184] FIG. 28 is an illustration of an example implementation 2800 in which stages of the cross-reference gesture 138 of FIG. 1 are shown as being input in conjunction with the computing device 102. The cross-reference gesture 138 is illustrated in FIG. 28 as showing the computing device 102 of FIG. 1 in greater detail.
[0185] The display device 108 is illustrated as displaying an image 2802. A finger of a user's hand 2804 is also illustrated as selecting the image 2802, although as previously described a variety of different techniques may be used to select the image 2802.
[0186] While the image 2802 is selected (e.g., in a selected state), a stylus 116 is illustrated as providing a stylus input involving one or more lines 2806, which in this instance is illustrated as the word “Eleanor.” The gesture module 104 may recognize the cross-reference gesture 138 from these inputs to provide a variety of functionality.
[0187] For example, the gesture module 104 may use the cross-reference gesture 138 to link the lines 2806 with the image 2802. Therefore, an operation that causes the image 2802 to be displayed may also cause the lines 2806 to be displayed in conjunction. In another example, the linking configures the lines 2806 to be selectable to navigate to the image 2802. For instance, selection of the lines 2806 may cause the image 2802 to be displayed, a portion of a document that contains the image 2802 (e.g., to jump to a page in the document that contains the image 2802), and so on. Likewise the cross-reference gesture may be used to group the objects, such that the objects move together during drag operations, or maintain the relative spatial relationships between image and annotations during document-reflow or other automatic or manual layout changes.
[0188] In a further example, the gesture module 104 may employ an ink analysis engine 2808 to identify “what is written” by the lines 2806, e.g., convert the lines to text. For instance, the ink analysis engine 2808 may be used to translate the lines 2806 to text that spells “Eleanor.” Additionally, the ink analysis engine may be used to group separate lines to be converted to text, e.g., lines that form separate characters may be grouped together for translation. In an implementation, the one or more lines may provide a hint for parsing by the ink analysis engine 2808, such as a special symbol to indicate that the lines are to be converted to text.
[0189] Accordingly, the gesture module 104 through performance of the cross-reference gesture 138 may use this text in a variety of different ways. In an implementation, the text is used as a caption for the selected image 2802 and/or other metadata that may be associated with the image, such as to identify one or more persons in the image 2802, signify a location shown in the image 2802, and so on. This metadata (e.g., the text) that is linked to the image 2802 may be accessed and leveraged for search or other tasks, an example of which is shown in the following figure.
[0190] FIG. 29 is an illustration of an example implementation 2900 in which stages of a cross-reference gesture 138 are shown to access metadata associated with the image 2802 using the fill gesture 136 of FIG. 28 . The gesture is illustrated in FIG. 29 using first, second, and third stages 2902, 2904, 2906. In the first stage 2902, the image 2802 of FIG. 28 is displayed in a user interface by the display device 108 of the computing device 102. The image 2802 optionally includes an indication 2908 that additional metadata is available for viewing that is associated with the image 2802.
[0191] In the second stage 2904, a finger of the user's hand 2804 is illustrated as selecting the indication 2908 and indicating movement 2910 similar to “flipping” the image 2802. In an implementation, upon identification of these inputs the gesture module 104 may provide an animation to give the appearance that the image 2802 is being “flipped over.” Alternatively, metadata may be revealed through a context menu command associated with the item, e.g. a “Properties . . . ” command.
[0192] In the third stage 2906, a result of the flip gesture is shown. In this example, a “back” 2912 of the image 2802 is displayed. The back 2912 includes a display of metadata associated with the image 2802, such as when the image 2802 was taken, a type for the image 2802, and the metadata input using the cross-reference gesture 138 of FIG. 28 , which is “Eleanor” in this example. The back 2912 of the image 2802 also includes an indication 2914 that the back 2912 may be “flipped back” to return to the image 2802 shown in the first stage 2902. Although “flipping” of the image 2802 using a flip gesture was described in relation to FIG. 29 , it should be readily apparent that a variety of different techniques may be used to access the metadata.
[0193] As previously described, although a specific implementation has been described using touch and/or stylus inputs in relation to FIGS. 28 and 29 , it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched, the gesture may be performed using touch or stylus inputs alone, and so on.
[0194] FIG. 30 is a flow diagram that depicts a procedure 3000 in an example implementation of the cross-reference gesture 138 of FIG. 1 in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2, and the example implementations 2800, 2900 of FIGS. 28 and 29 , respectively.
[0195] A first input is recognized as selecting an object displayed by a display device (block 3002). For example, the image 2802 may be tapped by a finger of the user's hand 2804, a stylus 116, through use of a cursor control device, and so on. In the illustrated implementation, a finger of the user's hand 2804 is illustrated as selecting and holding the image 2802.
[0196] A second input is recognized as one or more lines drawn outside the bounds of the object, the one or more lines recognized as being drawn while the object is selected (block 3004). For example, the gesture module 104 may recognizes the lines 2806 as stylus inputs that were drawn by the stylus 116 while the image 2802 was selected. Additionally, it should be realized that the lines 2806 may be continuous and/or made up of segments without departing from the spirit and scope thereof.
[0197] A cross-reference gesture is identified from the recognized first and second inputs, the cross-reference gesture effective to cause the one or more lines to be linked to the object (block 3006). As previously described, the lines 2806 may be linked in a variety of ways. For example, the gesture module 104 may employ an ink analysis engine 2808 to translate the lines to text. The text may then be saved in conjunction with the image 2802, used as a link to the image 2802, displayed as a caption for the image 2802, and so on.
[0198] Again, it should be noted that although a specific example was described in which the cross-reference gesture 138 was input using touch and stylus inputs, those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on.
[0199] Link Gesture
[0200] FIG. 31 is an illustration of an example implementation 3100 in which stages of the link gesture 140 of FIG. 1 are shown as being input in conjunction with the computing device 102. The link gesture 140 is illustrated in FIG. 31 using first, second, and third stages 3102, 3104, 3106. In the first stage 3102, the display device 108 of the computer 102 is illustrated as displaying first, second, third, and fourth images 3108, 3110, 3112, 3114.
[0201] In the second stage 3104, the third image 3112 is illustrated as being selected using a touch input, e.g., through use of a finger of the user's hand 106, although other implementations are also contemplated. A stylus 116 is illustrated as providing a stylus input that describes movement 3118 that begins within a boundary of the first image 3108, through the second image 3110, and ends at the third image 3112. For instance, the movement 3116 may involve placing the stylus 116 within the display of the first image 3108 and passing through the second image 3110 to the third image 3112, where the stylus 116 is lifted away from the display device 108. From these inputs, the gesture module 104 may recognize the link gesture 140.
[0202] The link gesture 140 may be used to provide a variety of different functionality. For example, the gesture module 104 may form links to be included with the third image 3112, an example of which is shown in the third stage 3106. In this stage, a back 3118 of the image 3112 is illustrated that includes a display of metadata associated with the image 3112, such as the title and type of the image. The metadata also includes links to the first and second images 3108, 3110, which are illustrated as the titles taken from the images of “Mom,” and “Child.” The links are selectable to navigate to the respective images, e.g., the link “Mom” is selectable to navigate to the first image 3108 and so on. Thus, the links may be formed using a simple gesture that does not involve manual input of text by a user. A variety of other functionality may also be made available via the link gesture 140, further discussion of which may be found in relation to FIGS. 32-33 .
[0203] As previously described, although a specific implementation has been described using touch and stylus inputs, it should be readily apparent that a variety of other implementations are also contemplated. For example, the touch and stylus inputs may be switched to perform the link gesture 140, the gesture may be performed using touch or stylus inputs alone, and so on. Additionally, the linking may be performed in combinations with a variety of different inputs. For instance, a path may be drawn around multiple objects, e.g., using a stylus to circle a collection, to select the objects within the path. An icon (e.g., a group icon) may then be selected to link and/or group the objects together. A variety of other instances are also contemplated.
[0204] FIG. 32 is a flow diagram that depicts a procedure 3200 in an example implementation of a link gesture in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 3100 of FIG. 31 .
[0205] A first input is recognized as selecting an object displayed by a display device (block 3202), such as through selection using one or more touch inputs, a stylus input, and so on. A second input is recognized as a line drawn from a second object displayed by the display device to the first object, the line recognized as being drawn while the first object is selected (block 3204). For example, the line may be recognized as movement 3116 of the stylus 116 from within a boundary of a second object (e.g., the second image 3112) to within a boundary of the object that is selected by the first input, e.g., the finger of the user's hand 106 in the second stage 3104 of FIG. 31 . Intervening image 3110, or other objects passed over by the stylus, may either be considered as additional images that should also be linked together into a common set, or may be ignored as intermediary objects that are not the targets of the link gesture. The dynamics of the link gesture (e.g. inflection points, momentary pauses while dragging, velocity thresholds, and so on) may be used to decide between these cases, if desired.
[0206] A link gesture is identified from the recognized first and second inputs, the link gesture effective to create a link between the first and second objects (block 3206). The gesture module 104, for instance, may identify the link gesture 140 and form a link that involves the first object selected by the first input and the second object that was involved with the first object by the second input. The link may employ a variety of functionality, such as a hyperlink to navigate between the first and second objects, store the link (e.g., with the first or second objects) for later navigation, provide an indication of the existence of the link (e.g., through underlining of the first or second object), and so on. A variety of other links are also contemplated, an example of which may be found in relation to the following figure.
[0207] FIG. 33 is an illustration of another example implementation 3300 in which stages of the link gesture 140 of FIG. 1 are shown as being input in conjunction with the computing device 102. The computing device 102 is illustrated as outputting a user interface by a display device 108. The user interface includes a listing of playlists and a listing of songs.
[0208] A finger of the user's hand 3302 is illustrated as selecting a playlist “About Last Night” and the stylus 116 is illustrated as moved from the song “My Way” to the selected playlist. In this way, metadata associated with the second object (e.g., the song) is associated with the selected object (e.g., the playlist), which in this case causes the song to be added to the playlist. Thus, the gesture module 104 may identify the link gesture 140 from the inputs and cause a corresponding operation to be performed. Although formation of a playlist is described in this example, a variety of different metadata may be associated using the link gesture 140, such as to classify movies by type, rate objects, and so on.
[0209] FIG. 34 is a flow diagram that depicts a procedure 3400 in an example implementation of a link gesture in accordance with one or more embodiments. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 3300 of FIG. 33 .
[0210] A first input is recognized as selecting an object displayed by a display device (block 3402). A second input is recognized as a line drawn from a second object displayed by the display device to the first object, the line recognized as being drawn while the first object is selected (block 3404). For example, the line may be recognized as being drawn from a list of metadata to a song, a listing of places to an image, and so on.
[0211] A link gesture is identified from the recognized first and second inputs, the link gesture effect to associate metadata represented by the second object with the first object (block 3406). Continuing with the previous example, the link gesture 140 may be effective to cause the metadata to be stored as a part of the first object, e.g., so that the playlist includes the song, the image includes a name of a person, and so on.
[0212] Yet again, it should be noted that although a specific example was described in which the link gesture 140 was input using touch and stylus inputs in FIGS. 31-34 , those inputs may be switched, a single input type (e.g., touch or stylus) may be used to provide the inputs, and so on.
[0213] Contextual Spatial Multiplexing
[0214] FIG. 35 depicts an example implementation 3500 showing techniques for contextual spatial multiplexing. In instances of the previous example implementations, different types of inputs (e.g., stylus inputs versus touch inputs) were used to specify different gestures. For example, the bimodal input module 114 may be used to distinguish between the types of inputs to identify gestures, such as one or more of the gestures previously described in relation to FIG. 1 and subsequent sections.
[0215] These techniques may also be leveraged for contextual spatial multiplexing. Contextual spatial multiplexing describes techniques in which specific areas of a user interface take on different functions for stylus or touch inputs. For example, the finger of the user's hand 3502 is illustrated as selecting the image 3504 at an initial point of the user interface. Additionally, the stylus 116 is illustrated as writing the word “Eleanor” 3506 which also began at the initial point in the user interface. Thus, the bimodal input module 114 may distinguish between the types of inputs (e.g., touch versus stylus inputs) to provide different functionality at the same point in the user interface.
[0216] In an implementation, primitives of touch (e.g., tap, hold, two-finger hold, drag, cross, pinch, and other hand or finger postures) and stylus (e.g., tap, hold, drag-off, drag-into, cross, stroke) can be composed by the bimodal input module 114 to create a larger possible space of intuitive and semantically rich gestures than either stylus or touch alone. For instance, direct touch mode switching may integrate mode activation, selection of object, and phrasing of subtasks into a single object-specific mode, e.g., to define a gesture as described above.
[0217] Additionally, the techniques may be composed, such as to arrive at different gestures. For example, selecting an object along with the phrasing of subtasks together afford composing of multiple tools and effects together. As previously described for the edge gesture 128 of FIGS. 14-18 , for instance, drawing and cutting using an edge of an object were described. In other instances, a priority may be assigned to the gestures by the gesture module to avoid potential ambiguities, e.g. cut takes precedence on edge gesture 128 that overlaps an item, rather than the brush gesture 132. Thus, in these implementations the stylus writes (or cuts) and touch manipulates, while the combination of stylus plus touch yields new techniques. But in some contexts other divisions between stylus and touch are possible, and indeed consistent with user expectations.
[0218] For example, the user interface displayed by the display device 108 of the computing device 102 may react differently depending on the area of the object that is engaged, and the context of surrounding objects and the page (background). For example, ink notations on the user interface may be ignored for some touch inputs (e.g. selection, direct manipulation) to make it easier to perform two-finger zooming on the page, as well as to avoid accidental disruption of stylus inputs, such as ink strokes. The size of objects also may be considered, e.g. objects that are over a threshold size may be directly manipulated via touch inputs. A variety of other implementations are also contemplated, further discussion of which may be found in relation to the following figure.
[0219] FIG. 36 is a flow diagram that depicts a procedure 3600 in an example implementation in which identification of whether an input is a stylus or touch input is used to identify an operation to be performed in conjunction with a user interface. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 3500 of FIG. 35 .
[0220] A determination is made as to whether an input is a touch input or a stylus input, the input effective to indicate interaction with a user interface displayed by a display device (block 3602). For example, the gesture module 104 may detect the input using a variety of functionality, such as a touchscreen, cameras (e.g., cameras included along with a plurality of pixels of the display device), and so on. The gesture module 104 may then make a determination as to whether the input is a touch input (e.g., entered using one or more fingers of a user's hand) or a stylus input (e.g., entered using a pointed input device). This determination may be performed in a variety of ways, such as by detecting the stylus 116 using one or more sensors, based on an amount of the display device 108 that is contacted using the stylus versus touch, use of image recognition, and so on.
[0221] An operation is identified to be performed by a computing device based at least in part on the determination such that the operation that is identified differs based on whether the determined input is the touch input or the stylus input (block 3604). The identified operation is caused to be performed by the computing device (block 3606). As shown in FIG. 35 , for example, the stylus input from the stylus 116 is used the write whereas the touch input from the finger of the user's hand 3502 may be used to select and move the image 3504 from the same point within the user interface. A variety of other examples are also contemplated, such as based on configuration of an object at which the interaction is directed. For instance, the gesture module 104 may be configured to make distinctions on whether the object is an image, represents a song, pertains to a document, size of the object, and so on to enable different operations to be performed based on the underlying and/or nearby objects. As another example, dragging a pen from a color pot may leave a pen stroke, whereas dragging a finger from a color pot may leave a smudge or finger paint stroke. Selecting a color pot with the pen, and then stroking with a finger; or conversely selecting a color pot with a finger, and then stroking the pen, may also imply different commands or parameters to commands (e.g. brush style, opacity, and so forth). Further discussion of such distinctions may be found in relation to the following figure.
[0222] FIG. 37 is a flow diagram that depicts another procedure 3700 in an example implementation in which identification of whether an input is a stylus or touch input is used to identify an operation to be performed in conjunction with a user interface. Aspects of the procedure may be implemented in hardware, firmware, software, or a combination thereof. The procedure is shown as a set of blocks in this example that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the environment 100 of FIG. 1 , the system 200 of FIG. 2 , and the example implementation 3500 of FIG. 35 .
[0223] A determination is made that an input is a touch input or a stylus input, the input effective to indicate interaction with a user interface displayed by a display device (block 3702). This determination may be performed in a variety of ways as previously and subsequently described. Responsive to the determination that the input is the touch input, a first operation is caused to be performed in conjunction with the user interface (block 3704). For example, the operation may involve moving an underlying object, e.g., the image 3504 of FIG. 35 .
[0224] Responsive to the determination that the input is the stylus input, a second operation is caused to be performed in conjunction with the user interface that is different than the first operation (block 3706). Continuing with the previous example, the stylus input provided by the stylus 116 may be used to write on the image 3504 as opposed to moving it. Additionally, it should be readily apparent that a variety of other considerations may also be employed by the gesture module 104, such as proximity to other objects, “where” in the user interface the interaction involving the input is to occur, and so on.
[0225] Example Device
[0226] FIG. 38 illustrates various components of an example device 3800 that can be implemented as any type of portable and/or computer device as described with reference to FIGS. 1 and 2 to implement embodiments of the gesture techniques described herein. Device 3800 includes communication devices 3802 that enable wired and/or wireless communication of device data 3804 (e.g., received data, data that is being received, data scheduled for broadcast, data packets of the data, etc.). The device data 3804 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 3800 can include any type of audio, video, and/or image data. Device 3800 includes one or more data inputs 3806 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.
[0227] Device 3800 also includes communication interfaces 3808 that can be implemented as any one or more o\f 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 3808 provide a connection and/or communication links between device 3800 and a communication network by which other electronic, computing, and communication devices communicate data with device 3800.
[0228] Device 3800 includes one or more processors 3810 (e.g., any of microprocessors, controllers, and the like) which process various computer-executable instructions to control the operation of device 3800 and to implement embodiments of a touch pull-in gesture. Alternatively or in addition, device 3800 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 3812. Although not shown, device 3800 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.
[0229] Device 3800 also includes computer-readable media 3814, 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 3800 can also include a mass storage media device 3816.
[0230] Computer-readable media 3814 provides data storage mechanisms to store the device data 3804, as well as various device applications 3818 and any other types of information and/or data related to operational aspects of device 3800. For example, an operating system 3820 can be maintained as a computer application with the computer-readable media 3814 and executed on processors 3810. The device applications 3818 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 3818 also include any system components or modules to implement embodiments of the gesture techniques described herein. In this example, the device applications 3818 include an interface application 3822 and a gesture-capture driver 3824 that are shown as software modules and/or computer applications. The gesture-capture driver 3824 is representative of software that is used to provide an interface with a device configured to capture a gesture, such as a touchscreen, track pad, camera, and so on. Alternatively or in addition, the interface application 3822 and the gesture-capture driver 3824 can be implemented as hardware, software, firmware, or any combination thereof. Additionally, the gesture-capture driver 3824 may be configured to support multiple input devices, such as separate devices to capture touch and stylus inputs, respectively. For example, the device may be configured to include dual display devices, in which one of the display device is configured to capture touch inputs while the other stylus inputs.
[0231] Device 3800 also includes an audio and/or video input-output system 3826 that provides audio data to an audio system 3828 and/or provides video data to a display system 3830. The audio system 3828 and/or the display system 3830 can include any devices that process, display, and/or otherwise render audio, video, and image data. Video signals and audio signals can be communicated from device 3800 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 3828 and/or the display system 3830 are implemented as external components to device 3800. Alternatively, the audio system 3828 and/or the display system 3830 are implemented as integrated components of example device 3800.
[0232] Conclusion
[0233] Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed invention.
Claims
What is claimed is:
1. A method comprising:
recognizing a first input, by a computing device, as selecting an object displayed by a display device using a plurality of touch inputs;
recognizing a second input, by the computing device, as movement of a stylus along an edge of the object, the movement recognized as occurring while the object is selected; and
identifying a gesture, by the computing device, from the recognized first and second inputs, the gesture effective to:
cause display of a line by the display device as drawn proximal to the edge and as following movement described by the second input that follows the edge of the object and continues on past another edge of the object; and
indicate that the object as selected using partial transparency.
2. A method as described in claim 1, wherein the first input is recognized as selecting two points of the object.
3. A method as described in claim 1, wherein:
the edge of the object is displayed as appearing over a second object and a background; and
the line appears as being drawn over the second object and the background.
4. A method as described in claim 1, wherein the first input and the second input are detected using a camera.
5. A method as described in claim 1, wherein the first input is further recognized as movement of the object within an image displayed by the display device before the recognizing of the second input.
6. A method as described in claim 1, wherein the gesture is further effective to cause display of the line to continue to follow subsequent movement of the stylus that has passed the edge of the object.
7. A method comprising:
recognizing a first input as selecting an object displayed by a display device using one or more touch inputs;
recognizing a second input as movement of a stylus along an edge of the object, the movement recognized as occurring while the object is selected; and
identifying a gesture from the recognized first and second inputs, the gesture effective to:
indicate selection of the object using partial transparency; and
cause display of a second object that is displayed beneath the object as being cut proximal to the edge and as following movement described by the second input, the cut continuing to follow subsequent movement of the stylus that has passed the edge of the object.
8. A method as described in claim 5, wherein the first input is further recognized as movement of the object within an image displayed by the display device to be placed over a second object, the movement of the object recognized as occurring before the recognizing of the second input.
9. A method as described in claim 5, wherein the first input is recognized as selecting two points of the object.
10. A computing device comprising one or more modules implemented at least partially in hardware, the one or more modules configured to cause operations to be performed comprising:
recognizing a first input as selecting an object displayed by a display device of the computing device using a plurality of touch inputs;
recognizing a stylus input as describing movement of a stylus along an edge of the object displayed by the display device, the movement recognized as occurring while the object is selected; and
identifying a gesture from the recognized first input and the stylus input, the gesture effective to:
indicate selection of the object using partial transparency; and
cause the edge of the selected object to act as a template such that a line drawn proximal to the edge as indicated by the stylus input is displayed by the display device as following the edge of the object and continues to follow subsequent movement of a source of the second input that has passed the edge of the object.
Patent Citations (161)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4843538(A) | 1989-06-01 | Lane et al. | Applicant |
| US5237647(A) | 1993-08-01 | Roberts et al. | Applicant |
| US5351995(A) | 1994-10-01 | Booker | Applicant |
| US5463725(A) | 1995-10-01 | Henckel et al. | Applicant |
| US5491783(A) | 1996-02-01 | Douglas et al. | Applicant |
| US5497776(A) | 1996-03-01 | Yamazaki et al. | Applicant |
| US5511148(A) | 1996-04-01 | Wellner | Applicant |
| US5555369(A) | 1996-09-01 | Menendez et al. | Applicant |
| US5596697(A) | 1997-01-01 | Foster et al. | Applicant |
| US5661773(A) | 1997-08-01 | Swerdloff et al. | Applicant |
| US5664128(A) | 1997-09-01 | Bauer | Applicant |
| US5731813(A) | 1998-03-01 | O'Rourke et al. | Applicant |
| US5817019(A) | 1998-10-01 | Kawashima | Applicant |
| US5838889(A) | 1998-11-01 | Booker | Applicant |
| US5898434(A) | 1999-04-01 | Small et al. | Applicant |
| US5969720(A) | 1999-10-01 | Lisle et al. | Applicant |
| US6037937(A) | 2000-03-01 | Beaton et al. | Applicant |
| US6061061(A) | 2000-05-01 | Conrad et al. | Applicant |
| US6072476(A) | 2000-06-01 | Harada et al. | Applicant |
| US6097392(A) | 2000-08-01 | Leyerle | Examiner |
| US6115724(A) | 2000-09-01 | Booker | Applicant |
| US6239798(B1) | 2001-05-01 | Ludolph et al. | Applicant |
| US6310610(B1) | 2001-10-01 | Beaton et al. | Applicant |
| US6340979(B1) | 2002-01-01 | Beaton et al. | Applicant |
| US6507352(B1) | 2003-01-01 | Cohen et al. | Applicant |
| US6525749(B1) | 2003-02-01 | Moran et al. | Examiner |
| US6545669(B1) | 2003-04-01 | Kinawi et al. | Applicant |
| US6859909(B1) | 2005-02-01 | Lerner et al. | Applicant |
| US6920619(B1) | 2005-07-01 | Milekic | Applicant |
| US7454717(B2) | 2008-11-01 | Hinckley et al. | Applicant |
| US7506269(B2) | 2009-03-01 | Lang | Applicant |
| US7532196(B2) | 2009-05-01 | Hinckley | Applicant |
| US7636071(B2) | 2009-12-01 | O'Gorman | Applicant |
| US7656393(B2) | 2010-02-01 | King et al. | Applicant |
| US7821780(B2) | 2010-10-01 | Choy | Applicant |
| USD631043(S) | 2011-01-01 | Kell | Applicant |
| US7956847(B2) | 2011-06-01 | Christie | Applicant |
| US8102858(B1) | 2012-01-01 | Rahim et al. | Examiner |
| US2001/0012000(A1) | 2001-08-01 | Eberhard | Applicant |
| US2001/0047263(A1) | 2001-11-01 | Smith et al. | Applicant |
| US2002/0060701(A1) | 2002-05-01 | Naughton et al. | Applicant |
| US2002/0097229(A1) | 2002-07-01 | Rose et al. | Applicant |
| US2002/0101457(A1) | 2002-08-01 | Lang | Applicant |
| US2002/0116421(A1) | 2002-08-01 | Fox et al. | Applicant |
| US2003/0179541(A1) | 2003-09-01 | Sullivan | Applicant |
| US2003/0231219(A1) | 2003-12-01 | Leung | Examiner |
| US2004/0236774(A1) | 2004-11-01 | Baird et al. | Applicant |
| US2005/0012723(A1) | 2005-01-01 | Pallakoff | Applicant |
| US2005/0101864(A1) | 2005-05-01 | Zheng et al. | Applicant |
| US2005/0129314(A1) | 2005-06-01 | Chen | Applicant |
| US2005/0198592(A1) | 2005-09-01 | Keely et al. | Applicant |
| US2006/0001650(A1) | 2006-01-01 | Robbins et al. | Examiner |
| US2006/0026521(A1) | 2006-02-01 | Hotelling et al. | Applicant |
| US2006/0026535(A1) | 2006-02-01 | Hotelling et al. | Applicant |
| US2006/0026536(A1) | 2006-02-01 | Hotelling et al. | Applicant |
| US2006/0031786(A1) | 2006-02-01 | Hillis et al. | Applicant |
| US2006/0092177(A1) | 2006-05-01 | Blasko | Applicant |
| US2006/0093219(A1) | 2006-05-01 | Gounares et al. | Applicant |
| US2006/0101354(A1) | 2006-05-01 | Hashimoto et al. | Applicant |
| US2006/0161870(A1) | 2006-07-01 | Hotelling et al. | Applicant |
| US2006/0197750(A1) | 2006-09-01 | Kerr et al. | Applicant |
| US2006/0238517(A1) | 2006-10-01 | King et al. | Applicant |
| US2006/0262188(A1) | 2006-11-01 | Elyada et al. | Applicant |
| US2007/0097096(A1) | 2007-05-01 | Rosenberg | Applicant |
| US2007/0106939(A1) | 2007-05-01 | Qassoudi | Applicant |
| US2007/0120762(A1) | 2007-05-01 | O'Gorman | Applicant |
| US2007/0168890(A1) | 2007-07-01 | Zhao et al. | Applicant |
| US2008/0005703(A1) | 2008-01-01 | Radivojevic et al. | Applicant |
| US2008/0036743(A1) | 2008-02-01 | Westerman et al. | Applicant |
| US2008/0040692(A1) | 2008-02-01 | Sunday et al. | Applicant |
| US2008/0065720(A1) | 2008-03-01 | Brodersen et al. | Applicant |
| US2008/0082903(A1) | 2008-04-01 | McCurdy et al. | Applicant |
| US2008/0164982(A1) | 2008-07-01 | Andrews et al. | Applicant |
| US2008/0165255(A1) | 2008-07-01 | Christie et al. | Applicant |
| US2008/0168396(A1) | 2008-07-01 | Matas et al. | Applicant |
| US2008/0211766(A1) | 2008-09-01 | Westerman et al. | Applicant |
| US2008/0211778(A1) | 2008-09-01 | Ording et al. | Applicant |
| US2008/0249682(A1) | 2008-10-01 | Wisniewski et al. | Applicant |
| US2008/0278455(A1) | 2008-11-01 | Atkins et al. | Applicant |
| US2009/0033632(A1) | 2009-02-01 | Szolyga et al. | Applicant |
| US2009/0059730(A1) | 2009-03-01 | Lyons et al. | Applicant |
| US2009/0077501(A1) | 2009-03-01 | Partridge et al. | Applicant |
| US2009/0079699(A1) | 2009-03-01 | Sun | Applicant |
| US2009/0094562(A1) | 2009-04-01 | Jeong et al. | Applicant |
| US2009/0138830(A1) | 2009-05-01 | Borgaonkar et al. | Examiner |
| US2009/0143141(A1) | 2009-06-01 | Wells et al. | Applicant |
| US2009/0167696(A1) | 2009-07-01 | Griffin | Applicant |
| US2009/0193366(A1) | 2009-07-01 | Davidson | Applicant |
| US2009/0249236(A1) | 2009-10-01 | Westerman et al. | Applicant |
| US2009/0251432(A1) | 2009-10-01 | Wang et al. | Applicant |
| US2009/0284478(A1) | 2009-11-01 | De la Torre Baltierra et al. | Applicant |
| US2009/0295753(A1) | 2009-12-01 | King et al. | Applicant |
| US2009/0309846(A1) | 2009-12-01 | Trachtenberg et al. | Applicant |
| US2009/0327975(A1) | 2009-12-01 | Stedman | Applicant |
| US2010/0013768(A1) | 2010-01-01 | Leung | Applicant |
| US2010/0016049(A1) | 2010-01-01 | Shirakawa et al. | Applicant |
| US2010/0020025(A1) | 2010-01-01 | Lemort et al. | Applicant |
| US2010/0045705(A1) | 2010-02-01 | Vertegaal et al. | Applicant |
| US2010/0050076(A1) | 2010-02-01 | Roth | Applicant |
| US2010/0081475(A1) | 2010-04-01 | Chiang et al. | Applicant |
| US2010/0083190(A1) | 2010-04-01 | Roberts et al. | Examiner |
| US2010/0088641(A1) | 2010-04-01 | Choi | Applicant |
| US2010/0090971(A1) | 2010-04-01 | Choi et al. | Applicant |
| US2010/0097338(A1) | 2010-04-01 | Miyashita et al. | Applicant |
| US2010/0115455(A1) | 2010-05-01 | Kim | Applicant |
| US2010/0134415(A1) | 2010-06-01 | Iwase et al. | Applicant |
| US2010/0188371(A1) | 2010-07-01 | Lowles et al. | Applicant |
| US2010/0201634(A1) | 2010-08-01 | Coddington | Examiner |
| US2010/0213040(A1) | 2010-08-01 | Yeh et al. | Examiner |
| US2010/0217428(A1) | 2010-08-01 | Strong et al. | Applicant |
| US2010/0241973(A1) | 2010-09-01 | Whiddett | Applicant |
| US2010/0251189(A1) | 2010-09-01 | Jaeger | Examiner |
| US2010/0262928(A1) | 2010-10-01 | Abbott | Applicant |
| US2010/0313124(A1) | 2010-12-01 | Privault et al. | Applicant |
| US2011/0050594(A1) | 2011-03-01 | Kim et al. | Applicant |
| US2011/0055729(A1) | 2011-03-01 | Mason et al. | Applicant |
| US2011/0055753(A1) | 2011-03-01 | Horodezky et al. | Applicant |
| US2011/0107220(A1) | 2011-05-01 | Perlman | Applicant |
| US2011/0115735(A1) | 2011-05-01 | Lev et al. | Applicant |
| US2011/0126094(A1) | 2011-05-01 | Horodezky et al. | Examiner |
| US2011/0143769(A1) | 2011-06-01 | Jones et al. | Applicant |
| US2011/0167336(A1) | 2011-07-01 | Aitken et al. | Applicant |
| US2011/0181524(A1) | 2011-07-01 | Hinckley | Applicant |
| US2011/0185299(A1) | 2011-07-01 | Hinckley | Applicant |
| US2011/0185300(A1) | 2011-07-01 | Hinckley | Applicant |
| US2011/0185320(A1) | 2011-07-01 | Hinckley | Applicant |
| US2011/0191704(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0191718(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0191719(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0199386(A1) | 2011-08-01 | Dharwada et al. | Applicant |
| US2011/0205163(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209039(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209057(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209058(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209088(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209089(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209093(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209097(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209098(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209099(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209100(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209101(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209102(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209103(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0209104(A1) | 2011-08-01 | Hinckley | Applicant |
| US2011/0231796(A1) | 2011-09-01 | Vigil | Applicant |
| US2011/0291964(A1) | 2011-12-01 | Chambers et al. | Applicant |
| US2012/0084705(A1) | 2012-04-01 | Lee et al. | Applicant |
| US2012/0096411(A1) | 2012-04-01 | Nash | Applicant |
| JP6282368 | 1994-10-01 | Applicant | |
| JP7281810 | 1995-10-01 | Applicant | |
| JP2001265523 | 2001-09-01 | Applicant | |
| JP2001290585 | 2001-10-01 | Applicant | |
| JP2008305087 | 2008-12-01 | Applicant | |
| JP2010250465 | 2010-11-01 | Applicant | |
| KR20090013927 | 2009-02-01 | Applicant | |
| KR1020090088501 | 2009-08-01 | Applicant | |
| KR20090106755 | 2009-10-01 | Applicant | |
| WO-9928812 | 1999-01-01 | Applicant | |
| WO-2011106467 | 2011-09-01 | Applicant | |
| WO-2011106468 | 2011-09-01 | Applicant |
Non-Patent Literature (56)
- “Final Office Action”, U.S. Appl. No. 12/709,245, (Jan. 6, 2012), 13 pages.Applicant
- “iQuery & Css Example—Dropdown Menu”, DesignReviver, Retrived from: <http://designreviver.com/tutorials/jquery-css-example-dropdown-menu/> on Nov. 22, 2011,(Oct. 7, 2008), 30 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/700,460, (Jan. 13, 2012), 21 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/709,245, (Nov. 30, 2011), 11 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/709,301, (Nov. 28, 2011), 9 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/709,348, (Dec. 7, 2011), 12 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/709,376, (Jan. 23, 2012), 14 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,081, (Dec. 23, 2011), 18 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,113, (Dec. 22, 2011), 20 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,127, (Dec. 27, 2011), 22 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,130, (Jan. 23, 2012), 7 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/025131, (Oct. 31, 2011), 10 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/025974, (Oct. 26, 2011), 8 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/025973, (Oct. 27, 2011), 13 pages.Applicant
- Vigil, Jose M., “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.Applicant
- Brandl, Peter et al., “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.Applicant
- Gross, Mark D., “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.Applicant
- Minsky, Margaret R., “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. 194-203.Applicant
- Olwal, Alex et al., “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.Applicant
- Yee, Ka-Ping “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.Applicant
- Elliott, Matthew “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.Applicant
- 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.Applicant
- Emigh, Jacqueline “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.Applicant
- Roth, Volker et al., “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.Applicant
- Pierce, Jeffrey S., et al., “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.Applicant
- Daniels, Martyn “Brave New World”, Retrieved from: <http://bookseller-association.blogspot.com/2009—03—01—archive.html> on Nov. 10, 2009, (Mar. 2009),54 pages.Applicant
- Hinckley, Ken et al., “Codex: A Dual Screen Tablet Computer”, Conference on Human Factors in Computing Systems, Available at <http://research.microsoft.com/en-us/um/people/kenh/codex-chi-2009-with-authors.pdf>,(2009),10 pages.Applicant
- “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.Applicant
- “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.Applicant
- Krazit, Tom “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.Applicant
- “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.Applicant
- Hinckley, Ken et al., “Stitching: Pen Gestures that Span Multiple Displays”, CHI 2004, Available at <http://www.cs.cornell.edu/˜francois/Papers/2004-Hinckley-AV104-Stitching.>,(2004),pp. 1-8.Applicant
- “Final Office Action”, U.S. Appl. No. 12/709,301, (Mar. 1, 2012), 11 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/709,348, (Feb. 17, 2012), 13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/700,510, (Feb. 7, 2012), 20 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/709,245, (Mar. 21, 2012), 14 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,053, (Feb. 3, 2012) ,8 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,133, (Jan. 31, 2012), 7 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/025132, (Oct. 26, 2011), 10 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/025575, (Sep. 30, 2011), 14 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/025971, (Oct. 31, 2011), 15 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US/2011025972, (Sep. 30, 2011), 14 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/020412, (Aug. 31, 2011), 9 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/020410, (Sep. 27, 2011), 9 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/020417, (Oct. 20, 2011), 8 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/709,376, (Mar. 30, 2012), 16 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/713,081, (May 9, 2012), 19 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/713,113, (Jun. 4, 2012), 18 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/713,127, (Jun. 6, 2012), 18 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/695,937, (Apr. 25, 2012), 14 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/709,204, (May 10, 2012), 20 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/709,282, (Apr. 12, 2012), 9 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,096, (Jun. 6, 2012), 9 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,110, (Jun. 21, 2012), 21 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/713,118, (Jun. 8, 2012), 7 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/695,959, (Apr. 17, 2012), 13 pages.Applicant