Patent Grant
10732997
This relates generally to user interface processing, including but not limited to, apparatuses and methods for recognizing gesture inputs.
An electronic device typically includes a user interface that may be used to interact with the computing device. The user interface may include a display and/or input devices such as a keyboard, mice, and touch-sensitive surfaces for interacting with various aspects of the user interface. In some devices with a touch-sensitive surface as an input device, a first set of touch-based gestures (e.g., two or more of: tap, double tap, horizontal swipe, vertical swipe, pinch, depinch, two finger swipe) are recognized as proper inputs in a particular context (e.g., in a particular mode of a first application), and other, different sets of touch-based gestures are recognized as proper inputs in other contexts (e.g., different applications and/or different modes or contexts within the first application). As a result, the software and logic required for recognizing and responding to touch-based gestures can become complex, and can require revision each time an application is updated or a new application is added to the computing device. These and similar issues may arise in user interfaces that utilize input sources other than touch-based gestures.
Thus, it would be desirable to have a comprehensive framework or mechanism for recognizing touch-based gestures and events, as well as gestures and events from other input sources, that is easily adaptable to virtually all contexts or modes of all application programs on a computing device, and that requires little or no revision when an application is updated or a new application is added to the computing device.
To address the aforementioned drawbacks, in accordance with some embodiments, a method is performed at an electronic device having one or more event sensors and configured to execute a software application that includes a plurality of views and an application state of the software application. The method includes displaying one or more views of the plurality of views. A respective view of the one or more displayed views includes one or more gesture recognizers, and a respective gesture recognizer has a corresponding delegate. The method includes detecting one or more events, and processing a respective event of the one or more events using the respective gesture recognizer. The processing of the respective event includes: processing the respective event at the respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, executing the respective gesture recognizer's corresponding delegate to determine one or more values in accordance with the application state, and conditionally sending information corresponding to the respective event to the software application in accordance with an outcome of the processing of the respective event by the respective gesture recognizer and in accordance with the one or more values determined by the corresponding delegate. The method furthermore includes executing the software application in accordance with information, received from the respective gesture recognizer, corresponding to the respective event.
In accordance with some embodiments, an electronic device includes: one or more event sensors for detecting events, one or more processors, memory, and one or more programs stored in the memory and configured to be executed by the one or more processors. The one or more programs include a software application having a plurality of views and an application state. The software application includes instructions for displaying one or more views of the plurality of views. A respective view of the one or more displayed views includes one or more gesture recognizers, and a respective gesture recognizer has a corresponding delegate. The software application further includes instructions for processing a respective event of the detected events using the respective gesture recognizer. The instructions for processing of the respective event include instructions for: processing the respective event at the respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, executing the corresponding delegate to determine one or more values in accordance with the application state, and conditionally sending information corresponding to the respective event to the software application in accordance with an outcome of the processing of the respective event by the respective gesture recognizer and in accordance with the one or more values determined by the corresponding delegate. The software application furthermore includes instructions for executing the software application in accordance with information, received from the respective gesture recognizer, corresponding to the respective event.
In accordance with some embodiments, a computer readable storage medium stores one or more programs for execution by one of more processors of an electronic device having one or more event sensors for detecting events. The one or more programs include a software application including a plurality of views and an application state of the software application. The software application includes instructions for displaying one or more views of the plurality of views. A respective view of the one or more displayed views includes one or more respective gesture recognizers, and a respective gesture recognizer has a corresponding delegate. The software application further includes instructions for processing a respective event of the detected events using the respective gesture recognizer. The instructions for processing of the respective event include instructions for: processing the respective event at the respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, executing the corresponding delegate to determine one or more values in accordance with the application state, and conditionally sending information corresponding to the respective event to the software application in accordance with an outcome of the processing of the respective event by the respective gesture recognizer and in accordance with the one or more values determined by the corresponding delegate. The software application furthermore includes instructions for executing the software application in accordance with information, received from the respective gesture recognizer, corresponding to the respective event.
In accordance with some embodiments, a method is performed at an electronic device having a touch-sensitive surface and configured to execute a software application that includes a plurality of views and an application state of the software application. The method includes displaying one or more views of the plurality of views. A respective view of the one or more displayed views includes a respective gesture recognizer. The respective gesture recognizer has a corresponding delegate. The method also includes detecting one or more touches, on the touch-sensitive surface, having a touch position that falls within one or more of the displayed views. The method further includes processing a respective touch of the one or more touches. Processing the respective touch includes executing the delegate corresponding to the respective gesture recognizer to obtain a receive touch value in accordance with the application state, and when the receive touch value meets predefined criteria, processing the respective touch at the respective gesture recognizer. Processing the respective touch also includes conditionally sending information corresponding to the respective touch to the software application. The method furthermore includes executing the software application in accordance with information, received from the respective gesture recognizer, corresponding to the respective touch.
In accordance with some embodiments, an electronic device includes a touch-sensitive surface, one or more processors, memory, and one or more programs stored in the memory and configured to be executed by the one or more processors. The one or more programs include a software application including a plurality of views and an application state of the software application. The software application includes instructions for displaying one or more views of the plurality of views. A respective view of the one or more displayed views includes a respective gesture recognizer. The respective gesture recognizer has a corresponding delegate. The software application also includes instructions for detecting one or more touches, on the touch-sensitive surface, having a touch position that falls within one or more of the displayed views. The software application further includes instructions for processing a respective touch of the one or more touches. The instructions for processing the respective touch include instructions for: executing the delegate corresponding to the respective gesture recognizer to obtain a receive touch value in accordance with the application state, and when the receive touch value meets predefined criteria, processing the respective touch at the respective gesture recognizer. The instructions for processing the respective touch also include instructions for conditionally sending information corresponding to the respective touch to the software application. The software application furthermore includes instructions for executing the software application in accordance with information, received from the respective gesture recognizer, corresponding to the respective touch.
In accordance with some embodiments, a computer readable storage medium stores one or more programs for execution by one of more processors of an electronic device having a touch-sensitive surface. The one or more programs include a software application including a plurality of views and an application state of the software application. The software application includes instructions for displaying one or more views of the plurality of views. A respective view of the one or more displayed views includes a respective gesture recognizer. The respective gesture recognizer has a corresponding delegate. The software application also includes instructions for detecting one or more touches, on the touch-sensitive surface, having a touch position that falls within one or more of the displayed views. The software application further includes instructions for processing a respective touch of the one or more touches. The instructions for processing the respective touch include instructions for: executing the delegate corresponding to the respective gesture recognizer to obtain a receive touch value in accordance with the application state, and when the receive touch value meets predefined criteria, processing the respective touch at the respective gesture recognizer. The instructions for processing the respective touch also include instructions for conditionally sending information corresponding to the respective touch to the software application. The software application furthermore includes instructions for executing the software application in accordance with information, received from the respective gesture recognizer, corresponding to the respective touch.
In accordance with some embodiments, a method is performed at an electronic device having a touch-sensitive surface and configured to execute a software application. The method includes displaying one or more views of the software application. The one or more displayed views include a plurality of gesture recognizers. The plurality of gesture recognizers includes at least one discrete gesture recognizer and at least one continuous gesture recognizer. The discrete gesture recognizer is configured to send a single action message in response to a respective gesture, and the continuous gesture recognizer is configured to send action messages at successive recognized sub-events of a respective recognized gesture. The method also includes detecting one or more touches, and processing each of the touches using one or more of the gesture recognizers. The processing of a respective touch includes processing the respective touch at a respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, and conditionally sending one or more respective action messages to the software application in accordance with an outcome of the processing of the respective touch at the respective gesture recognizer. The method further includes executing the software application in accordance with one or more action messages received from one or more of the gesture recognizers corresponding to one or more of the touches.
In accordance with some embodiments, an electronic device includes a touch-sensitive surface, one or more processors, memory, and one or more programs stored in the memory and configured to be executed by the one or more processors. The one or more programs include a software application, and the software application includes instructions for displaying one or more views of the software application. The one or more displayed views include a plurality of gesture recognizers. The plurality of gesture recognizers includes at least one discrete gesture recognizer and at least one continuous gesture recognizer. The discrete gesture recognizer is configured to send a single action message in response to a respective gesture, and the continuous gesture recognizer is configured to send action messages at successive recognized sub-events of a respective recognized gesture. The software application also includes instructions for detecting one or more touches and processing each of the touches using one or more of the gesture recognizers. The instructions for processing of a respective touch include instructions for: processing the respective touch at a respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, and conditionally sending one or more respective action messages to the software application in accordance with an outcome of the processing of the respective touch at the respective gesture recognizer. The software application further includes instructions for executing the software application in accordance with one or more action messages received from one or more of the gesture recognizers corresponding to one or more of the touches.
In accordance with some embodiments, a computer readable storage medium stores one or more programs for execution by one of more processors of an electronic device having a touch-sensitive surface. The one or more programs include a software application, and the software application includes instructions for displaying one or more views of the software application. The one or more displayed views include a plurality of gesture recognizers. The plurality of gesture recognizers includes at least one discrete gesture recognizer, and at least one continuous gesture recognizer. The discrete gesture recognizer is configured to send a single action message in response to a respective gesture, and the continuous gesture recognizer is configured to send action messages at successive recognized sub-events of a respective recognized gesture. The software application also includes instructions for: detecting one or more touches, and processing each of the touches using one or more of the gesture recognizers. The instructions for the processing of a respective touch includes instructions for processing the respective touch at a respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, and conditionally sending one or more respective action messages to the software application in accordance with an outcome of the processing of the respective touch at the respective gesture recognizer. The software application further includes instructions for executing the software application in accordance with one or more action messages received from one or more of the gesture recognizers corresponding to one or more of the touches.
Like reference numerals refer to corresponding parts throughout the drawings.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the present invention. The first contact and the second contact are both contacts, but they are not the same contact.
The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting (the stated condition or event)” or “in response to detecting (the stated condition or event),” depending on the context.
As used herein, the term “event” refers to an input detected by one or more sensors of the device. In particular, the term “event” includes a touch on a touch-sensitive surface. An event comprises one or more sub-events. Sub-events typically refer to changes to an event (e.g., a touch-down, touch-move, and lift-off of the touch can be sub-events). Sub-events in the sequence of one or more sub-events can include many forms, including without limitation, key presses, key press holds, key press releases, button presses, button press holds, button press releases, joystick movements, mouse movements, mouse button presses, mouse button releases, pen stylus touches, pen stylus movements, pen stylus releases, oral instructions, detected eye movements, biometric inputs, and detected physiological changes in a user, among others. Since an event may comprise a single sub-event (e.g., a short lateral motion of the device), the term “sub-event” as used herein also refers to an event.
As used herein, the terms “event recognizer” and “gesture recognizer” are used interchangeably to refer to a recognizer that can recognize a gesture or other events (e.g., motion of the device).
As noted above, in some devices with a touch-sensitive surface as an input device, a first set of touch-based gestures (e.g., two or more of: tap, double tap, horizontal swipe, vertical swipe) are recognized as proper inputs in a particular context (e.g., in a particular mode of a first application), and other, different sets of touch-based gestures are recognized as proper inputs in other contexts (e.g., different applications and/or different modes or contexts within the first application). Furthermore, two or more proper inputs (or gestures) may interfere with, or conflict with, each other (e.g., after detecting a single tap, it needs to be decided whether to recognize the single tap as a complete single tap gesture, or as part of a double tap gesture). As a result, the software and logic required for recognizing and responding to touch-based gestures can become complex, and can require revision each time an application is updated or a new application is added to the computing device.
When using touch-based gestures to control an application running in a device having a touch-sensitive surface, touches have both temporal and spatial aspects. The temporal aspect, called a phase, indicates when a touch has just begun, whether it is moving or stationary, and when it ends—that is, when the finger is lifted from the screen. A spatial aspect of a touch is the set of views or user interface windows in which the touch occurs. The views or windows in which a touch is detected may correspond to programmatic levels within a view hierarchy. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
In some embodiments, electronic device 104 includes a touch screen display. In these embodiments, user interface 113 may include an on-screen keyboard (not depicted) that is used by a user to interact with electronic devices 102 and 104. Alternatively, a keyboard may be separate and distinct from electronic device 104 (or electronic device 102). For example, a keyboard may be a wired or wireless keyboard coupled to electronic device 102 or 104.
In some embodiments, electronic device 102 includes display 126 and one or more input devices 128 (e.g., keyboard, mouse, trackball, microphone, physical button(s), touchpad, etc.) that are coupled to electronic device 102. In these embodiments, one or more of input devices 128 may optionally be separate and distinct from electronic device 102. For example, the one or more input devices may include one or more of: a keyboard, a mouse, a trackpad, a trackball, and an electronic pen, any of which may optionally be separate from the electronic device. Optionally, device 102 or 104 may include one or more sensors 130, such as one or more accelerometers, gyroscopes, GPS systems, speakers, infrared (IR) sensors, biometric sensors, cameras, etc. It is noted that the description above of various exemplary devices as input devices 128 or as sensors 130 is of no significance to the operation of the embodiments described herein, and that any input or sensor device herein described as an input device may equally well be described as a sensor, and vice versa. In some embodiments, signals produced by one or more sensors 130 are used as input sources for detecting events.
In some embodiments, electronic device 104 includes touch-sensitive display 156 (i.e., a display having a touch-sensitive surface) and one or more input devices 128 that are coupled to electronic device 104. In some embodiments, touch-sensitive display 156 has the ability to detect two or more distinct, concurrent (or partially concurrent) touches, and in these embodiments, display 156 is sometimes herein called a multitouch display or multitouch-sensitive display.
In some embodiments of electronic device 102 or 104 discussed herein, input devices 128 are disposed in electronic device 102 or 104. In other embodiments, one or more of input devices 128 is separate and distinct from electronic device 102 or 104; for example, one or more of input devices 128 may be coupled to electronic device 102 or 104 by a cable (e.g., USB cable) or wireless connection (e.g., Bluetooth connection).
When using input devices 128, or when performing a touch-based gesture on touch-sensitive display 156 of electronic device 104, the user generates a sequence of sub-events that are processed by one or more CPUs 110 of electronic device 102 or 104. In some embodiments, one or more CPUs 110 of electronic device 102 or 104 process the sequence of sub-events to recognize events.
Electronic device 102 or 104 typically includes one or more single- or multi-core processing units (“CPU” or “CPUs”) 110 as well as one or more network or other communications interfaces 112, respectively. Electronic device 102 or 104 includes memory 111 and one or more communication buses 115, respectively, for interconnecting these components. Communication buses 115 may include circuitry (sometimes called a chipset) that interconnects and controls communications between system components (not depicted herein). As discussed briefly above, electronic device 102 or 104 includes a user interface 113, including a display (e.g., display 126, or touch-sensitive display 156). Further, electronic device 102 or 104 typically includes input devices 128 (e.g., keyboard, mouse, touch sensitive surfaces, keypads, etc.). In some embodiments, the input devices 128 include an on-screen input device (e.g., a touch-sensitive surface of a display device). Memory 111 may include high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 111 may optionally include one or more storage devices remotely located from the CPU(s) 110. Memory 111, or alternately the non-volatile memory device(s) within memory 111, comprise a computer readable storage medium. In some embodiments, memory 111 (of electronic device 102 or 104) or the computer readable storage medium of memory 111 stores the following programs, modules and data structures, or a subset thereof:
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing functions described herein. The set of instructions can be executed by one or more processors (e.g., one or more CPUs 110). The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory 111 may store a subset of the modules and data structures identified above. Furthermore, memory 111 may store additional modules and data structures not described above.
A driver or a set of drivers 210 communicates with hardware 212. Drivers 210 can receive and process input data received from hardware 212. Core Operating System (“OS”) 208 can communicate with driver(s) 210. Core OS 208 can process raw input data received from driver(s) 210. In some embodiments, drivers 210 can be considered to be a part of core OS 208.
A set of OS application programming interfaces (“OS APIs”) 206, are software procedures that communicate with core OS 208. In some embodiments, APIs 206 are included in the device's operating system, but at a level above core OS 208. APIs 206 are designed for use by applications running on the electronic devices or apparatuses discussed herein. User interface (UI) APIs 204 can utilize OS APIs 206. Application software (“applications”) 132 running on the device can utilize UI APIs 204 in order to communicate with the user. UI APIs 204 can, in turn, communicate with lower level elements, ultimately communicating with various user interface hardware, e.g., multitouch display 156.
While each layer input/output processing stack 200 can utilize the layer underneath it, that is not always required. For example, in some embodiments, applications 132 can occasionally communicate with OS APIs 206. In general, layers at or above OS API layer 206 may not directly access Core OS 208, driver(s) 210, or hardware 212, as these layers are considered private. Applications in layer 132 and UI API 204 usually direct calls to the OS API 206, which in turn, accesses the layers Core OS 208, driver(s) 210, and hardware 212.
Stated in another way, one or more hardware elements 212 of electronic device 102 or 104, and software running on the device, such as, for example, drivers 210 (depicted in
In this example, each subordinate view includes lower-level subordinate views. In other examples, the number of view levels in the hierarchy 300 may differ in different branches of the hierarchy, with one or more subordinate views having lower-level subordinate views, and one or more other subordinate views not have any such lower-level subordinate views. Continuing with the example shown in
A touch sub-event 301-1 is represented in outermost view 302. Given the location of touch sub-event 301-1 over both the search results panel 304, and maps view 305, the touch sub-event is also represented over those views as 301-2 and 301-3, respectively. Actively involved views of the touch sub-event include the views search results panel 304, maps view 305 and outermost view 302. Additional information regarding sub-event delivery and actively involved views is provided below with reference to
Views (and corresponding programmatic levels) can be nested. In other words, a view can include other views. Consequently, the software element(s) (e.g., event recognizers) associated with a first view can include or be linked to one or more software elements associated with views within the first view. While some views can be associated with applications, others can be associated with high level OS elements, such as graphical user interfaces, window managers, etc.
In some embodiments, event recognizer global methods 311 include event monitor 312, hit view determination module 313, active event recognizer determination module 314, and event dispatcher module 315. In some embodiments, event recognizer global methods 311 are located within event delivery system 136. In some embodiments, event recognizer global methods 311 are implemented in operating system 118. Alternatively, event recognizer global methods 311 are implemented in application 132-1. In yet other embodiments, event recognizer global methods 311 are implemented as a stand-alone module, or a part of another module stored in memory 111 (e.g., a contact/motion module (not depicted)).
Event monitor 312 receives event information from sensors 130, touch-sensitive display 156, and/or input devices 128. Event information includes information about an event (e.g., a user touch on touch-sensitive display 156, as part of a multi-touch gesture or a motion of device 102 or 104) and/or a sub-event (e.g., a movement of a touch across touch-sensitive display 156). For example, event information for a touch event includes one or more of: a location and time stamp of a touch. Similarly, event information for a swipe event includes two or more of: a location, time stamp, direction, and speed of a swipe. Sensors 130, touch-sensitive display 156, and input devices 128 transmit information event and sub-event information to event monitor 312 either directly or through a peripherals interface, which retrieves and stores event information. Sensors 130 include one or more of: proximity sensor, accelerometer(s), gyroscopes, microphone, and video camera. In some embodiments, sensors 130 also include input devices 128 and/or touch-sensitive display 156.
In some embodiments, event monitor 312 sends requests to sensors 130 and/or the peripherals interface at predetermined intervals. In response, sensors 130 and/or the peripherals interface transmit event information. In other embodiments, sensors 130 and the peripheral interface transmit event information only when there is a significant event (e.g., receiving an input beyond a predetermined noise threshold and/or for more than a predetermined duration).
Event monitor 312 receives event information and determines the application 132-1 and application view 316-2 of application 132-1 to which to deliver the event information.
In some embodiments, event recognizer global methods 311 also include a hit view determination module 313 and/or an active event recognizer determination module 314.
Hit view determination module 313 provides software procedures for determining where an event or a sub-event has taken place within one or more views, when touch-sensitive display 156 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application 132-1 is a set views 316, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to a particular view within a view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 313 receives information related to events and/or sub-events. When an application has multiple views organized in a hierarchy, hit view determination module 313 identifies a hit view as the lowest view in the hierarchy which should handle the event or sub-event. In most circumstances, the hit view is the lowest level view in which an initiating event or sub-event occurs (i.e., the first event or sub-event in the sequence of events and/or sub-events that form a gesture). Once the hit view is identified by the hit view determination module, the hit view typically receives all events and/or sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 314 determines which view or views within a view hierarchy should receive a particular sequence of events and/or sub-events. In some application contexts, active event recognizer determination module 314 determines that only the hit view should receive a particular sequence of events and/or sub-events. In other application contexts, active event recognizer determination module 314 determines that all views that include the physical location of an event or sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of events and/or sub-events. In other application contexts, even if touch events and/or sub-events are entirely confined to the area associated with one particular view, views higher in the hierarchy still remain as actively involved views.
Event dispatcher module 315 dispatches the event information to an event recognizer (also called herein “gesture recognizer”) (e.g., event recognizer 320-1). In embodiments including active event recognizer determination module 314, event dispatcher module 315 delivers the event information to an event recognizer determined by active event recognizer determination module 314. In some embodiments, event dispatcher module 315 stores in an event queue the event information, which is retrieved by a respective event recognizer 320 (or event receiver 331 in a respective event recognizer 320).
In some embodiments, application 132-1 includes application internal state 317, which indicates the current application view(s) displayed on touch-sensitive display 156 when the application is active or executing. In some embodiments, device/global internal state 134 is used by event recognizer global methods 311 to determine which application(s) is(are) currently active, and application internal state 317 is used by event recognizer global methods 311 to determine application views 316 to which to deliver event information.
In some embodiments, application internal state 317 includes additional information (e.g., 344,
In some embodiments, application 132-1 includes one or more application views 316, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. At least one application view 316 of the application 132-1 includes one or more event recognizers 320 and one or more event handlers 322. Typically, a respective application view 316 includes a plurality of event recognizers 320 and a plurality of event handlers 322. In other embodiments, one or more of event recognizers 320 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 132-1 inherits methods and other properties. In some embodiments, a respective application view 316 also includes one or more of: data updater, object updater, GUI updater, and/or event data received.
A respective event recognizer 320-1 receives event information from event dispatcher module 315, and identifies an event from the event information. Event recognizer 320-1 includes event receiver 331 and event comparator 332.
The event information includes information about an event (e.g., a touch) or a sub-event (e.g., a touch movement). Depending on the event or sub-event, the event information also includes additional information, such as location of the event or sub-event. When the event or sub-event concerns motion of a touch, the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 332 compares the event information to one or more predefined gesture definitions (also called herein “event definitions”) and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 332 includes one or more gesture definitions 333 (as described above, also called herein “event definitions”). Gesture definitions 333 contain definitions of gestures (e.g., predefined sequences of events and/or sub-events), for example, gesture 1 (334-1), gesture 2 (334-2), and others. In some embodiments, sub-events in gesture definitions 333 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for gesture 1 (334-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase of the gesture, a first lift-off (touch end) for a next predetermined phase of the gesture, a second touch (touch begin) on the displayed object for a subsequent predetermined phase of the gesture, and a second lift-off (touch end) for a final predetermined phase of the gesture. In another example, the definition for gesture 2 (334-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object, a movement of the touch across touch-sensitive display 156, and lift-off of the touch (touch end).
In some embodiments, event recognizer 320-1 also includes information for event delivery 335. Information for event delivery 335 includes references to corresponding event handlers 322. Optionally, information for event delivery 335 includes action-target pair(s). In some embodiments, in response to recognizing a gesture (or a part of a gesture), event information (e.g., action message(s)) is sent to one or more targets identified by the action-target pair(s). In other embodiments, in response to recognizing a gesture (or a part of a gesture), the action-target pair(s) are activated.
In some embodiments, gesture definitions 333 include a definition of a gesture for a respective user-interface object. In some embodiments, event comparator 332 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 156, when a touch is detected on touch-sensitive display 156, event comparator 332 performs a hit test to determine which of the three user-interface objects, if any, is associated with the touch (event). If each displayed object is associated with a respective event handler 322, event comparator 332 uses the result of the hit test to determine which event handler 322 should be activated. For example, event comparator 332 selects an event handler 322 associated with the event and the object triggering the hit test.
In some embodiments, the definition for a respective gesture 333 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of events and/or sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 320-1 determines that the series of events and/or sub-events do not match any of the events in gesture definitions 333, the respective event recognizer 320-1 enters an event failed state, after which the respective event recognizer 320-1 disregards subsequent events and/or sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process events and/or sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 320-1 includes event recognizer state 336. Event recognizer state 336 includes a state of the respective event recognizer 320-1. Examples of event recognizer states are described in more detail below with reference to
In some embodiments, event recognizer state 336 includes recognizer metadata and properties 337-1. In some embodiments, recognizer metadata and properties 337-1 include one or more of the following: A) configurable properties, flags, and/or lists that indicate how the event delivery system should perform event and/or sub-event delivery to actively involved event recognizers; B) configurable properties, flags, and/or lists that indicate how event recognizers interact with one another; C) configurable properties, flags, and/or lists that indicate how event recognizers receive event information; D) configurable properties, flags, and/or lists that indicate how event recognizers may recognize a gesture; E) configurable properties, flags, and/or lists that indicate whether events and/or sub-events are delivered to varying levels in the view hierarchy; and F) references to corresponding event handlers 322.
In some embodiments, event recognizer state 336 includes event/touch metadata 337-2. Event/touch metadata 337-2 includes event/touch information about a respective event/touch that has been detected and corresponds to gesture definitions 333. The event/touch information includes one or more of: a location, time stamp, speed, direction, distance, scale (or change in scale), and angle (or change in angle) of the respective event/touch.
In some embodiments, a respective application view includes one or more delegates 321. A respective delegate 321 is assigned to a respective event recognizer 320. Alternately, a respective event recognizer 320 has a corresponding delegate 321, but the delegate 321 is not necessarily assigned to the respective recognizer 320 at a runtime, and instead the delegate for an event recognizer may be established prior to execution of the application (e.g., the delegate for an event recognizer may be indicated by the delegate property of an application view, established when the corresponding applicative view 316 is initialized). In some embodiments, some event recognizers do not have an assigned (or corresponding) delegate. Event recognizers lacking corresponding delegates perform in accordance with default rules, such as default rules governing event recognition exclusivity. In some embodiments, some event recognizers have multiple assigned (or corresponding) delegates. Delegates modify the behavior of the corresponding event recognizer, and can also be used to coordinate the behavior of multiple event recognizers. In some embodiments described below, a delegate, when assigned to a respective event recognizer, modifies multiple aspects of the behavior of the respective event recognizer.
In some embodiments, a respective event recognizer 320 activates event handler 322 associated with the respective event recognizer 320 when one or more particular events and/or sub-events of a gesture are recognized. In some embodiments, respective event recognizer 320 delivers event information associated with the event to event handler 322.
Event handler 322, when activated, performs one or more of: creating and/or updating data, creating and updating objects, and preparing display information and sending it for display on display 126 or touch-sensitive display 156.
In some embodiments, a respective application view 316-2 includes view metadata 323. View metadata 323 include data regarding a view. Optionally, view metadata includes the following properties, which influence event and/or sub-event delivery to event recognizers:
In some embodiments, a first actively involved view within the view hierarchy may be configured to prevent delivery of a respective sub-event to event recognizers associated with that first actively involved view. This behavior can implement the skip property 324-2. When the skip property is set for an application view, delivery of the respective sub-event is still performed for event recognizers associated with other actively involved views in the view hierarchy.
Alternately, a first actively involved view within the view hierarchy may be configured to prevent delivery of a respective sub-event to event recognizers associated with that first actively involved view unless the first actively involved view is the hit view. This behavior can implement the conditional NoHit skip property 324-3.
In some embodiments, a second actively involved view within the view hierarchy is configured to prevent delivery of the respective sub-event to event recognizers associated with the second actively involved view and to event recognizers associated with ancestors of the second actively involved view. This behavior can implement the stop property 324-1.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate electronic device 102 or 104 with input-devices, not all of which are initiated on touch screens, e.g., coordinating mouse movement and mouse button presses with or without single or multiple keyboard presses or holds, user movements, taps, drags, scrolls, etc., on touch-pads, pen stylus inputs, movement (e.g., rotation) of the device, oral instructions, detected eye movements, biometric inputs, and/or any combination thereof, which may be utilized as inputs corresponding to events and/or sub-events which define a gesture to be recognized.
A software application (e.g., application 132-1) has one or more event recognizers 340. In some embodiments, a respective event recognizer (e.g., 340-2) is an event recognizer class. The respective event recognizer (e.g., 340-2) includes event recognizer specific code 341 (e.g., a set of instructions defining the operation of event recognizers) and state machine 342.
In some embodiments, application state 317 of a software application (e.g., application 132-1) includes instances of event recognizers. Each instance of an event recognizer is an object having a state (e.g., event recognizer state 336). “Execution” of a respective event recognizer instance is implemented by executing corresponding event recognizer specific code (e.g., 341) and updating or maintaining the state 336 of the event recognizer instance 343. The state 336 of event recognizer instance 343 includes the state 338 of the event recognizer instance's state machine 342.
In some embodiments, application state 317 includes a plurality of event recognizer instances 343, each corresponding to an event recognizer that has been bound (also called “attached”) to a view of the application. In some embodiments, application state 317 includes a plurality of instances (e.g., 343-1 to 343-L) of a respective event recognizer (e.g., 340-2). In some embodiments, application state 317 includes instances 343 of a plurality of event recognizers (e.g., 340-1 to 340-R).
In some embodiments, a respective instance 343-2 of a gesture recognizer includes event recognizer state 336. As discussed above, event recognizer state 336 includes recognizer metadata and properties 337-1 and event/touch metadata 337-2. Event recognizer state 336 also includes view hierarchy reference(s) 337-3, indicating to which view the respective instance 343-2 of the gesture recognizer is attached.
In some embodiments, recognizer metadata and properties 337-1 include the following, or a subset or superset thereof:
In some embodiments, one or more event recognizers may be adapted to delay delivering one or more sub-events of the sequence of sub-events until after the event recognizer recognizes the event. This behavior reflects a delayed event. For example, consider a single tap gesture in a view for which multiple tap gestures are possible. In that case, a tap event becomes a “tap+delay” recognizer. In essence, when an event recognizer implements this behavior, the event recognizer will delay event recognition until it is certain that the sequence of sub-events does in fact correspond to its event definition. This behavior may be appropriate when a recipient view is incapable of appropriately responding to cancelled events. In some embodiments, an event recognizer will delay updating its event recognition status to its respective actively involved view until the event recognizer is certain that the sequence of sub-events does not correspond to its event definition. Delay touch began flag 352, delay touch end flag 363, and touch cancellation flag 364 are provided to tailor sub-event delivery techniques, as well as event recognizer and view status information updates to specific needs.
In some embodiments, recognizer metadata and properties 337-1 include the following, or a subset or superset thereof:
In some embodiments, exception list 353 can also be used by non-exclusive event recognizers. In particular, when a non-exclusive event recognizer recognizes an event or sub-event, subsequent events and/or sub-events are not delivered to the exclusive event recognizers associated with the currently active views, except for those exclusive event recognizers listed in exception list 353 of the event recognizer that recognized the event or sub-event.
In some embodiments, event recognizers may be configured to utilize the touch cancellation flag 364 in conjunction with the delay touch end flag 363 to prevent unwanted events and/or sub-events from being delivered to the hit view. For example, the definition of a single tap gesture and the first half of a double tap gesture are identical. Once a single tap event recognizer successfully recognizes a single tap, an undesired action could take place. If the delay touch end flag is set, the single tap event recognizer is prevented from sending sub-events to the hit view until a single tap event is recognized. In addition, the wait-for list of the single tap event recognizer may identify the double-tap event recognizer, thereby preventing the single tap event recognizer from recognizing a single tap until the double-tap event recognizer has entered the event impossible state. The use of the wait-for list avoids the execution of actions associated with a single tap when a double tap gesture is performed. Instead, only actions associated with a double tap will be executed, in response to recognition of the double tap event.
Turning in particular to forms of user touches on touch-sensitive surfaces, as noted above, touches and user gestures may include an act that need not be instantaneous, e.g., a touch can include an act of moving or holding a finger against a display for a period of time. A touch data structure, however, defines the state of a touch (or, more generally, the state of any input source) at a particular time. Therefore, the values stored in a touch data structure may change over the course of a single touch, enabling the state of the single touch at different points in time to be conveyed to an application.
Each touch data structure can comprise various entries. In some embodiments, touch data structures may include data corresponding to at least the touch-specific entries in event/touch metadata 337-2 such as the following, or a subset or superset thereof:
Thus, each touch data structure can define what is happening with a respective touch (or other input source) at a particular time (e.g., whether the touch is stationary, being moved, etc.) as well as other information associated with the touch (such as position). Accordingly, each touch data structure can define the state of a particular touch at a particular moment in time. One or more touch data structures referencing the same time can be added in a touch event data structure that can define the states of all touches a particular view is receiving at a moment in time (as noted above, some touch data structures may also reference touches that have ended and are no longer being received). Multiple touch event data structures can be sent to the software implementing a view as time passes, in order to provide the software with continuous information describing the touches that are happening in the view.
The ability to handle complex touch-based gestures, optionally including multi-touch gestures, can add complexity to the various software applications. In some cases, such additional complexity can be necessary to implement advanced and desirable interface features. For example, a game may require the ability to handle multiple simultaneous touches that occur in different views, as games often require the pressing of multiple buttons at the same time, or combining accelerometer data with touches on a touch-sensitive surface. However, some simpler applications and/or views need not require advanced interface features. For example, a simple soft button (i.e., a button that is displayed on a touch-sensitive display) may operate satisfactorily with single touches, rather than multi-touch functionality. In these cases, the underlying OS may send unnecessary or excessive touch data (e.g., multi-touch data) to a software component associated with a view that is intended to be operable by single touches only (e.g., a single touch or tap on a soft button). Because the software component may need to process this data, it may need to feature all the complexity of a software application that handles multiple touches, even though it is associated with a view for which only single touches are relevant. This can increase the cost of development of software for the device, because software components that have been traditionally easy to program in a mouse interface environment (i.e., various buttons, etc.) may be much more complex in a multi-touch environment.
In order to reduce the complexity in recognizing complex touch-based gestures, delegates can be used to control the behavior of event recognizers in accordance with some embodiments. As described below, delegates can determine, for example, whether a corresponding event recognizer (or gesture recognizer) can receive the event (e.g., touch) information; whether the corresponding event recognizer (or gesture recognizer) can transition from an initial state (e.g., event possible state) of state machine to another state; and/or whether the corresponding event recognizer (or gesture recognizer) can simultaneously recognize the event (e.g., touch) as a corresponding gesture without blocking other event recognizer(s) (or gesture recognizer(s)) from recognizing the event or getting blocked by other event recognizer(s) (or gesture recognizer(s)) recognizing the event.
It shall be understood, however, that the foregoing discussion regarding the complexity of evaluating and processing user touches on touch-sensitive surfaces also applies to all forms of user inputs to operate electronic device 102 or 104, not all of which are initiated on touch screens, e.g., coordinating mouse movement and mouse button presses with or without single or multiple keyboard presses or holds, device rotations or other movements, user movements such as taps, drags, scrolls, etc., on touch-pads, pen stylus inputs, oral instructions, detected eye movements, biometric inputs, detected physiological change in a user, and/or any combination thereof, which may be utilized as inputs corresponding to events and/or sub-events which define an event to be recognized.
Regardless of event type, event recognizer state machine 342 (including event recognizer state machine implemented as discrete event recognizer state machine 400) begins in event possible state 410, which indicates an initial state of the event recognizer state machine. Event recognizer state machine 342 may progress to any of the remaining states depending on what event and/or sub-event is received.
Starting from event possible state 410, if an event or sub-event is received that is not the first event or sub-event in a gesture definition, discrete event recognizer state machine 400 will transition to event failed state 430.
Starting from event possible state 410, if an event or sub-event is received that, by itself comprises the gesture definition for a gesture, discrete event recognizer state machine 400 will transition to event recognized state 420. However, even if the received event or sub-event comprises the gesture definition for the gesture, discrete event recognizer state machine 400 may nevertheless transition to event failed state 430 in accordance with metadata (e.g., a property) of the corresponding event recognizer, one or more values determined by a corresponding delegate, and/or the application state.
In some embodiments, after transitioning to event recognized state 420, the corresponding event recognizer checks (441) a delay flag (e.g., delay touch end flag 363). If the delay flag is raised (441—yes), the corresponding event recognizer delays (442) delivering event information until the delay flag is lowered.
In some embodiments, the corresponding event recognizer includes wait-for list 351, and the corresponding event recognizer waits for the event recognizers listed in wait-for list 351 to reach a certain state. For example, when a view includes a single tap gesture recognizer and a double tap gesture recognizer, a single tap gesture recognizer can be configured to wait for a double tap gesture recognizer to fail. In effect, transition of the single tap gesture recognizer to event recognized state 420 requires (or is conditioned upon) the failure of the double tap gesture recognizer to recognize the event. As a result, when there is a tap event, the single tap gesture recognizer recognizes the tap event as long as the tap event is not part of a multi-tap gesture.
After the delay and wait (442), if any, the corresponding gesture recognizer delivers events to the application (443). In some embodiments, events are delivered in the form of action messages. In some embodiments, action messages are delivered in accordance with action-target pair(s) 345. In some embodiments, the corresponding gesture recognizer activates action-target pair(s) 345.
As discussed above, continuous event recognizer state machines 402 starts from event possible state 410.
Starting from event possible state 410, if an event or sub-event is received that is not part of a begin sequence of event(s) and/or sub-event(s) in a gesture definition, discrete event recognizer state machine 400 will transition to event failed state 430.
Starting from event possible state 410, if an event or sub-event is received that is part of a begin sequence of event(s) and/or sub-event(s) in a given gesture definition, continuous event recognizer state machine 402 will transition to event began state 412. Similar to discrete event recognizer state machine 400, even if the received event or sub-event comprises part of a begin sequence of event(s) and/or sub-event(s) in the gesture definition, continuous event recognizer state machine 402 may transition to event failed state 430 in accordance with metadata (e.g., a property) of the corresponding event recognizer, one or more values determined by a corresponding delegate, and/or the application state.
From event began state 412, if the next event or sub-event received is an intermediate event or sub-event, but not the final event or sub-event in the given gesture definition, continuous event recognizer state machine 402 will transition to and remain in event changed state 414. Continuous event recognizer state machine 402 can remain in event changed state 414 for as long as the sequence of received events and/or sub-events continues to be part of the gesture definition. If, at any time continuous event recognizer state machine 402 is in event changed state 414, and continuous event recognizer state machine 402 receives an event or sub-event that is not part of the gesture definition, it will transition to event failed state 430, thereby determining that the current event (if any) is not the type of event that corresponds to this event recognizer (i.e., the event recognizer corresponding to continuous event recognizer state machine 402). If, on the other hand, continuous event recognizer state machine 402 is in event began state 412 or event changed state 414, and continuous event recognizer state machine 402 receives the last event or sub-event in a gesture definition, it will transition to event ended state 416, thereby completing a successful event recognition.
In some embodiments, each gesture recognizer state has a gesture recognizer state value. In some embodiments, event recognized state 420 (for discrete event recognizer state machine 400) and event ended state 416 (for continuous event recognizer state machine 402) have an identical gesture recognizer state value, such that a software component configured to response a recognition of a gesture by one type of gesture recognizer can also respond to the other type of gesture recognizer.
While in event began state 412 or event changed state 414, when a predefined interruption event (e.g., predefined in operating system 118 or control application 124, such as an incoming phone call) occurs, continuous event recognizer state machine 402 transitions to event canceled state 418.
Regardless of the gesture recognizer type, each gesture recognizer (e.g., 343) can be reset such that a corresponding event recognizer state machine returns (e.g., 342) to event possible state 410.
Starting from event possible state 410, if an event or sub-event is detected, the delegate corresponding to an event recognizer decides whether the event recognizer should receive (450) the event or sub-event. If the delegate returns a value that prevents the corresponding event recognizer from receiving the event or sub-event, the corresponding event recognizer does not receive the event or sub-event (or disregards the event or sub-event). As a result, the corresponding event recognizer remains in event possible state 410. If there is no delegate preventing the corresponding event recognizer from receiving the event or sub-event, the default behavior for the corresponding event recognizer is to receive the event or sub-event.
It is noted that the “should receive” operation 450 by the delegates of a set of event recognizers can be used to determine which event recognizers receive which touches on a touch-sensitive display or surface. For example, in a view that allows a user to use two touches to individually and simultaneously reposition two objects, or to select two different objects, the delegates of two event recognizers can be configured to allow one event recognizer to receive only a first one of the two touches and to allow a second event recognizer to receive only a second one of the two touches. All information about each of the two touches is therefore directed to only the event recognizer allowed, by its corresponding delegate, to receive that touch. Much more complex multi-touch inputs can also be recognized and processed through the use of multiple event recognizers and corresponding delegates that determine which touches are processed by which event recognizers.
If the event recognizer is allowed to receive the event or sub-event, the delegate corresponding to the event recognizer (or the control application 124 or operating system 118) decides whether the recognition of the event or sub-event by the event recognizer is blocked (451) by another event recognizer having already recognized the event. This initial level of blocking is based on a default exclusivity rule, and can be overridden by the delegate. If the recognition of the event or sub-event is blocked, the corresponding delegate (or operating system 118 or control application 124) also decides whether simultaneous recognition of the event by the event recognizer is allowed (452) in accordance with one or more values determined by the delegate. For example, if the event recognizer is on the exclusivity exception list 353 of the event recognizer that initially recognized the event, the delegate allows simultaneous recognition by both event recognizers. In another example, if the exclusivity flag 339 of the event recognizer is not set, the delegate allows simultaneous recognition by both event recognizers. If the simultaneous recognition is not allowed, the event recognizer transitions to event failed state 430.
If the corresponding event recognizer is not blocked (451—No) from recognizing the event or sub-event, or if simultaneous recognition is allowed (452—Yes), the corresponding event recognizer determines whether the event or sub-event matches (453) a corresponding gesture definition. If the event or sub-event does not match (453—No) the corresponding gesture definition, the corresponding gesture recognizer transitions to event failed state 430.
If the event or sub-event matches (453—Yes) the corresponding gesture definition, the corresponding delegate (or operating system 118 or control application 124) decides whether it can transition (“should begin” 454) out of event possible state 410 in accordance with one or more values determined by the delegate. If the event recognizer is not allowed (454—No) by the delegate to transition out of event possible state 410, the corresponding event recognizer is put into event failed state 430. If the event recognizer is allowed (454—Yes) to transition out of event possible state 410, the corresponding event recognizer transitions into event recognized state 420.
When the corresponding event recognizer transitions into event recognized state 420, the corresponding event recognizer (or operating system 118 or control application 124) also decides whether to allow the recognition of the event or sub-event by the other event recognizers (455). In some embodiments, the default is to prevent all other event recognizers from recognizing the same event, unless the delegate (or the application) of at least one of the event recognizers sets a property to allow simultaneous recognition. If the delegate corresponding to the event recognizer which has recognized the event or sub-event determined that the delegate will allow (455—Yes) other event recognizers to recognize the event or sub-event, the delegate (or operating system 118 or control application 124) sets (456) a property of the other event recognizers such that they can recognize the event or sub-event simultaneously. If the delegate does not allow other event recognizers to recognize the event or sub-event, the other event recognizers are prevented from recognizing the event or sub-event.
In some embodiments, prior to preventing a respective event recognizer from recognizing an event or sub-event, the delegate of that event recognizer is also invoked (see 452) to see if it will allow simultaneous recognition of the event or sub-event. In these embodiments, simultaneous recognition can be enabled by either the delegate of the first event recognizer to recognize the event, or the delegate of a second event recognizer. As shown by 452 and 455 in
The above described delegate operations, when implemented in the delegates for a set of event recognizers used by an application view (or set of simultaneously displayed views), can be used to customize the interaction of the event recognizers. The delegates can implement exceptions to a default exclusivity rule, which otherwise allows only one event recognizer to recognize a gesture based on the same received event(s). The user of delegates to implement exceptions to the default exclusivity rule, and thereby allow simultaneous event recognition by compatible event recognizers, facilitates the implementation of many useful functions in software applications. The use of delegates to modify and control the behavior of event recognizers allows for a compact representation and implementation of complex relationships, such as mutually exclusive sets of mutually compatible gestures.
From event began state 412, the corresponding event recognizer transitions into other states as described above. For brevity, the transition from event changed state 414 to event failed state 416 is not depicted.
The following table presents in a tabular format the processing of an exemplary sub-event sequence (e.g., a single tap) as related to the states of event recognizers described above. In this example, the sub-event sequence comprises a single tap, and the view has two tap gesture recognizers: a single tap gesture recognizer and a double tap gesture recognizer. Also in this example, both gesture recognizers are configured to simultaneously receive and recognize the sub-event sequence. Simultaneous recognition can be allowed by a delegate assigned to the single tap gesture recognizer or a delegate assigned to the second tap gesture recognizer.
Before delivery of sub-event information starts (sequence #0), both gesture recognizers are in event possible state 410. Even after detecting a finger down sub-event (sequence #1) and measuring a delay (sequence #2), both gesture recognizers remain in event possible state 410. In response to detecting a finger liftoff (sequence #3), the single tap gesture recognizer transitions into event recognized state 420. After detecting additional delay, the single tap gesture recognizer remains in event recognized state 420 until it is reset, in which case the single tap gesture recognizer returns to event possible state 410. On the other hand, the double tap gesture recognizer transitions into event failed state 430 when the measured additional delay exceeds a predefined duration (e.g., during which the double tap gesture recognizer anticipates a second finger down sub-event).
The following table presents in a tabular format the processing of the exemplary sub-event sequence when the behavior of one gesture recognizer is modified. In this example, the sub-event sequence comprises a single tap, and the view has two tap gesture recognizers: a single tap gesture recognizer and a double tap gesture recognizer. Also in this example, the single tap gesture recognizer is not allowed by its delegate to receive the sub-events.
Because the single tap gesture recognizer is not allowed by its delegate to receive the sub-events, the single tap gesture recognizer remains in event possible state 410. The double tap gesture recognizer transitions into event failed state 430 when the measured second delay exceeds the predefined threshold (sequence #4).
The following table presents in a tabular format the processing of the exemplary sub-event sequence when the behavior of one gesture recognizer is modified. In this example, the sub-event sequence comprises a single tap, and the view has two tap gesture recognizers: a single tap gesture recognizer and a double tap gesture recognizer. Also in this example, both gesture recognizers are not allowed to simultaneously recognize the sub-event sequence.
Similar to what was described above, after detecting finger liftoff (sequence #3), single tap gesture recognizer transitions from event possible state 410 to event recognized state 420. In general, a first gesture recognizer that recognizes the sub-event sequence blocks other gesture recognizers that have not yet recognized the sub-event sequence from recognizing the sub-event sequence. Unless a simultaneous recognition is allowed, blocked gesture recognizers transition into event failed state 430. In this case, because simultaneous recognition is not allowed, when the single tap gesture recognizer recognizes the sub-event sequence (at sequence #3), the double tap gesture recognizer transitions into, and remains in, event failed state 430 until it is reset.
The following table presents in a tabular format the processing of the exemplary sub-event sequence when the behavior of one gesture recognizer is modified by its delegate, and operation of the two gesture recognizers is coordinated in accordance with actions taken by the delegate(s) of one or both recognizers. In this example, the sub-event sequence comprises a single tap, and the view has two tap gesture recognizers: a single tap gesture recognizer and a double tap gesture recognizer. Also in this example, the single tap gesture recognizer is not allowed to begin (or transition out of event possible state 410).
After detecting finger liftoff (sequence #3), single tap gesture recognizer attempts to transition from event possible state 410 to event recognized state 420. However, the delegate assigned to the single tap gesture recognizer does not allow the state transition into the event recognized state 420, and as a result, the single tap gesture recognizer transitions into event failed state 430. The double tap gesture recognizer transitions into event failed state 430 when the measured delay exceeds the predefined threshold (sequence #4).
The following table presents in a tabular format the processing of the exemplary sub-event sequence when the behavior of one gesture recognizer is modified, and operation of two gesture recognizers is coordinated in accordance with actions taken by the delegate(s) of one or both recognizers. In this example, the sub-event sequence comprises a single tap, and the view has two tap gesture recognizers: a single tap gesture recognizer and a double tap gesture recognizer. Also in this example, the single tap gesture recognizer waits for (or requires) a failure of the double tap gesture recognizer.
After detecting finger liftoff (sequence #3), single tap gesture recognizer attempts to transition from event possible state 410 to event recognized state 420. However, due to the “wait-for” requirement or the failure requirement (that the double tap gesture recognizer fail), the single tap gesture recognizer delays transitioning into event recognized state 420. When the double tap gesture recognizer fails because the measured second delay exceeds the predefined threshold (sequence #4), the single tap gesture recognizer transitions into event recognized state 420. The “wait-for” requirement and/or the failure requirement may be implemented using delegates or in gesture recognizers.
The following table presents in a tabular format the processing of the exemplary sub-event sequence. In this example, the sub-event sequence comprises a pan gesture involving multiple intermediary sub-events, and the view has two gesture recognizers: a single tap gesture recognizer and a pan gesture recognizer. Also in this example, both gesture recognizers are allowed to simultaneously recognize the sub-event sequence.
Before delivery of sub-event information starts (sequence #0), both gesture recognizers are in event possible state 410. Even after detecting a finger down sub-event (sequence #1) and measuring a delay (sequence #2), the single tap gesture recognizer remains in event possible state 410, while the pan gesture recognizer transitions into event began state 412. In response to detecting a finger movement (sequence #3), the single tap gesture recognizer transitions into event failed state 430 as the sub-event does not match with the gesture definition for a single tap. The single tap gesture recognizer remains in event failed state 430 thereafter until it is reset. However, the pan gesture recognizer transitions into event changed state 414 in response to detecting the finger movement (sequence #4), and in some embodiments, sends action message(s) including the new location of the finger contact. After detecting additional finger movements (sequence #4 and 5), the pan gesture recognizer remains in event changed state 414, while sending action message(s) every time a finger movement is detected. When a finger liftoff is detected (sequence #6), the pan gesture recognizer transitions into event ended state 416.
Turning to the flow of event information and the interaction between event recognizers,
In some embodiments, gesture recognizers may block or prevent one another from recognizing the event or sub-event as a corresponding gesture. In this example, gesture recognizer 1 (516-1) prevents gesture recognizer 2 (516-2) from recognizing the event or sub-event as a corresponding gesture. As a result, in this example, only gesture recognizer 1 (516-1) sends an action message (518) to a corresponding target-action pair (e.g., target:action 1 (522-1)).
In
The software application (e.g., application 132-1) detects (534) one or more events, and processes (536) each of the events using one or more of the gesture recognizers (e.g., 320).
The respective event is processed (538) at a respective gesture recognizer (of the one or more gesture recognizers (e.g., 320)). In order to explain operation of the delegates, we assume that a respective gesture recognizer that processes the event has a corresponding delegate. The respective gesture recognizer calls the assigned delegate, and the assigned delegate is executed (540) to determine one or more values in accordance with the application state. In response, the respective gesture recognizer conditionally sends (542) information corresponding to the respective event to the software application, in accordance with the one or more values determined by the assigned delegate.
The software application is executed (544) in accordance with information received from one or more of the gesture recognizers corresponding to one or more of the events.
In other words, in these embodiments, a respective gesture recognizer invokes an assigned delegate to obtain one or more values that determine the behavior of the gesture recognizer. As described above, the behavior of the gesture recognizer modified by its corresponding delegate includes whether to receive touch/event information, whether to transition out of the event possible state, and/or whether to allow simultaneous recognition. Operations by the delegate (sometimes with the coordinated action of the delegates of other gesture recognizers) also coordinate the operation of two or more gesture recognizers by controlling which gesture recognizers receive which touches, by determining which gesture recognizer is allowed to transition to the “event recognized” or “event began” state, and by allowing or disabling simultaneous recognition.
In
The software application (e.g., application 132-1) detects (535) one or more touches, and processes (546) each of the one or more touches, using one or more of the gesture recognizers. In processing each of the one or more touches, the software application identifies (548) a set of candidate gesture recognizers of the plurality of gesture recognizers. In some embodiments, the candidate gesture recognizers are gesture recognizers attached to the hit view (e.g., gesture recognizers 516-1, 516-2, and 516-3 in
The delegate assigned to a respective candidate gesture recognizer is executed (550) to obtain a “receive touch value” in accordance with the application state. The “receive touch value” is used to determine whether the respective candidate gesture recognizer can receive the event/touch information (e.g., “should receive” step 450 in
Based on the receive touch value obtained from a respective delegate, a set of receiving gesture recognizers is identified (552). The set of receiving gesture recognizers comprise (552) a subset of the candidate gesture recognizers. In some embodiments, the set of receiving gesture recognizers include all candidate gesture recognizers that do not have respective assigned delegates. If more than one of the candidate gesture recognizers has a corresponding delegate, the delegate of each such candidate gesture recognizer is executed to determine whether the candidate gesture recognizer can receive the event/touch information. The “receive touch values” obtained from the delegates corresponding to the candidate gesture recognizers are used to identify the set of receiving gesture recognizers.
The respective touch is processed (554) at the set of receiving gesture recognizers. If processing of the respective touch by a respective gesture recognizer results in the recognition of an event or gesture (see match definition 453,
In other words, in these embodiments, a software application (or the operating system 118 or control application 124) invokes the delegates corresponding to respective candidate gesture recognizers to obtain values that indicate which of the respective candidate gesture recognizers (if any) should process the respective touch. In addition, other aspects of the behavior of the gesture recognizers can be further modified by the assigned delegate.
Method 600 is performed (602) at an electronic device (e.g., device 102 or 104) having one or more event sensors (e.g., 130) and configured to execute a software application (e.g., 132) that includes a plurality of views (e.g., application views 316) and an application state of the software application (e.g., 317).
The device (604) displays one or more views of the plurality of views. A respective view of the one or more displayed views includes one or more gesture recognizers (e.g., event recognizer 320-1). In some embodiments, at least a subset of the one or more displayed views includes one or more gesture recognizers, and the rest of the one or more displayed views do not include gesture recognizers.
A respective gesture recognizer of the one or more gesture recognizers has a corresponding delegate. In some embodiments, not all gesture recognizers have corresponding delegates (i.e., in some embodiments, some gesture recognizers do not have corresponding delegates). In some embodiments, the respective gesture recognizer corresponds to two or more delegates, where each delegate determines distinct values for the corresponding gesture recognizer for distinct conditions (e.g., a first delegate determines “should receive” 450, a second delegate determines “recognition blocked” 451, etc.). In some embodiments, two or more gesture recognizers correspond to (e.g., utilize) a same delegate.
In some embodiments, the device assigns (606) a respective delegate (e.g., delegate 321-1) to the respective gesture recognizer (e.g., 320-1) (e.g., see the description of step 532 in
In some embodiments, the one or more displayed views include (608) a plurality of gesture recognizers, and the device assigns distinct delegates to at least a subset of the plurality of gesture recognizers. In other words, the device may have fewer delegates than the number of gesture recognizers, since some gesture recognizers may not have assigned delegates.
The device detects (610) one or more events. In some embodiments, the device detects one or more events using sensors 130, input devices 128, and/or touch-sensitive display 156.
The device processes (612) a respective event of the one or more events using the respective gesture recognizer. The processing of the respective event includes processing the respective event at the respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer (e.g., comparing the event and gesture definitions 333 using event comparator 332), executing the corresponding delegate to determine one or more values in accordance with the application state (e.g., 540 in
In some embodiments, the delegate has instructions for determining event recognizer properties (such as “should begin”, “should receive”, and “simultaneous recognition”), and when executed, returns one or more corresponding values. In some embodiments, values for the event recognizer properties can be set by the software application in accordance with the application state. In some embodiments, the values for the properties are predefined by developers. In some embodiments, the internal properties of a respective event/gesture recognizer have default values that can be overridden by the delegate corresponding to the event/gesture recognizer.
For example, the device sends information corresponding to the respective event when the gesture recognizer is allowed to recognize the event (e.g., based on the one or more values determined by the gesture recognizer's corresponding delegate, the one or more values indicating whether the gesture recognizer can transition out of event possible state 410 to event recognized state 420 or event began state 412 or whether the gesture recognizer can simultaneously recognize the event despite the presence of a blocking gesture recognizer). In some embodiments, the device sends information corresponding to the respective event only when the event matches a corresponding gesture definition or a part thereof. Furthermore, application states or other conditions may prevent the respective gesture recognizer from sending information corresponding to the respective event.
The device executes (614) the software application (e.g., 132-1) in accordance with information, received from the respective gesture recognizer, corresponding to the respective event. For example, the software application (e.g., 132-1) includes a plurality of event handlers 322, and one or more of event handlers 322 are activated according to information received from the respective gesture recognizer (e.g., event handlers 322 listed in action-target pairs 345 are activated).
In some embodiments, the one or more event sensors (e.g., 130) include a touch-sensitive surface (e.g., 156 or a separate touch-sensitive surface) configured to detect one or more touches, and the one or more events include the one or more touches, and processing the respective event comprises processing a respective touch (616). In some embodiments, the one or more event sensors (e.g., 130) include accelerometers and the one or more events also include rotation or other movement of the electronic device.
In some embodiments, the device conditionally receives (618) the respective touch at the respective gesture recognizer in accordance with the one or more values determined by the assigned delegate. For example, the respective gesture recognizer receives the respective touch only when the one or more values (e.g., “receive touch value”) determined by the corresponding delegate allows the respective gesture recognizer to receive the respective touch (e.g., “should receive” 450 in
In some embodiments, processing the respective touch includes (620) the respective gesture recognizer disregarding the respective touch when the one or more values determined by the corresponding delegate matches predefined touch disregard criteria. In these embodiments, instead of conditionally receiving the respective touch as described in step 618, the respective gesture recognizer disregards the respective touch.
In some embodiments, processing the respective touch includes (622) blocking the respective gesture recognizer from receiving the respective touch when the one or more values determined by the corresponding delegate match predefined touch disregard criteria. In these embodiments, the gesture recognizer does not have a need for conditionally receiving or disregarding the respective touch, since the respective touch is blocked and therefore does not reach the respective gesture recognizer. In some embodiments, the blocking the respective gesture recognizer from receiving the respective touch includes instructing event dispatcher module 315 not to send event information to the corresponding gesture recognizer.
In some embodiments, processing the respective touch at the respective gesture recognizer includes (624), when the detected touch is consistent with the respective gesture definition (e.g., the respective touch matches the gesture definition or a part thereof), enabling a corresponding state transition in the respective gesture recognizer when the state transition is enabled by the corresponding delegate (e.g., “should begin” 454 in
In some embodiments, processing the respective touch at the respective gesture recognizer includes (626), when the detected touch is consistent with the respective gesture definition, conditionally enabling a corresponding state transition in the respective gesture recognizer when the state transition is enabled by the corresponding delegate. In other words, the state transition is conditionally enabled even if the corresponding delegate enables (e.g., does not block) the transition. For example, the condition for the state transition includes: whether the respective touch/event matches the gesture definition or a part thereof, whether the respective gesture recognizer is allowed to receive the respective touch/event, and/or whether the recognition of the respective touch/event is blocked.
In some embodiments, processing the respective touch at the respective gesture recognizer includes, when the detected touch is consistent with the respective gesture definition, (conditionally) disabling a corresponding state transition in the respective gesture recognizer when the state transition is prevented/disabled by another gesture recognizer that has also recognized a gesture. In particular, gesture recognizers can be paired (or grouped) so that one gesture recognizer can prevent the other gesture recognizer(s) from make a transition into event recognized state 420 or event began state 412 (e.g., when a first gesture recognizer is configured to prevent a second gesture recognizer, the first gesture recognizer, in recognizing an event/touch, prevents the second gesture recognizer from recognizing the event/touch, regardless of the values returned by the delegate corresponding to the second gesture recognizer).
In some embodiments, multiple gesture recognizers are listed based on priority (e.g., based on the sequence of the code, sequence of instantiation, view hierarchy corresponding to the respective gesture recognizer, or priority assigned by a developer or the software application). When two or more gesture recognizers simultaneously recognize a respective touch, the highest priority gesture recognizer blocks all other gesture recognizers from recognizing the respective touch.
In some embodiments, processing the respective touch at the respective gesture recognizer includes (628) simultaneously processing the gesture at a second gesture recognizer in accordance with one or more values determined by a delegate corresponding to the second gesture recognizer. For example, the delegate corresponding to the second gesture recognizer may allow the second gesture recognizer to process the gesture at the second gesture recognizer (e.g., step 452 in
In some embodiments, processing the respective touch at the respective gesture recognizer includes (630) simultaneously processing the gesture at a second gesture recognizer in accordance with one or more values determined by the delegate corresponding to the respective gesture recognizer. For example, the delegate corresponding to the gesture recognizer may allow the second gesture recognizer to process the gesture at the second gesture recognizer (e.g., steps 455 and 456 in
In some embodiments, processing the respective touch at the respective gesture recognizer includes simultaneously processing the gesture at a second gesture recognizer in accordance with values determined by the delegates corresponding respectively to the first and second gesture recognizers.
Method 700 is performed (702) at an electronic device (e.g., device 104) having a touch-sensitive surface (e.g., 156) and configured to execute a software application that includes a plurality of views (e.g., 316) and an application state of the software application (e.g., 317).
The device displays (704) one or more views of the plurality of views (e.g., 316). A respective view of the one or more displayed views includes one or more gesture recognizers (e.g., 320-1 or 343-2), and a respective gesture recognizer of the one or more gesture recognizers has a corresponding delegate (e.g., 321-1 or 346).
The device detects (706) one or more touches, on the touch-sensitive surface (e.g., 156 or 130). The one or more touches have a touch position that falls within one or more of the displayed views.
The device processes (708) a respective touch of the one or more touches (e.g., determining (453) whether the respective touch matches gesture definitions 333 by using event comparator 332). The processing a respective touch includes: executing (710) the delegate corresponding to the respective gesture recognizer to obtain a receive touch value in accordance with the application state (e.g., 550 in
In some embodiments, the plurality of views includes (712) a plurality of gesture recognizers (e.g., application views 316 and recognizers 320 in
In some embodiments, identifying the set of candidate gesture recognizers of the plurality of gesture recognizers includes identifying a set of gesture recognizers attached to the hit view. Optionally, identifying the set of candidate gesture recognizers of the plurality of gesture recognizers includes identifying a set of gesture recognizers that include a gesture definition corresponding to the respective touch. Furthermore, in some embodiments, identifying the set of receiving gesture recognizers includes identifying a subset of candidate gesture recognizers for which corresponding delegates provide respective receive touch values meeting receive touch criteria (e.g., the receive touch value indicates that the corresponding gesture recognize can receive the respective touch).
In some embodiments, processing the respective touch at each gesture recognizer of the one or more receiving gesture recognizers includes (718) processing the respective touch at a respective receiving gesture recognizer having a corresponding delegate in accordance with a respective gesture definition corresponding to the respective gesture recognizer, executing the delegate to determine one or more values in accordance with the application state, and conditionally sending information corresponding to the respective touch to the software application in accordance with an outcome of the processing of the respective touch by the respective gesture recognizer and in accordance with the one or more values determined by the delegate. The device executes the software application in accordance with information, received from one or more of the receiving gesture recognizers, corresponding to one or more of the touches.
In some embodiments, processing the respective touch at the respective receiving gesture recognizer includes (720), when the detected touch is consistent with the respective gesture definition (e.g., the respective touch matches the gesture definition or a part thereof), enabling a corresponding state transition in the respective gesture recognizer when the state transition is enabled by the corresponding delegate (e.g., “should begin” 454 in
In some embodiments, processing the respective touch at the respective receiving gesture recognizer includes (722), when the detected touch is consistent with the respective gesture definition, conditionally enabling a corresponding state transition in the respective gesture recognizer when the state transition is enabled by the corresponding delegate. For example, the condition for the state transition includes: whether the respective touch/event matches the gesture definition or a part thereof, whether the respective gesture recognizer is allowed to receive the respective touch/event, whether the recognition of the respective touch/event is blocked, and/or whether system level instructions (e.g., a shutdown process or other process having higher priority than the application) prevent the state transition.
In some embodiments, processing the respective touch at the respective receiving gesture recognizer includes (724) simultaneously processing the gesture at a second gesture recognizer in accordance with one or more values determined by the delegate corresponding to the second gesture recognizer. For example, the delegate corresponding to the second gesture recognizer may allow the second gesture recognizer to process the gesture at the second gesture recognizer (e.g., step 452 in
In some embodiments, processing the respective touch at the respective receiving gesture recognizer includes (726) simultaneously processing the gesture at a second gesture recognizer in accordance with one or more values determined by the delegate corresponding to the respective gesture recognizer (e.g., steps 455 and 456 in
The device executes (716) the software application in accordance with information, received from the respective gesture recognizer, corresponding to the respective touch (e.g., 545). For example, the software application (e.g., 132-1) includes a plurality of event handlers 322, and one or more of event handlers 322 are activated according to information received from the respective gesture recognizer (e.g., event handlers 322 listed in action-target pairs 345 are activated).
Method 800 is performed (802) at an electronic device (e.g., device 104) having a touch-sensitive surface and configured to execute a software application.
The device displays (804) one or more views (e.g., 316) of the software application (e.g., 132-1). The one or more displayed views include a plurality of gesture recognizers (e.g., 320). The plurality of gesture recognizers includes at least one discrete gesture recognizer (e.g.,
In some embodiments, the discrete gesture recognizer is configured (806) to send a single action message in response to a respective gesture, and the continuous gesture recognizer configured to send action messages at successive recognized sub-events of a respective recognized gesture.
In some embodiments, a discrete gesture recognizer is configured to send a single set of action messages in response to a respective gesture. When a plurality of target-action pairs are assigned to the respective discrete gesture recognizer, the single set of action messages includes a plurality of action messages. When a single target-action pair is assigned to the respective discrete gesture recognizer, the single set of action messages includes a single action message.
In some embodiments, each gesture recognizer has (822) a set of gesture recognizer states (e.g.,
In some embodiments, the discrete gesture recognizer has (824) a first set of gesture recognizer states including:
In some embodiments, the continuous gesture recognizer has a second set of gesture recognizer states including:
In some embodiments, gesture recognizer states have assigned values (e.g., gesture recognizer state values). In some embodiments, the gesture recognized state and the gesture ended state have (826) an identical gesture recognizer state value.
In some embodiments, the at least one discrete gesture recognizer includes (828): one or more of a tap gesture recognizer, and a swipe gesture recognizer; and the at least one continuous gesture recognizer includes: one or more of a long press gesture recognizer, a pinch gesture recognizer, a pan gesture recognizer, a rotate gesture recognizer, and a transform gesture recognizer.
In some embodiments, the at least one discrete gesture recognizer includes (830): a tap gesture recognizer, and a swipe gesture recognizer; and the at least one continuous gesture recognizer includes: a long press gesture recognizer, a pinch gesture recognizer, a pan gesture recognizer, a rotate gesture recognizer, and a transform gesture recognizer.
A tap gesture recognizer is configured to recognize a tap gesture; a swipe gesture recognizer is configured to recognize a swipe gesture (e.g., a flick of a touch on a touch-sensitive surface); a long press gesture recognizer is configured to recognize a long press gesture (e.g., a press and hold of a touch); a pinch gesture recognizer is configured to recognize a pinch gesture (e.g., contact and relative movement of two or more touches); a pan gesture recognizer is configured to recognize a pan gesture (e.g., touch and coherent movement of one or more touches); a rotate gesture recognizer is configured to recognize a rotation (e.g., contact and rotational movement of two or more touches); and a transform gesture recognizer is configured to recognize a transform gesture (e.g., a simultaneous movement of two or more touches representing panning, rotation, and pinch).
In some embodiments, at least one discrete gesture recognizer (e.g., one or more of the aforementioned discrete gesture recognizers) and at least one continuous gesture recognizer (e.g., one or more of the aforementioned continuous gesture recognizers) are distributed in a software library such that software developers can incorporate them into any third party software using the software library. In comparison, views have view styles (e.g., color, size, and shape of user interface objects and frames). In some embodiments, predefined view styles are distributed as a part of UI Interface API (e.g., 204 in
The device detects (808 in
The device processes (810) each of the touches using one or more of the gesture recognizers. The processing of a respective touch includes (812) processing the respective touch at a respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer (e.g., comparing the event and gesture definitions 333 using event comparator 332 and determining whether the event matches the gesture definitions 333 or a part thereof), and conditionally sending one or more respective action messages to the software application in accordance with an outcome of the processing of the respective touch at the respective gesture recognizer (e.g., sending an action message when the respective touch matches the gesture definition).
In some embodiments, the software application has (814) an application state. Conditionally sending the one or more respective action messages includes conditionally sending the one or more respective action messages further in accordance with the application state of the software application. For example, the application state of the software application may delay or prevent sending the one or more respective action messages (e.g., when the system resources are overused, when a higher priority process needs to be processed, etc.).
The device executes (816) the software application in accordance with one or more action messages received from one or more of the gesture recognizers corresponding to one or more of the touches. For example, the software application (e.g., 132-1) includes a plurality of event handlers 322, and one or more of event handlers 322 are activated according to action message received from one or more of the gesture recognizers.
In some embodiments, the device requests (818) additional information from the respective gesture recognizer. Executing the software application includes executing the software application further in accordance with the additional information. For example, the respective gesture recognizer can provide additional information (e.g., detailed information, such as a time stamp for each sub-event, the amount of jitter, speed, direction, duration, scale factor, angle, etc.).
In some embodiments, the additional information includes (820) the number and locations of respective touches processed at the respective gesture recognizer.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. patent application Ser. No. 12/789,695, filed May 28, 2010, which claims priority to U.S. Provisional Application Ser. No. 61/298,531, filed Jan. 26, 2010, entitled “Gesture Recognizers with Delegates for Controlling and Modifying Gesture Recognition,” each of which is incorporated herein by reference in its entirety. This relates to the following application, which is hereby incorporated by reference: U.S. patent application Ser. No. 12/566,660, “Event Recognition,” filed Sep. 24, 2009, now U.S. Pat. No. 8,285,499, which in turn claims priority to U.S. Provisional Patent Application No. 61/210,332, “Event Recognition,” filed on Mar. 16, 2009, which are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4455452 | Schuyler | Jun 1984 | A |
| 4674066 | Kucera | Jun 1987 | A |
| 5046434 | Breezer et al. | Sep 1991 | A |
| 5233547 | Kapp et al. | Aug 1993 | A |
| 5252951 | Tannenbaum et al. | Oct 1993 | A |
| 5454960 | Newsom | Oct 1995 | A |
| 5463725 | Henckel et al. | Oct 1995 | A |
| 5488204 | Mead et al. | Jan 1996 | A |
| 5495566 | Kwatinez | Feb 1996 | A |
| 5513309 | Meier et al. | Apr 1996 | A |
| 5530861 | Diamant et al. | Jun 1996 | A |
| 5534893 | Hansen, Jr. et al. | Jul 1996 | A |
| 5564112 | Hayes et al. | Oct 1996 | A |
| 5566337 | Szymanski et al. | Oct 1996 | A |
| 5570113 | Zetts | Oct 1996 | A |
| 5583543 | Takahashi et al. | Dec 1996 | A |
| 5589856 | Stein et al. | Dec 1996 | A |
| 5612719 | Beernick et al. | Mar 1997 | A |
| 5627567 | Davidson | May 1997 | A |
| 5627959 | Brown et al. | May 1997 | A |
| 5655094 | Cline et al. | Aug 1997 | A |
| 5676064 | Shuert | Oct 1997 | A |
| 5686940 | Kuga | Nov 1997 | A |
| 5698822 | Haneda et al. | Dec 1997 | A |
| 5708460 | Young et al. | Jan 1998 | A |
| 5745116 | Pisthua-Arnond | Apr 1998 | A |
| 5777605 | Yoshinobu et al. | Apr 1998 | A |
| 5798752 | Buxton et al. | Aug 1998 | A |
| 5818455 | Stone et al. | Oct 1998 | A |
| 5844547 | Minakuchi et al. | Dec 1998 | A |
| 5854853 | Wang | Dec 1998 | A |
| 5864636 | Chisaka | Jan 1999 | A |
| 5867158 | Murasaki et al. | Feb 1999 | A |
| 5880411 | Gillespie et al. | Mar 1999 | A |
| 5903902 | Orr et al. | May 1999 | A |
| 5917477 | Lee | Jun 1999 | A |
| 5959629 | Masui | Sep 1999 | A |
| 5999176 | Kamper | Dec 1999 | A |
| 6028602 | Weidenfeller et al. | Feb 2000 | A |
| 6034688 | Greenwood et al. | Mar 2000 | A |
| 6035343 | Tsushima et al. | Mar 2000 | A |
| 6049326 | Beyda et al. | Apr 2000 | A |
| 6061063 | Wagner et al. | May 2000 | A |
| 6089371 | Lin | Jul 2000 | A |
| 6141018 | Beri et al. | Oct 2000 | A |
| 6188391 | Seely et al. | Feb 2001 | B1 |
| 6259436 | Moon et al. | Jul 2001 | B1 |
| 6281886 | Ranieri | Aug 2001 | B1 |
| 6282316 | Arai | Aug 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6369821 | Merrill et al. | Apr 2002 | B2 |
| 6377965 | Hachamovitch et al. | Apr 2002 | B1 |
| 6446083 | Leight et al. | Sep 2002 | B1 |
| 6448986 | Smith | Sep 2002 | B1 |
| 6486896 | Ubillos | Nov 2002 | B1 |
| 6489951 | Wong et al. | Dec 2002 | B1 |
| 6498590 | Dietz et al. | Dec 2002 | B1 |
| 6559869 | Lui et al. | May 2003 | B1 |
| 6567102 | Kung | May 2003 | B2 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6570594 | Wagner | May 2003 | B1 |
| 6590595 | Wagner et al. | Jul 2003 | B1 |
| 6628835 | Brill et al. | Sep 2003 | B1 |
| 6631501 | Jurion et al. | Oct 2003 | B1 |
| 6636242 | Bowman-Amuah | Oct 2003 | B2 |
| 6639584 | Li | Oct 2003 | B1 |
| 6661409 | Demartines et al. | Dec 2003 | B2 |
| 6664989 | Snyder et al. | Dec 2003 | B1 |
| 6664991 | Chew et al. | Dec 2003 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6677965 | Ullmann et al. | Jan 2004 | B1 |
| 6690387 | Zimmerman et al. | Feb 2004 | B2 |
| 6707449 | Hinckley et al. | Mar 2004 | B2 |
| 6714221 | Christie et al. | Mar 2004 | B1 |
| 6714936 | Nevin, III | Mar 2004 | B1 |
| 6735583 | Bjarnestam et al. | May 2004 | B1 |
| 6741996 | Brechner et al. | May 2004 | B1 |
| 6757673 | Makus et al. | Jun 2004 | B2 |
| 6765557 | Segal et al. | Jul 2004 | B1 |
| 6778992 | Searle et al. | Aug 2004 | B1 |
| 6809724 | Shiraishi et al. | Oct 2004 | B1 |
| 6819315 | Toepke et al. | Nov 2004 | B2 |
| 6820237 | Abu-Hakima et al. | Nov 2004 | B1 |
| 6831631 | Chuang | Dec 2004 | B2 |
| 6839721 | Schwols | Jan 2005 | B2 |
| 6856326 | Zhai | Feb 2005 | B1 |
| 6868383 | Bangalore et al. | Mar 2005 | B1 |
| 6903927 | Anlauff | Jun 2005 | B2 |
| 6907575 | Duarte | Jun 2005 | B2 |
| 6912462 | Ogaki | Jun 2005 | B2 |
| 6957392 | Simister et al. | Oct 2005 | B2 |
| 6958749 | Matsushita | Oct 2005 | B1 |
| 6963937 | Kamper et al. | Nov 2005 | B1 |
| 6972776 | Davis et al. | Dec 2005 | B2 |
| 6975306 | Hinckley et al. | Dec 2005 | B2 |
| 6985137 | Kaikuranta | Jan 2006 | B2 |
| 6985178 | Morita et al. | Jan 2006 | B1 |
| 7009599 | Pihlaja | Mar 2006 | B2 |
| 7009626 | Anwar | Mar 2006 | B2 |
| 7013435 | Gallo et al. | Mar 2006 | B2 |
| 7023427 | Kraus et al. | Apr 2006 | B2 |
| 7030861 | Westerman et al. | Apr 2006 | B1 |
| 7030863 | Longe et al. | Apr 2006 | B2 |
| 7036094 | Cohen et al. | Apr 2006 | B1 |
| 7046230 | Zadesky et al. | May 2006 | B2 |
| 7062090 | Simmons et al. | Jun 2006 | B2 |
| 7075512 | Fabre et al. | Jul 2006 | B1 |
| 7084859 | Pryor | Aug 2006 | B1 |
| 7088374 | David et al. | Aug 2006 | B2 |
| 7102626 | Denny, III | Sep 2006 | B2 |
| 7117453 | Drucker et al. | Oct 2006 | B2 |
| 7152210 | Van Den Hoven et al. | Dec 2006 | B1 |
| 7154534 | Seki et al. | Dec 2006 | B2 |
| 7155048 | Ohara | Dec 2006 | B2 |
| 7171353 | Trower, II et al. | Jan 2007 | B2 |
| 7173623 | Calkins et al. | Feb 2007 | B2 |
| 7181373 | Le Cocq et al. | Feb 2007 | B2 |
| 7184796 | Karidis et al. | Feb 2007 | B2 |
| 7237199 | Menhardt et al. | Jun 2007 | B1 |
| 7240291 | Card et al. | Jul 2007 | B2 |
| 7337412 | Guido et al. | Feb 2008 | B2 |
| 7346850 | Swartz et al. | Mar 2008 | B2 |
| 7358965 | Barabe et al. | Apr 2008 | B2 |
| 7385592 | Collins | Jun 2008 | B2 |
| 7406696 | Burger et al. | Jul 2008 | B2 |
| 7420543 | Jayachandra | Sep 2008 | B2 |
| 7469381 | Ording | Dec 2008 | B2 |
| 7487447 | Jerger | Feb 2009 | B1 |
| 7499027 | Brigham, II et al. | Mar 2009 | B2 |
| 7561159 | Abel et al. | Jul 2009 | B2 |
| 7564448 | Yi | Jul 2009 | B2 |
| 7576732 | Lii | Aug 2009 | B2 |
| 7603143 | Kang et al. | Oct 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7673255 | Schechter et al. | Mar 2010 | B2 |
| 7694231 | Kocienda et al. | Apr 2010 | B2 |
| 7724242 | Hillis et al. | May 2010 | B2 |
| 7739604 | Lyons et al. | Jun 2010 | B1 |
| 7750893 | Hashimoto et al. | Jul 2010 | B2 |
| 7761541 | Morley et al. | Jul 2010 | B1 |
| 7778818 | Longe et al. | Aug 2010 | B2 |
| 7782307 | Westerman et al. | Aug 2010 | B2 |
| 7786975 | Ording et al. | Aug 2010 | B2 |
| 7812826 | Ording et al. | Oct 2010 | B2 |
| 7843427 | Ording et al. | Nov 2010 | B2 |
| 7844915 | Platzer et al. | Nov 2010 | B2 |
| 7864037 | Miller | Jan 2011 | B2 |
| 7872652 | Platzer et al. | Jan 2011 | B2 |
| 7900156 | Andre et al. | Mar 2011 | B2 |
| 7903115 | Platzer et al. | Mar 2011 | B2 |
| 7907125 | Weiss et al. | Mar 2011 | B2 |
| 7917584 | Arthursson | Mar 2011 | B2 |
| 7925996 | Hofmeister et al. | Apr 2011 | B2 |
| 7941760 | Kocienda et al. | May 2011 | B2 |
| 7962862 | Kulp et al. | Jun 2011 | B2 |
| 7966578 | Tolmasky et al. | Jun 2011 | B2 |
| 8051406 | Knight et al. | Nov 2011 | B2 |
| 8091045 | Christie et al. | Jan 2012 | B2 |
| 8112299 | Kim et al. | Feb 2012 | B2 |
| 8115744 | Kong et al. | Feb 2012 | B2 |
| 8135171 | Ho et al. | Mar 2012 | B2 |
| 8140570 | Ingrassia et al. | Mar 2012 | B2 |
| 8171432 | Matas et al. | May 2012 | B2 |
| 8174502 | Bolsinga et al. | May 2012 | B2 |
| 8214768 | Boule | Jul 2012 | B2 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8253695 | Ganatra et al. | Aug 2012 | B2 |
| 8285499 | Moore et al. | Oct 2012 | B2 |
| 8289289 | Rimon et al. | Oct 2012 | B2 |
| 8291344 | Chaudhri | Oct 2012 | B2 |
| 8296332 | Boley et al. | Oct 2012 | B2 |
| 8310459 | Nurmi | Nov 2012 | B2 |
| 8314775 | Westerman et al. | Nov 2012 | B2 |
| 8400416 | Ho et al. | Mar 2013 | B2 |
| 8411060 | Scholler et al. | Apr 2013 | B1 |
| 8416196 | Williamson et al. | Apr 2013 | B2 |
| 8428893 | Moore et al. | Apr 2013 | B2 |
| 8434003 | Zalewski et al. | Apr 2013 | B2 |
| 8436815 | Mazeev et al. | May 2013 | B2 |
| 8436821 | Plichta | May 2013 | B1 |
| 8489783 | Wilson | Jul 2013 | B2 |
| 8560975 | Beaver et al. | Oct 2013 | B2 |
| 8566044 | Shaffer et al. | Oct 2013 | B2 |
| 8566045 | Shaffer et al. | Oct 2013 | B2 |
| 8570277 | Rekimoto | Oct 2013 | B2 |
| 8645827 | Beaver et al. | Feb 2014 | B2 |
| 8656311 | Harper | Feb 2014 | B1 |
| 8676824 | Tavor | Mar 2014 | B2 |
| 8682602 | Moore et al. | Mar 2014 | B2 |
| 8775820 | Freeburne | Jul 2014 | B1 |
| 9285908 | Moore et al. | Mar 2016 | B2 |
| 9311112 | Shaffer | Apr 2016 | B2 |
| 9389712 | Beaver | Jul 2016 | B2 |
| 9684521 | Shaffer | Jun 2017 | B2 |
| 9690481 | Beaver | Jun 2017 | B2 |
| 9720594 | Beaver et al. | Aug 2017 | B2 |
| 9965177 | Moore | May 2018 | B2 |
| 10521109 | Beaver | Dec 2019 | B2 |
| 20010009033 | Morisaki et al. | Jul 2001 | A1 |
| 20010011998 | Agata et al. | Aug 2001 | A1 |
| 20010012001 | Rekimoto et al. | Aug 2001 | A1 |
| 20010028369 | Gallo et al. | Oct 2001 | A1 |
| 20010045949 | Chithambaram et al. | Nov 2001 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020015064 | Robotham et al. | Feb 2002 | A1 |
| 20020025024 | Tybinkowski et al. | Feb 2002 | A1 |
| 20020036618 | Wakai et al. | Mar 2002 | A1 |
| 20020101418 | Vernier et al. | Aug 2002 | A1 |
| 20020171675 | Fox et al. | Nov 2002 | A1 |
| 20020191029 | Gillespie et al. | Dec 2002 | A1 |
| 20020194589 | Cristofalo et al. | Dec 2002 | A1 |
| 20030063073 | Geaghan et al. | Apr 2003 | A1 |
| 20030071850 | Geidl | Apr 2003 | A1 |
| 20030071858 | Morohoshi | Apr 2003 | A1 |
| 20030080946 | Chuang | May 2003 | A1 |
| 20030095096 | Robbin et al. | May 2003 | A1 |
| 20030095135 | Kaasila et al. | May 2003 | A1 |
| 20030095697 | Wood et al. | May 2003 | A1 |
| 20030122787 | Zimmerman et al. | Jul 2003 | A1 |
| 20030132959 | Simister et al. | Jul 2003 | A1 |
| 20030146941 | Bailey et al. | Aug 2003 | A1 |
| 20030160832 | Ridgley et al. | Aug 2003 | A1 |
| 20030174149 | Fujisaki et al. | Sep 2003 | A1 |
| 20030184525 | Tsai | Oct 2003 | A1 |
| 20030197689 | May | Oct 2003 | A1 |
| 20030197744 | Irvine | Oct 2003 | A1 |
| 20030210258 | Williams | Nov 2003 | A1 |
| 20030214531 | Chambers et al. | Nov 2003 | A1 |
| 20030214553 | Dodge | Nov 2003 | A1 |
| 20030217336 | Gounares et al. | Nov 2003 | A1 |
| 20030222917 | Trantow | Dec 2003 | A1 |
| 20040001627 | Simmons et al. | Jan 2004 | A1 |
| 20040021676 | Chen et al. | Feb 2004 | A1 |
| 20040021698 | Baldwin et al. | Feb 2004 | A1 |
| 20040025115 | Sienel et al. | Feb 2004 | A1 |
| 20040027398 | Jaeger | Feb 2004 | A1 |
| 20040030914 | Kelley et al. | Feb 2004 | A1 |
| 20040039474 | Kontani | Feb 2004 | A1 |
| 20040070573 | Graham | Apr 2004 | A1 |
| 20040080541 | Saiga et al. | Apr 2004 | A1 |
| 20040095387 | Demsey et al. | May 2004 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040111672 | Bowman et al. | Jun 2004 | A1 |
| 20040125136 | Wallenius | Jul 2004 | A1 |
| 20040135817 | Daughtery et al. | Jul 2004 | A1 |
| 20040155888 | Padgitt et al. | Aug 2004 | A1 |
| 20040160419 | Padgitt | Aug 2004 | A1 |
| 20040189721 | Pettiross et al. | Sep 2004 | A1 |
| 20040207542 | Chang et al. | Oct 2004 | A1 |
| 20040210847 | Berson et al. | Oct 2004 | A1 |
| 20040215643 | Brechner et al. | Oct 2004 | A1 |
| 20040221168 | Girard | Nov 2004 | A1 |
| 20040222992 | Calkins et al. | Nov 2004 | A1 |
| 20040224638 | Fadell et al. | Nov 2004 | A1 |
| 20040225965 | Garside et al. | Nov 2004 | A1 |
| 20040263486 | Seni | Dec 2004 | A1 |
| 20050005241 | Hunleth et al. | Jan 2005 | A1 |
| 20050008343 | Frohlich et al. | Jan 2005 | A1 |
| 20050012723 | Pallakoff | Jan 2005 | A1 |
| 20050017957 | Yi | Jan 2005 | A1 |
| 20050024341 | Gillespie et al. | Feb 2005 | A1 |
| 20050027666 | Beck, Jr. et al. | Feb 2005 | A1 |
| 20050057524 | Hill et al. | Mar 2005 | A1 |
| 20050078088 | Davis et al. | Apr 2005 | A1 |
| 20050088443 | Blanco et al. | Apr 2005 | A1 |
| 20050122806 | Arakawa et al. | Jun 2005 | A1 |
| 20050145807 | Lapstun et al. | Jul 2005 | A1 |
| 20050162402 | Watanachote | Jul 2005 | A1 |
| 20050168488 | Montague | Aug 2005 | A1 |
| 20050179648 | Barabe et al. | Aug 2005 | A1 |
| 20050183035 | Ringel et al. | Aug 2005 | A1 |
| 20050193015 | Logston et al. | Sep 2005 | A1 |
| 20050195154 | Robbins et al. | Sep 2005 | A1 |
| 20050198588 | Lin et al. | Sep 2005 | A1 |
| 20050210419 | Kela et al. | Sep 2005 | A1 |
| 20050212767 | Marvit et al. | Sep 2005 | A1 |
| 20050237308 | Autio | Oct 2005 | A1 |
| 20050268247 | Baneth | Dec 2005 | A1 |
| 20050270269 | Tokkonen | Dec 2005 | A1 |
| 20050275618 | Juh et al. | Dec 2005 | A1 |
| 20050275636 | Dehlin et al. | Dec 2005 | A1 |
| 20060010400 | Dehlin et al. | Jan 2006 | A1 |
| 20060022956 | Lengeling et al. | Feb 2006 | A1 |
| 20060025218 | Hotta | Feb 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060026676 | O'Donoghue | Feb 2006 | A1 |
| 20060028455 | Hinckley et al. | Feb 2006 | A1 |
| 20060031786 | Hillis et al. | Feb 2006 | A1 |
| 20060036955 | Baudisch et al. | Feb 2006 | A1 |
| 20060038796 | Hinckley et al. | Feb 2006 | A1 |
| 20060048073 | Jarrett et al. | Mar 2006 | A1 |
| 20060055662 | Rimas-Ribikauskas et al. | Mar 2006 | A1 |
| 20060055669 | Das | Mar 2006 | A1 |
| 20060055789 | Jin et al. | Mar 2006 | A1 |
| 20060059462 | Yamamoto | Mar 2006 | A1 |
| 20060061551 | Fateh | Mar 2006 | A1 |
| 20060066588 | Lyon et al. | Mar 2006 | A1 |
| 20060077183 | Studt | Apr 2006 | A1 |
| 20060077544 | Stark | Apr 2006 | A1 |
| 20060082549 | Hoshino et al. | Apr 2006 | A1 |
| 20060094502 | Katayama et al. | May 2006 | A1 |
| 20060097991 | Hotelling et al. | May 2006 | A1 |
| 20060112335 | Hofmeister et al. | May 2006 | A1 |
| 20060123353 | Matthews et al. | Jun 2006 | A1 |
| 20060125799 | Hillis et al. | Jun 2006 | A1 |
| 20060125803 | Westerman et al. | Jun 2006 | A1 |
| 20060136833 | Dettinger et al. | Jun 2006 | A1 |
| 20060156249 | Blythe et al. | Jul 2006 | A1 |
| 20060161871 | Hotelling et al. | Jul 2006 | A1 |
| 20060176403 | Gritton et al. | Aug 2006 | A1 |
| 20060181510 | Faith | Aug 2006 | A1 |
| 20060187215 | Rosenberg et al. | Aug 2006 | A1 |
| 20060190833 | SanGiovanni et al. | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060221061 | Fry | Oct 2006 | A1 |
| 20060236263 | Bathiche et al. | Oct 2006 | A1 |
| 20060238495 | Davis | Oct 2006 | A1 |
| 20060242602 | Schechter et al. | Oct 2006 | A1 |
| 20060242607 | Hudson | Oct 2006 | A1 |
| 20060247915 | Bradford et al. | Nov 2006 | A1 |
| 20060262104 | Sullivan et al. | Nov 2006 | A1 |
| 20060262136 | Vaisanen | Nov 2006 | A1 |
| 20060271520 | Ragan | Nov 2006 | A1 |
| 20060274042 | Krah et al. | Dec 2006 | A1 |
| 20060279548 | Geaghan | Dec 2006 | A1 |
| 20060284792 | Foxlin | Dec 2006 | A1 |
| 20060288313 | Hillis | Dec 2006 | A1 |
| 20070006078 | Jewsbury et al. | Jan 2007 | A1 |
| 20070008066 | Fukuda | Jan 2007 | A1 |
| 20070013697 | Gilboa | Jan 2007 | A1 |
| 20070024646 | Saarinen et al. | Feb 2007 | A1 |
| 20070036346 | Kwon | Feb 2007 | A1 |
| 20070046643 | Hillis et al. | Mar 2007 | A1 |
| 20070050469 | Gupta et al. | Mar 2007 | A1 |
| 20070055967 | Poff et al. | Mar 2007 | A1 |
| 20070061126 | Russo et al. | Mar 2007 | A1 |
| 20070064004 | Bonner et al. | Mar 2007 | A1 |
| 20070067745 | Choi et al. | Mar 2007 | A1 |
| 20070075965 | Huppi et al. | Apr 2007 | A1 |
| 20070081726 | Westerman et al. | Apr 2007 | A1 |
| 20070089069 | Hsieh et al. | Apr 2007 | A1 |
| 20070094352 | Choi et al. | Apr 2007 | A1 |
| 20070109275 | Chuang | May 2007 | A1 |
| 20070120835 | Sato | May 2007 | A1 |
| 20070132789 | Ording et al. | Jun 2007 | A1 |
| 20070149252 | Jobs et al. | Jun 2007 | A1 |
| 20070150826 | Anzures et al. | Jun 2007 | A1 |
| 20070150842 | Chaudhri et al. | Jun 2007 | A1 |
| 20070152976 | Townsend et al. | Jul 2007 | A1 |
| 20070152978 | Kocienda et al. | Jul 2007 | A1 |
| 20070152979 | Jobs et al. | Jul 2007 | A1 |
| 20070152980 | Kocienda et al. | Jul 2007 | A1 |
| 20070152983 | McKillop et al. | Jul 2007 | A1 |
| 20070152984 | Ording et al. | Jul 2007 | A1 |
| 20070155434 | Jobs et al. | Jul 2007 | A1 |
| 20070156364 | Rothkopf | Jul 2007 | A1 |
| 20070157089 | van Os et al. | Jul 2007 | A1 |
| 20070174257 | Howard | Jul 2007 | A1 |
| 20070176903 | Dahlin et al. | Aug 2007 | A1 |
| 20070177803 | Elias et al. | Aug 2007 | A1 |
| 20070177804 | Elias et al. | Aug 2007 | A1 |
| 20070185876 | Mendis et al. | Aug 2007 | A1 |
| 20070198926 | Joguet et al. | Aug 2007 | A1 |
| 20070214436 | Myers | Sep 2007 | A1 |
| 20070214462 | Boillot | Sep 2007 | A1 |
| 20070226636 | Carpenter et al. | Sep 2007 | A1 |
| 20070236472 | Bentsen et al. | Oct 2007 | A1 |
| 20070242056 | Engelhardt et al. | Oct 2007 | A1 |
| 20070242607 | Sadler et al. | Oct 2007 | A1 |
| 20070247435 | Benko et al. | Oct 2007 | A1 |
| 20070247442 | Andre et al. | Oct 2007 | A1 |
| 20070252821 | Hollemans et al. | Nov 2007 | A1 |
| 20070262964 | Zotov et al. | Nov 2007 | A1 |
| 20070277124 | Shin et al. | Nov 2007 | A1 |
| 20070288856 | Butlin et al. | Dec 2007 | A1 |
| 20070291009 | Wright et al. | Dec 2007 | A1 |
| 20070296707 | Kang et al. | Dec 2007 | A1 |
| 20080001923 | Hall et al. | Jan 2008 | A1 |
| 20080005703 | Radivojevic et al. | Jan 2008 | A1 |
| 20080012835 | Rimon et al. | Jan 2008 | A1 |
| 20080016096 | Wilding et al. | Jan 2008 | A1 |
| 20080027642 | Winberry et al. | Jan 2008 | A1 |
| 20080028327 | Hirota et al. | Jan 2008 | A1 |
| 20080034029 | Fang et al. | Feb 2008 | A1 |
| 20080036743 | Westerman et al. | Feb 2008 | A1 |
| 20080041640 | Gillespie et al. | Feb 2008 | A1 |
| 20080043020 | Snow et al. | Feb 2008 | A1 |
| 20080048978 | Trent, Jr. et al. | Feb 2008 | A1 |
| 20080072143 | Assadollahi | Mar 2008 | A1 |
| 20080082934 | Kocienda et al. | Apr 2008 | A1 |
| 20080084400 | Rosenberg | Apr 2008 | A1 |
| 20080094356 | Ording et al. | Apr 2008 | A1 |
| 20080094368 | Ording et al. | Apr 2008 | A1 |
| 20080104544 | Collins et al. | May 2008 | A1 |
| 20080114614 | Mahesh et al. | May 2008 | A1 |
| 20080115086 | Rupp et al. | May 2008 | A1 |
| 20080120576 | Kariathungal et al. | May 2008 | A1 |
| 20080122806 | Ahn | May 2008 | A1 |
| 20080158170 | Herz et al. | Jul 2008 | A1 |
| 20080158191 | Yang et al. | Jul 2008 | A1 |
| 20080162751 | Wilson | Jul 2008 | A1 |
| 20080165022 | Herz et al. | Jul 2008 | A1 |
| 20080165132 | Weiss et al. | Jul 2008 | A1 |
| 20080165136 | Christie et al. | Jul 2008 | A1 |
| 20080165140 | Christie et al. | Jul 2008 | A1 |
| 20080165141 | Christie | Jul 2008 | A1 |
| 20080165160 | Kocienda et al. | Jul 2008 | A1 |
| 20080165161 | Platzer | Jul 2008 | A1 |
| 20080166049 | Wang et al. | Jul 2008 | A1 |
| 20080168384 | Platzer et al. | Jul 2008 | A1 |
| 20080168388 | Decker | Jul 2008 | A1 |
| 20080168395 | Ording et al. | Jul 2008 | A1 |
| 20080168402 | Blumenberg | Jul 2008 | A1 |
| 20080168405 | Tolmasky et al. | Jul 2008 | A1 |
| 20080168478 | Platzer et al. | Jul 2008 | A1 |
| 20080172633 | Jeon et al. | Jul 2008 | A1 |
| 20080195388 | Bower et al. | Aug 2008 | A1 |
| 20080207130 | Kunii | Aug 2008 | A1 |
| 20080218489 | Park et al. | Sep 2008 | A1 |
| 20080225014 | Kim | Sep 2008 | A1 |
| 20080231610 | Hotelling et al. | Sep 2008 | A1 |
| 20080316178 | Caliksan et al. | Dec 2008 | A1 |
| 20080316183 | Westerman et al. | Dec 2008 | A1 |
| 20090037849 | Immonen et al. | Feb 2009 | A1 |
| 20090048000 | Ade-Hall | Feb 2009 | A1 |
| 20090049388 | Taib et al. | Feb 2009 | A1 |
| 20090051671 | Konstas | Feb 2009 | A1 |
| 20090058820 | Hinckley | Mar 2009 | A1 |
| 20090058830 | Herz et al. | Mar 2009 | A1 |
| 20090063135 | Fux et al. | Mar 2009 | A1 |
| 20090064047 | Shim et al. | Mar 2009 | A1 |
| 20090070098 | Patryshev | Mar 2009 | A1 |
| 20090207140 | Hansson | Aug 2009 | A1 |
| 20090211891 | Lai et al. | Aug 2009 | A1 |
| 20090225037 | Williamson et al. | Sep 2009 | A1 |
| 20090225038 | Bolsinga et al. | Sep 2009 | A1 |
| 20090225039 | Williamson et al. | Sep 2009 | A1 |
| 20090225041 | Kida et al. | Sep 2009 | A1 |
| 20090228828 | Beatty et al. | Sep 2009 | A1 |
| 20090228901 | Beaver et al. | Sep 2009 | A1 |
| 20090231281 | Whytock et al. | Sep 2009 | A1 |
| 20090244020 | Sjolin | Oct 2009 | A1 |
| 20090251434 | Rimon et al. | Oct 2009 | A1 |
| 20090259969 | Pallakoff | Oct 2009 | A1 |
| 20090262087 | Kim | Oct 2009 | A1 |
| 20090271704 | Cohen | Oct 2009 | A1 |
| 20090273571 | Bowens | Nov 2009 | A1 |
| 20090282332 | Porat | Nov 2009 | A1 |
| 20090284479 | Dennis et al. | Nov 2009 | A1 |
| 20090300530 | Falchuk | Dec 2009 | A1 |
| 20090303187 | Pallakoff | Dec 2009 | A1 |
| 20090304281 | Yipu | Dec 2009 | A1 |
| 20090309847 | Russell et al. | Dec 2009 | A1 |
| 20090322687 | Duncan et al. | Dec 2009 | A1 |
| 20090322699 | Hansson | Dec 2009 | A1 |
| 20090322700 | D'Souza et al. | Dec 2009 | A1 |
| 20100013676 | Do et al. | Jan 2010 | A1 |
| 20100020025 | Lemort et al. | Jan 2010 | A1 |
| 20100020221 | Tupman et al. | Jan 2010 | A1 |
| 20100030612 | Kim et al. | Feb 2010 | A1 |
| 20100046850 | Ho et al. | Feb 2010 | A1 |
| 20100060666 | Fong | Mar 2010 | A1 |
| 20100066676 | Kramer et al. | Mar 2010 | A1 |
| 20100085323 | Bogue | Apr 2010 | A1 |
| 20100107116 | Rieman et al. | Apr 2010 | A1 |
| 20100146458 | Wadekar | Jun 2010 | A1 |
| 20100149122 | Lin | Jun 2010 | A1 |
| 20100156804 | Young | Jun 2010 | A1 |
| 20100169841 | Singh | Jul 2010 | A1 |
| 20100177053 | Yasutake | Jul 2010 | A2 |
| 20100182246 | Petschnigg et al. | Jul 2010 | A1 |
| 20100182248 | Chun | Jul 2010 | A1 |
| 20100188328 | Dodge et al. | Jul 2010 | A1 |
| 20100235118 | Moore et al. | Sep 2010 | A1 |
| 20100235745 | Shintani | Sep 2010 | A1 |
| 20100245267 | Min et al. | Sep 2010 | A1 |
| 20100267449 | Gagner et al. | Oct 2010 | A1 |
| 20100281435 | Bangalore et al. | Nov 2010 | A1 |
| 20100283739 | Zhang et al. | Nov 2010 | A1 |
| 20100299594 | Zalewski et al. | Nov 2010 | A1 |
| 20100309147 | Fleizach et al. | Dec 2010 | A1 |
| 20100325575 | Platzer et al. | Dec 2010 | A1 |
| 20110037714 | Seo et al. | Feb 2011 | A1 |
| 20110047459 | Van Der Westhuizen | Feb 2011 | A1 |
| 20110069021 | Hill | Mar 2011 | A1 |
| 20110090257 | Ko et al. | Apr 2011 | A1 |
| 20110102336 | Seok et al. | May 2011 | A1 |
| 20110102464 | Godavari | May 2011 | A1 |
| 20110115745 | Cabrera Cordon | May 2011 | A1 |
| 20110167391 | Momeyer et al. | Jul 2011 | A1 |
| 20110179380 | Shaffer et al. | Jul 2011 | A1 |
| 20110179386 | Shaffer et al. | Jul 2011 | A1 |
| 20110179387 | Shaffer et al. | Jul 2011 | A1 |
| 20110181526 | Shaffer et al. | Jul 2011 | A1 |
| 20110242032 | Seo et al. | Oct 2011 | A1 |
| 20110252306 | Williamson et al. | Oct 2011 | A1 |
| 20110252307 | Williamson et al. | Oct 2011 | A1 |
| 20110252368 | Anzures et al. | Oct 2011 | A1 |
| 20110258537 | Rives et al. | Oct 2011 | A1 |
| 20110291951 | Tong | Dec 2011 | A1 |
| 20110295596 | Hung et al. | Dec 2011 | A1 |
| 20110298724 | Ameling | Dec 2011 | A1 |
| 20110304550 | Romera Jolliff | Dec 2011 | A1 |
| 20110304560 | Dale et al. | Dec 2011 | A1 |
| 20110307833 | Dale et al. | Dec 2011 | A1 |
| 20110310046 | Beaver et al. | Dec 2011 | A1 |
| 20110310047 | Moore et al. | Dec 2011 | A1 |
| 20110314429 | Blumenberg | Dec 2011 | A1 |
| 20110314430 | Blumenberg | Dec 2011 | A1 |
| 20110321125 | Kyohgoku et al. | Dec 2011 | A1 |
| 20120023443 | Blumenberg | Jan 2012 | A1 |
| 20120023460 | Blumenberg | Jan 2012 | A1 |
| 20120023461 | Blumenberg | Jan 2012 | A1 |
| 20120023509 | Blumenberg | Jan 2012 | A1 |
| 20120026104 | Ho et al. | Feb 2012 | A1 |
| 20120092286 | O'Prey | Apr 2012 | A1 |
| 20120098768 | Bendewald et al. | Apr 2012 | A1 |
| 20120133579 | Prieur et al. | May 2012 | A1 |
| 20120169593 | Mak | Jul 2012 | A1 |
| 20120221929 | Bolsinga et al. | Aug 2012 | A1 |
| 20120242584 | Tuli | Sep 2012 | A1 |
| 20120256849 | Crumly | Oct 2012 | A1 |
| 20120278725 | Gordon et al. | Nov 2012 | A1 |
| 20120299852 | Hsu et al. | Nov 2012 | A1 |
| 20120304133 | Nan et al. | Nov 2012 | A1 |
| 20130009986 | Shah et al. | Jan 2013 | A1 |
| 20130016039 | Moore et al. | Jan 2013 | A1 |
| 20130069899 | Beaver et al. | Mar 2013 | A1 |
| 20130120280 | Kukulski | May 2013 | A1 |
| 20130135217 | Honji | May 2013 | A1 |
| 20130239046 | Platzer et al. | Sep 2013 | A1 |
| 20130244574 | Okuno et al. | Sep 2013 | A1 |
| 20130246861 | Colley et al. | Sep 2013 | A1 |
| 20130275888 | Williamson et al. | Oct 2013 | A1 |
| 20140033131 | Shaffer et al. | Jan 2014 | A1 |
| 20140145995 | Beaver et al. | May 2014 | A1 |
| 20140160052 | Moore et al. | Jun 2014 | A1 |
| 20140173419 | Williamson | Jun 2014 | A1 |
| 20140181731 | Plater et al. | Jun 2014 | A1 |
| 20140189716 | George | Jul 2014 | A1 |
| 20140310661 | Frederickson et al. | Oct 2014 | A1 |
| 20140361982 | Shaffer | Dec 2014 | A1 |
| 20160018981 | Amerige et al. | Jan 2016 | A1 |
| 20160110230 | Moore et al. | Jan 2016 | A1 |
| 20160077597 | Silawan | Mar 2016 | A1 |
| 20160091977 | Ortega | Mar 2016 | A1 |
| 20160162180 | Moore et al. | Jun 2016 | A1 |
| 20160334990 | Beaver et al. | Nov 2016 | A1 |
| 20160342325 | Blumenberg | Nov 2016 | A1 |
| 20160370987 | Amerige et al. | Dec 2016 | A1 |
| 20170046063 | Shaffer et al. | Feb 2017 | A1 |
| 20170160925 | Beaver et al. | Apr 2017 | A1 |
| 20170308277 | Platzer et al. | Oct 2017 | A1 |
| 20180052522 | Shaffer | Feb 2018 | A1 |
| 20180260113 | Beaver et al. | Sep 2018 | A1 |
| 20190138181 | Blumenberg | May 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2007283771 | Apr 2007 | AU |
| 2755443 | Sep 2010 | CA |
| 1326564 | Dec 2001 | CN |
| 1331815 | Jan 2002 | CN |
| 1422481 | Jun 2003 | CN |
| 1695105 | Nov 2005 | CN |
| 1704886 | Dec 2005 | CN |
| 1797308 | Jul 2006 | CN |
| 1841284 | Oct 2006 | CN |
| 1845046 | Oct 2006 | CN |
| 1860429 | Nov 2006 | CN |
| 1942853 | Apr 2007 | CN |
| 1967458 | May 2007 | CN |
| 1969254 | May 2007 | CN |
| 101040244 | Sep 2007 | CN |
| 101052939 | Oct 2007 | CN |
| 101089804 | Dec 2007 | CN |
| 101339453 | Jan 2009 | CN |
| 101356492 | Jan 2009 | CN |
| 101410781 | Apr 2009 | CN |
| 101526880 | Sep 2009 | CN |
| 101529368 | Sep 2009 | CN |
| 101578577 | Nov 2009 | CN |
| 101636711 | Jan 2010 | CN |
| 101727240 | Jun 2010 | CN |
| 101853105 | Oct 2010 | CN |
| 102768608 | Nov 2012 | CN |
| 103109249 | May 2013 | CN |
| 202007013923 | Dec 2007 | DE |
| 202005021427 | Feb 2008 | DE |
| 0 538 705 | Apr 1993 | EP |
| 0 626 635 | Nov 1994 | EP |
| 0 635 779 | Jan 1995 | EP |
| 0 701 220 | Mar 1996 | EP |
| 0 712 825 | May 1996 | EP |
| 0 880 091 | Nov 1998 | EP |
| 1 443 395 | Aug 2004 | EP |
| 1 517 228 | Mar 2005 | EP |
| 1 171 682 | Nov 2006 | EP |
| 1 860 539 | Nov 2007 | EP |
| 2 031 837 | Mar 2009 | EP |
| 2 141 576 | Jan 2010 | EP |
| 1 964 022 | Mar 2010 | EP |
| 2 184 673 | May 2010 | EP |
| 2 354 930 | Aug 2011 | EP |
| 2 390 766 | Nov 2011 | EP |
| 2 409 222 | Jan 2012 | EP |
| 2 472 384 | Jul 2012 | EP |
| 1517521 | Jul 1978 | GB |
| 2319591 | May 1998 | GB |
| 2 351 639 | Jan 2001 | GB |
| 2351639 | Jan 2001 | GB |
| 2373778 | Oct 2002 | GB |
| 2404547 | Jul 2003 | GB |
| 02-140822 | May 1990 | JP |
| 03-271976 | Dec 1991 | JP |
| H05-019969 | Jan 1993 | JP |
| H05-298002 | Nov 1993 | JP |
| 06-149467 | May 1994 | JP |
| H06-274329 | Sep 1994 | JP |
| 08-16314 | Jan 1996 | JP |
| H09-44285 | Feb 1997 | JP |
| H09-114586 | May 1997 | JP |
| H10-500509 | Jan 1998 | JP |
| H11-085354 | Mar 1999 | JP |
| 2000-163031 | Jun 2000 | JP |
| 2000-163443 | Jun 2000 | JP |
| 2000-222130 | Aug 2000 | JP |
| 2000-322199 | Nov 2000 | JP |
| 2001-027924 | Jan 2001 | JP |
| 2001-051798 | Feb 2001 | JP |
| 2001-167227 | Jun 2001 | JP |
| 2001-290585 | Oct 2001 | JP |
| 2002-041242 | Feb 2002 | JP |
| 2002-244848 | Aug 2002 | JP |
| 2003-296024 | Oct 2003 | JP |
| 2003-330605 | Nov 2003 | JP |
| 2005-056286 | Mar 2005 | JP |
| 2005-082086 | Mar 2005 | JP |
| 2005-092476 | Apr 2005 | JP |
| 2005-100391 | Apr 2005 | JP |
| 2005-108211 | Apr 2005 | JP |
| 2005-165532 | Jun 2005 | JP |
| 2005-242669 | Sep 2005 | JP |
| 2005-275652 | Oct 2005 | JP |
| 2005-322088 | Nov 2005 | JP |
| 2006-024039 | Jan 2006 | JP |
| 2006-085356 | Mar 2006 | JP |
| 2006-085703 | Mar 2006 | JP |
| 2006-102275 | Apr 2006 | JP |
| 2006-314167 | Nov 2006 | JP |
| 2006-350490 | Dec 2006 | JP |
| 2007-523394 | Aug 2007 | JP |
| 2008-503125 | Jan 2008 | JP |
| 2008-027082 | Feb 2008 | JP |
| 2008-508600 | Mar 2008 | JP |
| 2008-508601 | Mar 2008 | JP |
| 2008-146165 | Jun 2008 | JP |
| 2008-203973 | Sep 2008 | JP |
| 2008-312153 | Dec 2008 | JP |
| 2009-110286 | May 2009 | JP |
| 2009-169825 | Jul 2009 | JP |
| 2009-525538 | Jul 2009 | JP |
| 10-503124 | Jan 2010 | JP |
| 12-014299 | Jan 2012 | JP |
| 2006-245128 | Sep 2014 | JP |
| 2009-0057304 | Jun 2009 | KR |
| 2009-0057421 | Jun 2009 | KR |
| WO 0038042 | Jun 2000 | WO |
| WO 0129702 | Apr 2001 | WO |
| WO 0177792 | Oct 2001 | WO |
| WO 0201338 | Jan 2002 | WO |
| WO 0208881 | Jan 2002 | WO |
| WO 0213176 | Feb 2002 | WO |
| WO 0221338 | Mar 2002 | WO |
| WO 03060622 | Jul 2003 | WO |
| WO 03081458 | Oct 2003 | WO |
| WO 04001560 | Dec 2003 | WO |
| WO 2005029460 | Mar 2005 | WO |
| WO 05052773 | Jun 2005 | WO |
| WO 06003590 | Jan 2006 | WO |
| WO 2006003591 | Jan 2006 | WO |
| WO 06020304 | Feb 2006 | WO |
| WO 06020305 | Feb 2006 | WO |
| WO 2006026183 | Mar 2006 | WO |
| WO 2006045530 | May 2006 | WO |
| WO 2006067711 | Jun 2006 | WO |
| WO 2006094308 | Sep 2006 | WO |
| WO 2006124248 | Nov 2006 | WO |
| WO 2006128248 | Dec 2006 | WO |
| WO 2007037806 | Apr 2007 | WO |
| WO 2007067858 | Jun 2007 | WO |
| WO 2007079425 | Jul 2007 | WO |
| WO 2007089766 | Aug 2007 | WO |
| WO 2008020446 | Feb 2008 | WO |
| WO 2008030779 | Mar 2008 | WO |
| WO 2008030879 | Mar 2008 | WO |
| WO 2008030880 | Mar 2008 | WO |
| WO 2008085846 | Jul 2008 | WO |
| WO 2008085848 | Jul 2008 | WO |
| WO 2008085855 | Jul 2008 | WO |
| WO 2008085871 | Jul 2008 | WO |
| WO 2008085877 | Jul 2008 | WO |
| WO 2008148021 | Dec 2008 | WO |
| WO 2009018314 | Feb 2009 | WO |
| WO 2009111189 | Sep 2009 | WO |
| WO 2009111458 | Sep 2009 | WO |
| WO 2009111460 | Sep 2009 | WO |
| WO 2009111469 | Sep 2009 | WO |
| WO 2010041155 | Apr 2010 | WO |
| WO 2010107669 | Sep 2010 | WO |
| WO 2010144201 | Dec 2010 | WO |
| Entry |
|---|
| Office Action, dated Oct. 30, 2014, received in Chinese Patent Application No. 201210128932.5, which corresponds with U.S. Appl. No. 11/620,727, 3 pages. |
| Office Action, dated May 11, 2015, received in Chinese Patent Application No. 201210128932.5, which corresponds with U.S. Appl. No. 11/620,727, 4 pages. |
| Office Action, dated Dec. 24, 2014, received in Chinese Patent Application No. 201210128915.1, which corresponds with U.S. Appl. No. 11/620,727, 2 pages. |
| Notice of Allowance, dated Feb. 5, 2016, received in Chinese Patent Application No. 201210128915.1, which corresponds with U.S. Appl. No. 11/620,727, 2 pages. |
| Certificate of Patent, dated Mar. 16, 2016, received in Chinese Patent Application, No. 201210128915.1, which corresponds with U.S. Appl. No. 11/620,727, 1 page. |
| Office Action, dated Nov. 15, 2014, received in Chinese Patent Application No. 201210128911.3, which corresponds with U.S. Appl. No. 11/620,727, 2 pages. |
| Office Action, dated Jan. 29, 2016, received in Chinese Patent Application No. 201210128911.3, which corresponds with U.S. Appl. No. 11/620,727, 6 pages. |
| Office Action, dated Dec. 19, 2011, received in European Patent Application No. 08705471.4, which corresponds with U.S. Appl. No. 11/620,727, 6 pages. |
| Office Action, dated Jan. 29, 2015, received in Patent Application No. 08705471.4, which corresponds with U.S. Appl. No. 11/620,727, 8 pages. |
| Patent, dated Jun. 2, 2017, received in Hong Kong Patent Application No. 13104177.2, which corresponds with U.S. Appl. No. 11/620,727, 2 pages. |
| Office Action, dated Nov. 5, 2012, received in U.S. Appl. No. 13/221,836, 16 pages. |
| Final Office Action, dated May 15, 2013, received in U.S. Appl. No. 13/221,836, 22 pages. |
| Office Action, dated Oct. 30, 2013, received in U.S. Appl. No. 13/221,836, 31 pages. |
| Final Office Action, dated May 20, 2014, received in U.S. Appl. No. 13/221,836, 36 pages. |
| Decision on Appeal, dated Jan. 3, 2017, received in U.S. Appl. No. 13/221,836, 6 pages. |
| Notice of Allowance, dated Feb. 21, 2017, received in U.S. Appl. No. 13/221,836, 10 pages. |
| Office Action, dated Jul. 24, 2012, received in U.S. Appl. No. 13/221,837, 13 pages. |
| Final Office Action, dated Feb. 14, 2013, received in U.S. Appl. No. 13/221,837, 13 pages. |
| Examiner's Answer, dated Feb. 11, 2014, received in U.S. Appl. No. 13/221,837, 19 pages. |
| Office Action, dated Jan. 10, 2012, received in U.S. Appl. No. 13/251,121, 16 pages. |
| Final Office Action, dated Jul. 9, 2012, received in U.S. Appl. No. 13/251,121, 21 pages. |
| Final Office Action, dated Sep. 23, 2013, received in U.S. Appl. No. 13/251,121, 24 pages. |
| Office Action, dated May 1, 2013, received in U.S. Appl. No. 13/251,121, 17 pages. |
| Examiner's Answer, dated Apr. 29, 2014, U.S. Appl. No. 13/251,121, 41 pages. |
| Notice of Allowance, dated Sep. 20, 2016, received in U.S. Appl. No. 13/251,121, 7 pages. |
| Office Action, dated Jan. 31, 2012, received in U.S. Appl. No. 13/251,146, 16 pages. |
| Final Office Action, dated Jun. 20, 2012, received in U.S. Appl. No. 13/251,146, 14 pages. |
| Office Action, dated Apr. 11, 2013, received in U.S. Appl. No. 13/251,146, 15 pages. |
| Final Office Action, dated Oct. 2, 2013, received in U.S. Appl. No. 13/251,146, 20 pages. |
| Examiner's Answer dated May 7, 2014, received in U.S. Appl. No. 13/251,146, 43 pages. |
| Office Action, dated Feb. 10, 2012, received in U.S. Appl. No. 13/251,150, 23 pages. |
| Final Office Action, dated Jul. 5, 2012, received in U.S. Appl. No. 13/251,150, 27 pages. |
| Office Action, dated Jun. 7, 2013, received in U.S. Appl. No. 13/251,150, 34 pages. |
| Final Office Action, dated Dec. 11, 2013, received in U.S. Appl. No. 13/251,150, 44 pages. |
| Examiner's Answer, dated Jun. 17, 2014, received in U.S. Appl. No. 13/251,150, 47 pages. |
| Notice of Allowance, dated Dec. 21, 2016, received in U.S. Appl. No. 13/251,150, 10 pages. |
| Office Action, dated Jan. 20, 2012, received in U.S. Appl. No. 13/251,152, 20 pages. |
| Final Office Action, dated Jun. 20, 2012, received in U.S. Appl. No. 13/251,152, 24 pages. |
| Office Action, dated Apr. 23, 2013, received in U.S. Appl. No. 13/251,152, 29 pages. |
| Final Office Action, dated Oct. 18, 2013, received in U.S. Appl. No. 13/251,152, 29 pages. |
| Examiner's Answer, dated May 21, 2014, received in U.S. Appl. No. 13/251,152, 45 pages. |
| Notice of Allowance, dated Sep. 7, 2016, received in U.S. Appl. No. 13/251,152, 8 pages. |
| Notice of Allowance, dated Dec. 1, 2016, received in U.S. Appl. No. 13/251,152, 8 pages. |
| Office Action, dated Aug. 29, 2012, received in U.S. Appl. No. 11/620,715, 15 pages. |
| Final Office Action, dated Mar. 1, 2013, received in U.S. Appl. No. 11/620,715, 15 pages. |
| Examiner's Answer, dated Feb. 13, 2014, received in U.S. Appl. No. 11/670,715, 22 pages. |
| Decision on Appeal, dated Jun. 2, 2017, received in U.S. Appl. No. 11/620,715, 10 pages. |
| Office Action, dated Jul. 21, 2011, received in Chinese Patent Application No. 200880001855.9, which corresponds with U.S. Appl. No. 11/620,715, 2 pages. |
| Office Action, dated Jun. 6, 2012, received in Chinese Patent Application No. 200880001855.9, which corresponds with U.S. Appl. No. 11/620,715, 3 pages. |
| Office Action, dated Nov. 5, 2012, received in Chinese Patent Application No. 200880001855.9, which corresponds with U.S. Appl. No. 11/620,715, 2 pages. |
| Office Action, dated Mar. 7, 2013, received in Chinese Patent Application No. 200880001855.9, which corresponds with U.S. Appl. No. 11/620,715, 1 page. |
| Office Action, dated Jul. 29, 2014, received in Chinese Patent Application No. 200880001855.9, which corresponds with U.S. Appl. No. 11/620,715, 14 pages. |
| Office Action, dated Oct. 20, 2014, received in European Patent Application No. 08712946.6, which corresponds with U.S. Appl. No. 11/620,715, 6 pages. |
| Office Action, dated Oct. 30, 2012, received in European Patent Application No. 08712946.6, which corresponds with U.S. Appl. No. 11/620,715, 5 pages. |
| Notice of Allowance, dated Dec. 21, 2016, received in European Patent Application No. 08712946.6, which corresponds with U.S. Appl. Appl. No. 11/620,715, 7 pages. |
| Decision to Grant, dated May 11, 2017, received in European Patent Application No. 08712946.6, which corresponds with U.S. Appl. No. 11/620,715, 1 page. |
| Patent, dated Jul. 6, 2017, received in European Patent Application No. 08712946.6, which corresponds with U.S. Appl. No. 11/620,715, 1 page. |
| Office Action, dated Jun. 18, 2012, received in U.S. Appl. No. 13/464,800, 10 pages. |
| Notice of Allowance, dated Nov. 13, 2012, received in U.S. Appl. No. 13/464,800, 8 pages. |
| Notice of Allowance, dated Dec. 19, 2012, received in U.S. Appl. No. 13/464,800, 9 pages. |
| Office Action, dated Oct. 9, 2012, received in U.S. Appl. No. 13/084,472, 14 pages. |
| Final Office Action, dated Jun. 20, 2013, received in U.S. Appl. No. 13/084,472, 20 pages. |
| Office Action, dated Dec. 6, 2013, received in U.S. Appl. No. 13/084,472, 23 pages. |
| Final Office Action, dated Jun. 17, 2014, received in U.S. Appl. No. 13/084,472, 31 pages. |
| Office Action, dated Dec. 10, 2014, received in U.S. Appl. No. 13/084,472, 24 pages. |
| Notice of Allowance, dated Jul. 7, 2015, received in U.S. Appl. No. 13/084,472, 8 pages. |
| Notice of Allowance, dated Oct. 26, 2015, received in U.S. Appl. No. 13/084,472, 8 pages. |
| Notice of Allowance, dated Jan. 15, 2014, received in U.S. Appl. No. 13/620,390, 10 pages. |
| Supplemental Notice of Allowance, dated Jan. 27, 2014, received in U.S. Appl. No. 13/620,390, 2 pages. |
| Office Action, dated Mar. 5, 2013, received in U.S. Appl. No. 13/670,378, 28 pages. |
| Notice of Allowance, dated Jul. 24, 2013, received in U.S. Appl. No. 13/670,378, 9 pages. |
| Office Action, dated Feb. 26, 2016, received in U.S. Appl. No. 14/043,774, 5 pages. |
| Notice of Allowance, dated Jun. 27, 2016, received in U.S. Appl. No. 14/043,774, 7 pages. |
| Office Action, dated Apr. 28, 2015, received in U.S. Appl. No. 13/791,621, 6 pages. |
| Notice of Allowance, dated Nov. 5, 2015, received in U.S. Appl. No. 13/791,621, 5 pages. |
| Notice of Allowance, dated Mar. 1, 2016, received in U.S. Appl. No. 13/791,621, 7 pages. |
| Office Action, dated Apr. 27, 2016, received in U.S. Appl. No. 14/290,931, 12 pages. |
| Final Office Action, dated Nov. 25, 2016, received in U.S. Appl. No. 14/290,931, 13 pages. |
| Notice of Allowance, dated Apr. 7, 2017, received in U.S. Appl. No. 14/290,931, 11 pages. |
| Office Action, dated Nov. 2, 2016, received in U.S. Appl. No. 14/290,931, 21 pages. |
| Notice of Allowance, dated Apr. 20, 2017, received in U.S. Appl. No. 14/188,635, 11 pages. |
| Notice of Allowance, dated May 18, 2017, received in U.S. Appl. No. 14/188,635, 5 pages. |
| Office Action, dated Jan. 4, 2016, received in U.S. Appl. No. 14/171,680, 7 pages. |
| Notice of Allowance, dated Apr. 18, 2016, received in U.S. Appl. No. 14/171,680, 5 pages. |
| Notice of Allowance, dated May 28, 2015, received in U.S. Appl. No. 14/180,267, 11 pages. |
| Notice of Allowance, dated Sep. 15, 2015, received in U.S. Appl. No. 14/180,267, 5 pages. |
| Notice of Allowance, dated Dec. 31, 2015, received in U.S. Appl. No. 14/180,267, 5 pages. |
| Notice of Allowance, dated Feb. 11, 2016, received in U.S. Appl. No. 14/180,267, 2 pages. |
| Office Action, dated Jun. 30, 2017, recived in U.S. Appl. No. 15/046,252, 8 pages. |
| Office Action, dated Sep. 12, 2016, received in U.S. Appl. No. 15/197,704, 7 pages. |
| Notice of Allowance, dated Jan. 20, 2017, received in U.S. Appl. No. 15/197,704, 5 pages |
| Notice of Allowance, dated May 5, 2017, received in U.S. Appl. No. 15/197,704, 5 pages. |
| Office Action, dated Apr. 21, 2017, received in U.S. Appl. No. 15/432,746, 9 pages. |
| Office Action, dated Aug. 30, 2017, received in U.S. Appl. No. 15/432,746, 9 pages |
| Extended European Search Report, dated Dec. 7, 2011, received in European Patent Application No. 11184186.2, which corresponds to U.S. Appl. No. 12/566,660, 6 pages. |
| International Search Report and Written Opinion, dated Oct. 5, 2010, received in International Patent Application No. PCT/US2010/027118, which corresponds with U.S. Appl. No. 12/566,660, 15 pages. |
| International Preliminary Report on Patentability, dated Sep. 20, 2011, received in International Patent Application No. PCT/US2010/027118, which corresponds with U.S. Appl. No. 12/566,660, 10 pages. |
| Invitation to Pay Additional Fees, PCT Application PCT/US2010/027118, dated Jul. 13, 2010, 5 pages. |
| International Search Report and Written Opinion, dated Jun. 1, 2011, received in International Patent Application No. PCT/US2011/020404, which corresponds with U.S. Appl. No. 12/789,684, 7 pages. |
| International Preliminary Report on Patentability, dated Jul. 10, 2012, received in International Patent Application No. PCT/US2011/020404, which corresponds with U.S. Appl. No. 12/789,684, 5 pages. |
| Extended European Search Report, dated May 20, 2011, received in European Patent Application No. 11152015.1, which corresponds with U.S. Appl. No. 12/789,695, 9 pages. |
| International Search Report and Written Opinion, dated May 20, 2011, received in International Patent Application No. PCT/US2011/022516, which corresponds with U.S. Appl. No. 12/789,695, 13 pages. |
| International Preliminary Report on Patentability, dated Aug. 9, 2012, received in International Patent Application No. PCT/US2011/022516, which corresponds with U.S. Appl. No. 12/789,695, 11 pages. |
| International Search Report and Written Opinion, dated Dec. 13, 2011, received in International Patent Application No. PCT/US11/039583, which corresponds with U.S. Appl. No. 12/892,848, 10 pages. |
| International Preliminary Report on Patentability, dated Dec. 14, 2012, received in International Patent Application No. PCT/US2011/039583, which corresponds with U.S. Appl. No. 12/892,848, 7 pages. |
| International Search Report and Written Opinion, dated Jun. 1, 2012, received in International Patent Application No. PCT/US2011/065859, which corresponds with U.S. Appl. No. 13/077,925, 21 pages. |
| International Preliminary Report on Patentability, dated Jun. 25, 2013, received in International Patent Application No. PCT/US2011/065859, which corresponds with U.S. Appl. No. 13/077,925, 15 pages. |
| Invitation to Pay Additional Fees, PCT Application PCT/US2011/065859, dated Mar. 12, 2012, 5 pages. |
| Extended European Search Report, dated Apr. 21, 2009, received in European Patent Application No. 09154313.2, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Extended European Search Report, dated Mar. 2, 2011, received in European Patent Application No. 11150786.9, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Extended European Search Report, dated Mar. 1, 2011, received in European Patent Application No. 11150788.5, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Extended European Search Report, dated Nov. 23, 2011, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Extended European Search Report, dated Nov. 24, 2011, received in European Patent Application No. 11184169.8, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Extended European Search Report, dated Nov. 18, 2011, received in European Patent Application No. 11184170.6, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Extended European Search Report, dated Nov. 18, 2011, received in European Patent Application No. 11184172.2, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Extended European Search Report, dated Nov. 30, 2011, received in European Patent Application No. 11184409.8, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Extended European Search Report, dated Jun. 5, 2012, received in European Patent Application No. 12156394.4, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Extended European Search Report, dated Jul. 9, 2012, received in European Patent Application No. 12156395.1, which corresponds with U.S. Appl. No. 12/042,318, 8 pages. |
| Extended European Search Report, dated Aug. 4, 2017, received in European Patent Application No. 17158104.4, which corresponds with U.S. Appl. No. 12/042,318, 8 pages. |
| International Search Report and Written Opinion, dated Apr. 16, 2009, received in International Patent Application No. PCT/US2009/034772, which corresponds with U.S. Appl. No. 12/042,318, 9 pages. |
| International Preliminary Report on Patentability, dated Sep. 7, 2010, received in International Patent Application No. PCT/US2009/034772, which corresponds with U.S. Appl. No. 12/042,318, 7 pages. |
| Extended European Search Report, dated Feb. 28, 2013, received in European Patent Application No. 12188748.3, which corresponds with U.S. Appl. No. 12/042,067, 8 pages. |
| Extended European Search Report, dated Dec. 22, 2015, received in European Patent Application No. 15175530.3, which corresponds with U.S. Appl. No. 12/042,067, 9 pages. |
| International Search Report and Written Opinion, dated Jul. 3, 2009, received in International Patent Application No. PCT/US2009/035856, which corresponds with U.S. Appl. No. 12/042,067, 10 pages. |
| International Preliminary Report on Patentability, dated Sep. 16, 2010, received in International Patent Application No. PCT/US2009/035856, which corresponds with U.S. Appl. No. 12/042,067, 6 pages |
| Extended European Search Report, dated Jan. 13, 2012, received in European Patent Application No. 11184226.6, which corresponds with U.S. Appl. No. 12/042,299, 7 pages. |
| Extended European Search Report, dated Jan. 13, 2012, received in European Patent Application No. 11184224.1, which corresponds with U.S. Appl. No. 12/042,299, 7 pages. |
| Extended European Search Report, dated Jan. 13, 2012, received in European Patent Application No. 11184223.3, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Extended European Search Report, dated Jan. 13, 2012, received in European Patent Application No. 11184222.5, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| International Search Report and Written Opinion, dated Nov. 11, 2009, received in International Patent Application No. PCT/US2009/035874, which corresponds with U.S. Appl. No. 12/042,299, 10 pages. |
| International Preliminary Report on Patentability, dated Sep. 16, 2010, received in International Patent Application No. PCT/US2009/035874, which corresponds with U.S. Appl. No. 12/042,299, 7 pages. |
| International Search Report and Written Opinion, dated Jul. 3, 2009, received in International Patent Application No. PCT/US2009/035858, which corresponds with U.S. Appl. No. 12/042,237, 10 pages. |
| International Preliminary Report on Patentability, dated Sep. 7, 2010, received in International Patent Application No. PCT/US2009/035858, which corresponds with U.S. Appl. No. 12/042,237, 6 pages. |
| International Search Report and Written Opinion, dated Jun. 4, 2008, received in International Patent Application No. PCT/US2008/000089, which corresponds with U.S. Appl. No. 11/620,717, 10 pages. |
| International Preliminary Report on Patentability, dated Jul. 7, 2009, received in International Patent Application No. PCT/US2008/000089, which corresponds with U.S. Appl. No. 11/620,717, 9 pages. |
| International Search Report and Written Opinion, dated Apr. 22, 2008, received in International Patent Application No. PCT/US2008/000060, which corresponds with U.S. Appl. No. 11/620,717, 8 pages. |
| International Preliminary Report on Patentability, dated Jul. 7, 2009, received in International Patent Application No. PCT/US2008/000060, which corresponds with U.S. Appl. No. 11/620,727, 7 pages |
| International Search Report and Written Opinion, dated May 2, 2008, received in International Patent Application No. PCT/US2008/000069, which corresponds with U.S. Appl. No. 11/620,715, 12 pages. |
| International Preliminary Report on Patentability, dated Jul. 7, 2009, received in International Patent Application No. PCT/US2008/000069, which corresponds with U.S. Appl. No. 11/620,715, 8 pages. |
| International Search Report and Written Opinion, dated Dec. 4, 2014, received in International Patent Application No. PCT/US2014/040406, which corresponds with U.S. Appl. No. 14/290,931, 9 pages. |
| International Preliminary Report on Patentability, dated Dec. 15, 2015, received. In International Patent Application No. PCT/US2014/040406, which corresponds with U.S. Appl. No. 14/290,931, 6 pages. |
| Office Action, dated Dec. 9, 2011, received in U.S. Appl. No. 12/566,660, 6 pages. |
| Notice of Allowance, dated May 24, 2012, received in U.S. Appl. No. 12/566,660, 9 pages. |
| Notice of Allowance, dated Jul. 26, 2012, received in U.S. Appl. No. 12/566,660, 5 pages. |
| Office Action, dated Oct. 17, 2012, received in Australian Patent Application No. 2010226120, which corresponds with U.S. Appl. No. 12/566,660, 3 pages. |
| Notice of Allowance, dated Nov. 2, 2012, received in Canadian Patent Application No. 2,755,443, which corresponds with U.S. Appl. No. 12/566,660, 1 page. |
| Notice of Allowance, dated Apr. 10, 2014, received in Canadian Patent Application No. 2,817,648, which corresponds with U.S. Appl. No. 12/566,660, 1 page. |
| Office Action, dated Oct. 9, 2013, received in Canadian Patent Application No. 2,817,890, which corresponds with U.S. Appl. No. 12/566,660, 3 pages. |
| Office Action, dated Apr. 22, 2014, received in Canadian Patent Application No. 2,817,890, which corresponds with U.S. Appl. No. 12/566,660, 3 pages. |
| Letters Patent, dated Dec. 29, 2015, received in Canadian Patent Application No. 2,817,890, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Office Action, dated Nov. 28, 2016, received in Canadian Patent Application No. 2,909,730, which corresponds with U.S. Appl. No. 12/566,660, 4 pages. |
| Office Action, dated Oct. 31, 2013, received in Chinese Patent Application No. 201080020598.0, which corresponds with U.S. Appl. No. 12/566,660, 4 pages. |
| Decision to Grant, dated Apr. 24, 2014, received in Chinese Patent Application No. 201080020598.0, which corresponds with U.S. Appl. No. 12/566,660, 1 page. |
| Office Action, dated Sep. 26, 2016, received in Chinese Patent Application No. 2016092101783870, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Notice of Allowance, dated Mar. 21, 2017, received in Chinese Patent Application No. 201410299526.4, which corresponds with U.S. Appl. No. 12/566,660, 3 pages. |
| Patent, dated Apr. 19, 2017, received in Chinese Patent Application No. 201410299526.4, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Office Action, dated Apr. 5, 2017, received in Chinese Patent Application No. 201410299325.4, which corresponds with U.S. Appl. No. 12/566,660, 8 pages. |
| Notice of Allowance, dated Mar. 10, 2017, received in Chinese Patent Application No. 201410299324.X, which corresponds with U.S. Appl. No. 12/566,660, 3 pages. |
| Patent, dated Apr. 12, 2017, received in Chinese Patent Application No. 201410299324.X, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Office Action, dated Jun. 19, 2013, received in European Patent Application No. 10712825.8, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Office Action, dated Jul. 1, 2015, received in European Patent Application No. 10712825.8, which corresponds with U.S. Appl. No. 12/566,660, 6 pages. |
| Office Action, dated Mar. 20, 2014, received in European Patent Application No. 11184186.2, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Office Action, dated Jun. 3, 2013, received in Japanese Patent Application No. 2012500844, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Office Action, dated Feb. 24, 2014, received in Japanese Patent Application No. 2012-500844, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Notice of Allowance, dated Aug. 1, 2014, received in Japanese Patent Application No. 2012-500844, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Office Action, dated Sep. 7, 2015, received in Japanese Patent Application No. 2014-129689, which corresponds with U.S. Appl. No. 12/566,660, 3 pages. |
| Certificate of Patent, dated Jan. 7, 2016, received in Japanese Patent Application No. 2014-129689, which corresponds with U.S. Appl. No. 12/566,660, 3 pages. |
| Certificate of Patent, dated Feb. 5, 2016, received in Japanese Patent Application No. 2014-129689, which corresponds with U.S. Appl. No. 12/566,660, 1 page. |
| Office Action, dated Nov. 18, 2016, received in Japanese Patent Application No. 2016-017396, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Notice of Allowance, dated Jun. 20, 2017, received in Japanese Patent Application No. 2016-017396, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Patent, dated Jul. 28, 2017, received in Japanese Patent Application No. 2016017396, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Notice of Allowance, dated May 29, 2013, received in Korean Patent Application No. 2011-7024288, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Office Action, dated Oct. 4, 2013, received in U.S. Appl. No. 12/789,684, 19 pages. |
| Final Office Action, dated Mar. 7, 2014, received in U.S. Appl. No. 12/789,684, 23 pages. |
| Office Action, dated Jul. 18, 2014, received in U.S. Appl. No. 12/789,684, 29 pages. |
| Office Action, dated Jan. 28, 2015, received in U.S. Appl. No. 12/789,684, 29 pages. |
| Notice of Allowance, dated Aug. 14, 2015, received in U.S. Appl. No. 12/789,684, 15 pages. |
| Office Action, dated Mar. 4, 2013, received in U.S. Appl. No. 12/789,695, 13 pages. |
| Office Action, dated Oct. 24, 2013, received in U.S. Appl. No. 12/789,695, 14 pages. |
| Final Office Action, dated May 7, 2014, received in U.S. Appl. No. 12/789,695, 17 pages. |
| Office Action, dated Jul. 1, 2015, received in U.S. Appl. No. 12/789,695, 15 pages. |
| Final Office Action, dated Feb. 22, 2016, received in U.S. Appl. No. 12/789,695, 17 pages. |
| Notice of Acceptance, dated May 1, 2014, received in Australian Patent Application No. 2011209720, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Office Action, dated Jun. 28, 2013, received in Australian Patent Application No. 2011209720, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Office Action, dated Aug. 27, 2015, received in Australian Patent Application No. 2014213525, which corresponds with U.S. Appl. No. 12/789,695, 6 pages. |
| Notice of Allowance, dated Apr. 14, 2016, received in Australian Patent Application No. 2014213525, which corresponds with U.S. Appl. No. 12/789,695, 1 page. |
| Certificate of Grant, dated Aug. 11, 2016, received in Australian Patent Application No. 2014213525, which corresponds with U.S. Appl. No. 12/789,695, 1 page. |
| Office Action, dated Jun. 13, 2017, received in Australian Patent Application No. 2016204905, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Office Action, dated Oct. 22, 2012, received in Chinese Patent Application No. 201110063183.8, which corresponds with U.S. Appl. No. 12/789,695, 2 pages. |
| Office Action, dated Aug. 26, 2013, received in Chinese Patent Application No. 201110063183.8, which corresponds with U.S. Appl. No. 12/789,695, 2 pages. |
| Decision to Grant, dated Feb. 24, 2014, received in Chinese Application No. 201110063183.8, which corresponds with U.S. Appl. No. 12/789,695, 1 page. |
| Office Action, dated Dec. 3, 2015, received in Chinese Patent Application No. 201310557439.X, which corresponds with U.S. Appl. No. 12/789,695, 2 pages. |
| Notice of Allowance, dated Jul. 27, 2016, received in Chinese Patent Application No. 201310557439.X, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Patent Certificate, dated Aug. 31, 2016, received in Chinese Patent Application No. 201310557439.X, which corresponds with U.S. Appl. No. 12/789,695, 2 pages. |
| Office Action, dated Feb. 2, 2016, received in Chinese Patent Application No. 2013105574402, which corresponds with U.S. Appl. No. 12/789,695, 5 pages. |
| Office Action, dated Nov. 9, 2016, received in Chinese Patent Application No. 2013105574402, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Office Action, dated May 24, 2016, received in Chinese Patent Application No. 2013105574402, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Office Action, dated Aug. 24, 2016, received in Chinese Patent Application No. 2016082000182820, which corresponds with U.S. Appl. No. 12/789,695, 2 pages. |
| Office Action, dated Jul. 10, 2017, received in Chinese Patent Application No. 2016082000182820, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Office Action, dated Jul. 26, 2013, received in European Patent Application No. 11152015.1, which corresponds with U.S. Appl. No. 12/789,695, 6 pages. |
| Office Action, dated Mar. 29, received in European Patent Application No. 11152015.1, which corresponds with U.S. Appl. No. 12/789,695, 11 pages. |
| Office Action, dated Jul. 17, 2015, received in Japanese Patent Application No. 2014-044208, which corresponds with U.S. Appl. No. 12/789,695, 5 pages. |
| Notice of Allowance, dated Apr. 15, 2016, received in Japanese Patent Application No. 2014-044208, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Patent Certificate, dated May 20, 2016, received in Japanese Patent Application No. 2014-044208, which corresponds with U.S. Appl. No. 12/789,695, 2 page. |
| Notice of Allowance, date Jul. 28, 2017, received in Japanese Patent Application No. 2016-098113, which corresponds with U.S. Appl. No. 12/789,695, 5 pages. |
| Office Action, dated Apr. 30, 2014, received in Korean Patent Application No. 2012-7022239, which corresponds with U.S. Appl. No. 12/789,695, 2 pages. |
| Notice of Allowance, dated Mar. 30, 2015, received in Korean Patent Application No. 2012-7022239, which corresponds with U.S. Appl. No. 12/789,695, 2 pages. (KR version only). |
| Notice of Allowance, dated May 23, 2016, received in Korean Patent Application No. 10-2014-7030745, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Letters Patent, dated Jul. 29, 2016, received in Korean Patent Application No. 102014-7030745, which corresponds with U.S. Patent Application No. 12/789,695, 2 pages. |
| Notice of Allowance, dated Nov. 9, 2016, received in Korean Patent Application No. 10-2016-7020780, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Patent, dated Jan. 5, 2017, received in Korean Patent Application No. 10-2016-7020780, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Notice of Allowance, dated May 15, 2013, received in U.S. Appl. No. 12/892,848, 10 pages. |
| Office Action, dated Aug. 14, 2013, received in Australian Patent Application No. 2011268047, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Notice of Allowance, dated Mar. 18, 2016, received in Australian Patent Application No. 2014200702, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Certificate of Grant, dated Sep. 22, 2016, received in Australian Patent Application No. 2014200702, which corresponds with U.S. Appl. No. 12/892,848, 1 page. |
| Office Action, dated May 12, 2017, received in Australian Patent Application No. 2016204284, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Office Action, dated Dec. 3, 2014, received in Chinese Patent Application No. 201180022994.1, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Office Action, dated Nov. 24, 2015, received in Chinese Patent Application No. 201180022994.1, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Notice of Allowance, dated Apr. 6, 2016, received in Chinese Patent Application No. 201180022994.1, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Patent Certificate, dated May 18, 2016, received in Chinese Patent Application No. 201180022994.1, which corresponds with U.S. Appl. No. 12/892,848, 1 page. |
| Office Action, dated Aug. 22, 2013, received in European Patent Application No. 11727371.4, which corresponds with U.S. Appl. No. 12/892,848, 6 pages. |
| Office Action, dated Aug. 26, 2015, received in European Patent Application No. 11727371.4, which corresponds with U.S. Appl. No. 12/892,848, 9 pages. |
| Notice of Allowance, dated Aug. 22, 2014, received in Japanese Patent Application No. 2013-515382, which corresponds with U.S. Appl. No. 12/892,848, 3 pages. |
| Office Action, dated Nov. 13, 2015, received in Japanese Patent Application No. 2014-191701, which corresponds with U.S. Appl. No. 12/892,848, 3 pages. |
| Notice of Allowance, dated Jun. 27, 2016, received in Japanese Patent Application No. 2014-191701, which corresponds with U.S. Appl. No. 12/892,848, 3 pages. |
| Certificate of Patent, dated Jul. 29, 2016, received in Japanese Patent Application No. 2014-191701, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Notice of Allowance, dated Jun. 5, 2017, received in Japanese Patent Application No. 2016-144701, which corresponds with U.S. Appl. No. 12/892,848, 5 pages. |
| Patent, dated Jun. 23, 2017, received in Japanese Patent Application No. 2016-144701, which corresponds with U.S. Appl. No. 12/892,848, 2 pages. |
| Office Action, dated Oct. 9, 2012, received in U.S. Appl. No. 12/892,851, 11 pages. |
| Final Office Action, dated Jul. 19, 2013, received in U.S. Appl. No. 12/892,851, 12 pages. |
| Office Action, dated May 22, 2014, received in U.S. Appl. No. 12/892,851, 11 pages. |
| Office Action, dated Nov. 4, 2016, received in U.S. Appl. No. 12/892,851, 13 pages. |
| Final Office Action, dated Jun. 30, 2017, received in U.S. Appl. No. 12/892,851, 17 pages. |
| Notice of Allowance, dated Jun. 27, 2013, received in U.S. Appl. No. 13/077,925, 10 pages. |
| Office Action, dated Dec. 10, 2014, received in Australian Patent Application No. 2011349513, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Certificate of Grant, dated Jul. 16, 2015, received in Australian Patent Application No. 2011349513, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Office Action, dated Mar. 15, 2016, received in Australian Patent Application No. 2015203638, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Office Action, dated Apr. 30, 2014, received in Chinese Patent Application No. 201110463262.8, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Office Action, dated Sep. 23, 2015, received in Chinese Patent Application No. 201110463262.8, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Notice of Allowance, dated Apr. 1, 2016, received in Chinese Patent Application No. 20110463262.8, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Letters Patent, dated May 4, 2016, received in Chinese Patent Application No. 20110463262.8, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Office Action, dated Oct. 19, 2012, received in Chinese Patent Application No. 201120580018.5, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Office Action, dated Apr. 22, 2013, received in Chinese Patent Application No. 201120580018.5, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Notification of Grant, dated Jul. 26, 2013, received in Chinese Patent Application No. 201120580018.5, which corresponds with U.S. Appl. No. 13/077,925, 1 page. |
| Office Action, dated Jul. 1, 2014, received in European Patent Application No. 11808779.0, which corresponds with U.S. Appl. No. 13/077,925, 5 pages. |
| Decision to Grant, dated Jul. 20, 2017, received in European Patent Application No. 11808779.0, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Grant, dated Aug. 4, 2017, received in Hong Kong Patent Application No. 13104376.1, which corresponds with U.S. Appl. No. 13/077,925, 1 page. |
| Notice of Allowance, dated Jun. 27, 2016, received in Japanese Patent Application No. 2015-077922, which corresponds with U.S. Appl. No. 13/077,925, 5 pages. |
| Certificate of Patent, dated Aug. 5, 2016, received in Japanese Patent Application No. 2015-077922, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Office Action, dated Jun. 2, 2017, received in Japanese Patent Application No. 2016-146769, which corresponds with U.S. Appl. No. 13/077,925, 7 pages. |
| Office Action, dated Jun. 26, 2014, received in Korean Patent Application No. 2013-7019463, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Office Action, dated Oct. 20, 2015, received in Korean Patent Application No. 2014-7036632, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Notice of Allowance, dated Apr. 29, 2016, received in Korean Patent Application No. 2014-7036632, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Letters Patent, dated Jul. 29, 2016, received in Korean Patent Application No. 2014-7036632, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Office Action, dated Aug. 23, 2016, received in Korean Patent Application No. 2016-7020964, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Notice of Allowance, dated Mar. 31, 2017, received in Korean Patent Application No. 2016-7020964, which corresponds with U.S. Appl. No. 13/077,925, 4 pages. |
| Patent, dated Jun. 30, 2017, received in Korean Patent Application No. 2016-7020964, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Office Action, dated Jul. 20, 2017, received in Korean Patent Application No. 2017-7018175, which corresponds with U.S. Appl. No. 13/077,925, 5 pages. |
| Office Action, dated Apr. 8, 2014, received in Taiwanese Patent Application No. 100147539, which corresponds with U.S. Appl. No. 13/077,925, 4 pages. |
| Notice of Allowance, dated Oct. 5, 2015, received in Taiwanese Patent Application No. 103144867, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Certificate of Grant, dated Feb. 1, 2016, received in Taiwanese Patent Application No. 103144867, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Office Action, dated Feb. 16, 2011, received in U.S. Appl. No. 12/042,318, 25 pages. |
| Final Office Action, dated Sep. 15, 2011, received in U.S. Appl. No. 12/042,318, 39 pages. |
| Notice of Allowance, dated Dec. 16, 2013, received in U.S. Appl. No. 12/042,318, 30 pages. |
| Office Action, dated Feb. 25, 2011, received in Australian Patent Application 2009200493, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Office Action, dated Aug. 9, 2011, received in Australian Patent Application No. 2009200493, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Feb. 22, 2012, received in Australian Patent Application No. 2011205170, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Notice of Acceptance, dated Jul. 3, 2013, received in Australian Patent Application No. 2011205170, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Dec. 13, 2011, received in Australian Patent Application No. 2011101154, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Letters Patent, dated May 7, 2012, received in Australian Patent Application No. 2011101154, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Dec. 13, 2011, received in Australian Patent Application No. 2011101157, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Letters Patent, dated May 8, 2012, received in Australian Patent Application No. 2011101157, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Dec. 13, 2011, received in Australian Patent Application No. 2011101156, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Letters Patent, dated May 8, 2012, received in Australian Patent Application No. 2011101156, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Dec. 13, 2011, received in Australian Patent Application No. 2011101155, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Letters Patent, May 8, 2012, received in Australian Patent Application No. 2011101155, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Sep. 3, 2012, received in Australian Patent Application No. 2011265335, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Notice of Acceptance, dated Nov. 8, 2012, received in Australian Patent Application No. 2011265335, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Notice of Acceptance, dated Jul. 14, 2016, received in Australian Patent Application No. 2013242854, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Certificate of Grant, dated Nov. 24, 2016, received in Australian Patent Application No. 2013242854, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Feb. 17, 2017, received in Australian Patent Application No. 2016206268, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Jan. 18, 2012, received in Canadian Patent Application No. 2,653,363, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Sep. 3, 2013, received in Canadian Patent Application No. 2,653,363, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Notice of Allowance, dated Apr. 29, 2014, received in Canadian Patent Application No. 2653363, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Jan. 7, 2016, received in Canadian Patent Application No. 2653363, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Office Action, dated Dec. 28, 2016, received in Canadian Patent Application No. 2653363, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Mar. 15, 2017, received in Canadian Patent Application No. 2,931,604, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Office Action, dated Aug. 6, 2010, received in Chinese Patent Application No. 200910118596.4, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Decision to Grant, dated Mar. 22, 2011, received in Chinese Patent Application No. 200910118596.4, 3 pages. |
| Office Action, dated Aug. 5, 2013, received in Chinese Patent Application No. 201110148738.9, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Jun. 5, 2014, received in Chinese Patent Application No. 201110148738.9, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Feb. 8, 2014, received in Chinese Patent Application No. 201110148738.9, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Jan. 21, 2013, received in Chinese Patent Application No. 201110148738.9, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Jun. 22, 2010, received in Danish Patent Application No. 102009011687.7, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Office Action, dated Feb. 12, 2010, received in European Patent Application No. 09154313.2, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Decision revoking the European Patent, dated Apr. 2, 2014, received in European Patent Application No. 09154313.2, which corresponds with U.S. Appl. No. 12/042,318, 28 pages. |
| Summons to Oral Proceedings, dated May 15, 2013, received in European Patent Application No. 09154313.2, which corresponds with U.S. Appl. No. 12/042,318, 30 pages. |
| New Summons to Oral Proceedings, dated Jul. 18, 2013, received in European Patent Application No. 09154313.2, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Decision to Grant, dated Jul. 26, 2012, received in European Patent Application No. 11150786.9, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated May 9, 2014, received in European Patent Application No. 11150788.5, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Decision to Grant, dated Sep. 17, 2015, received in European Application No. 11150788.5, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Patent, dated Oct. 14, 2015, received in European Patent Application No. 11150788.5, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated May 14, 2014, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Apr. 15, 2015, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Office Action, dated Nov. 25, 2015, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 7 pages. |
| Office Action, dated Feb. 16, 2016, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Intention to Grant, dated Sep. 28, 2016, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Decision to Grant, dated Mar. 23, 2017, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Patent, dated Apr. 19, 2017, received in European Patent Application No. 11184167.2, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated May 14, 2014, received in Patent Application No. 11184169.8, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Nov. 25, 2015, received in European Patent Application No. 11184169.8, which corresponds with U.S. Appl. No. 12/042,318, 8 pages. |
| Office Action, dated Feb. 16, 2016, received in European Patent Application No. 11184169.8, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Intention to Grant, dated Sep. 29, 2016, received in European Patent Application No. 11184169.8, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Decision to Grant, dated Mar. 23, 2017, received in European Patent Application No. 11184169.8, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated May 16, 2014, received in European Patent Application No. 11184170.6, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Office Action, dated Apr. 16, 2015, received in European Patent Application No. 11184170.6, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Nov. 30, 2015, received in European Patent Application No. 11184170.6, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Intention to Grant, dated Jul. 8, 2016, received in European Patent Application No. 11184170.6, which corresponds with U.S. Appl. No. 12/042,318, 7 pages. |
| Office Action, dated May 16, 2014, received in European Patent Application No. 11184172.2, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Office Action, dated Apr. 17, 2015, received in European Patent Application No. 11184172.2, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Nov. 30, 2015, received in European Patent Application No. 11184172.2, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Intention to Grant, dated Jul. 8, 2016, received in European Patent Application No. 11184172.2, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Office Action, dated May 16, 2014, received in European Patent Application No. 11184409.8, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Apr. 22, 2015, received in European Patent Application No. 11184409.8, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Nov. 30, 2015, received in European Patent Application No. 11184409.8, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Intention to Grant, dated Jul. 1, 2016, received in European Patent Application No. 11184409.8, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Office Action, dated Oct. 22, 2014, received in European Patent Application No. 12156394.4, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Nov. 25, 2015, received in European Patent Application No. 12156394.4, which corresponds with U.S. Appl. No. 12/042,318, 8 pages. |
| Decision to Grant, dated Jul. 28, 2016, received in European Patent Application No. 12156394.4, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Oct. 22, 2014, received in European Patent Application No. 12156395.1, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Nov. 25, 2015, received in European Application No. 12156395.1, which corresponds with U.S. Appl. No. 12/042,318, 9 pages. |
| Intention to Grant, dated Aug. 9, 2016, received in European Application No. 12156395.1, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Certificate of Grant, dated Nov. 30, 2012, received in Honk Kong Patent Application No. 11110416.2, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Certificate of Grant, dated Jul. 17, 2015, received in Hong Kong Patent Application No. 12105027.2, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Jul. 20, 2015, received in Israel Patent Application No. 197386, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Notice of Allowance, dated Nov. 23, 2015, received in Israel Patent Application No. 197386, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Patent, dated May 30, 2016, received in Israel Patent Application No. 197386, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Aug. 26, 2011, received in Japanese Patent Application No. 2009-080377, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Decision to Grant, dated Jul. 27, 2012, received in Japanese Patent Application No. 2009-080377, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Decision to Grant, dated Nov. 1, 2013, received in Japanese Patent Application No. 2012-186775, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Office Action, dated Apr. 4, 2016, received in Japanese Patent Application No. 2015-085361, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Office Action, dated Jan. 18, 2011, received in U.S. Appl. No. 12/042,067, 13 pages. |
| Final Office Action, dated Jul. 28, 2011, received in U.S. Appl. No. 12/042,067, 12 pages. |
| Office Action, dated Mar. 14, 2013, received in U.S. Appl. No. 12/042,067, 15 pages. |
| Notice of Allowance, dated Dec. 6, 2013, received in U.S. Appl. No. 12/042,067, 9 pages. |
| Notice of Allowance, dated Sep. 27, 2013, received in U.S. Appl. No. 12/042,067, 10 pages. |
| Office Action, dated Jun. 13, 2012, received in Chinese Patent Application No. 200980000014.0, which corresponds with U.S. Appl. No. 12/042,067, 2 pages. |
| Office Action, dated Oct. 19, 2011, received in Chinese Patent Application No. 200980000014.0, which corresponds with U.S. Appl. No. 12/042,067, 2 pages. |
| Decision to Grant, dated Nov. 27, 2012, received in Chinese Patent Application No. 200980000014.0, which corresponds with U.S. Patent Application No. 12/042,067, 1 page. |
| Office Action, dated May 4, 2015, received in Chinese Patent Application No. 20130053142.X, which corresponds with U.S. Appl. No. 12/042,067, 6 pages. |
| Office Action, dated Mar. 21, 2016, received in Chinese Patent Application No. 20130053142.X, which corresponds with U.S. Appl. No. 12/042,067, 7 pages. |
| Office Action, dated Oct. 10, 2016, received in Chinese Patent Application No. 201310053142.X, which corresponds with U.S. Appl. No. 12/042,067, 8 pages. |
| Office Action, dated Jun. 2, 2017, received in Chinese Patent Application No. 201310053142.X, which corresponds with U.S. Appl. No. 12/042,067, 2 pages. |
| Decision to Grant, dated Apr. 14, 2016, received in European Patent Application No. 09700006.1, which corresponds with U.S. Appl. No. 12/042,067, 1 page. |
| Office Action, dated Oct. 19, 2010, received in German Patent Application No. 112009000001.0, which corresponds with U.S. Appl. No. 12/042,067, 5 pages. |
| Office Action, dated Sep. 26, 2012, received in German Patent Application No. 112009000001.0, which corresponds with U.S. Appl. No. 12/042,067, 5 pages. |
| Office Action, dated Oct. 15, 2010, received in European Patent Application No. 09700006.1, which corresponds with U.S. Appl. No. 12/042,067, 4 pages. |
| Decision to Refuse, dated Jul. 15, 2013, received in European Patent Application No. 09700006.1, which corresponds with U.S. Appl. No. 12/042,067, 12 pages. |
| Summons to Oral Proceedings, dated Mar. 7, 2013, received in European Patent Application No. 09700006.1, which corresponds with U.S. Appl. No. 12/042,067, 5 pages. |
| Summons to Oral Proceedings, dated Mar. 10, 2015, received in European Patent Application No. 09700006.1, which corresponds with U.S. Appl. No. 12/042,067, 9 pages. |
| Decision to Grant, dated Apr. 12, 2015, received in European Patent Application No. 09700006.1, which corresponds with U.S. Appl. No. 12/042,067, 5 pages. |
| Office Action, dated Oct. 30, 2013, received in European Patent Application No. 12188748.3, which corresponds with U.S. Appl. No. 12/042,067, 5 pages. |
| Decision to refuse, dated Dec. 12, 2014, received in European Patent Application No. 12188748.3, which corresponds with U.S. Appl. No. 12/042,067, 12 pages. |
| Summons to Attend Oral Proceedings, dated Apr. 22, 2014, received in European Patent Application No. 12188748.3, which corresponds with U.S. Appl. No. 12/042,067, 3 pages. |
| Office Action, dated Oct. 24, 2011, received in Japanese Patent Application No. 2010-502356, which corresponds with U.S. Appl. No. 12/042,067, 2 pages. |
| Office Action, dated Jan. 6, 2014, received in Japanese Patent Application No. 2012-224838, which corresponds with U.S. Appl. No. 12/042,067, 1 page. |
| Office Action, dated Jan. 4, 2011, received in U.S. Appl. No. 12/042,299, 9 pages. |
| Final Office Action, dated Jul. 8, 2011, received in U.S. Appl. No. 12/042,299, 8 pages. |
| Office Action, dated May 3, 2012, received in U.S. Appl. No. 12/042,299, 9 pages. |
| Notice of Allowance, dated Dec. 12, 2012, received in U.S. Appl. No. 12/042,299, 8 pages. |
| Office Action, dated Oct. 26, 2011, received in Chinese Patent Application No. 200980000013.6, which corresponds with U.S. Appl. No. 12/042,299, 2 pages. |
| Office Action, dated Dec. 5, 2012, received in Chinese Patent Application No. 200980000013.6, which corresponds with U.S. Appl. No. 12/042,299, 2 pages. |
| Office Action, dated Jun. 6, 2012, received in Chinese Patent Application No. 200980000013.6, which corresponds with U.S. Appl. No. 12/042,299, 2 pages. |
| Office Action, dated Jul. 3, 2013, received in Chinese Patent Application No. 200980000013.6, which corresponds with U.S. Appl. No. 12/042,299, 6 pages. |
| Notification of Grant, dated Nov. 6, 2013, received in Chinese Patent Application No. 200980000013.6, which corresponds with U.S. Appl. No. 12/042,299, 3 pages. |
| Office Action, dated Apr. 28, 2016, received in Chinese Patent Application No. 2016042501712900, which corresponds with U.S. Appl. No. 12/042,299, 2 pages. |
| Office Action, dated Jul. 20, 2017, received in Chinese Patent Application No. 201410028534.5, which corresponds with U.S. Appl. No. 12/042,299. |
| Office Action, dated Jun. 1, 2016, received in Chinese Patent Application No. 2014100285627, which corresponds with U.S. Appl. No. 12/042,299, 3 pages. |
| Office Action, dated Apr. 26, 2017, received in Chinese Patent Application No. 2014100285627, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Office Action, dated Aug. 10, 2010, received in German Patent Application No. 112009000003.7, which corresponds with U.S. Appl. No. 12/042,299, 3 pages. |
| Office Action, dated Sep. 26, 2012, received in German Patent application No. 112009000003.7, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Office Action, dated Mar. 9, 2012, received in European Patent Application No. 09700007.9, which corresponds with U.S. Appl. No. 12/042,299, 7 pages. |
| Office Action, dated Nov. 26, 2010, received in European Patent Application No. 09700007.9, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Office Action, dated Aug. 28, 2014, received in European Patent Application No. 09700007.9, which corresponds with U.S. Appl. No. 12/042,299, 8 pages. |
| Summons to oral proceedings, dated Oct. 30, 2013, received in European Patent Application No. 09700007.9, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Office Action, dated Sep. 12, 2012, received in European Patent Application No. 11184226.6, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Office Action, dated Jul. 25, 2016, received in European Patent Application No. 11184226.6, which corresponds with U.S. Appl. No. 12/042,299, 9 pages. |
| Office Action, dated Sep. 12, 2012, received in European Patent Application No. 11184224.1, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Decision to Refuse, dated Feb. 11, 2015, received in European Patent Application No. 11184224.1, which corresponds with U.S. Appl. No. 12/042,299, 10 pages. |
| Summons to Attend Oral Proceedings, dated Oct. 30, 2013, received in European Patent Application No. 11184224.1, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Office Action, dated Sep. 12, 2012, received in European Patent Application No. 11184223.3, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Summons to Attend Oral Proceedings, dated Oct. 30, 2013, received in European Patent Application No. 11184223.3, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Decision to refuse, dated Feb. 11, 2015, received in European Patent Application No. 11184223.3, which corresponds with U.S. Appl. No. 12/042,299, 10 pages. |
| Office Action, dated Sep. 12, 2012, received in European Patent Application No. 11184222.5, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Summons to Attend Oral Proceedings, dated Oct. 30, 2013, received in European Patent Application No. 11184222.5, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Decision to refuse dated Feb. 11, 2015, received in European Patent Application No. 11184222.5, which corresponds with U.S. Appl. No. 12/042,299, 10 pages. |
| Office Action, dated Aug. 15, 2011, received in Japanese Patent Application No. 2010-502358, which corresponds with U.S. Appl. No. 12/042,299, 2 pages. |
| Decision to Grant, dated Mar. 23, 2012, received in Japanese Patent Application No. 2010-502358, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Office Action, dated Sep. 6, 2013, received in Japanese Patent Application No. 2012-088747, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Office Action, dated Aug. 11, 2014, received in Japanese Patent Application No. 2012-088747, which corresponds with U.S. Appl. No. 12/042,299, 1 page. |
| Decision to Grant, dated Feb. 16, 2015, received in Japanese Patent Application No. 2012-088747, which corresponds with U.S. Appl. No. 12/042,299, 3 pages. |
| Office Action, dated Nov. 30, 2015, received in Japanese Patent Application No. 2014-250268, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Letters Patent, dated Jul. 15, 2016, received in Japanese Patent Application No. 2014-250268, which corresponds with U.S. Appl. No. 12/042,299, 2 pages. |
| Office Action, dated Jun. 2, 2017, received in Japanese Patent Application No. 2016-133582, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Notice of Allowance, dated Jun. 13, 2013, received in U.S. Appl. No. 13/077,927, 10 pages. |
| Office Action, dated Jan. 3, 2013, received in U.S. Appl. No. 13/077,931, 13 pages. |
| Final Office Action, dated Sep. 9, 2013, received in U.S. Appl. No. 13/077,931, 14 pages. |
| Office Action, dated Jul. 17, 2014, received in U.S. Appl. No. 13/077,931, 21 pages. |
| Office Action, dated Aug. 20, 2015, received in U.S. Appl. No. 13/077,931, 22 pages. |
| Notice of Allowance, dated Dec. 31, 2014, received in U.S. Appl. No. 13/077,931, 8 pages. |
| Notice of Allowance, dated Jan. 14, 2016, received in U.S. Appl. No. 13/077,931, 8 pages. |
| Office Action, dated Nov. 21, 2012, received in U.S. Appl. No. 13/163,624, 9 pages. |
| Office Action, dated Mar. 22, 2013, received in U.S. Appl. No. 13/163,624, 9 pages. |
| Office Action, dated Oct. 24, 2013, received in U.S. Appl. No. 13/163,624, 8 pages. |
| Notice of Allowance, dated May 12, 2014, received in U.S. Appl. No. 13/163,624, 5 pages. |
| Office Action, dated Mar. 20, 2013, received in U.S. Appl. No. 13/163,626, 8 pages. |
| Office Action, dated Nov. 26, 2012, received in U.S. Appl. No. 13/163,626, 8 pages. |
| Office Action, dated Oct. 24, 2013, received in U.S. Appl. No. 13/163,626, 8 pages. |
| Notice of Allowance, dated Mar. 31, 2014, received in U.S. Appl. No. 13/163,626, 5 pages. |
| Office Action, dated Dec. 30, 2010, received in U.S. Appl. No. 12/042,237, 9 pages. |
| Final Office Action, dated Jun. 2, 2011, received in U.S. Appl. No. 12/042,237, 9 pages. |
| Office Action, dated Sep. 14, 2011, received in U.S. Appl. No. 12/042,237, 8 pages. |
| Notice of Allowance, dated Mar. 6, 2012, received in U.S. Appl. No. 12/042,237, 8 pages. |
| Office Action, dated Jul. 14, 2011, received in Chinese Patent Application No. 200980000015.5, which corresponds with U.S. Appl. No.12/042,237, 2 pages. |
| Office Action, dated Feb. 22, 2012, received in Chinese Patent Application No. 200980000015.5, which corresponds with U.S. Appl. No.12/042,237, 2 pages. |
| Office Action, dated Sep. 11, 2012, received in Chinese Patent Application No. 200980000015.5, which corresponds with U.S. Appl. No. 12/042,237, 1 page. |
| Office Action, dated Apr. 27, 2017, received in Chinese Patent Application No. 201510175905.7, which corresponds with U.S. Appl. No. 12/042,237, 5 pages. |
| Office Action, dated Jun. 30, 2017, received in Chinese Patent Application No. 201510175915.0, which corresponds with U.S. Appl. No. 12/042,237, 5 pages. |
| Office Action, dated Sep. 26, 2012, received in German Patent Application No. 112009000002.9, which corresponds with U.S. Appl. No. 12/042,237, 5 pages. |
| Office Action, dated Jul. 12, 2010, received in European Patent Application No. 09700008.7, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Summons to oral proceedings, dated Mar. 10, 2015, received in European Patent Application No. 09700008.7, which corresponds with U.S. Appl. No. 12/042,299, 12 pages. |
| Summons to oral proceedings, dated Mar. 27, 2013, received in European Patent Application No. 09700008.7, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Decision to Refuse, dated Oct. 8, 2013, received in European Patent Application No. 09700008.7, which corresponds with U.S. Appl. No. 12/042,237, 15 pages. |
| Decision to Grant, dated Dec. 2, 2015, received in European Patent Application No. 09700008.7, which corresponds with U.S. Appl. No. 12/042,237, 5 pages. |
| Decision to Grant, dated Apr. 14, 2016, received in European Patent Application No. 09700008.7, which corresponds with U.S. Appl. No. 12/042,237, 1 page. |
| Patent Certificate, May 11, 2016, received in European Patent Application No. 09700008.7, which corresponds with U.S. Appl. No. 12/042,237, 2 pages. |
| Office Action, dated Nov. 16, 2016, received in European Patent Application No. 15175530.3, which corresponds with U.S. Appl. No. 12/042,237, 4 pages. |
| Office Action, dated Sep. 2, 2013, received in Japanese Patent Application No. 2010-502357, which corresponds with U.S. Appl. No. 12/042,237, 11 pages. |
| Office Action, dated Mar. 4, 2013, received in Japanese Patent Application No. 2010-502357, which corresponds with U.S. Appl. No. 12/042,237, 2 pages. |
| Office Action, dated Jan. 16, 2012, received in Japanese Patent Application No. 2010-502357, which corresponds with U.S. Appl. No. 12/042,237, 2 pages. |
| Office Action, dated Sep. 24, 2013, received in Japanese Patent Application No. 2012-218235, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Letters Patent, dated Oct. 31, 2014, received in Japanese Patent Application No. 2012-218235, which corresponds with U.S. Appl. No. 12/042,237, 2 pages. |
| Office Action, dated May 20, 2015, received in U.S. Appl. No. 13/221,827, 26 pages. |
| Office Action, dated Jun. 23, 2014, received in U.S. Appl. No. 13/221,827, 18 pages. |
| Office Action, dated Oct. 4, 2016, received in U.S. Appl. No. 13/221,827, 20 pages. |
| Notice of Allowance, dated May 5, 2017, received in U.S. Appl. No. 13/221,827, 20 pages. |
| Notice of Allowance, dated Dec. 3, 2012, received in U.S. Appl. No. 13/221,830, 6 pages. |
| Notice of Allowance, dated May 23, 2012, received in U.S. Appl. No. 13/221,830, 7 pages. |
| Office Action, dated Nov. 4, 2011, received in U.S. Appl. No. 11/620,727, 15 pages. |
| Final Office Action, dated Mar. 12, 2012, received in U.S. Appl. No. 11/620,727, 20 pages. |
| Office Action, dated Aug. 15, 2012, received in U.S. Appl. No. 11/620,727, 19 pages. |
| Final Office Action, dated Mar. 7, 2013, received in U.S. Appl. No. 11/620,727, 23 pages. |
| Examiner'Answer, dated Feb. 13, 2014, received in U.S. Appl. No. 11/670,727), 23 pages. |
| Office Action, dated Jan. 6, 2012, received in Chinese Patent Application No. 200880001811.6, which corresponds with U.S. Appl. No. 11/620,727, 2 pages. |
| Office Action, dated Aug. 10, 2011, received in Chinese Patent Application No. 200880001811.6, which corresponds with U.S. Appl. No. 11/620,727, 3 pages. |
| Office Action, dated Oct. 21, 2010, received in Chinese Patent Application No. 200880001811.6, which corresponds with U.S. Appl. No. 11/620,727, 2 pages. |
| Office Action, dated Feb. 21, 2014, received in Chinese Patent Application No. 201210128932.5, which corresponds with U.S. Appl. No. 11/620,727, 2 pages. |
| Allen, “Override the GNU C Library-Painlessly,” http://www.ibm.com/developerworks/linux/library/l-glibc/index.html, Apr. 1, 2002, 4 pages. |
| Anonymous, “Firegestures Version History: Add-ons for Firefox,” Internet Article, http://addons.mozilla.org/en-US/firefox/addons/version/6366, Oct. 28, 2009, 6 pages. |
| Anonymous, “Firegestures: Changelog,” Internet Article, http://www.xuldev.org/firegestures/changelong.php, Oct. 27, 2009, 8 pages. |
| Anonymous, “Firegestures: Firefox Extension,” Internet Article, http://www.xuldev.org/firegesture/, Oct. 27, 2009, 2 pages. |
| Apple, “Safari Web Content Guide for iPhone,” Apple Inc.; Feb. 5, 2008, 96 pages. |
| Apple Inc. v. HTC Corporation, Brief Details of Claim, in the High Court of Justice, Chancery Division, Patents Court, Sep. 12, 2011, 2 pages. |
| Apple Inc. v. HTC Corporation Intervention of the Infringer according to Art. 105 EPC, Dec. 12, 2011, 24 pages. |
| Apple vs. HTC, Justice Floyd, Royal Courts of Justice, Jul. 4, 2012, 26 pages. |
| Apple Inc. v. HTC Corporation, Particulars of Claim, In the High Court of Justice, Chancery Division, Patents Court, Sep. 12, 2011, 4 pages. |
| Apple Inc. v. HTC Corporation, Particulars of Infringement, In the High Court of Justice, Chancery Division, Patents Court, Sep. 12, 2011, 5 pages. |
| Apple vs HTC, Reference to Complaint, Letter from Powell Gilbert, Apr. 5, 2012, 12 pages. |
| Apple vs HTC, Reference to Complaint, Letter from Powell Gilbert, Jul. 29, 2011, 22 pages. |
| Apple Inc. vs. Samsung Electronics Co. Ltd. et al., Judgment, District Court of the Hague, Aug. 24, 2011, 65 pages. |
| Apple Inc. vs. Samsung Electronics Co. Ltd., et al., Samsung's Motion to Supplement Invalidity, U.S. District Court, Jan. 27, 2012, 47 pages. |
| Ballard, “Microsoft Makes Research Technologies Available for Licensing,” http://www.theserverside.com/news/thread.tss?thread_id=33761, May 5, 2005, 3 pages. |
| Bederson, “Photo Mesa 3.1.2, Screen Shots,” May 24, 2006, 5 pages. |
| Benko et al., “Precise Selection Techniques for Multi-Touch Screens,” Department of Computer Science, Columbia University, NY, Jan. 16, 2006, 10 pages. |
| Brown, et al., “Distributed Active Objects,” Fifth International World Wide Web Conference, Paris, France, May 6-10, 1996, 18 pages. |
| Buxton, “Multi-Touch Systems that I Have Known and Loved,” Jan. 12, 2007, http://www.billbuxton.com/multitouchOverview.html, 25 pages. |
| Chartier, “Apple Releases iOS 4.3 Beta for Developers,” Macworld.com, www.macworld.com/article/1157114/ios_4_3.html, Jan. 12, 2011, 7 pages. |
| Chen, “The Web is Everywhere,” IEEE Communications Magazine, Feb. 5, 2008, 1 page. |
| Davis, “Flash to the Core,” http://www.amazon.com/Flash-Core-Joshua-David/dp/0735712881:Amazon.com, Jul. 24, 2002, 5 pages. |
| Dewid, “Scroll Control Box,” IBM Technical Disclosure Bulletin, vol. 38, 04, Apr. 1993, 6 pages. |
| Dietz et al., “DiamondTouch: A Multi-User Touch Technology,” Mitsubishi Electric Research Laboratories, Cambridge, Massachusetts, Oct. 2003, 11 pages. |
| Dodge et al., “Microsoft Office Excel 2003 Office Manual,” Microsoft Press, vol. 1, Jul. 12, 2004, 5 pages. |
| Esenther et al., “Fluid DTMouse: Better Mouse Support for Touch-Based Interactions,” Mitsubishi Electric Research Laboratories, Cambridge, Massachusetts, May 2006, 5 pages. |
| Feng et al., “Wireless Java Programming with Java 2 Micro Edition,” ASCII Corporation, Kenichi Suzuki, Japan, May 11, 2002, 90 pages. |
| Flanagan, JavaScript, 5th Ed., O'Reilly Japan, Jan. 31, 2008, 35 pages. |
| Forlines et al., “DTLens: Multi-user Tabletop Spatial Data Exploration,” Mitsubishi Electric Research Laboratories, Cambridge, Massachusetts, Oct. 2005, 5 pages. |
| Forlines et al., “Glimpse: A Novel Input Model for Multi-Level Devices,” Mitsubishi Electric Research Laboratory, Cambridge, Massachusetts, Dec. 2005, 5 pages. |
| Han, “TED Ideas Worth Spreading,” http://www.ted.com/talks/jeff_han_demos_his_breakthrough_touchscreen.html, Feb. 25, 2006, 1 page. |
| Holzner, “Built-in JavaScript Objects,” JavaScript Complete, McGraw/Hill, New York, Jun. 1998, 9 pages. |
| IPhone Development Wiki, “UI GestureRecognizer”, http://iphonedevwiki.net/index.php?title+UIGestureRecognizer&oldid=319, Oct. 31, 2009, 3 pages. |
| Ivanov, “API Hooking Revealed”, Code Project, www.codeproject.com/Articles/2082/API-hooking-revealed, Dec. 2, 2002, 16 pages. |
| JazzMutant, “Lemur v1.3 Examples Package: CursorModes.xml,” http://www.jazzmutant.com/support_download.php>, Jan. 31, 2006, 4 pages. |
| JazzMutant, The Lemur Owner's Manual, 2005 JazzMutant SAS and Cycling '74, //www.jazzmutant.com/support_download.php, Oct. 31, 2005, 108 pages. |
| JazzMutant, Lemur v1.3 Documentation Addendum, http://www.jazzmutant.com/support_download.php, Mar. 22, 2005, 3 pages. |
| JazzMutant, Lemur v1.3 Examples package: LightStepSeq.xml, http://www.jazzmutant.com/support_download.php, Jan. 31, 2006, 5 pages. |
| JazzMutant, Support, web.archive.org/web/20060421144624/http://vvww.jazzmutant.com/support_download.php, Apr. 21, 2006, 2 pages. |
| Karlson et al., AppLens and LaunchTile: Two Designs for One-handed Thumb Use on Small Devices, PowerPoint presentation, Computer Science Department, University of Maryland, College Park, MD, Apr. 2-7, 2005, 17 pages. |
| Karlson et al.,“AppLens and LaunchTile: Two Designs for One-handed Thumb Use on Small Devices,” paper, Computer Science Department, University of Maryland, College Park, MD, Apr. 2-7, 2005, 10 pages. |
| KennyTM, “UIGestureRecognizer,” from iPhone Development Wiki, Oct. 31, 2009, http://iphonedevwiki.net/index.php?title=UIGestureRecognizer&oldid=319http://iphonedevwiki.net/index.php?title=UIGestureRecognizer&action=history, 3 pages. |
| Kim et al., “HCI (Human Computer Interaction) Using Multi-touch Tabletop Display,” Department of Computer Engineering, Chonnam National University, Gwangju Korea, Aug. 24, 2007, 4 pages. |
| Lin et al., “Embedded GUI Based on Linux OS and Design Improvement Thereof,” May 13, 2004, 6 pages. |
| Maemo.org, “Coding Style and Programming Guidelines,” http://maemo.org/development/documentation/manuals/3-x/maemo_coding_style_and_programming_guides, Nov. 28, 2007, 14 pages. |
| Malik, “An Exploration of Multi-Finger Interaction on Multi-Touch Surfaces”, A thesis submitted in conformity with the requirements for the degree of Doctor of Philosophy Graduate Department of Computer Science—University of Toronto, Dec. 18, 2007, 184 pages. |
| Masui et al., “Elastic Graphical Interfaces for Precise Data Manipulation,” Software Research Laboratories, SHARP Corporation, Nara, Japan, Apr. 1995, 2 pages. |
| Matsuda et al., “Phosphorylcholine-endcapped oligomer and block co-oligomer and surface biological reactivity,” Biomaterials, Jun. 24, 2003, 11 pages. |
| Mertz et al., “The Influence of Design Techniques on User Interfaces: the DigiStrips Experiment for Air Traffic Control,” HCI-aero 2000, Toulouse, France, Sep. 2000, 6 pages. |
| “Microsoft Word 2003 Screen Shots,” Microsoft 2003, 2 pages. |
| Microsoft, “Microsoft Windows Software Development Kit Update for Windows Vista,” www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=23719, Mar. 22, 2007, 26 pages. |
| Microsoft, Window Styles—Microsoft Windows SDK—Screenshot, Mar. 22, 2007, 2 pages. |
| Miller, “Archive—Java Technology Products Download, PersonalJava Application Environment,” http://java.sun.com/products/personaljava/touchable/, Apr. 13, 2006, 12 pages. |
| Millhollon, “Microsoft Office Word 2003 Inside Out,” Microsoft Press, Redmond, Washington, Oct. 2, 2003, 7 pages. |
| Nathan, “Silverlight 1.0 Unleashed,” Sam's Publishing, XP055236068, ISBN: 978-0672-33007-0, Oct. 16, 2007, 271 pages. (Part One & Part Two). |
| Nokia, “Hildon User Interface Style Guide Summary,” Version 1.1, Apr. 12, 2006, 15 pages. |
| Olsen, “Building Interactive Systems: Principles for Human-Computer Interaction,” Jan. 7, 2009, 6 pages. |
| Olsen, “Developing User Interfaces,” Morgan Kaufmann Publishers, San Francisco, California, 1998, Chapter 4, 40 pages. |
| Petzold, “Programming Microsoft Windows with C#,” Core Reference, Jan. 18, 2002, 5 pages. |
| Pixley, “Document Object Model (DOM) Level 2 Events Specification, Version 1,” Netscape Communications Corp., W3C, Nov. 13, 2000, 47 pages. |
| Plaisant et al., “Touchscreen Toggle Design,” Human-Computer Interaction Laboratory, University of Maryland, College Park, MD, May 3-7, 1992, 2 pages. |
| Pleading notes Mr. B.J. Berghuis van Woortman, Aug. 10-11, 2010, 16 pages. |
| Pleading notes Mr. Kleemans, Mr Blomme and Mr Van Oorschot, Aug. 10, 2011, 35 pages. |
| Pogue, “Windows Vista for Starters: The Missing Manual,” Safari Books Online, Jan. 25, 2007, 18 pages. |
| Quinn Emanuel, Apple Inc. vs. Samsung Electronics Co. Ltd., et al., Samsung's Patent Local Rule 3-3 and 3-4 Disclosures, U.S. District Court, Oct. 7, 2011, 287 pages. |
| Quinn Emanuel, Translation Letter to the EPO, dated Apr. 11, 2012, received in European Patent Application No. 08713567.9, 53 pages. |
| Quinn Emanuel on behalf of Motorola, Statement letter re Notice of the Opposition Division, Dec. 3, 2013, 13 pages. |
| Quinn Emanuel on behalf of Motorola, Statement letter re briefs, Jan. 21, 2014, 9 pages. |
| Quinn Emanuel, response to Appeal Proceedings for European Patent Application No. 09154313.2 (Ep 2 098 948 B1), which corresponds with U.S. Appl. No. 12/042,318, Dec. 8, 2014, 34 pages. |
| Räihä, “Delegation: Dynamic Specialization,” Department of Computer Science, University of Tempere, Finland, Nov. 11, 1994, 8 pages. |
| Ramachandran et al., “An Architecture for Ink Annotations on Web Documents,” Proceedings of the 7th International Conference on Document Analysis and Recognition, Aug. 3-6, 2003, 5 pages. |
| Rappin et al., “wxPython in Action,” Manning Publications, http://up07.net/t2az7xty4dpz/sharebookpro.com_350770414.rar, Mar. 2006, 40 pages. |
| Rogers, “It's for You! An iPhone Development Primer for the Busy College Professor,” Computer Science and Information Systems, Northwest Missouri State University, Maryville, MO, Oct. 1, 2009, 8 pages. |
| Rowan, “Breakthrough Internet Device, Eureka Man,” available online at https://web.archive.org/web/20070709083626/http:/leurekaman.com/towards-multti-touch-in-the-browser, Jan. 31, 2007, 2 pages. |
| Rubine, “The Automatic Recognition of Gestures,” submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, Dec. 1991, 285 pages. |
| Salmoni, “The Zooming User Interface,” Advogato, Aug. 16, 2004, 14 pages. |
| Samsung, Statement of Defense also Counterclaim (Smartphones), Judge in Interlocutory Proceedings of the Court in the Hague, Jul. 20, 2011, 48 pages. |
| Samsung, Statement of Defense also Counterclaim (Tablets), Judge in Interlocutory Proceedings of the Court in the Hague, Jul. 20, 2011, 44 pages. |
| Sells, Windows Forms Programming in C#, Microsoft.net Development Series, Mar. 1, 2004, 9 pages. |
| Shen et al., “Informing the Design of Direct-Touch Tabletops,”, Mitsubishi Electric Research Labs, Oct. 2006, 11 pages. |
| Tidwell, “Magnetism, Designing Interfaces: Patterns for Effective Interaction Design,” O'Reilly Media, Inc., Nov. 21, 2005, 2 pages. |
| Touch, “A Glance at Touch,” Technology Handbook, http://www.carrolltouch.com, Jun. 7, 1998, 37 pages. |
| Venners, “Java's Security Architecture; Java's Security Model and Built-In Safety Features,” JavaWorld, Jul. 1997, 7 pages. |
| W3C, “Document Object Model (DOM) Level 2 Events Specifications,” Version 1.0, Nov. 13, 2000, 47 pages. |
| Wagner & Geyer, Remarks submitted for the Opposition Division, Aug. 10, 2012, 73 pages. |
| Webster's Dictionary, Definition of the word “Contemporaneous”, Jan. 21, 2014, 2 pages. |
| Westerman, “Hand Tracking Finger Identification and Chordic Manipulation on a Multi-touch Surface,” a dissertation submitted to the Faculty of the University of Delaware in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Electrical Engineering, Mar. 20, 1999, 363 pages. |
| Wikibooks, “Java Programming/Applets/Event Listeners,” en.wikibooks.org/w/index.php?title=Java_Programming/Applets/Event_Listeners&oldid =849558, May 1, 2007, 6 pages. |
| Withers & Rogers LLP, Apple vs. Samsung, Proprietor's Response to Communication under Rule 79(1) EPC, dated Mar. 8, 2012, 8 pages. |
| Withers & Rogers, Apple's Response to Notice of Intervention from Motorola, Jun. 21, 2012, 3 pages. |
| Withers & Rogers, Apple's Response to Addendum from Samsung, Jun. 21, 2012, 3 pages. |
| Withers & Rogers, Preliminary Response to Opponent O1's written submissions, Dec. 3, 2013, 11 pages. |
| Withers Rogers, Revised Second Auxiliary Request, Jan. 30, 2014, 8 pages. |
| Withers Rogers, Grounds of Appeal in support of the Notice of Appeal, Aug. 4, 2014, 24 pages. |
| Withers Rogers, Comments on Sections 3.1 and 3.4 of the Withdrawn Appeal, Oct. 14, 2014, 3 pages. |
| YouTube, “A Lemurized Formula,” http://www.youtube.com/watch?v=sHAMyQak-LM, Dec. 15, 2007, 1 page. |
| Zimmerman & Partner, Samsung Electronics GMmbH, Supplement to Notice of Opposition, Apr. 5, 2011, 6 pages. |
| Zimmerman & Partner, Samsung Electronics GmbH/Apple Inc. vs EP 2 126 678 B1 (08713567.9) Opposition, Jan. 30, 2012, 27 pages. |
| Zimmermann & Partner, Response to Summons letter, Nov. 7, 2013, 33 pages. |
| Zimmermann & Partner, Response to letter dated Jan. 3, 2014, 10 pages. |
| TR—Notice of Allowance, dated Jan. 30, 2012, received in Canadian Patent Application No. 2,658,177, 1 page. |
| TR—Office Action, dated Jun. 22, 2011, received in Canadian Patent Application No. 2,658,177, 2 pages. |
| TR—Office Action, dated Dec. 1, 2009, received in Canadian Patent Application No. 2,658,177, 2 pages. |
| TR—Office Action, dated Nov. 4, 2013, received in Canadian Patent Application No. 2,759090, 3 pages. |
| TR—Office Action, dated Nov. 7, 2013, received in Canadian Patent Application No. 2,759,091, 4 pages. |
| TR—Final Office Action, dated Nov. 13, 2009, received in U.S. Appl. No. 11/620,709, 8 pages. |
| TR—Office Action, dated Apr. 1, 2009, received in U.S. Appl. No. 11/620,709, 8 pages. |
| TR—Office Action, dated Jun. 9, 2010, received in U.S. Appl. No. 11/620,709, 8 pages. |
| TR—Office Action, dated Jul. 21, 2010, received in U.S. Appl. No. 11/620,710, 29 pages. |
| TR—Notice of Allowance, dated Jul. 20, 2010, received in U.S. Appl. No. 11/620,717, 11 pages. |
| TR—Office Action, dated Jul. 8, 2009, received in U.S. Appl. No. 11/620,717, 6 pages. |
| TR—Office Action, dated Dec. 29, 2009, received in U.S. Appl. No. 11/620,717, 8 pages. |
| TR—Office Action (Final), dated Jun. 23, 2009, received in U.S. Appl. No. 11/620,720, 17 pages |
| TR—Office Action, dated Nov. 18, 2009, received in U.S. Appl. No. 11/620,720, 17 pages. |
| TR—Office Action, dated Dec. 23, 2008, received in U.S. Appl. No. 11/620,720, 18 pages. |
| TR—Final Office Action, dated Nov. 17, 2009, received in U.S. Appl. No. 11/620,723, 8 pages. |
| TR—Office Action, dated Apr. 1, 2009, received in U.S. Appl. No. 11/620,723, 8 pages. |
| TR—Office Action, dated Jun. 8, 2010, received in U.S. Appl. No. 11/620,723, 8 pages. |
| TR—Notice of Allowance, dated Oct. 29, 2008, received in U.S. Appl. No. 11/956,969, 5 pages. |
| TR—Office Action, dated Mar. 30, 2012, received in U.S. Appl. No. 12/207,429, 9 pages. |
| TR—Notice of Allowance, dated May 17, 2012, received in U.S. Appl. No. 12/270,805, 14 pages. |
| TR—Office Action, dated Oct. 11, 2011, received in U.S. Appl. No. 12/270,805, 27 pages. |
| TR—Office Action, dated Oct. 11, 2011, received in U.S. Appl. No. 12/270,807, 26 pages. |
| TR—Notice of Allowance, dated May 11, 2012, received in U.S. Appl. No. 12/270,810, 12 pages. |
| TR—Notice of Allowance, dated Jul. 11, 2012, received in U.S. Appl. No. 12/270,810, 17 pages. |
| TR—Notice of Allowance, dated Sep. 19, 2012, received in U.S. Appl. No. 12/270,812, 22 pages. |
| TR—Office Action, dated Oct. 13, 2011, received in U.S. Appl. No. 12/270,812, 12 pages. |
| TR—Final Office Action, dated Feb. 14, 2013, received in U.S. Appl. No. 12/270,815, 12 pages. |
| TR—Office Action, dated May 17, 2012, received in U.S. Appl. No. 12/270,815, 11 pages. |
| TR—Office Action, dated Oct. 11, 2011, received in U.S. Appl. No. 12/270,815, 12 pages. |
| TR—Notice of Allowance, dated Feb. 23, 2012, received in U.S. Appl. No. 12/869,182, 5 pages. |
| TR—Notice of Allowance, dated Dec. 12, 2012, received in U.S. Appl. No. 12/869,182, 5 pages. |
| TR—Office Action, dated Jun. 20, 2012, received in U.S. Appl. No. 12/869,182, 6 pages. |
| TR—Office Action, dated Oct. 24, 2011, received in U.S. Appl. No. 12/869,182, 7 pages. |
| TR—Notice of Allowance, dated Oct. 22, 2013, received in U.S. Appl. No. 13/867,950, 8 pages. |
| TR—Notice of Allowance, dated Nov. 15, 2013, received in U.S. Appl. No. 13/867,950, 7 pages. |
| TR—Office Action, dated Jun. 26, 2013, received in U.S. Appl. No. 13/867,950, 5 pages. |
| TR—Office Action, dated Sep. 24, 2014, received in U.S. Appl. No. 14/189,922, 7 pages. |
| TR—Certificate of Grant, dated Feb. 3, 2012, received in Hong Kong Patent Application No. 10103983.1, 2 pages. |
| TR—Summons, dated Oct. 28, 2011, received in European Patent Application No. 08705751.9, 9 pages. |
| TR—Office Action, dated Nov. 26, 2012, received European Patent Application No. 08712964.9, 6 pages. |
| TR—Office Action, dated Oct. 7, 2011, received in European Patent Application No. 08713567.9, 1 page. |
| TR—Office Action, dated Dec. 29, 2009, received in European Patent Application No. 08713567.9, 5 pages. |
| TR—Patent, ction, dated Jun. 21, 2012, received in European Patent Application No. 08713567.9, 2 pages. |
| TR—Ex Parte Reexamination Communication, dated Jul. 26, 2013, received in U.S. Appl. No. 90/012,332, 61 pages. |
| TR—Office Action, dated Jul. 1, 2008, received in Australian Patent Application No. 2008100283, 2 pages. |
| TR—Office Action, dated Feb. 19, 2009, received in Australian Patent No. 2008201540, 2 pages. |
| TR—Office Action, dated Jul. 15, 2009, received in Australian Patent Application No. 2008201540, 2 pages. |
| TR—Office Action, dated Feb. 11, 2009, received in Australian Patent Application No. 2009200366, 2 pages. |
| TR—Office Action, dated Nov. 24, 2011, received in Australian Patent Application No. 2009208099, 3 pages. |
| TR—Office Action, dated Apr. 8, 2010, received in Australian Patent Application No. 2009208103, 2 pages. |
| TR—Office Action, dated Apr. 14, 2011, received in Australian Patent Application No. 2009208103, 3 pages. |
| TR—Office Action, dated Feb. 12, 2010, received in Japanese Patent Application No. 2009-544996, 3 pages. |
| TR—Office Action, dated Jun. 1, 2011, received in Japanese Patent Application No. 2009-544996, 1 page. |
| TR—Office Action, dated Nov. 8, 2010, received in Japanese Patent Application No. 2009-544996, 6 pages. |
| TR—Patent, dated May 20, 2011, received in Japanese Patent Application No. 2009-544996, 1 page. |
| TR—Office Action, dated Oct. 26, 2012, received in Japanese Patent Application No. 2010-157302, 4 pages. |
| TR—Office Action, dated Apr. 15, 2013, received in Japanese Patent Application No. 2010-157303, 4 pages. |
| TR—Office Action, dated Oct. 15, 2012, received in Japanese Patent Application No. 2010-157303, 4 pages. |
| TR—Notice of Allowance, dated Nov. 9, 2011, received in Australian Patent Application No. 2011201639, 2 pages. |
| TR—Innovation Patent, dated Mar. 2, 2012, received in Australian Patent Application No. 2012100050, 1 page. |
| TR—Office Action, Sep. 9, 2013, received in Australian Patent Application No. 2012200689, 3 pages. |
| TR—Office Action, dated Aug. 27, 2009, received in Korean Patent Application No. 2009-7003574,1 page. |
| TR—Office Action, dated Jun. 25, 2013, received in Korean Patent Application No. 2013-7000337, 3 pages. |
| TR—Office Action, dated Oct. 29, 2010, received in German Patent Application No. 112008000144.8, 4 pages. |
| Office Action, Jan. 5, 2012, received in Chinese Patent Application No. 200800000019.9, which corresponds with U.S. Appl. No. 11/956,969, 2 pages. |
| TR—Office Action, dated Feb. 18, 2013, received in Chinese Patent Application No. 200800000019.9, 2 pages. |
| TR—Office Action, dated Jul. 23, 2013, received in Chinese Patent Application No. 200800000019.9, 2 pages. |
| TR—Office Action, dated Sep. 20, 2012, received in Chinese Patent Application No. 200800000019.9, 1 page. |
| TR—Office Action, dated Nov. 23, 2010, received in Chinese Patent Application No. 200800000019.9, 2 pages. |
| TR—Office Action, dated Jan. 29, 2012, received in Chinese Patent Application No. 200880001827.7, 5 pages. |
| TR—Office Action, dated Jul. 2, 2013, received in Chinese Patent Application No. 200880001827.7, 1 page. |
| TR—Office Action, dated Nov. 11, 2010, received in Chinese Patent Application No. 200880001827.7, 2 pages. |
| TR—EESR, dated Nov. 29, 2011, received in European Patent Application No. 11182954.5, 6 pages. |
| TR—EESR, dated Nov. 30, 2011, received in European Patent Application No. 11182959.4, 5 pages. |
| TR—EESR, dated Jan. 12, 2011, received in European Patent Application No. 11182962.8, 8 pages. |
| TR—EESR, dated Jan. 12, 2011, received in European Patent Application No. 11182963.6, 7 pages. |
| TR—International Search Report, dated May 31, 2005, received in International Patent Application No. PCT/US2005/000089, 7 pages. |
| TR—International Preliminary Report on Patentability, dated Jun. 18, 2008, received in International Patent Application No. PCT/US2005/000089, 5 pages. |
| TR—International Search Report, dated Jul. 31, 2008, received in International Patent Application No. PCT/US2008/000058, 7 pages. |
| TR—International Preliminary Report on Patentability, dated Jul. 7, 2009, received in International Patent Application No. PCT/US2008/000058, 5 pages. |
| TR—International Search Report, dated Mar. 6, 2008, received in International Patent Application No. PCT/US2008/000103, 11 pages. |
| TR—International Preliminary Report on Patentability, dated Jul. 7, 2009, received in International Patent Application No. PCT/US2008/000103, 9 pages. |
| TR—Invitation to Pay Additional Fees, PCT Application PCT/US2008/050292, dated Jul. 18, 2008, 4 pages. |
| Office Action, dated Jan. 8, 2018, received in European Patent Application No. 11184186.2, which corresponds with U.S. Appl. No. 12/566,660, 4 pages. |
| Office Action, dated Jan. 26, 2018, received in Chinese Patent Application No. 201410198170.5, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Certificate of Grant, dated Mar. 22, 2018, received in Australian Patent Application No. 2016204284, which corresponds with U.S. Appl. No. 12/892,848, 1 page. |
| Office Action, dated Feb. 23, 2018, received in Japanese Patent Application No. 2016-146769, which corresponds with U.S. Appl. No. 13/077,925, 6 pages. |
| Notice of Allowance, dated Jan. 31, 2018, received in Korean Patent Application No. 2017-7018175, which corresponds with U.S. Appl. No. 13/077,925, 4 pages. |
| Certificate of Grant, dated Feb. 1, 2018, received in Australian Patent Application No. 2013242854, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Office Action, dated Feb. 2, 2018, received in Canadian Patent Application No. 2,931,604, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Certificate of Grant, dated Jan. 26, 2018, received in Hong Kong Patent Application No. 12106620.1, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Certificate of Grant, dated Jan. 26, 2018, received in Hong Kong Patent Application No. 12106621.0, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Office Action, dated Feb. 9, 2018, received in Chinese Patent Application No. 201410028534.5, which corresponds with U.S. Appl. No. 12/042,299, 3 pages. |
| Patent, dated Feb. 9, 2018, received in Chinese Patent Application No. 2014100285627, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Office Action, dated Feb. 1, 2018, received in Chinese Patent Application No. 201510175905.7, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Office Action, dated Jan. 17, 2018, received in Chinese Patent Application No. 201510175915.0, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Office Action, dated Feb. 15, 2018, received in U.S. Appl. No. 15/139,260 (7410), 22 pages. |
| Notice of Allowance, dated Mar. 20, 2018, received in U.S. Appl. No. 15/432,746 (7463), 5 pages. |
| Apple Inc., “iPad User Guide for iOS 4.2 Software”, http://support.apple.com/kb/index?page=answerlink&ur1=http%3A%2F%2Fmanuals.infor.apple.com%2Fen_US%2FiPad_iOS4_User_Guide.pdf&answerid=16777220&src=support_site.manuals.search, Nov. 8, 2010, 181 pages. |
| Notice of Allowance, dated Oct. 24, 2017, received in Canadian Patent Application No. 2,909,730, which corresponds with U.S. Appl. No. 12/566,660, 1 page. |
| Notice of Allowance, dated Oct. 24, 2017, received in Chinese Patent Application No. 201310557440.2, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Patent Certificate, dated Dec. 5, 2017, received in Chinese Patent Application No. 201310557440.2, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Notice of Acceptance, dated Nov. 15, 2017, received in Australian Patent Application No. 2016204284, which corresponds with U.S. Appl. No. 12/892,848, 3 pages. |
| Office Action, dated Oct. 24, 2017, received in Australian Patent Application No. 2017200807, which corresponds with U.S. Appl. No.13/077,925, 3 pages. |
| Notice of Allowance, dated Oct. 6, 2017, received in Australian Patent Application No. 2016206268, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Certificate of Granted, dated Oct. 27, 2017, received in Hong Kong Patent Application No. 12106622.9, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Certificate of Granted, dated Nov. 3, 2017, received in Hong Kong Patent Application No. 12106623.8, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Certificate of Grant, dated Nov. 3, 2017, received in Hong Kong Patent Application No. 12106624.7, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Office Action, dated Nov. 3, 2017, received in Hong Kong Patent Application No. 13100042.3, which corresponds with U.S. Appl. No.12/042,318, 2 pages. |
| Certificate of Grant, dated Oct. 13, 2017, received in Hong Kong Patent Application No. 13100043.2, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Patent, dated Oct. 13, 2017, received in Japanese Patent Application No. 2015-085361, which corresponds with U.S. Appl. No. 12/042,318, 2 pages. |
| Appeal Decision, dated Oct. 9, 2017, received in European Patent Application No.12188748.3, which corresponds with U.S. Appl. No.12/042,067, 16 pages. |
| Patent, dated Aug. 4, 2017, received in Honk Kong Application No. 10111901.3, which corresponds with U.S. Appl. No. 12/042,067, 2 pages. |
| Notice of Allowance, dated Nov. 28, 2017, received in Chinese Patent Application No. 2014100285627, which corresponds with U.S. Appl. No. 12/042,067, 2 pages. |
| Decision to Refuse Application, dated Sep. 6, 2017, received in European Patent Application No. 09700007.9, which corresponds with U.S. Appl. No. 12/042,299, 15 pages. |
| Summons to Attend Oral Proceedings, dated Dec. 6, 2017, received in European Patent Application No. 11184226.6, which corresponds with U.S. Appl. No. 12/042,299, 8 pages. |
| Notice of Allowance, dated Nov. 17, 2017, received in Japanese Patent Application No. 2016-133582, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Patent, dated Jan. 5, 2018, received in Japanese Patent Application No. 2016-133582, which corresponds with U.S. Appl. No. 12/042,299, 2 pages. |
| Patent, dated Aug. 4, 2017, received in Honk Kong Application No. 10100282.5, which corresponds with U.S. Appl. No. 12/042,237, 2 pages. |
| Summons to Attend Oral Proceedings, dated Dec. 6, 2017, received in European Patent Application No. 08705471.4, which corresponds with U.S. Appl. No. 11/620,727, 6 pages. |
| Notice of Allowance, dated Dec. 19, 2017, received in U.S. Appl. No. 15/046,252, 5 pages. |
| Final Office Action, dated Jan. 18, 2018, received in U.S. Appl. No. 15/432,746, 9 pages. |
| Office Action, dated Jan. 19, 2018, received in U.S. Appl. No. 14/978,655, 13 pages. |
| Extended European Search Report, dated Oct. 18, 2017, received in European Patent Application No. 17177247.8, which corresponds to U.S. Appl. No. 13/077,925, 11 pages. |
| Extended European Search Report, dated Nov. 3, 2017, received in European Patent Application No. 17165698.6, which corresponds with U.S. Appl. No. 11/620,715, 9 pages. |
| Intention to Grant, dated Nov. 2, 2018, received in European Patent Application No. 11727371.4, which corresponds with U.S. Appl. No. 12/892,848, 5 pages. |
| Office Action, dated Jan. 11, 2019, received in Chinese Patent Application No. 201610383388.7, which corresponds with U.S. Appl. No. 13/077,925, 5 pages. |
| Office Action, dated Dec. 14, 2018, received in Australian Patent Application No. 2017279639, which corresponds with U.S. Apppl. No. 12/042,318, 2 page. |
| Oral Summons, dated Jan. 24, 2019, received in German Patent Application No. 112009000002.9, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Office Action, dated Feb. 2, 2018, received in Chinese Patent Application No. 201510379780.X, which corresponds with U.S. Appl. No. 11/620,715, 5 pages. |
| Final Office Action, dated Dec. 10, 2018, received in U.S. Appl. No. 15/768,323, 12 pages. |
| Office Action, dated Aug. 23, 2018, received in European Patent Application No. 10712825.8, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Notice of Allowance, dated Sep. 3, 2018, received in Japanese Patent Application No. 2017-139218, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Patent, dated Sep. 28, 2018, received in Japanese Patent Application No, 2017-139218, which corresponds with U.S. Appl. No. 12/566,660, 2 pages. |
| Notice of Allowance, dated Aug. 16, 2018, received in Chinese Patent Application No. 201410198170.5, which corresponds with U.S. Appl. No. 12/789,695, 5 pages. |
| Patent, dated Oct. 30, 2018, received in Chinese Patent Application No. 201410198170.5, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Office Action, dated Aug. 23, 2018, recieved in European Patent Application No. 11152015.1, which corresponds with U.S. Appl. No. 12/789,695, 7 pages. |
| Office Action, dated Aug. 27, 2018, received in Chinese Patent Application No. 201610455059.9, which corresponds with U.S. Appl. No. 12/892,848, 5 pages. |
| Notice of Allowance, dated Nov. 8, 2018, received in U.S. Appl. No. 12/892,851, 7 pages. |
| Certificate of Grant, dated Aug. 23, 2018, received in Australian Patent Application No. 2017200807, which corresponds with U.S. Appl. No. 13/077,925, 1 page. |
| Office Action, dated Sep. 14, 2018, received in European Patent Application No. 17177247.8, which corresponds with U.S. Appl. No. 13/077,925, 6 pages. |
| Notice of Allowance, dated Jul. 31, 2018, received in Chinese Patent Application No. 201410028534.5), which corresponds with U.S. Appl. No. 12/042,299, 3 pages. |
| Oral Summons, dated Sep. 3, 2018, received in European Patent Application No. 11184224.1, which corresponds with U.S. Appl. No. 12/042,299, 7 pages. |
| Oral Summons, dated Sep. 5, 2018, received in European Patent Application No. 11184223.3, which corresponds with U.S. Appl. No. 12/042,299, 6 pages. |
| Notice of Allowance, dated Sep. 25, 2018, received in Japanese Patent Application No. 2017-238833, which correspond with U.S. Appl. No. 12/042,299, 5 pages. |
| Oral Summons, dated Sep. 3, 2018, received in European Patent Application No. 11184222.5, which corresponds with U.S. Appl. No. 12/042,299, 6 pages. |
| Patent, dated Nov. 2, 2018, received in Japanese Patent Applications No. 2017-238833, which correspond with U.S. Appl. No. 12/042,299, 2 pages. |
| Office Action, dated Oct. 8, 2018, received in Chinese Patent Application No. 201510175905.7, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Decision to Refuse a European Patent Application, dated Jul. 20, 2018, received in European Patent Application No. 08705471.4, which corresponds with U.S. Appl. No. 11/670,727, 14 pages. |
| Office Action dated Nov. 13, 2018, received in Chinese Patent Application No. 20148003219.7, which corresponds with U.S. Appl. No. 14/290,931, 4 pages. |
| Office Action, dated Oct. 24, 2018, received in European Patent Application No. 14734672.0, which corresponds with U.S. Appl. No. 14/290,931, 8 pages. |
| Notice of Allowance, dated Aug. 13, 2018, received in U.S. Appl. No. 15/139,260, 10 pages. |
| Office Action, dated Oct. 19, 2018, received in U.S. Appl. No. 15/647,180, 12 pages. |
| “Dreamweaver”, www.inforpower.com.cn, Feb. 29, 2008, 18 pages. |
| Hong et al., “SATIN: A Toolkit for Informal Ink-based Applications”, University of California, Berkeley, CA, 2000, 10 pages. |
| Landay, “Extending an Existing User Interface Toolkit to Support Gesture Recognition”, School of Computer Science,Pittsburgh, PA, USA, 1993, 2 pages. |
| “MySQL”, www.pptph.com.cn, Jul. 31, 2001, 9 pages. |
| Patent, dated Jun. 5, 2018, received in Canadian Patent Application No. 2,909,730, which corresponds with U.S. Appl. No. 12/566,660, 4 pages. |
| Office Action, dated Jun. 12, 2018, received in Indian Patent Application No. 6174/CHENP/2011, which corresponds with U.S. Appl. No. 12/566,332, 8 pages. |
| Office Action, dated Jul. 13, 2018, received in Japanese Patent Application No. 2017-139218, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Office Action, dated May 25, 2018, received in Australian Patent Application No. 2016204905, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Notice of Acceptance, dated Jul. 5, 2018, recieved in Australian Patent Application No. 2016204905, which corresponds with U.S. Appl. No. 12/789,695, 3 pages. |
| Oral Summons, dated Apr. 23, 2018, received in European Patent Application No. 11727371.4, which corresponds with U.S. Appl. No. 12/892,848, 11 pages. |
| Notice of Allowance, dated Jun. 27, 2018, received in U.S. Appl. No. 12/892,851 (5323), 7 pages. |
| Notice of Acceptance, dated Apr. 20, 2018, received in Australian Patent Application No. 2017200807, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Grant, dated May 4, 2018, received in Hong Kong Patent Application No. 14104128.1, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Patent, dated Apr. 26, 2018, received in Korean Patent Application No. 2017-7018175, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Oral Summons, dated Jul. 11, 2018, received in German Patent Application No. 102009011687.7, which corresponds with U.S. Appl. No.12/042,318, 30 pages. |
| Office Action, dated Jul. 9, 2018, received in Japanese Patent Application No. 2017-195359, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Decision to Refuse, datred Jun. 5, 2018, received in European Patent Application No. 11184226.6, which corresponds with U.S. Appl. No. 12/042,299, 14 pages. |
| Office Action, dated Jul. 11, 2018, received in Chinese Patent Application No. 201510175915.0, which corresponds with U.S. Appl. No. 12/042,237, 4 pages. |
| Office Action, dated Apr. 2, 2018, in Chinese Patent Application No. 201480032919.7, which corresponds with U.S. Appl. No, 14/290,931, 4 pages. |
| Office Action, dated Apr. 4, 2018, received in U.S. Appl. No. 15/786,323, 11 pages. |
| Office Action, dated Jun. 12, 2018, received in U.S. Appl. No. 15/676,954, 10 pages. |
| Decision to Grant, dated Sep. 19, 2019, received in European Patent Application No, 11184186.2, which corresponds with U.S. Appl. No, 12/566,660, 1 page. |
| Decision to Grant, dated Sep. 19, 2019, received in Hong Kong Patent Application No. 12107271.1, which corresponds with U.S. Appl. No. 12/566,660, 1 pages. |
| Office Action, dated Oct. 7, 2019, received in Japanese Patent Application Na. 2018-175226, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Patent, dated Sep. 13, 2019, received in Chinese Patent Application No. 201610383388.7, which corresponds with U.S. Appl. No. 13/077,925 6 pages. |
| Notice of Allowance, dated Sep. 4, 2019, received in Chinese Patent Application No. 201310053142.X, which corresponds with U.S. Appl. No. 12/042,067, 3 pages. |
| Decision to Grant, dated Aug. 13, 2019, received in German Patent application No, 112009000003.7, which corresponds with U.S. Appl. No. 12/042,299, 10 pages. |
| Certificate of Grant, dated Sep. 6, 2019, received in Hong Kong Patent Application No. 14110202.7, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Notice of Allowance, dated Oct. 10, 2019, received in Chinese Patent Application No. 201510175905.7, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Decision to Grant, dated Sep. 27, 2019, received in German Patent Application No. 112009000002.9, which corresponds with U.S. Appl. No. 12/042,237, 2 pages. |
| Office Action, dated Oct. 10, 2019, received in U.S. Appl. No. 15/647,180, 14 pages. |
| Notice of Allowance, dated Aug. 21, 2019, received in U.S. Appl. No. 15/979,357, 21 pages. |
| Oral Summons, dated Apr. 11, 2019, received in Indian Patent Application No. 6174/CHENP/2011, which corresponds with U.S. Appl. No. 12/566,332, 5 pages. |
| Summons, dated Mar. 15, 2019, received in European Patent Application No. 11152015.1, which corresponds with U.S. Appl. No. 12/789,695, 4 pages. |
| Decision to Grant, dated Mar. 21, 2019, received in European Patent Application No. 11727371.4, which corresponds with U.S. Appl. No. 12/892,848, 4 pages. |
| Final Office Action, dated Jan. 28, 2019, received in Japanese Patent Application No. 2016-146769, which corresponds with U.S. Appl. No. 13/077,925, 8 pages. |
| Intention to Grant, dated Feb. 12, 2019, received in Australian Patent Application No. 2017279639, which corresponds with U.S. Appl. No. 12/042,318, 3 page. |
| Notice of Allowance, dated Dec. 10, 2018, received in Canadian Patent Application No. 2,931,604, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Notice of Allowance, dated Apr. 2, 2019, received in Canadian Patent Application No. 3,011,844, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Patent, dated Feb. 7, 2019, received in German Patent Application No. 102009011687.7, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Summons, dated Feb. 8, 2019, received in German Patent application No. 112009000003.7, which corresponds with U.S. Appl. No. 12/042,299, 10 pages. |
| Decision to Refuse an EP App, dated Feb. 26, 2019, eceived in European Patent Application No. 11184224.1, which corresponds with U.S. Appl. No. 12/042,299, 5 pages. |
| Decision to Refuse a EP App, dated Feb. 26, 2019, received in European Patent Application No. 11184223.3, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Rejection Decision, dated Apr. 24, 2019, received in Chinese Patent Application No. 201510175905.7, which corresponds with U.S. Appl. No. 12/042,237, 2 pages. |
| Notice of Allowance, dated Feb. 18, 2019, received in Chinese Patent Application No. 201510175915.0, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Summons, dated Feb. 18, 2019, received in European Patent Application No. 15175530.3, which corresponds with U.S. Appl. No. 12/042,237, 6 pages. |
| Office Action, dated Feb. 28, 2019, received in European Patent Application No. 17165698.6, which corresponds with U.S. Appl. No. 11/620,715, 7 pages. |
| Notice of Allowance, dated Mar. 29, 2019, received in Chinese Patent Application No. 201480032919.7, which corresponds with U.S. Appl. No. 14/290,931. 3 pages. |
| Final Office Action, dated Mar. 1, 2019, received in U.S. Appl. No. 15/676,954, 13 pages. |
| Oral Summons, dated May 9, 2019, received in European Patent Application No. 10712825.8, which corresponds with U.S. Appl. No. 12/566,660, 9 pages. |
| Office Action, dated May 17, 2019, received in Chinese Patent Application No. 201610455059.9, which corresponds with U.S. Appl. No. 12/892,848, 4 pages. |
| Patent, dated Apr. 17, 2019, received in European Patent Application No. 11727371.4, which corresponds with U.S. Appl. No. 12/892,848, 3 pages. |
| Office Action, dated Jun. 29, 2019, received in Australian Patent Application No. 2018211275, which corresponds with U.S. Appl. No. 13/077,925, 2 pages. |
| Notice of Allowance, dated Aug. 9, 2019, received in Chinese Patent Application No. 201610383388.7, which corresponds with U.S. Appl. No. 13/077,925, 3 pages. |
| Office Action, dated Jul. 11, 2019, received in European Patent Application No. 17177247.8, which corresponds with U.S. Appl. No. 13/077,925, 7 pages. |
| Certificate of Grant, dated Jun. 6, 2019, received in Australian Patent Application No. 2017279639, which corresponds with U.S. Appl. No. 12/042,318, 1 page. |
| Patent, dated Jul. 9, 2019, received in Canadian Patent Application No. 2,931,604, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Patent, dated Jul. 9, 2019, received in Canadian Patent Application No. 3,011,844, which corresponds with U.S. Appl. No. 12/042,318, 4 pages. |
| Notice of Allowance, dated May 20, 2019, received in Israel Patent Application No. 197386, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated Jun. 3, 2019, received in Japanese Patent Application No. 2017-195359, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Office Action, dated May 31, 2019, received in Chinese Patent Application No. 201310053142.X, which corresponds with U.S. Appl. No. 12/042,067, 3 pages. |
| Office Action, dated May 21, 2019, received in German Patent application No. 112009000003.7, which corresponds with U.S. Appl. No. 12/042,299, 4 pages. |
| Patent, dated May 3, 2019, received in Chinese Patent Application No. 201510175915.0, which corresponds with U.S. Appl. No. 12/042,237, 4 pages. |
| Office Action, dated Jul. 23, 2019, received in Chinese Patent Application No. 201510379780.X, which corresponds with U.S. Appl. No. 11/620,715, 6 pages. |
| Patent, dated Jun. 14, 2019, received in Chinese Patent Application No. 201480032919.7, which corresponds with U.S. Appl. No. 14/290,931, 6 pages. |
| Office Action, dated Apr. 30, 2019, received in U.S. Appl. No. 15/339,768, 19 pages. |
| Final Office Action, dated May 8, 2019, received in U.S. Appl. No. 15/647,180, 15 pages. |
| Office Action, dated May 30, 2019, received in U.S. Appl. No. 15/786,323, 13 pages. |
| Office Action, dated Jul. 8, 2019, received in U.S. Appl. No. 15/676,954, 13 pages. |
| Office Action, dated Nov. 7, 2019, received in German Patent Application No. 112010001143.5, which corresponds with U.S. Appl. No. 12/566,660, 14 pages. |
| Patent, dated Oct. 16, 2019, received in European Patent Application No. 11184186.2, which corresponds with U.S. Appl. No. 12/566,660, 6 pages. |
| Office Action, dated Oct. 21, 2019, received in Chinese Patent Application No. 201610455059.9, which corresponds with U.S. Appl. No. 12/892,848, 4 pages. |
| Patent, dated Oct. 1, 2019, received in Israel Patent Application No. 244139, which corresponds with U.S. Appl. No. 12/042,318, 6 pages. |
| Patent, dated Oct. 11, 2019, received in Chinese Patent Application No. 201310053142.X, which corresponds with U.S. Appl. No. 12/042,067, 3 pages. |
| Office Action, dated Nov. 15, 2019, received in Japanese Patent Application No. 2018-200268, 5 pages. |
| Patent, dated Nov. 26, 2019, received in Chinese Patent Application No. 201510175905.7, which corresponds with U.S. Appl. No. 12/042,237, 6 pages. |
| Office Action, dated Nov. 1, 2019, received in Chinese Patent Application No. 201510379780.X, which corresponds with U.S. Appl. No. 11/620,715, 3 pages. |
| Final Office Action, dated Nov. 22, 2019, received in U.S. Appl. No. 15/339,768, 22 pages. |
| Notice of Allowance, dated Nov. 22, 2109, received in U.S. Appl. No. 16/240,662, 12 pages. |
| Patent, dated Dec. 12, 2019, received in Indian Patent Application No. 6174/CHENP/2011, which corresponds with U.S. Appl. No. 12/566,660, 4 pages. |
| Patent, dated Dec. 13, 2019, received in Hong Kong Patent Application No. 13107104.3, which corresponds with U.S. Appl. No. 12/892,848, 6 pages. |
| Patent, dated Nov. 21, 2019, received in German Patent application No. 112009000003.7, which corresponds with U.S. Patent Application No. 12/042,299, 4 pages. |
| Final Office Action, dated Dec. 11, 2019. U.S. Appl. No. 15/786,323, 17 pages. |
| Notice of Allowance, dated Mar. 24, 2020, received in U.S. Appl. No. 15/339,768,17 pages. |
| Final Office Action, dated Feb. 27, 2020, received in U.S. Appl. No. 15/647,180, 15 pages. |
| Final Office Action, dated Feb. 6, 2020, received in U.S. Appl. No. 15/676,954, 12 pages. |
| Notice of Allowance, dated Jan. 10, 2020, received in Japanese Patent Application No. 2017-195359, which corresponds with U.S. Appl. No. 12/042,318, 5 pages. |
| Patent, dated Feb. 10, 2020, received in Japanese Patent Application No. 2017-195359, which corresponds with U.S. Appl. No. 12/042,318, 3 pages. |
| Patent, dated Jan. 9, 2020, received in German Patent Application No. 112009000002.9, which corresponds with U.S. Appl. No. 12/042,237, 3 pages. |
| Decision to Refuse, dated Jan. 2, 2020, received in European Patent Application No. 15175530.3, which corresponds with U.S. Appl. No. 12/042,237, 12 pages. |
| Patent, dated Feb. 28, 2020, received in Hong Kong Patent Application No. 15112846.4, which corresponds with U.S. Appl. No. 12/042,237, 7 pages. |
| Notice of Allowance, dated Apr. 3, 2020, received in Japanese Patent Application No. 2018-175226, which corresponds with U.S. Appl. No. 12/566,660, 5 pages. |
| Notice of Allowance, dated Apr. 8, 2020, received in Chinese Patent Application No. 201610455059.9, which corresponds with U.S. Appl. No. 12/892,848, 3 pages. |
| Intention to Grant, dated Mar. 20, 2020, received in European Patent Application No. 17158104.4, which corresponds with U.S. Appl. No. 12/042,318, 7 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170286131 A1 | Oct 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61298531 | Jan 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12789695 | May 2010 | US |
| Child | 15623322 | US |
