Device, method, and graphical user interface for copying formatting attributes
An electronic device simultaneously displays on a touch-sensitive display a first user interface object and a second user interface object. The second user interface object has formatting attributes, one or more of which are distinct from corresponding formatting attributes in the first user interface object. The device detects a first contact on the first user interface object and a second contact on the second user interface object. While continuing to detect the first contact and the second contact, the device detects movement of the second contact across the touch-sensitive display, and moves the second user interface object in accordance with the movement of the second contact. The device changes one or more formatting attributes for the second user interface object to match corresponding formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving.
Latest Apple Patents:
- User interfaces for viewing live video feeds and recorded video
- Transmission of nominal repetitions of data over an unlicensed spectrum
- Systems and methods for intra-UE multiplexing in new radio (NR)
- Method and systems for multiple precoder indication for physical uplink shared channel communications
- Earphone
This application is a divisional application of U.S. patent application Ser. No. 12/848,074, filed on Jul. 30, 2010, now U.S. Pat. No. 9,081,494, issued Jul. 14, 2015, the entire contents of which is incorporated herein by reference.
FIELD OF THE INVENTIONThis relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that receive touch-based inputs to change formatting attributes (e.g., colors, line thickness, font, etc.) of user interface objects.
BACKGROUND OF THE INVENTIONThe use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate user interface objects on a display.
Exemplary manipulations include changing the formatting attributes (e.g., colors, line thickness, font, etc.) of one or more user interface objects. Exemplary user interface objects include digital images, video, text, icons, and other graphics. A user may need to perform such manipulations on user interface objects in a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processing application (e.g., Pages from Apple Inc. of Cupertino, Calif.), or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, Calif.).
But existing methods for changing object formatting attributes are cumbersome and inefficient. For example, existing keyboard-based methods require multiple steps that go through menus to change object attributes, which is tedious and creates a significant cognitive burden on a user. In addition, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
SUMMARY OF THE INVENTIONAccordingly, there is a need for computing devices with faster, more efficient methods and interfaces for changing the formatting attributes of user interface objects, including copying the formatting attributes of user interface objects from one object to another object. Such methods and interfaces may complement or replace conventional methods for changing the formatting attributes of user interface objects. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for computing devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions may include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions may be included in a computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, an electronic device includes a touch-sensitive display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the second set of formatting attributes are distinct from corresponding one or more formatting attributes in the first set of formatting attributes. The one or more programs also include instructions for: detecting a first contact on the first user interface object, and detecting a second contact on the second user interface object. The one or more programs also include instructions for, while continuing to detect the first contact on the first user interface object and the second contact on the second user interface object: detecting movement of the second contact across the touch-sensitive display; moving the second user interface object in accordance with the movement of the second contact; maintaining the second set of formatting attributes for the second user interface object if the second user interface object does not contact the first user interface object while moving the second user interface object in accordance with the movement of the second contact; and changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving the second user interface object in accordance with the movement of the second contact.
In accordance with some embodiments, a method is performed at an electronic device with a touch-sensitive display. The method includes simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the second set of formatting attributes are distinct from corresponding one or more formatting attributes in the first set of formatting attributes. The method also includes: detecting a first contact on the first user interface object, and detecting a second contact on the second user interface object. The method furthermore includes, while continuing to detect the first contact on the first user interface object and the second contact on the second user interface object: detecting movement of the second contact across the touch-sensitive display; moving the second user interface object in accordance with the movement of the second contact; maintaining the second set of formatting attributes for the second user interface object if the second user interface object does not contact the first user interface object while moving the second user interface object in accordance with the movement of the second contact; and changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving the second user interface object in accordance with the movement of the second contact.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by an electronic device with a touch-sensitive display, cause the device to simultaneously display on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the second set of formatting attributes are distinct from corresponding one or more formatting attributes in the first set of formatting attributes. The instructions also cause the device to: detect a first contact on the first user interface object, and detect a second contact on the second user interface object. The instructions furthermore cause the device to, while continuing to detect the first contact on the first user interface object and the second contact on the second user interface object: detect movement of the second contact across the touch-sensitive display; move the second user interface object in accordance with the movement of the second contact; maintain the second set of formatting attributes for the second user interface object if the second user interface object does not contact the first user interface object while moving the second user interface object in accordance with the movement of the second contact; and change one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving the second user interface object in accordance with the movement of the second contact.
In accordance with some embodiments, a graphical user interface on an electronic device with a touch-sensitive display, a memory, and one or more processors to execute one or more programs stored in the memory includes a simultaneous display of a first user interface object at a first location on the display and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the second set of formatting attributes are distinct from corresponding one or more formatting attributes in the first set of formatting attributes. A first contact is detected on the first user interface object. A second contact is detected on the second user interface object. While continuing to detect the first contact on the first user interface object and the second contact on the second user interface object, movement of the second contact across the touch-sensitive display is detected; the second user interface object is moved in accordance with the movement of the second contact; the second set of formatting attributes for the second user interface object is maintained if the second user interface object does not contact the first user interface object while moving the second user interface object in accordance with the movement of the second contact; and one or more formatting attributes in the second set of formatting attributes for the second user interface object are changed to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving the second user interface object in accordance with the movement of the second contact.
In accordance with some embodiments, an electronic device includes a touch-sensitive display; and means for simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the second set of formatting attributes are distinct from corresponding one or more formatting attributes in the first set of formatting attributes. The electronic device also includes: means for detecting a first contact on the first user interface object; and means for detecting a second contact on the second user interface object. The electronic device furthermore includes, while continuing to detect the first contact on the first user interface object and the second contact on the second user interface object: means for detecting movement of the second contact across the touch-sensitive display; means for moving the second user interface object in accordance with the movement of the second contact; means for maintaining the second set of formatting attributes for the second user interface object if the second user interface object does not contact the first user interface object while moving the second user interface object in accordance with the movement of the second contact; and means for changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving the second user interface object in accordance with the movement of the second contact.
In accordance with some embodiments, an information processing apparatus for use m an electronic device with a touch-sensitive display includes means for simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the second set of formatting attributes are distinct from corresponding one or more formatting attributes in the first set of formatting attributes. The information processing apparatus also includes: means for detecting a first contact on the first user interface object; and means for detecting a second contact on the second user interface object. The information processing apparatus furthermore includes, while continuing to detect the first contact on the first user interface object and the second contact on the second user interface object: means for detecting movement of the second contact across the touch-sensitive display; means for moving the second user interface object in accordance with the movement of the second contact; means for maintaining the second set of formatting attributes for the second user interface object if the second user interface object does not contact the first user interface object while moving the second user interface object in accordance with the movement of the second contact; and means for changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving the second user interface object in accordance with the movement of the second contact.
In accordance with some embodiments, an electronic device includes a touch-sensitive display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the first set of formatting attributes are distinct from corresponding one or more formatting attributes in the second set of formatting attributes. The one or more programs also include instructions for: detecting a first contact on the first user interface object; detecting a second contact on the first user interface object; and, in response to detecting the second contact on the first user interface object, displaying a style indicia at a location corresponding to the second contact on the touch-sensitive display. The style indicia graphically represents a subset of the first set of formatting attributes. The one or more programs furthermore include instructions for, while continuing to detect the first contact on the first user interface object: detecting movement of the second contact across the touch-sensitive display; moving the style indicia in accordance with the movement of the second contact; and detecting termination of the second contact. The one or more programs include instructions for, in response to detecting the termination of the second contact: maintaining the second set of formatting attributes for the second user interface object if a location of the style indicia, when the second contact is terminated, does not correspond to the second location; and changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the location of the style indicia, when the second contact is terminated, corresponds to the second location.
In accordance with some embodiments, a method is performed at an electronic device with a touch-sensitive display. The method includes simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the first set of formatting attributes are distinct from corresponding one or more formatting attributes in the second set of formatting attributes. The method also includes: detecting a first contact on the first user interface object; detecting a second contact on the first user interface object, and in response to detecting the second contact on the first user interface object, displaying a style indicia at a location corresponding to the second contact on the touch-sensitive display. The style indicia graphically represents a subset of the first set of formatting attributes. The method also includes, while continuing to detect the first contact on the first user interface object: detecting movement of the second contact across the touch-sensitive display; moving the style indicia in accordance with the movement of the second contact; and detecting termination of the second contact. The method includes, in response to detecting the termination of the second contact: maintaining the second set of formatting attributes for the second user interface object if a location of the style indicia, when the second contact is terminated, does not correspond to the second location; and changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the location of the style indicia, when the second contact is terminated, corresponds to the second location.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by an electronic device with a touch-sensitive display, cause the device to simultaneously display on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the first set of formatting attributes are distinct from corresponding one or more formatting attributes in the second set of formatting attributes. The instructions also cause the device to: detect a first contact on the first user interface object; detect a second contact on the first user interface object; and in response to detecting the second contact on the first user interface object, display a style indicia at a location corresponding to the second contact on the touch-sensitive display. The style indicia graphically represents a subset of the first set of formatting attributes. The instructions also cause the device to, while continuing to detect the first contact on the first user interface object: detect movement of the second contact across the touch-sensitive display; move the style indicia in accordance with the movement of the second contact; and detect termination of the second contact. The instructions cause the device to, in response to detecting the termination of the second contact: maintain the second set of formatting attributes for the second user interface object if a location of the style indicia, when the second contact is terminated, does not correspond to the second location; and change one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the location of the style indicia, when the second contact is terminated, corresponds to the second location.
In accordance with some embodiments, a graphical user interface on an electronic device with a touch-sensitive display, a memory, and one or more processors to execute one or more programs stored in the memory includes a simultaneous display of: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the first set of formatting attributes are distinct from corresponding one or more formatting attributes in the second set of formatting attributes. A first contact is detected on the first user interface object. A second contact is detected on the first user interface object. In response to detecting the second contact on the first user interface object, a style indicia is displayed at a location corresponding to the second contact on the touch-sensitive display. The style indicia graphically represents a subset of the first set of formatting attributes. While continuing to detect the first contact on the first user interface object, movement of the second contact across the touch-sensitive display is detected; the style indicia is moved in accordance with the movement of the second contact; and termination of the second contact is detected. In response to detecting the termination of the second contact, the second set of formatting attributes for the second user interface object is maintained if a location of the style indicia, when the second contact is terminated, does not correspond to the second location; and one or more formatting attributes in the second set of formatting attributes for the second user interface object are changed to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the location of the style indicia, when the second contact is terminated, corresponds to the second location.
In accordance with some embodiments, an electronic device includes a touch-sensitive display; and means for simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the first set of formatting attributes are distinct from corresponding one or more formatting attributes in the second set of formatting attributes. The electronic device also includes: means for detecting a first contact on the first user interface object; means for detecting a second contact on the first user interface object; and means, enabled in response to detecting the second contact on the first user interface object, for displaying a style indicia at a location corresponding to the second contact on the touch-sensitive display. The style indicia graphically represents a subset of the first set of formatting attributes. The electronic device furthermore includes, while continuing to detect the first contact on the first user interface object: means for detecting movement of the second contact across the touch-sensitive display; means for moving the style indicia in accordance with the movement of the second contact; means for detecting termination of the second contact; and, in response to detecting termination of the second contact: means for maintaining the second set of formatting attributes for the second user interface object if a location of the style indicia, when the second contact is terminated, does not correspond to the second location; and means for changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the location of the style indicia, when the second contact is terminated, corresponds to the second location.
In accordance with some embodiments, an information processing apparatus for use m an electronic device with a touch-sensitive display includes means for simultaneously displaying on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location. The first user interface object has a first set of formatting attributes, and the second user interface object has a second set of formatting attributes. One or more formatting attributes in the first set of formatting attributes are distinct from corresponding one or more formatting attributes in the second set of formatting attributes. The information processing apparatus also includes: means for detecting a first contact on the first user interface object; means for detecting a second contact on the first user interface object; and means, enabled in response to detecting the second contact on the first user interface object, for displaying a style indicia at a location corresponding to the second contact on the touch-sensitive display. The style indicia graphically represents a subset of the first set of formatting attributes. The information processing apparatus furthermore includes, while continuing to detect the first contact on the first user interface object: means for detecting movement of the second contact across the touch-sensitive display; means for moving the style indicia in accordance with the movement of the second contact; means for detecting termination of the second contact; and, in response to detecting the termination of the second contact: means for maintaining the second set of formatting attributes for the second user interface object if a location of the style indicia, when the second contact is terminated, does not correspond to the second location; and means for changing one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the location of the style indicia, when the second contact is terminated, corresponds to the second location.
In accordance with some embodiments, an electronic device includes a touch-sensitive display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for displaying on the touch-sensitive display at least a portion of an electronic document at a first magnification. The displayed portion of the electronic document includes at least a first user interface object. The one or more programs also include instructions for, while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object: detecting a second contact on the touch-sensitive display, and detecting movement of the second contact across the touch-sensitive display. The one or more programs furthermore include instructions for, in response to detecting the movement of the second contact across the touch-sensitive display: when a first predefined condition is satisfied, increasing the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact; and when a second predefined condition is satisfied, copying the first user interface object and displaying a second user interface object at the first magnification at a location that corresponds to the second contact. The second user interface object is a copy of the first user interface object.
In accordance with some embodiments, a method is performed at an electronic device with a touch-sensitive display. The method includes displaying on the touch-sensitive display at least a portion of an electronic document at a first magnification. The displayed portion of the electronic document includes at least a first user interface object. The method also includes, while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object: detecting a second contact on the touch-sensitive display; and detecting movement of the second contact across the touch-sensitive display. The method furthermore includes, in response to detecting the movement of the second contact across the touch-sensitive display: when a first predefined condition is satisfied, increasing the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact; and when a second predefined condition is satisfied, copying the first user interface object and displaying a second user interface object at the first magnification at a location that corresponds to the second contact. The second user interface object is a copy of the first user interface object.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by an electronic device with a touch-sensitive display, cause the device to display on the touch-sensitive display at least a portion of an electronic document at a first magnification. The displayed portion of the electronic document includes at least a first user interface object. The instructions also cause the device to, while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object: detect a second contact on the touch-sensitive display; and detect movement of the second contact across the touch-sensitive display. The instructions furthermore cause the device to, in response to detecting the movement of the second contact across the touch-sensitive display: when a first predefined condition is satisfied, increase the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact; and when a second predefined condition is satisfied; copy the first user interface object and display a second user interface object at the first magnification at a location that corresponds to the second contact. The second user interface object is a copy of the first user interface object.
In accordance with some embodiments, a graphical user interface on an electronic device with a touch-sensitive display, a memory, and one or more processors to execute one or more programs stored in the memory includes at least a portion of an electronic document at a first magnification. The displayed portion of the electronic document includes at least a first user interface object. While detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object: a second contact is detected on the touch-sensitive display; and movement of the second contact across the touch-sensitive display is detected. In response to detecting the movement of the second contact across the touch-sensitive display, when a first predefined condition is satisfied, the magnification at which the electronic document is displayed is increased from the first magnification to a second magnification in accordance with the movement of the second contact; and when a second predefined condition is satisfied, the first user interface object is copied and a second user interface object is displayed at the first magnification at a location that corresponds to the second contact. The second user interface object is a copy of the first user interface object.
In accordance with some embodiments, an electronic device includes: a touch-sensitive display; and means for displaying on the touch-sensitive display at least a portion of an electronic document at a first magnification. The displayed portion of the electronic document includes at least a first user interface object. The electronic device also includes, while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object: means for detecting a second contact on the touch-sensitive display; means for detecting movement of the second contact across the touch-sensitive display; and, in response to detecting the movement of the second contact across the touch-sensitive display: means, enabled when a first predefined condition is satisfied, for increasing the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact; and means, enabled when a second predefined condition is satisfied, for copying the first user interface object and displaying a second user interface object at the first magnification at a location that corresponds to the second contact. The second user interface object is a copy of the first user interface object.
In accordance with some embodiments, an information processing apparatus for use in an electronic device with a touch-sensitive display includes means for displaying on the touch-sensitive display at least a portion of an electronic document at a first magnification. The displayed portion of the electronic document includes at least a first user interface object. The information processing apparatus also includes; while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object: means for detecting a second contact on the touch-sensitive display; means for detecting movement of the second contact across the touch-sensitive display; and, in response to detecting the movement of the second contact across the touch-sensitive display: means, enabled when a first predefined condition is satisfied, for increasing the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact; and means, enabled when a second predefined condition is satisfied, for copying the first user interface object and displaying a second user interface object at the first magnification at a location that corresponds to the second contact. The second user interface object is a copy of the first user interface object.
Thus, electronic devices with touch-sensitive displays are provided with faster, more efficient methods and interfaces for changing formatting attributes of user interface objects, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for changing formatting attributes of user interface objects.
For a better understanding of the aforementioned embodiments of the invention as well as additional embodiments thereof, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Many electronic devices have graphical user interfaces that display and manipulate user interface objects. The objects typically have a variety of formatting attributes (e.g., colors, line thickness, font, etc.). A user may want to change the formatting attributes of a first object to match the formatting attributes of a second object (i.e., copy the formatting attributes). Existing methods for copying formatting attributes typically require a sequence of user inputs that navigate in a menu system. For example, a user typically needs to display a menu. The displayed menu may or may not include menu options for changing formatting attributes. When the displayed menu does not include menu options for changing formatting attributes, the user needs to search through multiple menus and/or sub-menus to find a menu that has the menu options for changing formatting attributes. After displaying the menu that has the menu options for changing formatting attributes, the user needs to select a respective menu option for changing a respective formatting attribute (e.g., one of color, line thickness, and font, etc.) to initiate changing the respective formatting attribute. In some of the embodiments described below, an improved method for copying formatting attributes from a first user interface object to a second user interface object is disclosed. The first user interface object and the second user interface object are selected based on respective finger contacts. The second user interface object is moved in accordance with the finger contact on the second user interface object such that the second user interface object contacts the first user interface object. In response, the formatting attributes of the second user interface object are changed to match the corresponding formatting attributes of the first user interface object. This method streamlines the process of copying formatting attributes by changing a plurality of formatting attributes in response to a single gesture, thereby eliminating the need to navigate through menus or use extra, separate steps to change respective formatting attributes. In other embodiments described below, a method for copying formatting attributes from a first user interface object to a second user interface object using a “swatch” of style attributes is disclosed. In still other embodiments described below, heuristics for distinguishing between similar gestures that produce separate, distinct object manipulations are disclosed.
Below,
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 “includes,” “including,” “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 “resolution” of a display refers to the number of pixels (also called “pixel counts” or “pixel resolution”) along each axis or in each dimension of the display. For example, a display may have a resolution of 320×480 pixels. Furthermore, as used herein, the term “resolution” of a multifunction device refers to the resolution of a display in the multifunction device. The term “resolution” does not imply any limitations on the size of each pixel or the spacing of pixels. For example, compared to a first display with a 1024×768-pixel resolution, a second display with a 320×480-pixel resolution has a lower resolution. However, it should be noted that the physical size of a display depends not only on the pixel resolution, but also on many other factors, including the pixel size and the spacing of pixels. Therefore, the first display may have the same, smaller, or larger physical size, compared to the second display.
As used herein, the term “video resolution” of a display refers to the density of pixels along each axis or in each dimension of the display. The video resolution is often measured in a dots-per-inch (DPI) unit, which counts the number of pixels that can be placed in a line within the span of one inch along a respective dimension of the display.
Embodiments of computing devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the computing device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), may also be used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the computing device may include one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application,
a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device may support the variety of applications with user interfaces that are intuitive and transparent to the user.
The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. No. 11/459,606, “Keyboards for Portable Electronic Devices,” filed Jul. 24, 2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference in their entireties. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of the components. The various components shown in
Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU 120 and the peripherals interface 118, may be controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU I10 and memory 2. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 may include display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from portable device 100, whereas touch sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
In some embodiments, device 100 may include a physical or virtual wheel (e.g., a click wheel) as input control device 116. A user may navigate among and interact with one or more graphical objects (e.g., icons) displayed in touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of touch screen 112 and display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 may also include one or more optical sensors 164.
Device 100 may also include one or more proximity sensors 166.
Device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple Inc.) devices.
Contact/motion module 130 may detect contact with touch screen 112 (in conjunction with display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detects contact on a touchpad. In some embodiments, contact/motion module 130 and controller 160 detects contact on a click wheel.
Contact/motion module 130 may detect a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture may be detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:
-
- contacts module 137 (sometimes called an address book or contact list);
- telephone module 138;
- video conferencing module 139;
- e-mail client module 140;
- instant messaging (IM) module 141;
- workout support module 142;
- camera module 143 for still and/or video images;
- image management module 144;
- video player module 145;
- music player module 146;
- browser module 147;
- calendar module 148;
- widget modules 149, which may include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
- widget creator module 150 for making user-created widgets 149-6;
- search module 151;
- video and music player module 152, which merges video player module 145 and music player module 146;
- notes module 153;
- map module 154; and/or
- online video module 155.
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, and speaker 111, video player module 145 includes executable instructions to display, present or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, music player module 146 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files. In some embodiments, device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, OPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the content of which is hereby incorporated by reference in its entirety.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (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 re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.
The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a mam, home, or root menu from any user interface that may be displayed on device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is(are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch sensitive display 112 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 is a set of views, 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 programmatic levels within a programmatic or 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 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the 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 184 compares the event information to predefined event or sub-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 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-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, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 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 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent 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 sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 176 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
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 multifunction devices 100 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 of the device, oral instructions, detected eye movements, biometric inputs, and/or any combination thereof, which may be utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also may accept verbal input for activation or deactivation of some functions through microphone 113.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that may be implemented on portable multifunction device 100.
-
- Signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals;
- Time 404;
- Bluetooth indicator 405;
- Battery status indicator 406;
- Tray 408 with icons for frequently used applications, such as:
- Phone 138, which may include an indicator 414 of the number of missed calls or voicemail messages;
- E-mail client 140, which may include an indicator 410 of the number of unread e-mails;
- Browser 147; and
- Music player 146; and
- Icons for other applications, such as:
- IM 141;
- Image management 144;
- Camera 143;
- Video player 145;
- Weather 149-1;
- Stocks 149-2;
- Workout support 142;
- Calendar 148;
- Calculator 149-3;
- Alarm clock 149-4;
- Dictionary 149-5; and
- User-created widget 149-6.
In some embodiments, user interface 400B includes the following elements, or a subset or superset thereof:
-
- 402, 404, 405, 406, 141, 148, 144, 143, 149-3, 149-2, 149-1, 149-4, 410, 414, 138, 140, and 147, as described above;
- Map 154;
- Notes 153;
- Settings 412, which provides access to settings for device 100 and its various applications 136, as described further below;
- Video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152; and
- Online video module 155, also referred to as YouTube (trademark of Google Inc.)
- play 45 module 155.
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture may be replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture may be replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice may be used simultaneously, or a mouse and finger contacts may be used simultaneously.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on a multifunction device with a display and a touch-sensitive surface, such as device 300 or portable multifunction device 100.
Although
In
In
Although style indicia 514 in
In
In some embodiments, when style indicia 514 contacts object 512 while moving style indicia 514 in accordance with contacts 513 and 515, one or more formatting attributes of object 512 are changed to match corresponding formatting attributes of object 510 (not shown).
Alternatively, as shown in
Although
In
In
In some embodiments, at least one of the contacts does not need to be detected on a user interface object to increase the magnification. For example, in
In
Although
In
As described below, method 600 provides an intuitive way to copy formatting attributes of a user interface object to match formatting attributes of another user interface object. The method reduces the cognitive burden on a user when copying formatting attributes of a user interface object, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to copy formatting attributes of a user interface object faster and more efficiently conserves power and increases the time between battery charges.
The device simultaneously displays (602) on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location (e.g., objects 502 and 504 in
Exemplary formatting attributes include: text color, font, font size, text background color, fill color and pattern, line weight and style, line colors, and shadow.
The device detects (604) a first contact (e.g., a single-finger contact) on the first user interface object (e.g., contact 505 on object 502 in
In some embodiments, the first contact is made (608) with a first number of fingers and the second contact is made with a second number of fingers, and the first number is distinct from the second number. In some embodiments, the first contact is a single-finger contact, and the second contact is a two-finger contact.
Operations 612-624 are performed while the device continues (610) to detect the first contact.
The device detects (612) movement of the second contact across the touch-sensitive display (e.g., contact 507 in
In some embodiments, the first user interface object is maintained (614) at the first location while detecting the movement of the second contact (e.g., object 502 in
The device moves (616) the second user interface object in accordance with the movement of the second contact (e.g., object 504 in
In some embodiments, the device displays (618) visual indicia of the second location while moving the second user interface object in accordance with the movement of the second contact (e.g., visual indicia 506 in
In some embodiments, the visual indicia of the second location has (620) a shape of the second user interface object (e.g., the visual indicia 506 is a residual image of the second user interface object). In some embodiments, the visual indicia of the second location has the shape and size of the second user interface object.
The device maintains (622) the second set of formatting attributes for the second user interface object if the second user interface object does not contact the first user interface object while moving the second user interface object in accordance with the movement of the second contact. For example, in
The device changes (624) one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the second user interface object contacts the first user interface object while moving the second user interface object in accordance with the movement of the second contact. For example, in
In some embodiments, after detecting movement of the second contact across the touch-sensitive display, the device detects (626) termination (e.g., lift-off) of the second contact, and in response to detecting termination of the second contact, returns the second user interface object to the second location (e.g., in
In other embodiments, the second user interface object does not return to the second location. Instead, the location the second user interface object after termination of the second contact is in accordance with the location and/or movement of the second contact at termination. In other words, in some embodiments, the device detects a lift-off of the second contact, and in response to detecting the lift-off of the second contact, the device maintains the second user interface object at a location of the second contact when the lift-off of the second contact is detected (e.g., in
Note that details of the processes described above with respect to method 600 are also applicable in an analogous manner to the methods described below, including methods 700 and 800. For brevity, these details are not repeated below.
As described below, method 700 provides an intuitive way to copy formatting attributes of a user interface object to match formatting attributes of another user interface object. The method reduces the cognitive burden on a user when copying formatting attributes of a user interface object, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to copy formatting attributes of a user interface object faster and more efficiently conserves power and increases the time between battery charges.
The device simultaneously displays (702) on the touch-sensitive display: a first user interface object at a first location on the display, and a second user interface object at a second location on the display distinct from the first location (e.g., objects 510 and 512 in
The device detects (704) a first contact on the first user interface object (e.g., contact 511 in
The device detects (706) a second contact on the first user interface object. In some embodiments, at least one of the first contact and the second contact comprises a multi-finger contact (e.g., in
In some embodiments, in response to detecting the second contact on the first user interface object, the device displays (708) a style indicia at a location corresponding to the second contact on the touch-sensitive display (e.g., the style indicia is displayed first when the second contact is detected on the first user interface object). The style indicia graphically represents a subset of the first set of formatting attributes. In some embodiments, the style indicia and the first user interface object have a same visual style (e.g., in
Operations 712-722 are performed while the device continues (710) to detect the first contact.
The device detects (712) movement of the second contact across the touch-sensitive display (e.g., movement of the second contact that comprises contact 513 and contact 515, as shown in
The device moves (714) the style indicia in accordance with the movement of the second contact (e.g., style indicia 514 in
The device detects (716) termination of the second contact (e.g., lift-off of the second contact that comprises contact 513 and 515, as shown in
In response to detecting the termination of the second contact (718), the device maintains (720) the second set of formatting attributes for the second user interface object if a location of the style indicia when the second contact is terminated does not correspond to the second location (e.g., style indicia 514 does not contact object 512 when the second contact is terminated, or a location of a centroid of style indicia 514 does not correspond to the location of object 512 when the second contact is terminated).
In response to detecting the termination of the second contact (718), the device changes (722) one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the location of the style indicia when the second contact is terminated corresponds to the second location (e.g., style indicia 514 contacts object 512 when the second contact is terminated as shown in
Alternatively, the device maintains the second set of formatting attributes for the second user interface object if the style indicia does not contact the second user interface object while moving the style indicia in accordance with the movement of the second contact, and the device changes one or more formatting attributes in the second set of formatting attributes for the second user interface object to match corresponding one or more formatting attributes in the first set of formatting attributes for the first user interface object if the style indicia contacts the second user interface object while moving the style indicia in accordance with the movement of the second contact.
Note that details of the processes described above with respect to method 700 are also applicable in an analogous manner to method 800 described below. For brevity, these details are not repeated below.
As described below, method 800 provides an intuitive way to manipulate a user interface object in a variety of ways (e.g., creating a duplicate (copy) of the user interface object, magnifying the user interface object (e.g., via a zoom-in animation), and/or rotating the user interface object) using heuristics that distinguish between similar, but distinct multi-touch gestures. The method reduces the cognitive burden on a user and chances of error when manipulating a user interface object, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate a user interface object faster and more efficiently conserves power and increases the time between battery charges.
The device displays (802) on the touch-sensitive display at least a portion of an electronic document at a first magnification. The displayed portion of the electronic document includes at least a first user interface object. For example, in
Operations 806-828 are performed while the device detects (804) a first contact on the touch-sensitive display at a location that corresponds to the first user interface object (e.g., contact 521 in
The device detects (806) a second contact on the first user interface object. In some embodiments, at least one of the first contact and the second contact comprises a multi-finger contact. For example, in
The device detects (808) movement of the second contact across the touch-sensitive display (e.g., movement of second contact comprising contact 523 and contact 525 in
In response to detecting the movement of the second contact across the touch-sensitive display (810), the device performs the following operations (e.g., operations 812 through 828).
Alternatively, in some embodiments, the device detects movement of at least one of the first contact and the second contact across the touch-sensitive display, and in response to detecting the movement of at least one of the first contact and the second contact across the touch-sensitive display, the device performs operations analogous to operations 812 through 828 described below.
When a first predefined condition is satisfied, the device increases (812) the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact (e.g., magnification is increased in
When a second predefined condition is satisfied, the device copies (814) the first user interface object and displays a second user interface object at the first magnification at a location that corresponds to the second contact. The second user interface object is a copy of the first user interface object. For example, in
Examples of the first predefined condition and the second predefined condition (816) are described below with reference to operations 820 through 826 (shown in
In some embodiments, the first predefined condition is satisfied (820) when the second contact is a single-finger contact (e.g., contact 527 in
In some embodiments, the first predefined condition is satisfied (822) when the second contact is a single-finger contact (e.g., contact 527 in
In some embodiments, the first predefined condition is satisfied (824) when the second contact is initially detected at a location other than a location of the first user interface object (e.g., contact 531 in
In some embodiments, the first predefined condition is satisfied (826) when the first contact and the second contact are detected within a predefined time interval from each other (e.g., the first contact and the second contact are detected within 0.2 seconds of each other), and the second predefined condition is satisfied when the second contact is detected more than the predefined time interval after the first contact is detected (e.g., the first contact and the second contact are detected more than 0.2 seconds apart).
In some embodiments, a combination of two or more conditions described above and/or additional conditions may be used.
In some embodiments, when a third predefined condition is satisfied, the device rotates (818) the first user interface object in accordance with the movement of the second contact (e.g., object 520 in
In some embodiments, the first predefined condition is satisfied (828 in
The operations in the information processing methods described above may be implemented by running one or more functional modules in information processing apparatus such as general purpose processors or application specific chips. These modules, combinations of these modules, and/or their combination with general hardware (e.g., as described above with respect to
The operations described above with reference to
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.
Claims
1. An electronic device, comprising:
- a touch-sensitive display;
- one or more processors;
- memory; and
- one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying on the touch-sensitive display at least a portion of an electronic document at a first magnification, wherein the displayed portion of the electronic document includes at least a first user interface object; and while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object: detecting a second contact on the touch-sensitive display; detecting movement of the second contact across the touch-sensitive display; and in response to detecting the movement of the second contact across the touch-sensitive display: in accordance with a determination that a first predefined condition is satisfied, increasing the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact, wherein the first predefined condition is satisfied when the first contact and the second contact are detected within a predefined time interval from each other, and the second contact is detected at a location other than a location of the first user interface object; and in accordance with a determination that a second predefined condition is satisfied, rotating the first user interface object in accordance with the movement of the second contact, wherein the second predefined condition is different from the first predefined condition and is satisfied when the first contact and the second contact are detected within the predefined time interval from each other, and the second contact is detected on the first user interface object.
2. The electronic device of claim 1, wherein the first predefined condition includes that the second contact is a single-finger contact, and the second predefined condition includes that the second contact is a two-finger contact.
3. The electronic device of claim 1, wherein the first predefined condition includes that the second contact is a single-finger contact, and the second predefined condition includes that the second contact is a two-finger contact that is initially detected at a location that corresponds to the first user interface object.
4. The electronic device of claim 1, wherein the first predefined condition includes that the second contact is initially detected at a location other than a location of the first user interface object, and the second predefined condition includes that the second contact is initially detected at a location that corresponds to the first user interface object.
5. The electronic device of claim 1, wherein the first predefined condition includes that the first contact and the second contact are detected within a predefined time interval from each other, and the second predefined condition includes that the second contact is detected more than the predefined time interval after the first contact is detected.
6. The electronic device of claim 1, the one or more programs including instructions for, in accordance with a determination that a third predefined condition is satisfied, copying the first user interface object and displaying a second user interface object at a first magnification at a location that corresponds to the second contact, wherein the second user interface object is a copy of the first user interface object.
7. The electronic device of claim 6, wherein the third predefined condition is satisfied when the second contact is detected more than the predefined time interval after the first contact is detected.
8. A method, comprising:
- at an electronic device with a touch-sensitive display: displaying on the touch-sensitive display at least a portion of an electronic document at a first magnification, wherein the displayed portion of the electronic document includes at least a first user interface object; and while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object, detecting a second contact on the touch-sensitive display; detecting movement of the second contact across the touch-sensitive display; and in response to detecting the movement of the second contact across the touch-sensitive display: in accordance with a determination that a first predefined condition is satisfied, increasing the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact, wherein the first predefined condition is satisfied when the first contact and the second contact are detected within a predefined time interval from each other, and the second contact is detected at a location other than a location of the first user interface object; and in accordance with a determination that a second predefined condition is satisfied, rotating the first user interface object in accordance with the movement of the second contact, wherein the second predefined condition is different from the first predefined condition and is satisfied when the first contact and the second contact are detected within the predefined time interval from each other, and the second contact is detected on the first user interface object.
9. The method of claim 8, wherein the first predefined condition includes that the second contact is a single-finger contact, and the second predefined condition includes that the second contact is a two-finger contact.
10. The method of claim 8, wherein the first predefined condition includes that the second contact is a single-finger contact, and the second predefined condition includes that the second contact is a two-finger contact that is initially detected at a location that corresponds to the first user interface object.
11. The method of claim 8, wherein the first predefined condition includes that the second contact is initially detected at a location other than a location of the first user interface object, and the second predefined condition includes that the second contact is initially detected at a location that corresponds to the first user interface object.
12. The method of claim 8, wherein the first predefined condition includes that the first contact and the second contact are detected within a predefined time interval from each other, and the second predefined condition includes that the second contact is detected more than the predefined time interval after the first contact is detected.
13. The method of claim 8, the one or more programs including instructions for, in accordance with a determination that a third predefined condition is satisfied, copying the first user interface object and displaying a second user interface object at a first magnification at a location that corresponds to the second contact, wherein the second user interface object is a copy of the first user interface object.
14. The method of claim 13, wherein the third predefined condition is satisfied when the second contact is detected more than the predefined time interval after the first contact is detected.
15. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with a touch-sensitive display, cause the device to:
- display on the touch-sensitive display at least a portion of an electronic document at a first magnification, wherein the displayed portion of the electronic document includes at least a first user interface object; and
- while detecting a first contact on the touch-sensitive display at a location that corresponds to the first user interface object, detect a second contact on the touch-sensitive display; detect movement of the second contact across the touch-sensitive display;
- and in response to detecting the movement of the second contact across the touch-sensitive display: in accordance with a determination that a first predefined condition is satisfied, increase the magnification at which the electronic document is displayed from the first magnification to a second magnification in accordance with the movement of the second contact, wherein the first predefined condition is satisfied when the first contact and the second contact are detected within a predefined time interval from each other, and the second contact is detected at a location other than a location of the first user interface object; and in accordance with a determination that a second predefined condition is satisfied, rotate the first user interface object in accordance with the movement of the second contact, wherein the second predefined condition is different from the first predefined condition and is satisfied when the first contact and the second contact are detected within the predefined time interval from each other, and the second contact is detected on the first user interface object.
16. The non-transitory computer readable storage medium of claim 15, wherein the first predefined condition includes that the second contact is a single-finger contact, and the second predefined condition includes that the second contact is a two-finger contact.
17. The non-transitory computer readable storage medium of claim 15, wherein the first predefined condition includes that the second contact is a single-finger contact, and the second predefined condition includes that the second contact is a two-finger contact that is initially detected at a location that corresponds to the first user interface object.
18. The non-transitory computer readable storage medium of claim 15, wherein the first predefined condition includes that the second contact is initially detected at a location other than a location of the first user interface object, and the second predefined condition includes that the second contact is initially detected at a location that corresponds to the first user interface object.
19. The non-transitory computer readable storage medium of claim 15, wherein the first predefined condition includes that the first contact and the second contact are detected within a predefined time interval from each other, and the second predefined condition includes that the second contact is detected more than the predefined time interval after the first contact is detected.
20. The non-transitory computer readable storage medium of claim 15, the one or more programs including instructions for, in accordance with a determination that a third predefined condition is satisfied, copying the first user interface object and displaying a second user interface object at a first magnification at a location that corresponds to the second contact, wherein the second user interface object is a copy of the first user interface object.
21. The non-transitory computer readable storage medium of claim 20, wherein the third predefined condition is satisfied when the second contact is detected more than the predefined time interval after the first contact is detected.
4885786 | December 5, 1989 | Anderson et al. |
5283561 | February 1, 1994 | Lumelsky et al. |
5327161 | July 5, 1994 | Logan et al. |
5359703 | October 25, 1994 | Robertson et al. |
5371845 | December 6, 1994 | Newell et al. |
5424756 | June 13, 1995 | Ho et al. |
5463725 | October 31, 1995 | Henckel et al. |
5483261 | January 9, 1996 | Yasutake |
5490241 | February 6, 1996 | Mallgren et al. |
5499334 | March 12, 1996 | Staab |
5511148 | April 23, 1996 | Wellner |
5533183 | July 2, 1996 | Henderson et al. |
5581670 | December 3, 1996 | Bier et al. |
5675753 | October 7, 1997 | Hansen et al. |
5729673 | March 17, 1998 | Cooper et al. |
5732227 | March 24, 1998 | Kuzunuki et al. |
5808601 | September 15, 1998 | Leah et al. |
5825352 | October 20, 1998 | Bisset et al. |
5841435 | November 24, 1998 | Dauerer et al. |
5872559 | February 16, 1999 | Shieh |
5880743 | March 9, 1999 | Moran et al. |
5886697 | March 23, 1999 | Naughton et al. |
5910800 | June 8, 1999 | Shields et al. |
6025844 | February 15, 2000 | Parsons |
6028271 | February 22, 2000 | Gillespie et al. |
6065021 | May 16, 2000 | George |
6073036 | June 6, 2000 | Heikkinen et al. |
6075531 | June 13, 2000 | Destefano |
6160551 | December 12, 2000 | Naughton et al. |
6175364 | January 16, 2001 | Wong et al. |
6208329 | March 27, 2001 | Ballare |
6215490 | April 10, 2001 | Kaply |
6232957 | May 15, 2001 | Hinckley |
6253218 | June 26, 2001 | Aoki et al. |
6266057 | July 24, 2001 | Kuzunuki et al. |
6278443 | August 21, 2001 | Amro et al. |
6323846 | November 27, 2001 | Westerman et al. |
6346935 | February 12, 2002 | Nakajima et al. |
6392673 | May 21, 2002 | Andrew et al. |
6480813 | November 12, 2002 | Bloomquist et al. |
6545669 | April 8, 2003 | Kinawi et al. |
6565608 | May 20, 2003 | Fein et al. |
6570557 | May 27, 2003 | Westerman et al. |
6646655 | November 11, 2003 | Brandt et al. |
6657615 | December 2, 2003 | Harada |
6677932 | January 13, 2004 | Westerman |
6686935 | February 3, 2004 | Richard |
6690365 | February 10, 2004 | Hinckley et al. |
6807361 | October 19, 2004 | Girgensohn et al. |
6856259 | February 15, 2005 | Sharp |
6888536 | May 3, 2005 | Westerman et al. |
6903751 | June 7, 2005 | Saund et al. |
6928619 | August 9, 2005 | Clow et al. |
7030861 | April 18, 2006 | Westerman et al. |
7093192 | August 15, 2006 | Mullen et al. |
7110005 | September 19, 2006 | Arvin et al. |
7134093 | November 7, 2006 | Etgen et al. |
7158158 | January 2, 2007 | Fleming et al. |
7190379 | March 13, 2007 | Nissen |
7216293 | May 8, 2007 | Kataoka et al. |
7218226 | May 15, 2007 | Wehrenberg |
7287241 | October 23, 2007 | Balsiger |
7454717 | November 18, 2008 | Hinckley et al. |
7456823 | November 25, 2008 | Poupyrev et al. |
7469381 | December 23, 2008 | Ording |
7469833 | December 30, 2008 | Kelley et al. |
7477233 | January 13, 2009 | Duncan et al. |
7489324 | February 10, 2009 | Royal et al. |
7555710 | June 30, 2009 | Kobashi et al. |
7557797 | July 7, 2009 | Ludwig |
7614008 | November 3, 2009 | Ording |
7619618 | November 17, 2009 | Westerman et al. |
7633076 | December 15, 2009 | Huppi et al. |
7634725 | December 15, 2009 | Nishikawa |
7653883 | January 26, 2010 | Hotelling et al. |
7657849 | February 2, 2010 | Chaudhri et al. |
7663607 | February 16, 2010 | Hotelling et al. |
7688306 | March 30, 2010 | Wehrenberg et al. |
7694231 | April 6, 2010 | Kocienda et al. |
7705830 | April 27, 2010 | Westerman et al. |
7728823 | June 1, 2010 | Lyon et al. |
7743348 | June 22, 2010 | Robbins et al. |
7812826 | October 12, 2010 | Ording et al. |
7856605 | December 21, 2010 | Ording et al. |
7904810 | March 8, 2011 | Chen et al. |
7934156 | April 26, 2011 | Forstall et al. |
7936341 | May 3, 2011 | Weiss |
7956847 | June 7, 2011 | Christie |
8023158 | September 20, 2011 | Maki et al. |
8024667 | September 20, 2011 | Shaw et al. |
8095884 | January 10, 2012 | Karunakaran et al. |
8161400 | April 17, 2012 | Kwon |
8171401 | May 1, 2012 | Sun |
8171431 | May 1, 2012 | Grossman et al. |
8176435 | May 8, 2012 | Jitkoff et al. |
8176438 | May 8, 2012 | Zaman et al. |
8209630 | June 26, 2012 | Thimbleby et al. |
8276085 | September 25, 2012 | Sherwani |
8291349 | October 16, 2012 | Park et al. |
8291350 | October 16, 2012 | Park et al. |
8312387 | November 13, 2012 | Williams et al. |
8448083 | May 21, 2013 | Migos et al. |
8456431 | June 4, 2013 | Victor |
8458617 | June 4, 2013 | Victor |
8464173 | June 11, 2013 | Victor |
8539385 | September 17, 2013 | Capela et al. |
8539386 | September 17, 2013 | Capela et al. |
8612884 | December 17, 2013 | Capela et al. |
8677268 | March 18, 2014 | Capela et al. |
8766928 | July 1, 2014 | Weeldreyer et al. |
8780069 | July 15, 2014 | Victor |
8799826 | August 5, 2014 | Missig et al. |
8832585 | September 9, 2014 | Missig et al. |
8863016 | October 14, 2014 | Victor |
8972879 | March 3, 2015 | Migos et al. |
9081494 | July 14, 2015 | Migos |
9098182 | August 4, 2015 | Migos et al. |
9310907 | April 12, 2016 | Victor |
20020015024 | February 7, 2002 | Westerman et al. |
20020018075 | February 14, 2002 | Maulik et al. |
20020057292 | May 16, 2002 | Holtz |
20020062321 | May 23, 2002 | Shibata |
20020109668 | August 15, 2002 | Rosenberg et al. |
20020109708 | August 15, 2002 | Peurach et al. |
20020161772 | October 31, 2002 | Bergelson et al. |
20030014382 | January 16, 2003 | Iwamoto et al. |
20030128192 | July 10, 2003 | Van Os |
20030142137 | July 31, 2003 | Brown et al. |
20030179240 | September 25, 2003 | Gest |
20030189597 | October 9, 2003 | Anderson et al. |
20030210268 | November 13, 2003 | Kataoka et al. |
20030234768 | December 25, 2003 | Rekimoto et al. |
20040066407 | April 8, 2004 | Regan et al. |
20040088656 | May 6, 2004 | Washio |
20040141009 | July 22, 2004 | Hinckley et al. |
20040150668 | August 5, 2004 | Myers et al. |
20040174399 | September 9, 2004 | Wu et al. |
20040225968 | November 11, 2004 | Look et al. |
20040239691 | December 2, 2004 | Sprang et al. |
20050052427 | March 10, 2005 | Wu et al. |
20050068290 | March 31, 2005 | Jaeger |
20050071774 | March 31, 2005 | Lipsky et al. |
20050088418 | April 28, 2005 | Nguyen |
20050088423 | April 28, 2005 | Keely et al. |
20050091008 | April 28, 2005 | Green et al. |
20050108620 | May 19, 2005 | Allyn et al. |
20050108656 | May 19, 2005 | Wu et al. |
20050177796 | August 11, 2005 | Takahashi |
20050188329 | August 25, 2005 | Cutler et al. |
20050231512 | October 20, 2005 | Niles et al. |
20050289476 | December 29, 2005 | Tokkonen |
20060001650 | January 5, 2006 | Robbins et al. |
20060022955 | February 2, 2006 | Kennedy |
20060026521 | February 2, 2006 | Hotelling et al. |
20060026535 | February 2, 2006 | Hotelling et al. |
20060033721 | February 16, 2006 | Woolley et al. |
20060033724 | February 16, 2006 | Chaudhri et al. |
20060055662 | March 16, 2006 | Rimas-Ribikauskas et al. |
20060055684 | March 16, 2006 | Rimas-Ribikauskas et al. |
20060085757 | April 20, 2006 | Andre et al. |
20060085767 | April 20, 2006 | Hinckley et al. |
20060112335 | May 25, 2006 | Hofmeister et al. |
20060125803 | June 15, 2006 | Westerman et al. |
20060129945 | June 15, 2006 | Dettinger et al. |
20060136246 | June 22, 2006 | Tu |
20060136833 | June 22, 2006 | Dettinger et al. |
20060161870 | July 20, 2006 | Hotelling et al. |
20060174568 | August 10, 2006 | Kinoshita et al. |
20060184966 | August 17, 2006 | Hunleth et al. |
20060190833 | August 24, 2006 | Sangiovanni et al. |
20060197750 | September 7, 2006 | Kerr et al. |
20060197753 | September 7, 2006 | Hotelling |
20060238517 | October 26, 2006 | King et al. |
20060238521 | October 26, 2006 | Westerman et al. |
20060248469 | November 2, 2006 | Czerwinski et al. |
20060279532 | December 14, 2006 | Olszewski et al. |
20070050726 | March 1, 2007 | Wakai et al. |
20070055940 | March 8, 2007 | Moore et al. |
20070064004 | March 22, 2007 | Bonner et al. |
20070067711 | March 22, 2007 | Woodall et al. |
20070079236 | April 5, 2007 | Schrier et al. |
20070113198 | May 17, 2007 | Robertson et al. |
20070126732 | June 7, 2007 | Robertson et al. |
20070150810 | June 28, 2007 | Katz et al. |
20070152980 | July 5, 2007 | Kocienda et al. |
20070152984 | July 5, 2007 | Ording et al. |
20070160345 | July 12, 2007 | Sakai et al. |
20070177803 | August 2, 2007 | Elias et al. |
20070186178 | August 9, 2007 | Schiller |
20070192744 | August 16, 2007 | Reponen |
20070192749 | August 16, 2007 | Baudisch |
20070198942 | August 23, 2007 | Morris |
20070220444 | September 20, 2007 | Sunday et al. |
20070229471 | October 4, 2007 | Kim et al. |
20070236475 | October 11, 2007 | Wherry |
20070245257 | October 18, 2007 | Chan et al. |
20070247435 | October 25, 2007 | Benko et al. |
20070253025 | November 1, 2007 | Terayoko |
20070257890 | November 8, 2007 | Hotelling et al. |
20070263025 | November 15, 2007 | Ohashi et al. |
20080019591 | January 24, 2008 | Iwayama et al. |
20080022197 | January 24, 2008 | Bargeron et al. |
20080034317 | February 7, 2008 | Fard et al. |
20080036743 | February 14, 2008 | Westerman et al. |
20080042978 | February 21, 2008 | Perez-Noguera |
20080052945 | March 6, 2008 | Matas et al. |
20080066015 | March 13, 2008 | Blankenhorn |
20080066016 | March 13, 2008 | Dowdy et al. |
20080072173 | March 20, 2008 | Brunner et al. |
20080094368 | April 24, 2008 | Ording et al. |
20080094370 | April 24, 2008 | Ording et al. |
20080098331 | April 24, 2008 | Novick et al. |
20080100642 | May 1, 2008 | Betancourt et al. |
20080109751 | May 8, 2008 | Fitzmaurice et al. |
20080111766 | May 15, 2008 | Uchino et al. |
20080136786 | June 12, 2008 | Lanfermann |
20080140868 | June 12, 2008 | Kalayjian et al. |
20080147664 | June 19, 2008 | Fujiwara et al. |
20080148181 | June 19, 2008 | Reyes et al. |
20080150715 | June 26, 2008 | Tang et al. |
20080165141 | July 10, 2008 | Christie |
20080165142 | July 10, 2008 | Kocienda et al. |
20080167834 | July 10, 2008 | Herz et al. |
20080168403 | July 10, 2008 | Westerman et al. |
20080180404 | July 31, 2008 | Han |
20080180405 | July 31, 2008 | Han et al. |
20080180406 | July 31, 2008 | Han et al. |
20080186285 | August 7, 2008 | Shimizu |
20080211766 | September 4, 2008 | Westerman et al. |
20080229223 | September 18, 2008 | Kake |
20080244410 | October 2, 2008 | Schormann |
20080259040 | October 23, 2008 | Ording et al. |
20080267468 | October 30, 2008 | Geiger et al. |
20080270886 | October 30, 2008 | Gossweiler et al. |
20080278455 | November 13, 2008 | Atkins et al. |
20080284799 | November 20, 2008 | Hollemans et al. |
20080297482 | December 4, 2008 | Weiss |
20080303786 | December 11, 2008 | Nakamura et al. |
20080309632 | December 18, 2008 | Westerman et al. |
20080320391 | December 25, 2008 | Lemay et al. |
20080320419 | December 25, 2008 | Matas et al. |
20090013350 | January 8, 2009 | Ohlfs et al. |
20090051660 | February 26, 2009 | Feland et al. |
20090051946 | February 26, 2009 | Hibi |
20090079700 | March 26, 2009 | Abernathy |
20090083655 | March 26, 2009 | Beharie et al. |
20090100383 | April 16, 2009 | Sunday et al. |
20090113330 | April 30, 2009 | Garrison et al. |
20090122018 | May 14, 2009 | Vymenets et al. |
20090140997 | June 4, 2009 | Jeong et al. |
20090150775 | June 11, 2009 | Miyazaki et al. |
20090158326 | June 18, 2009 | Hunt et al. |
20090164936 | June 25, 2009 | Kawaguchi |
20090172606 | July 2, 2009 | Dunn et al. |
20090174679 | July 9, 2009 | Westerman |
20090178008 | July 9, 2009 | Herz et al. |
20090183930 | July 23, 2009 | Yang et al. |
20090184939 | July 23, 2009 | Wohlstadter et al. |
20090228792 | September 10, 2009 | Van Os et al. |
20090231275 | September 17, 2009 | Odgers |
20090237363 | September 24, 2009 | Levy et al. |
20090239587 | September 24, 2009 | Negron et al. |
20090256809 | October 15, 2009 | Minor |
20090256857 | October 15, 2009 | Davidson et al. |
20090259964 | October 15, 2009 | Davidson et al. |
20090282332 | November 12, 2009 | Porat |
20090303231 | December 10, 2009 | Robinet et al. |
20090307589 | December 10, 2009 | Inose et al. |
20090309881 | December 17, 2009 | Zhao et al. |
20090327975 | December 31, 2009 | Stedman |
20100002002 | January 7, 2010 | Lipsky et al. |
20100004030 | January 7, 2010 | Nam |
20100007623 | January 14, 2010 | Kaneko et al. |
20100017734 | January 21, 2010 | Cummins |
20100026647 | February 4, 2010 | Abe et al. |
20100031202 | February 4, 2010 | Morris et al. |
20100031203 | February 4, 2010 | Morris et al. |
20100050076 | February 25, 2010 | Roth |
20100053111 | March 4, 2010 | Karlsson |
20100058238 | March 4, 2010 | Ben Moshe |
20100088624 | April 8, 2010 | Bligh et al. |
20100088641 | April 8, 2010 | Choi |
20100090971 | April 15, 2010 | Choi et al. |
20100095205 | April 15, 2010 | Kinoshita |
20100095206 | April 15, 2010 | Kim |
20100107101 | April 29, 2010 | Shaw et al. |
20100134425 | June 3, 2010 | Storrusten |
20100146436 | June 10, 2010 | Jakobson et al. |
20100156813 | June 24, 2010 | Duarte et al. |
20100162105 | June 24, 2010 | Beebe et al. |
20100185949 | July 22, 2010 | Jaeger |
20100194703 | August 5, 2010 | Fedor et al. |
20100211920 | August 19, 2010 | Westerman |
20100214571 | August 26, 2010 | Luo |
20100218100 | August 26, 2010 | Simon et al. |
20100228746 | September 9, 2010 | Harada |
20100231533 | September 16, 2010 | Chaudhri |
20100235794 | September 16, 2010 | Ording |
20100241955 | September 23, 2010 | Price et al. |
20100283743 | November 11, 2010 | Coddington |
20100283750 | November 11, 2010 | Kang et al. |
20100283754 | November 11, 2010 | Nakao |
20100289760 | November 18, 2010 | Jonoshita et al. |
20100299598 | November 25, 2010 | Shin et al. |
20100302176 | December 2, 2010 | Nikula et al. |
20100313125 | December 9, 2010 | Fleizach et al. |
20100313126 | December 9, 2010 | Jung et al. |
20100318904 | December 16, 2010 | Hillis et al. |
20100325529 | December 23, 2010 | Sun |
20100333044 | December 30, 2010 | Kethireddy |
20110004830 | January 6, 2011 | Von Kaenel et al. |
20110010672 | January 13, 2011 | Hope |
20110012848 | January 20, 2011 | Li et al. |
20110012856 | January 20, 2011 | Maxwell et al. |
20110018821 | January 27, 2011 | Kii |
20110029927 | February 3, 2011 | Lietzke et al. |
20110029934 | February 3, 2011 | Locker et al. |
20110069016 | March 24, 2011 | Victor |
20110069017 | March 24, 2011 | Victor |
20110069018 | March 24, 2011 | Atkins et al. |
20110074710 | March 31, 2011 | Weeldreyer et al. |
20110093812 | April 21, 2011 | Fong |
20110093821 | April 21, 2011 | Wigdor et al. |
20110109581 | May 12, 2011 | Ozawa et al. |
20110128367 | June 2, 2011 | Yoshioka et al. |
20110145759 | June 16, 2011 | Leffert et al. |
20110163944 | July 7, 2011 | Bilbrey et al. |
20110163968 | July 7, 2011 | Hogan |
20110179368 | July 21, 2011 | King et al. |
20110179373 | July 21, 2011 | Moore et al. |
20110185316 | July 28, 2011 | Reid et al. |
20110185321 | July 28, 2011 | Capela et al. |
20110209058 | August 25, 2011 | Hinckley et al. |
20110209100 | August 25, 2011 | Hinckley |
20110209102 | August 25, 2011 | Hinckley et al. |
20110209104 | August 25, 2011 | Hinckley et al. |
20110231796 | September 22, 2011 | Vigil |
20110252370 | October 13, 2011 | Chaudhri |
20110252380 | October 13, 2011 | Chaudhri |
20110252381 | October 13, 2011 | Chaudhri |
20110258537 | October 20, 2011 | Rives et al. |
20110302519 | December 8, 2011 | Fleizach et al. |
20120023453 | January 26, 2012 | Wagner |
20120023459 | January 26, 2012 | Westerman |
20120026100 | February 2, 2012 | Migos et al. |
20120030568 | February 2, 2012 | Migos et al. |
20120030569 | February 2, 2012 | Migos et al. |
20120044150 | February 23, 2012 | Karpin et al. |
20130174062 | July 4, 2013 | Stoustrup |
20130215064 | August 22, 2013 | Cholewin et al. |
20130263055 | October 3, 2013 | Victor |
20140351707 | November 27, 2014 | Missig et al. |
20160216868 | July 28, 2016 | Victor |
101063925 | October 2007 | CN |
101446884 | June 2009 | CN |
101458586 | June 2009 | CN |
101599002 | December 2009 | CN |
101617288 | December 2009 | CN |
1577746 | September 2005 | EP |
1615114 | January 2006 | EP |
1840717 | October 2007 | EP |
2060970 | May 2009 | EP |
2068237 | June 2009 | EP |
2284675 | February 2011 | EP |
7-175587 | July 1995 | JP |
2001-228971 | August 2001 | JP |
2004-234661 | August 2004 | JP |
2009-217815 | September 2009 | JP |
2013-541061 | November 2013 | JP |
10-2005-0051638 | June 2005 | KR |
10-2009-0070491 | July 2009 | KR |
00/16186 | March 2000 | WO |
2006/020305 | February 2006 | WO |
2007/098243 | August 2007 | WO |
2008/044024 | April 2008 | WO |
2008/085737 | July 2008 | WO |
2008/138046 | November 2008 | WO |
2009/084141 | July 2009 | WO |
2009/084809 | July 2009 | WO |
2012/015933 | February 2012 | WO |
- Office Action received for Chinese Patent Application No. 201180016102.7, mailed on Aug. 25, 2015, 23 pages (14 pages of English Translation and 9 pages of Official copy).
- Notice of Acceptance received for Australian Patent Application No. 2011282703, mailed on May 8, 2015, 2 pages.
- Office Action Received for European Patent Application No. 09756118.7, mailed on Oct. 8, 2015, 6 pages.
- Notice of Allowance received for U.S. Appl. No. 13/909,002, mailed on Dec. 4, 2015, 7 pages.
- Office Action received for Japanese Patent Application No. 2013521943, mailed on Nov. 2, 2015, 4 pages (2 pages of English Translation and 2 pages of Official Copy).
- Intention to Grant received for European Patent Application No. 11702357.2, mailed on Feb. 26, 2016, 6 pages.
- Office Action received for Chinese Patent Application No. 2011800161027, mailed on Mar. 9, 2016, 8 pages (3 pages of English Translation and 5 pages of Official Copy).
- Notice of Allowance received for Chinese Patent Application No. 201180037474.8, mailed on Mar. 3, 2016, 3 pages (2 pages of English Translation and 1 page of Official Copy).
- Decision on Appeal received for Japanese Patent Application No. 2013521943, mailed on Mar. 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy).
- Office Action received for Australian Patent Application No. 2015202218, issued on Feb. 12, 2016, 5 pages.
- Decision to Grant received for European Patent Application No. 11702357.2, mailed on Jul. 14, 2016, 2 Pages.
- Non Final Office Action received for U.S. Appl. No. 14/455,303, mailed on Jul. 29, 2016, 27 pages.
- Office Action received for European Patent Application No. 11702358.0, mailed on Jun. 28, 2016, 5 pages.
- Advisory Action received for U.S. Appl. No. 12/848,087, mailed on Jun. 17, 2015, 3 pages.
- Extended European Search Report received for European Patent Application No. 16177552.3, mailed on Sep. 30, 2016, 7 pages.
- Notice of Allowance received for Chinese Patent Application No. 201180016102.7, mailed on Sep. 5, 2016, 4 pages (2 pages of English Translation and 2 pages of Official Copy).
- Office Action received for European Patent Application No. 11741385.6, mailed on Sep. 27, 2016, 8 pages.
- Summons to Attend Oral Proceedings received for European Patent Application No. 09756118.7, mailed on Sep. 23, 2016, 8 pages.
- Office Action received for Chinese Patent Application No. 201180037474.8, mailed on Aug. 24, 2015, 8 pages (3 pages of English Translation and 5 pages of Official Copy).
- Non-Final Office Action received for U.S. Appl. No. 13/909,002, mailed on Jun. 23, 2015, 6 pages.
- Apple Inc. vs. Samsung Electronics Co. Ltd. et al., Judgment in Interlocutory proceeding, Case No. 396957/KG ZA 11-730, civil law sector, Aug. 24, 2011, pp. 1-65.
- Apple Inc. vs. Samsung Electronics Co. Ltd., et al., Samsung's Motion to Supplement Invalidity Contentions, Case No. 11-cv-01846-LHK, filed Jan. 27, 2012 together with Exhibit 6, Jan. 27, 2012, 47 pages.
- Apple Inc. vs. Samsung Electronics Co. Ltd., et al., Samsung's Patent Local Rule 3-3 and 3-4 Disclosures, Case No. 11-cv-01846-LHK, dated Oct. 7, 2011, together with Exhibits G-1 through G-7 and Exhibit H, Oct. 7, 2011, 287 pages.
- HTC Europe Co. Ltd and Apple Inc. Invalidity Claim dated Apr. 5, 2012, together with annexes, Apr. 5, 2012, 12 pages.
- HTC Europe Co. Ltd and Apple Inc. invalidity Claim dated Jul. 29, 2011, together with amended Particulars of Claim and amended Grounds of Invalidity, Jul. 29, 2011, 22 pages.
- Motorola Mobility Opposition Grounds to Apple Inc. European Patent EP 2126678 dated Apr. 11, 2012, together with Exhibits E3, E4, and E5 re: CHT 2005, Apr. 2-7, 2005, Portland Oregon, USA, Apr. 2012, 53 pages.
- Pleading notes Mr B.J. Berghuis van Woortman, in matter of Apple Inc. vs Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731, Aug. 10-11, 2010, pp. 1-16.
- Pleading notes Mr Kleemans, Mr Blomme and Mr Van Oorschot, in matter of Apple Inc. vs Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731, Aug. 10, 2011, 35 pages.
- Samsung Electronics GmbH vs Apple Inc., “List scrolling and document translation, scaling and rotation on a touch-screen display”, Opposition, Jan. 30, 2012, 27 pages.
- Samsung Electronics vs Apple Inc., Statement of Defense Also Counterclaim, Case No. KG ZA 2011-730, Jul. 20, 2011, 44 pages.
- Samsung Electronics vs Apple Inc., Statement of Defense Also Counterclaim, Case No. KG ZA 2011-731, Jul. 20, 2011, 48 pages.
- Office Action received for European Patent Application No. 09756118.7, mailed on Feb. 13, 2013, Feb. 13, 2013, 5 pages.
- Office Action received for European Patent Application No. 09756118.7, mailed on Mar. 7, 2014, 7 pages.
- Notice of Allowance received for Korean Patent Application No. 10-2012-7022209, mailed on Apr. 28, 2014, 5 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Office Action Received for Korean Patent Application No. 10-2012-7022448, mailed on Jun. 13, 2014, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Notice of Allowance received for Korean Patent Application No. 10-2013-7003785, mailed on Aug. 14, 2014, 2 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Office Action received for Korean Patent Application No. 10-2013-7003785, mailed on Jan. 28, 2014, 4 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Office Action received for European Patent Application No. 11702357.2, mailed on Jan. 14, 2014, 5 pages.
- Office Action received for European Patent Application No. 11741385.6, mailed on Jan. 22, 2014, 3 pages.
- Office Action received for European Patent Application No. 11741385.6, mailed on Sep. 16, 2014, 7 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,171, mailed on Apr. 1, 2014, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,206 mailed on May 8, 2014, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,206, mailed on Aug. 21, 2014, 6 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/567,405, mailed on Jan. 16, 2014, 19 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,405, mailed on Jun. 11, 2014, 9 pages.
- Notice of Allowance received for U.S. Appl. No. 12/768,623, mailed on Feb. 20, 2014, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,063, mailed on Dec. 4, 2014, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,063, mailed on Mar. 27, 2015, 8 pages.
- Non Final Office Action received for U.S. Appl. No. 12/848,067, mailed on Apr. 16, 2014, 40 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,067, mailed on Dec. 12, 2014, 2 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,067, mailed on Oct. 22, 2014, 23 pages.
- Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Jan. 28, 2015, 30 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Jul. 14, 2014, 18 pages.
- Non-Final Office Action received for U.S. Appl. No. 13/909,001, mailed on Sep. 26, 2013, Sep. 26, 2013, 7 pages.
- Notice of Allowance received for U.S. Appl. No. 13/909,001, mailed on Mar. 3, 2014, 7 pages.
- Office Action received for Chinese Patent Application No. 201180016102.7, mailed on Oct. 16, 2014, 10 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Office Action received for Chinese Patent Application No. 201180037474.8, mailed on Dec. 22, 2014, 6 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Office Action received for Japanese Patent Application No. 2013-521943, mailed on Jan. 6, 2014, 2 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Office Action received for Japanese Patent Application No. 2013-521943, mailed on Sep. 1, 2014, 2 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)).
- Beaudouin-Lafon, M. , “Novel Interaction Techniques for Overlapping Windows”, Available at <http://portal.acm.org/citation.cfm?id=502371>, 2001, pp. 153-154.
- Guimbretiere, Francois , “Paper Augmented Digital Documents”, CHI Letters, vol. 5, No. 2, 2003, pp. 51-60.
- International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2009/057899, mailed on Apr. 5, 2012, 14 pages.
- International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/022519, mailed on Aug. 9, 2012, 8 pages.
- International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/022525, mailed on Aug. 9, 2012, 8 pages.
- International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/022532, mailed on Aug. 9, 2012, 11 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2009/057899, Jun. 14, 2010, 19 pages.
- Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2009/057899, mailed on Apr. 29, 2010, Apr. 29, 2010, 8 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/022519, Jul. 1, 2011, 8 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/022525, Apr. 27, 2011, 10 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/022532, mailed on May 24, 2011, 16 pages.
- International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/045552, Feb. 5, 2013, 7 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/045552, Dec. 13, 2011, 10 pages.
- Office Action received for Korean Patent Application No. 10-2012-7022209, mailed on Oct. 21, 2013, 4 pages.
- Notice of Allowance received for Korean Patent Application No. 10-2012-7022448, mailed on Apr. 27, 2015, 2 pages.
- Final Office Action received for U.S. Appl. No. 12/567,171, mailed on Jan. 3, 2013, Jan. 3, 2013, 12 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/567,171, mailed on Jul. 6, 2012, Jul. 6, 2012, 13 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,171, mailed on Oct. 4, 2013, 9 pages., Oct. 4, 2013, 9 pages.
- Final Office Action received for U.S. Appl. No. 12/567,206 mailed on Apr. 4, 2013, Apr. 4, 2013, 21 pages.
- Non Final Office Action received for U.S. Appl. No. 12/567,206 mailed on Aug. 30, 2012, Aug. 30, 2012, 13 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,206, mailed on Aug. 8, 2013, Aug. 8, 2013, 8 pages.
- Final Office Action received for U.S. Appl. No. 12/567,405, mailed on Dec. 17, 2012, Dec. 17, 2012, 19 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/567,405, mailed on May 17, 2012, May 17, 2012, 14 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/567,460, mailed on Aug. 4, 2011, Aug. 4, 2011, 13 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Apr. 10, 2013, Apr. 10, 2013, 9 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Aug. 10, 2012, Aug. 10, 2012, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Dec. 24, 2012, Dec. 24, 2012, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Jan. 18, 2012, Jan. 18, 2012, 8 pages.
- Final Office Action received for U.S. Appl. No. 12/567,553, mailed on Mar. 12, 2012, Mar. 12, 2012, 15 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/567,553, mailed on Sep. 16, 2011, Sep. 16, 2011, 11 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Apr. 2, 2013, Apr. 2, 2013, 9 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Aug. 10, 2012, Aug. 10, 2012, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Dec. 24, 2012, Dec. 24, 2012, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Jun. 12, 2012, Jun. 12, 2012, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,570, mailed on Dec. 19, 2012, Dec. 19, 2012, 7 pages.
- Notice of Allowance received for U.S. Appl. No. 12/567,570, mailed on Mar. 27, 2013, Mar. 27, 2013, 8 pages.
- Final Office Action received for U.S. Appl. No. 12/768,623, mailed on Jan. 22, 2013, Jan. 22, 2013, 34 pages.
- Final Office Action received for U.S. Appl. No. 12/768,623, mailed on Oct. 23, 2013, Oct. 23, 2013, 31 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/768,623, mailed on Jun. 7, 2012, Jun. 7, 2012, 12 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/768,623, mailed on May 30, 2013, May 30, 2013, 34 pages.
- Final Office Action received for U.S. Appl. No. 12/790,504, mailed on Apr. 1, 2013, Apr. 1, 2013, 21 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/790,504, mailed on Oct. 3, 2012, Oct. 3, 2012, 22 pages.
- Notice of Allowance received for U.S. Appl. No. 12/790,504, mailed on Aug. 13, 2013, Aug. 13, 2013, 14 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/790,508, mailed on Nov. 7, 2012, Nov. 7, 2012, 32 pages.
- Notice of Allowance received for U.S. Appl. No. 12/790,508, mailed on Jul. 10, 2013, Jul. 10, 2013, 7 pages.
- Notice of Allowance received for U.S. Appl. No. 12/790,508, mailed on Nov. 8, 2013, Nov. 8, 2013, 11 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/790,516, mailed on Aug. 27, 2012, Aug. 27, 2012, 9 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/790,516, mailed on Feb. 2, 2012, Feb. 2, 2012, 10 pages.
- Notice of Allowance received for U.S. Appl. No. 12/790,516, mailed on May 15, 2013, May 15, 2013, 7 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/790,524, mailed on Sep. 24, 2012, Sep. 24, 2012, 22 pages.
- Notice of Allowance received for U.S. Appl. No. 12/790,524, mailed on Feb. 5, 2013, Feb. 5, 2013, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/790,524, mailed on May 13, 2013, May 13, 2013, 6 pages.
- Final Office Action received for U.S. Appl. No. 12/848,063, mailed on Oct. 11, 2013, Oct. 11, 2013, 15 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/848,063, mailed on Aug. 9, 2012, Aug. 9, 2012, 14 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/848,063, mailed on Mar. 29, 2013, Mar. 29, 2013, 13 pages.
- Final Office Action received for U.S. Appl. No. 12/848,067 mailed on Jan. 10, 2013, Jan. 10, 2013, 35 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/848,067, mailed on Jun. 6, 2012, 16 pages.
- Final Office Action received for U.S. Appl. No. 12/848,074, mailed on Apr. 3, 2013, Apr. 3, 2013, 15 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/848,074, mailed on Jun. 29, 2012, Jun. 29, 2012, 12 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on Apr. 28, 2015, 5 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on Jun. 3, 2015, 5 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on Mar. 13, 2015, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on May 13, 2014, 10 pages.
- Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Aug. 22, 2013, Aug. 22, 2013, 22 pages.
- Non-Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Mar. 7, 2013, Mar. 7, 2013, 19 pages.
- Notice of Acceptance received for Australian Patent Application No. 2011209729, mailed on Jan. 15, 2015, 2 pages.
- Office Action received for Australian Patent Application No. 2011209729, mailed on Jun. 24, 2013, Jun. 24, 2013, 4 pages.
- Office Action received for Australian Patent Application No. 2011282703, mailed on Oct. 21, 2013, Oct. 21, 2013, 3 pages.
- Office Action received for Japanese Patent Application No. 2013-521943, mailed on Feb. 27, 2015, 2 pages.
- Spaces (software), Wikipedia, the free encyclopedia, available at <http://en.wikipedia.org/wiki/Spaces—(software)>, Jul. 15, 2009, 3 pages.
- Virtual Desktop, Wikipedia, the free encyclopedia, available at <http://en.wikipedia.org/wiki/Virtual—desktop>, Jul. 20, 2009, 5 pages.
- ALAI6666, “Jeff Han's 8 ft. Multi-Touch Display Wall”, Available online at <http://www.youtube.com/watch?v=JfFwgPuEdSk>, retrieved on May 16, 2007, 2 pages.
- Alessandro, Valli, “Minority Report interface prototype”, Available online at <http://www.youtube.com/watch?v=3bn-zZX9kdc>, retrieved on Jul. 12, 2006, 3 pages.
- Angell, “Is Bimanual the Future Paradigm for Human Computer Interaction?”, University of Plymouth, 2006, 2006, 36 pages.
- apple.com, “Pages. Keyboard Shortcuts”, available at <http://www.apple.com/support/pages./shortcuts/>, retrieved on Jan. 18, 2010, 6 pages.
- Apted et al., “Tabletop Sharing of Digital Photographs for the Elderly”, CHI 2006: Proceedings, Apr. 2006, Montreal, Quebec, Canada, Apr. 2006, 10 pages.
- Autodesklabs, “Autodesk Design on Jeff Han's Perceptive Pixel Multi-Touch”, Available online at <http://www.youtube.com/watch?v=O7ENumwMohs>, retrieved on Jul. 27, 2007, 2 pages.
- Baudisch, Patrick, “The Cage: Efficient Construction in 3D using a Cubic Adaptive Grid”, Proceedings of the 9th annual ACM symposium on User interface software and technology UIST '96, Nov. 6, 1996, 2 pages.
- Beaudouin-Lafon et al., “CPN/Tools: A Post-WIMP Interface for Editing and Simulating Coloured Petri Nets”, Proceedings of 22nd International Conference on Application and Theory of Petri Nets 2001, 2001, pp. 1-10.
- Bederson, B., “PhotoMesa: A Zoomable Image Browser Using Quantum Treemaps and Bubblemaps”, UIST 2001, Oriando, Florida, Nov. 2001, Nov. 2001, 10 pages.
- Benko et al., “Precise Selection Techniques for Multi-Touch Screens”, CHI 2006, Apr. 22-27, 2006, 10 pages.
- BestSheep1, “TDesktop Multiuser”, Available online on <http://www.youtube.com/watch?v=PjsO-lbli34>, retrieved on Sep. 6, 2007, 2 pages.
- Botjunkie, “Microsoft Surface Demo @ CES 2008”, Available online at <http://www.youtube.com/watch?v=Zxk—WywMTzc>, retrieved on Jan. 8, 2008, 2 pages.
- Brandl et al., “Combining and Measuring the Benefits of Bimanual Pen and Direct-Touch Interaction on Horizontal Interfaces”, AVI'08, May 2008, Naples, Italy, May 2008, pp. 1-8.
- Brandl, P., “Combining and Measuring the Benefits of Bimanual Pen and Direct-Touch Interaction on Horizontal Interfaces”, Media Interaction Lab, Slide presentation, May 2008, 26 pages.
- Bumptop, “3D Desktop”, Available online at <http://www.youtube.com/watch?v=l—lxBwvf3Vk>, retrieved on Sep. 18, 2006, Sep. 18, 2006, 2 pages.
- Butz et al., “Hybrid Widgets on an Interactive Tabletop”, Ubicomp '07, Innsbruck, Austria, Sep. 2007, 7 pages.
- Buxton, Bill, “A Multi-Touch Three Dimensional Touch-Tablet”, Available online at <http://www.youtube.com/watch?v=Arrus9CxUiA>, retrieved on Nov. 18, 2009, 3 pages.
- Buxton et al., “A Study in Two-Handed Input”, Proceedings of CHI '86, Boston, MA, Apr. 1986, 10 pages.
- Buxton, W., “Chapter 11: Two-Handed Input in Human-Computer Interaction”, Aug. 22, 2008, pp. 11.1-11.18.
- Buxton, W., “Chapter 5: Case Study 1: Touch Tablets”, Haptic Input, Jan. 4, 2009, 20 pages.
- Buxton et al., “Issues and Techniques in Touch-Sensitive Tablet Input”, Computer Graphics, vol. 19(3), http://http://www.dgp.toronto.edu/OTP/papers/bill.buxton/touch.html, Proceedings of SIGGRAPH'85, 1985, pp. 215-224.
- Buxton et al., “Multi-Touch Systems that I Have Known and Loved”, http://www.billbuxton.com/multitouchOverview.html, Jan. 12, 2007, pp. 1-21.
- Buxton, Bill, “Multi-Touch Systems that I Have Known and Loved”, available at <http://www.billbuxton.com/multitouchOverview.html>, Jan. 12, 2007, 14 pages.
- Chanfrado, “Multi Touch (new touchscreen technology)”, Available online at <http://www.youtube.com/watch?v=1ftJhDBZqss>, retrieved on Mar. 17, 2006, 2 pages.
- Chen et al., “Relative role of merging and two-handed operation on command selection speed”, Int. J. Human-Computer Studies 66 (2008), Jun. 2008, pp. 729-740.
- Cho et al., “Interaction for Tabletop Computing Environment: An Analysis and Implementation”, Science and Technology (2005), ACM, 2005, pp. 11-18.
- Cocoadex, “Photo Touch: Multi-touch Photo Organization for your Mac”, Available online at <http://www.youtube.com/watch?v=D7x7jV3P1-0>, retrieved on Mar. 30, 2008, 3 pages.
- Continuumshow, “IdentityMine's Multitude of Multi-touch Apps”, Youtube, available online at <http://www.youtube.com/watch?v=HcpdNb9LHns>, Nov. 6, 2008, 2 pages.
- Couturier et al., “Pointing Fingers: Using Multiple Direct Interactions with Visual Objects to Perform Music”, Proceedings of the 2003 Conference on New Interfaces for Musical Expression May 2003, Montreal, Canada, May 2003, pp. 184-187.
- Cutedraw, “Moving, Rotating, Resizing and Flipping Shapes”, CuteDraw 2.0 Help System, available at <http://www.cutedraw.com/Moving,%20Rotating,%20Resizing%20Flipping%20Shapes.php>, 2007, 5 pages.
- Darthstoo, “Wii Multi-touch Photo Gallery”, Available online at <http://www.youtube.com/watch?v=0CYVxQ2OM9s>, retrieved on Apr. 10, 2008, 3 pages.
- Derene, G., “Microsoft Surface: Behind-the-Scenes First Look”, Popular Mechanics.com, Jul. 1, 2007 http://www.popularmechanics.com/technology/gadgets/news/4217348?page=3, Jul. 1, 2007, 4 pages.
- Dwigdor, “Lucid Touch: a See-Through Multi-Touch Mobile Device”, Available online at <http://www.youtube.com/watch?v=qbMQ7urAvuc>, retrieved on Aug. 21, 2007, 2 pages.
- Engadget, “LG.Philips 52-inch multi-touch display”, Available online at <http://www.youtube.com/watch?v=9qO-diu4jq4>, retrieved on Jan. 8, 2008, 2 pages.
- F0xmuld3r, “Multi-touch interface (from Adobe TED)”, Available online at <http://www.youtube.com/watch?v=UcKgyn-gUbY>, retrieved on Aug. 3, 2006, 2 pages.
- Faas, Ryan, “Spaces: A Look at Apple's Take on Virtual Desktops in Leopard”, Computerworld, available at <http://www.computerworld.com/s/article/9005267/Spaces—A—look—at—Apple—s—take—on—virtual—desktops—in—Leopard?taxonomyName . . . >, Nov. 21, 2006, 3 pages.
- Fingerworks Forums, “Is the Multitouch Lemur?”, Available at <http://64233.167.104/search?q=cache:sjVdtyFBvRMJ:forums.finger>, retrieved on Nov. 16, 2005, Dec. 24, 2004, 2 pages.
- Fingerworks, Inc., “Installation and Operation Guide for iGesture Products w/Keys”, available at <www.fingerworks.com>, © 2002, 10 pages.
- Fingerworks, Inc., “Installation and Operation Guide for the TouchStream and TouchStream LP”, available at <http://www.fingerworks.com>, 2002, pp. 1-25.
- Fingerworks, Inc., “Quick Reference Guide for iGesture Products”, available at <http://www.fingerworks.com>, 1999-2002, 2 pages.
- Fingerworks, Inc., “Quick Reference Guide for TouchStream ST/LP”, available at <http://www.fingerworks.com>, 2001-2003, 4 pages.
- Fingerworks, Inc., “TouchStream LP Silver”, available at <http://www.fingerworks.com>, Apr. 27, 2005, 18 pages.
- Google Docs, “Drawings: Moving, resizing and rotating objects”, Downloaded from <https://support.google.com/docs/answer/141914?hl=-en> on Jan. 18, 2010, 1 page.
- Guimbretière et al., “Benefits of Merging Command Selection and Direct Manipulation”, ACM Transactions on Computer-Human Interaction, vol. 12, No. 3, Sep. 2005, Sep. 2005, pp. 460-476.
- Guimbretière, F., “People, Paper and Computers”, University of Maryland Institute for Advanced Computer Studies, 2008, 5 pages.
- Hcikonstanz, “Multi-touch Interaction: Browser Control”, Available online at <http://www.youtube.com/watch?v=jTOK5Zbfm4U>, retrieved on Sep. 12, 2008, 2 pages.
- Hinckley, K., “Haptic Issues for Virtual Manipulation”, University of Virginia, Dissertation Presented Dec. 1996, http://research.microsoft.com/en-us/um/people/kenh/all-published-papers/hinckley-thesis-haptic-issues-for-virtual-manipulation.pdf, Dec. 1996, 216 pages.
- Hinckley et al., “Interaction and Modeling Techniques for Desktop Two-Handed Input”, UIST '98, San Francisco, CA, Nov. 1998, 10 pages.
- Hodges et al., “ThinSight: Versatile Multi-touch Sensing for Thin Form-factor Displays”, UIST '07, Newport, Rhode Island, USA, Oct. 7-10, 2007, 10 pages.
- Hudson, Scott E., “Adaptive Semantic Snaping—A Technique for Semantic Feedback at the Lexical Level”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1990, pp. 65-70.
- I3pgroup, “I3 MultiTouch Interactive Table”, Youtube, available online at <http://www.youtube.com/watch?v=M2oijV-bRrw>, Nov. 16, 2007, 2 pages.
- IBM, “Resizing Shapes by Dragging Sizing Handles”, IBM WebSphere Help System, available at <http://publib.boulder.ibm.com/infocenter/wsadhelp/v5r1m2/index.jsp?topic=/com.rational.xtools.umivisualizer.doc/topics/tresizedrag.html>, 1999, 1 page.
- Inkspace, “Inkscape tutorial: Basic”, Inkscape.org, Apr. 20, 2005 http://web.archive.org/web20051225021958/http://inkscape.org/doc/basic/tutorial-basic.html, Apr. 20, 2005, pp. 1-7.
- Intuilab, “Multitouch Time and Geo Tagging Photosharing with IntuiFace”, Available online at <http://www.youtube.com/watch?v=ftsx21liFvo>, retrieved on Jan. 31, 2008, 3 pages.
- Jin et al., “GIA: Design of a Gesture-Based Interaction Photo Album”, Pers Ubiquit Comput, Jul. 1, 2004, pp. 227-233.
- Kane et al., “Slide Rule: Making Mobile Touch Screens Accessible to Blind People Using Multi-Touch Interaction Techniques”, ASSETS, Oct. 13-15, 2008, pp. 73-80.
- Karsenty et al., “Inferring Graphical Constraints with Rockit”, Digital-Paris Research Laboratory, Mar. 1992, 30 pages.
- Krishnaarava, “Cubit—Open Source Multitouch Display”, Available online at <http://www.youtube.com/watch?v=btFlrrDiUxk>, retrieved on May 2, 2008, May 2, 2008, 3 pages.
- Kristensson et al., “InfoTouch: An Explorative Multi-Touch Visualization Interface for Tagged Photo Collections”, Proceedings NordiCHI 2008, Oct. 20-22, 2008, pp. 491-494.
- Kurata et al., “Tangible Tabletop Interface for an Expert to Collaborate with Remote Field Workers”, CollabTech2005, Jul. 16, 2005, Slides, Jul. 16, 2005, 27 pages.
- Kurata et al., “Tangible Tabletop Interface for an Expert to Collaborate with Remote Field Workers”, CollabTech2005, Jul. 16, 2005, pp. 58-63.
- Kurtenbach et al., “The Design of a GUI Paradigm Based on Tablets, Two-Hands, and Transparency”, Mar. 27, 1997, 8 pages.
- Lee et al., “A Multi-Touch Three Dimensional Touch-Sensitive Tablet”, CHI '85 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1985, pp. 21-25.
- Malik et al., “Visual Touchpad: A Two-Handed Gestural Input Device”, ICMI'04 Proceedings of the 6th International Conference on Multimodal Intercases, ACM, Oct. 13-15, 2004, pp. 289-296.
- Markandtanya, “Imagining Multi-touch in Outlook”, May 2008, 3 pages.
- Markusson, D., “Interface Development of a Multi-Touch Photo Browser”, Umea University, Master's Thesis presented, Apr. 18, 2008, 76 pages.
- Matsushita et al., “Dual Touch: A Two-Handed Interface for Pen-Based PDAs”, UIST '00, San Diego, California, Nov. 2000, 2 pages.
- Matsushita et al., “HoloWall: Designing a Finger, Hand, Body and Object Sensitive Wall”, UIST '97 Proceedings of the 10th annual ACM symposium on User interface software and technology, Oct. 1997, 2 pages.
- Media Interaction Lab, “Bimanual Pen & Touch”, http://mi-lab.org/projects/bimanual-pen-touch/, Nov. 2008, 5 pages.
- microsoft.com, “Quickly Copy Formatting with the Format Painter”, available at <http://office.microsoft.com/enus/help/HA012176101033.aspx>, 2003, 1 page.
- microsoft.com, “Resize an Object”, Microsoft Office Online, available at <http://office.microsoft.com/en-us/publisher/HP051139751033.aspx>, 2010, 2 pages.
- Moscovich et al., “Indirect Mappings of Multi-touch Input Using One and Two Hands”, CHI 2008, Florence, Italy, Apr. 2008, 9 pages.
- Moscovich et al., “Multi-Finger Cursor Techniques”, GI '06 Proceedings of Graphics Interface 2006, Quebec City, Quebec, Canada, Jun. 9, 2006, 7 pages.
- Moscovich, T., “Multi-touch Interaction”, CHI 2006, Montréal, Québec, Canada, Apr. 2006, pp. 1-4.
- Moscovich, T., “Principles and Applications of Multi-touch Interaction”, Brown University, Dissertation Presented, May 2007, 114 pages.
- Mueller et al., “Visio 2007 for Dummies”, John Wiley & Sons, Dec. 18, 2006, pp. 178-181.
- Murphy, Peter, “Review: SBSH Calendar Touch”, available at <http://justanothermobilemonday.com/Wordpress/2008/12/08/review-sbsh-calendar-touch/>, Dec. 8, 2008, 7 pages.
- Nepsihus, “PhotoApp (Multi-Touch)”, Available online at <http://www.youtube.com/watch?v=RJTVULGnZQ0>, retrieved on Dec. 30, 2007, 3 pages.
- Raskin, A., “Enso 2.0 Design Thoughts”, Aza's Thoughts, http://www.azarask.in/blog/post/enso-20-design-thoughts/, Dec. 6, 2008, 16 pages.
- Raskin, A., “Visual Feedback: Why Modes Kill”, Humanized, Dec. 2006, 18 pages.
- Sahlin et al., “Flash® CS4 All-in-One for Dummies®”, John Wiley & Sons, Dec. 3, 2008, 4 pages.
- Shen et al., “Informing the Design of Direct-Touch Tabletops”, IEEE Sep./Oct. 2006, Sep./Oct. 2006, pp. 36-46.
- Shen, C., “Interactive tabletops: User Interface, Metaphors and Gestures”, SIGGRAPH2007, Aug. 2007, 14 pages.
- Tabletopresearch201, “Gesture Registration, Relaxation, and Reuse for Multi-Point”, Youtube, available online at <http://www.youtube.com/watch?v=dT4dXuah2yM>, May 19, 2008, 2 pages.
- Thomas, Glaser, “Photoshop MT—Desktop Digital Imaging on FTIR multitouch”, Available online at <http://www.youtube.com/watch?v=JmHNr9EH1iU>, retrieved on Feb. 7, 2007, 2 pages.
- Tse et al., “Enabling Interaction with Single User Applications Through Speech and Gestures on a Multi-User Tabletop”, Mitsubishi Electric Research Laboratories, 2005, pp. 336-343.
- Ullmer et al., “The metaDESK: Models and Prototypes for Tangible User Interfaces”, UIST '97, Banff, Alberta, Canada, Oct. 14, 1997, pp. 1-10.
- Unwirelife1, “HP TouchSmart tx2—Multi-Touch Part 2”, Youtube, available online at <http://www.youtube.com/watch?v=Yon3vRwc94A>, Dec. 19, 2008, 2 pages.
- Vanderlin, Todd, “Smart Surface Beta”, Available online at <http://www.youtube.com/watch?v=68wFqxdXENw>, retrieved on Mar. 29, 2008, 3 pages.
- Westerman, Wayne, “Hand Tracking, Finger Identification and Chordic Manipulation on a Multi-Touch Surface”, Doctoral Dissertation, 1999, 363 Pages.
- Wilson, A., “Robust Computer Vision-Based Detection of Pinching for One and Two-Handed Gesture Input”, UIST '06, Montreux, Switzerland, Oct. 2006, 4 pages.
- Wu et al., “Multi-Finger and Whole Hand Gestural Interaction Techniques for Multi-User Tabletop Displays”, UiST '03, Vancouver, BC, Canada, © ACM 2003, Nov. 5-7, 2003, pp. 193-202.
- Yee, K., “Two-Handed Interaction on a Tablet Display”, SIGCHI 2004, Vienna, Austria, Apr. 2004, 4 pages.
- ZAC96, “Microsoft Surface Demo”, Available online at <http://www.youtube.com/watch?v=rKgU6ubBgJA>, retrieved on Aug. 17, 2007, 2 pages.
Type: Grant
Filed: Jul 7, 2015
Date of Patent: Apr 18, 2017
Patent Publication Number: 20150309692
Assignee: Apple Inc. (Cupertino, CA)
Inventor: Charles J. Migos (San Bruno, CA)
Primary Examiner: Toan Vu
Application Number: 14/793,574
International Classification: G06F 3/01 (20060101); G06F 3/0488 (20130101); G06F 3/041 (20060101); G06F 3/0484 (20130101); G06F 3/00 (20060101);