CN105260049B - For contacting the equipment for carrying out display additional information, method and graphic user interface in response to user - Google Patents

Abstract

The present invention discloses an electronic device having a touch-sensitive surface and a display, the electronic device comprising one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device detects a contact on the touch-sensitive surface when a focus selector corresponding to the contact is located at a corresponding location on the display that is associated with additional information not originally displayed on the display. When the focus selector is at the corresponding position, the device displays the Associated additional information without waiting until a predefined delay time has elapsed; and when it is determined that the contact has an intensity lower than a corresponding intensity threshold, the device waits until a predefined delay time has elapsed to display the Additional Information.

Description

Apparatus, method and graphic for displaying additional information in response to user contact user interface

This application is a divisional application of an invention patent application with an application date of May 8, 2013, an application number of 201380035982.1, and an invention title of "Apparatus, method and graphical user interface for displaying additional information in response to user contact".

Related Patent Applications

This patent application claims priority to Provisional Patent Application: U.S. Provisional Patent Application Serial No. 61, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Displaying Additional Information in Response to a User Contact" /778,171, U.S. Provisional Patent Application No. 61/747,278, filed December 29, 2012, entitled "Device, Method, and Graphical User Interface for Manipulating User Interface Objects with Visual and/or Haptic Feedback," and U.S. Provisional Patent Application No. 61/688,227, entitled "Device, Method, and Graphical User Interface for Manipulating User Interface Objects with Visual and/or Haptic Feedback," filed May 9, which is hereby incorporated by reference in its entirety .

This patent application is also related to the following provisional patent applications: U.S. Provisional Patent Application Serial No. 61/778,092, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Selecting Object within a Group of Objects," U.S. Provisional Patent Application Serial No. 61/778,125, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Navigating User Interface Hierarchies," and filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Manipulating Framed Graphical Objects", U.S. Provisional Patent Application Serial No. 61/778,156, filed March 12, 2013, U.S. Provisional Patent Application, entitled "Device, Method, and Graphical User Interface for Scrolling Nested Regions" Patent Application Serial No. 61/778,179, U.S. Provisional Patent Application Serial No. 61/778,191, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application" U.S. Provisional Patent Application Serial No. 61/778,211, filed March 12, entitled "Device, Method, and Graphical User Interface for Facilitating UserInteraction with Controls in a User Interface," filed March 12, 2013, entitled " Device, Method, and Graphical User Interface for Forgoing Generation of Tactile Output for a Multi-Contact Gesture", U.S. Provisional Patent Application Serial No. 61/778,239, filed March 12, 2013, entitled "Device, Method, a ndGraphical User Interface for Providing Tactile Feedback for OperationsPerformed in a User Interface, U.S. Provisional Patent Application Serial No. 61/778,284, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Providing Feedback for Changing Activation States of a User Interface Object", U.S. Provisional Patent Application Serial No. 61/778,287, filed March 12, 2013, U.S. Provisional Patent entitled "Device, Method, and Graphical User Interface for Transitioning between Touch Input to DisplayOutput Relationships" Application Serial No. 61/778,363, U.S. Provisional Patent Application Serial No. 61/778,363, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Moving a User Interface Object Based on an Intensity of a Press Input" 778,367, U.S. Provisional Patent Application Serial No. 61/778,265, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning between Display States in Response to a Gesture," filed March 12, 2013 U.S. Provisional Patent Application Serial No. 61/778,373, filed March 13, 2013, entitled "Device, Method, and Graphical User Interface for Managing Activation of a Control Based on Contact Intensity," titled "Device, Method, and Graphical User Interface for Displaying ContentAssociated with a Corres ponding Affordance" U.S. Provisional Patent Application Serial No. 61/778,412, U.S. Provisional Patent Application Serial No. 61/778,413 entitled "Device, Method, and Graphical User Interface for Selecting User Interface Objects" filed on March 13, 2013, U.S. Provisional Patent Application Serial No. 61/778,414, filed March 13, 2013, entitled "Device, Method, and Graphical User Interface for Moving and Dropping a User Interface Object," filed March 13, 2013, entitled U.S. Provisional Patent Application Serial No. 61/778,416 for "Device, Method, and Graphical User Interface for Determining Whether to Scroll or Select Content," and filed March 13, 2013, entitled "Device, Method, and Graphical User Interface for Switching between User Interfaces", which are hereby incorporated by reference in their entirety.

This application is also related to the following provisional patent applications: U.S. Provisional Patent Application Serial No. 61/645,033, filed May 9, 2012, entitled "AdaptiveHaptic Feedback for Electronic Devices," filed June 28, 2012, and entitled U.S. Provisional Patent Application Serial No. 61/665,603 for "Adaptive Haptic Feedback for Electronic Devices," and U.S. Provisional Patent Application Serial No. 61/681,098, filed August 8, 2012, entitled "Adaptive Haptic Feedback for Electronic Devices," which Both applications are incorporated herein by reference in their entirety.

technical field

This document generally relates to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that detect inputs for manipulating a user interface.

Background technique

The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has grown significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touchscreen displays. Such surfaces are widely used for manipulating user interface objects on a display.

Exemplary manipulations include adjusting the position and/or size of one or more user interface objects or activating a button or opening a file/application represented by the user interface object, and associating metadata with one or more user interface objects or Other ways to manipulate the user interface. Exemplary user interface objects include digital images, video, text, icons, control elements such as buttons, and other graphics. In some cases, a user will need to perform such manipulations of user interface objects in a file management program (e.g., Finder from Apple Inc., Cupertino, California), an image management application (e.g., from Aperture or iPhoto from Apple Inc. (Cupertino, California), digital content (e.g., video and music) management applications (e.g., iTunes from Apple Inc. (Cupertino, California)), drawing applications, rendering applications (e.g., Keynote from Apple Inc. (Cupertino, California)), word processing applications (e.g., Pages from Apple Inc. (Cupertino, California)), website creation applications (e.g., from Apple Inc. (upertino, California) iWeb), a disc editing application (eg, iDVD from Apple Inc. (Cupertino, California)), or a spreadsheet application (eg, Numbers from Apple Inc. (Cupertino, California)).

However, existing methods for performing these manipulations are cumbersome and inefficient. Furthermore, existing methods take longer than necessary, wasting energy. This latter consideration is particularly important in battery-operated devices.

Contents of the invention

Therefore, electronic devices need to have faster, more efficient methods and interfaces for manipulating user interfaces. Such methods and interfaces optionally supplement or replace conventional methods for manipulating user interfaces. Such methods and interfaces reduce the cognitive load on the user and result in a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

The above-mentioned deficiencies and other problems associated with user interfaces for electronic devices having 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 (eg, laptop, tablet, or handheld). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), memory, one or more processors, and one or more modules, programs or sets of instructions stored in the memory for performing various functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, rendering, word processing, web page creation, disk editing, spreadsheet creation, game playing, making and receiving phone calls, video conferencing, emailing, instant messaging, Fitness Support, Digital Photography, Digital Video Recording, Internet Browsing, Digital Music Playback, and/or Digital Video Playback. Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

Electronic devices need to have faster, more efficient methods and interfaces for performing user interface operations on electronic devices with track pads or touch screens. Examples of such operations include scrolling through a list of items or deleting an item in the list. Such methods and interfaces may supplement or replace conventional methods for performing user interface operations. Such methods and interfaces reduce the cognitive load on the user and result in a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

According to some embodiments, a method is performed at an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The method includes displaying a user interface on a display and detecting a user gesture on the touch-sensitive surface, the gesture comprising a contact corresponding to a focus selector at a corresponding location in the user interface, wherein the gesture is associated with a corresponding operation. The method also includes, in response to detecting the gesture, requesting confirmation that the user wants the device to perform a corresponding action based on determining that the contact has a maximum intensity below a first intensity threshold. The method also includes performing the corresponding operation without requesting confirmation that the user wants the device to perform the corresponding operation based on determining that the maximum intensity of the contact is above the first intensity threshold.

According to some embodiments, an electronic device comprises a display unit configured to display a user interface on the display unit; a touch-sensitive surface unit configured to detect a user's gesture on the touch-sensitive surface unit, the A gesture includes a contact corresponding to a focus selector at a corresponding location in the user interface, where the gesture is associated with a corresponding operation; and a processing unit coupled to the display unit and the touch-sensitive surface unit. The processing unit is configured to: in response to detecting the gesture: request confirmation that the user wants the device to perform a corresponding action based on a determination that the contact has a maximum intensity below a first intensity threshold; and based on a determination that the maximum intensity of the contact is above the first intensity threshold , perform the action without requesting confirmation that the user wants the device to perform the action.

Accordingly, an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with a faster, more efficient method and interface for performing user interface operations, thereby Increase the effectiveness, efficiency and user satisfaction of such equipment. Such methods and interfaces may supplement or replace conventional methods for performing user interface operations.

Electronic devices need to have faster, more efficient methods and interfaces for displaying additional (e.g., initially not displayed) information. Such methods and interfaces may supplement or replace conventional methods for displaying such additional information. Such methods and interfaces reduce the cognitive load on the user and result in a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

According to some embodiments, the method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes detecting a contact on the touch-sensitive surface when a focus selector corresponding to the contact is located at a corresponding location on the display that is associated with additional information that was not originally displayed on the display. The method also includes, when the focus selector is at the corresponding location: displaying an intensity associated with the corresponding location based on determining that the contact has an intensity above the corresponding intensity threshold before the predefined delay time has elapsed with the focus selector at the corresponding location. associated additional information without waiting until a predefined delay time has elapsed; and upon determining that the contact has an intensity below a corresponding intensity threshold, waiting until a predefined delay time has elapsed to display when the focus selector is at the corresponding position Additional information associated with the location.

According to some embodiments, an electronic device includes a display unit configured to display additional information associated with a respective location; a touch-sensitive surface unit configured to receive a contact on the touch-sensitive surface unit; or a plurality of sensor units configured to detect the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit and the sensor unit. The processing unit is configured to: detect a contact on the touch-sensitive surface unit when a focus selector corresponding to the contact is located at a corresponding location on the display unit associated with additional information not originally displayed on the display unit; and when When the focus selector is at the respective location: enabling an additional display of the information without waiting until a predefined delay time has elapsed; and upon determining that the contact has an intensity below a corresponding intensity threshold, waiting until the predefined delay time has elapsed to enable communication with the Display of additional information associated with the corresponding location.

Accordingly, an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with a faster, more efficient method and interface for displaying Additional (eg, not originally displayed) information, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace conventional methods for displaying additional (eg, not initially displayed) information when contact is detected.

Electronic devices need to have faster, more efficient methods and interfaces for removing icons from predefined areas. Such methods and interfaces may supplement or replace conventional methods for removing icons from predefined areas. Such methods and interfaces reduce the cognitive load on the user and result in a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

According to some embodiments, the method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes: displaying a plurality of icons in a predefined area on a display, wherein the plurality of icons includes a corresponding icon; detecting a gesture comprising: contact on the touch-sensitive surface when the focus selector is positioned over the corresponding icon , and subsequent movement of the contact on the touch-sensitive surface, the subsequent movement corresponding to movement of the focus selector outside the predefined area; and in response to detecting the gesture: based on determining that the contact has an intensity below a corresponding intensity threshold during the gesture maximum intensity, to display an indication that the gesture is being performed during the gesture, and to retain the corresponding icon in the predefined area after the gesture has ended; The corresponding icon is moved during the movement, and the corresponding icon is removed from the predefined area after the gesture has ended.

According to some embodiments, an electronic device includes a display unit configured to display a plurality of icons in a predefined area on the display unit, wherein the plurality of icons includes corresponding icons; a touch-sensitive surface unit, the touch-sensitive surface unit being configured to receive a gesture; one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit and sensor unit. The processing unit is configured to detect a gesture comprising a contact on the touch-sensitive surface unit when the focus selector is over a corresponding icon, and a subsequent movement of the contact on the touch-sensitive surface unit, the subsequent movement corresponding to the focus movement of the selector outside the predefined area, and in response to detecting the gesture: enabling display during the gesture of an indication that the gesture is being performed based on determining that the contact had a maximum intensity during the gesture that is below a corresponding intensity threshold, and at retaining the corresponding icon in the predefined area after the gesture has ended; and upon determining that the contact reached an intensity above a corresponding intensity threshold during the gesture, moving the corresponding icon according to movement of the contact during the gesture, and removing from the predetermined area after the gesture has ended The defined area removes the corresponding icon.

Accordingly, an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with a faster, more efficient method and interface for removing icons, thereby increasing the effectiveness, efficiency and user satisfaction of such devices. Such methods and interfaces may supplement or replace conventional methods for removing icons from predefined areas.

Electronic devices need to have faster, more efficient methods and interfaces for displaying content layers. Such methods and interfaces may supplement or replace conventional methods for displaying content layers. Such methods and interfaces reduce the cognitive load on the user and result in a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

According to some embodiments, the method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes: displaying first content on a display, wherein portions of the first content relate to corresponding portions of second content that are not displayed on the display; and detecting touch when a focus selector is over the first portion of the first content. The intensity of the contact on the touch-sensitive surface is increased above the corresponding intensity threshold; and in response to detecting the intensity of the contact on the touch-sensitive surface is increased above the corresponding intensity threshold: stop displaying the first portion of the first content, and display the first portion of the first content A first portion of the second content corresponding to the first portion of the first content.

According to some embodiments, the electronic device comprises a display unit configured to display first content on the display unit, wherein portions of the first content relate to corresponding portions of the second content not displayed on the display; the touch-sensitive surface unit, the touch-sensitive surface unit is configured to receive contact; one or more sensors, the one or more sensors are configured to detect the intensity of contact with the touch-sensitive surface unit; and a processing unit, the processing unit is coupled to the display unit, touch-sensitive surface unit and sensor. The processing unit is configured to: when the focus selector is positioned over a first portion of the first content, detect an increase in the intensity of the contact on the touch-sensitive surface unit above a corresponding intensity threshold; The intensity of the contact is increased above a corresponding intensity threshold: stopping display of the first portion of the first content and enabling display of a first portion of the second content corresponding to the first portion of the first content.

Accordingly, an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with faster, more efficient methods and interfaces for displaying content layers, thereby increasing To maximize the utility, efficiency and user satisfaction of such equipment. Such methods and interfaces may supplement or replace conventional methods for displaying content layers.

Electronic devices need to have faster, more efficient methods and interfaces for switching between user interfaces (such as in an email client application) by using user input such as input on a trackpad or touch screen or from a touch-sensitive surface. Navigate between the inbox view and the conversation view in the . Such methods and interfaces can supplement or replace conventional methods for navigating between user interfaces. Such methods and interfaces reduce the cognitive load on the user and result in a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

According to some embodiments, the method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes displaying a first user interface on a display. The method also includes detecting a first gesture on the touch-sensitive surface when the focus selector is positioned over a first representation of an object in the first user interface, the first gesture comprising a gesture with an intensity above a corresponding intensity threshold during the first gesture. First touch for maximum strength. The method also includes, in response to detecting the first gesture, replacing the first user interface with a second user interface including a second representation of the object. The method also includes detecting a second gesture on the touch-sensitive surface when the focus selector is over a second representation of an object in a second user interface, the second gesture comprising having a button above a corresponding Intensity Threshold The maximum intensity of the second contact. The method also includes replacing the second user interface with the first user interface in response to detecting the second gesture.

According to some embodiments, an electronic device includes a display unit configured to display a first user interface comprising a first representation of an object and a second user interface comprising a second representation of an object; a touch-sensitive surface unit, the touch-sensitive The surface unit is configured to detect a first gesture on the touch-sensitive surface unit when the focus selector is positioned over a first representation of an object in the first user interface, the first gesture comprising an intensity greater than a corresponding intensity threshold during the first gesture. and detecting a second gesture on the touch-sensitive surface element when the focus selector is over a second representation of an object in a second user interface, the second gesture included in the second gesture during a second contact having a maximum intensity above a corresponding intensity threshold; and a processing unit coupled to the display unit and the touch-sensitive surface unit. The processing unit is configured to: in response to detecting the first gesture, replace the first user interface with the second user interface; and in response to detecting the second gesture, replace the second user interface with the first user interface.

Accordingly, an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with faster, more efficient methods and interfaces for displaying user interface navigation between devices, thereby increasing the effectiveness, efficiency and user satisfaction of such devices. Such methods and interfaces may supplement or replace conventional methods for navigating between displayed user interfaces.

According to some embodiments, an electronic device includes a display, a touch-sensitive surface, memory, one or more processors, one or more programs, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface; The one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include instructions for performing operations of any of the methods mentioned in paragraph [0057]. According to some embodiments, having a display, a touch-sensitive surface, memory, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and one or more programs executing one or more programs stored in the memory The graphical user interface on the electronic device of a processor includes one or more elements displayed in any of the methods mentioned in paragraph [0057], the one or more elements being updated in response to an input, such as in paragraph [0057] described in any of the methods mentioned. According to some embodiments, a computer-readable storage medium has stored therein instructions that are executed by an electronic device having a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The apparatus, when executed, causes the apparatus to perform the operations of any of the methods mentioned in paragraph [0057]. According to some embodiments, an electronic device comprises: a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface; and for performing any of the methods mentioned in paragraph [0057] operating device. According to some embodiments, an information processing device for use in an electronic device having a display and a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, comprises a method for implementing paragraph [ 0057] mentioned in any method of operation of the device.

Description of drawings

For a better understanding of the various described embodiments of the present invention, reference should be made to the following description of the embodiments taken in conjunction with the following drawings, in which like reference numerals indicate corresponding parts throughout.

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display, according to some embodiments.

Figure IB is a block diagram illustrating exemplary components for event handling, according to some embodiments.

Figure 2 illustrates a portable multifunction device with a touch screen, according to some embodiments.

3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface, according to some embodiments.

Figure 4A illustrates an exemplary user interface for an application menu on a portable multifunction device, according to some embodiments.

4B illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface separate from a display, according to some embodiments.

5A-5I illustrate exemplary user interfaces for performing user interface operations, according to some embodiments.

6A-6B are flowcharts illustrating methods of performing user interface operations, according to some embodiments.

Figure 7 is a functional block diagram of an electronic device according to some embodiments.

8A-8N illustrate example user interfaces for displaying additional information associated with a location on a display based on contact intensity (eg, pressure) and contact timing (eg, duration), according to some embodiments.

9A-9B are flowcharts illustrating a method of displaying additional information associated with a location on a display based on contact intensity (eg, pressure) and contact timing (eg, duration), according to some embodiments.

Figure 10 is a functional block diagram of an electronic device according to some embodiments.

11A-11U illustrate example user interfaces for removing icons from predefined areas, according to some embodiments.

12A-12B are flowcharts illustrating a method of removing an icon from a predefined area, according to some embodiments.

Figure 13 is a functional block diagram of an electronic device according to some embodiments.

14A-14L illustrate example user interfaces for displaying content layers, according to some embodiments.

15A-15C are flowcharts illustrating a method of displaying content layers according to some embodiments.

Figure 16 is a functional block diagram of an electronic device according to some embodiments.

17A-17H illustrate example user interfaces for navigating between displayed user interfaces, according to some embodiments.

18A-18C are flowcharts illustrating methods of navigating between displayed user interfaces, according to some embodiments.

Figure 19 is a functional block diagram of an electronic device according to some embodiments.

Detailed ways

The methods, devices, and GUIs described herein provide visual and/or tactile feedback that makes manipulation of user interface objects more efficient and intuitive for users. For example, in systems where the click action of the trackpad is decoupled from the contact intensity (e.g., contact force, contact pressure, or a substitute thereof) required to reach an activation threshold, the device may generate different haptic outputs for different activation events ( For example, a "different click") (eg, such that a click that achieves a certain result is distinguished from a click that produces no result or achieves a different result than the specific result). In addition, haptic output may be generated in response to other events unrelated to increased intensity of contact, such as when a user interface object moves to a particular location, boundary, or orientation, or when an event occurs at the device (e.g., "Stop").

Additionally, in systems where the trackpad or touchscreen display is sensitive to a range of contact intensities that includes more than one or two specific intensity values (e.g., not just a simple on/off binary intensity determination), the user interface may provide an indication of the intensity of the touch. Response to a range of contact intensities (eg, visual or tactile cues). In some implementations, the pre-activation threshold response and/or the post-activation threshold response to the input is displayed as a continuous animation. As one example of such a response, a preview of the operation is displayed in response to detecting that the intensity of the contact has increased but is still below an activation threshold for performing the operation. As another example of such a response, the animation associated with the operation is continued even after the activation threshold for the operation has been reached. Both of these examples provide the user with a continuous response to the force or pressure of the user's contact, which provides richer and more intuitive visual and/or tactile feedback to the user. More specifically, such continuous force responses give the user the experience of being able to press lightly to preview an action and/or press deeply to "step through" or "pass through" a predefined user interface state corresponding to that action.

Additionally, for devices with touch-sensitive surfaces that are sensitive to a range of contact intensity, multiple contact intensity thresholds may be monitored by the device, and different functions may be mapped to different contact intensity thresholds. This serves to increase the "gesture space" available, thereby allowing easy access to improved features for users who know that increasing contact intensity at or beyond the second "deep press" intensity threshold will The device is caused to perform an operation different from that it would perform if the contact intensity were between the first "activation" intensity threshold and the second "deep press" intensity threshold. An advantage of assigning additional functionality to the second "deep press" intensity threshold while maintaining familiar functionality at the first "activate" intensity threshold is that, in some cases, an inexperienced user who is confused by the additional functionality may be able to do so by applying only up to the first "activation" intensity threshold. One "activate" intensity threshold to use familiar functions, while more experienced users can take advantage of additional functions by applying an intensity at a second "deep press" intensity threshold.

Additionally, for devices with touch-sensitive surfaces that are sensitive to a range of contact intensities, the device can provide additional functionality by allowing users to perform complex operations with a single continuous contact. For example, when selecting a group of objects, the user can move continuous contact around the touch-sensitive surface and can press while dragging (eg, applying a strength greater than a "deep press" strength threshold) to add additional elements to the selection. In this way, the user can intuitively interact with the user interface, wherein objects in the user interface are made "stickier" with contact than with a harder press.

The following describes a number of different approaches to providing an intuitive user interface on devices where the tap action is decoupled from the force required to reach an activation threshold and/or where the device is sensitive to a wide range of contact intensities. Using one or more of these methods, optionally in combination with each other, facilitates providing a user interface that intuitively provides the user with additional information and functionality, thereby reducing the user's cognitive load and improving the human-machine interface. Such improvements in the human-machine interface allow the user to use the device more quickly and efficiently. For battery-operated devices, these improvements save power and increase the time between battery charges. For ease of explanation, systems, methods and user interfaces for illustrative examples including some of these methods are described below as follows:

• Many electronic devices have a user interface for performing user interface operations such as viewing user interface objects (photos, email messages, etc.) and deleting user interface objects. In some cases, destructive actions are performed (eg, deleting an email) and the device requires additional input (eg, confirmation input) before performing these actions. However, providing an input sequence can be confusing and time-consuming for the user. In embodiments described below, the device determines whether to perform a specific destructive operation based on a contact intensity corresponding to a request to perform a specific destructive operation, thereby providing a more intuitive and efficient user interface for performing a destructive operation. Specifically, FIGS. 5A-5I illustrate exemplary user interfaces for performing user interface operations. 6A-6B are flowcharts illustrating methods of performing user interface operations. The user interfaces in Figures 5A-5I are used to illustrate the process in Figures 6A-6B.

• Many electronic devices have a graphical user interface that includes user interface objects. In some cases, additional (eg, hidden) information associated with a user interface object is displayed at the user's request. Some devices display such additional information after, for example, detecting a focus selector over a user interface object for an extended period of time.

However, such methods are time consuming and frustrating for users. Embodiments described below provide improved methods of displaying additional information based on contact intensity (eg, pressure) on a touch-sensitive surface, thereby providing a more convenient and efficient user interface for displaying additional information. Specifically, FIGS. 8A-8N illustrate methods for displaying on the display additional information associated with a location (eg, corresponding to a user interface object) based on contact intensity (eg, pressure) and contact timing (eg, duration). An example user interface for information. 9A-9B are flowcharts illustrating methods of displaying additional information based on contact intensity (eg, pressure) and contact timing (eg, duration). The user interfaces in Figures 8A-8N are used to illustrate the process in Figures 9A-9B.

• Many electronic devices have a graphical user interface that includes an application taskbar or launcher bar. In some cases, users are able to remove or rearrange icons in the application taskbar or launch bar. However, users may become frustrated or confused when icons are accidentally removed or rearranged. Additionally, adding back an icon that was accidentally removed and undoing the accidental rearrangement operation is frustrating and inefficient for the user. Embodiments described below provide an improved method for removing unwanted icons from a predefined area, such as the launch bar, where the device determines whether to remove or rearrange icons in the predefined area based on contact intensity, thereby providing greater convenience for the user. Talk about a more intuitive and efficient user interface that is less frustrating. Specifically, FIGS. 11A-11U illustrate exemplary user interfaces for removing icons from predefined areas. 12A-12B are flowcharts illustrating a method of removing an icon from a predefined area. The user interfaces in Figures 11A-11U are used to illustrate the process in Figures 12A-12B.

• Many electronic devices include applications or user interfaces in which different corresponding content, such as content layers, can be displayed. Users tend to lose their place within a layer or become confused about how to navigate within the layer. Embodiments described below provide an efficient and intuitive user interface for navigating and displaying layers of content by determining whether, and optionally how much, underlying layers to reveal based on the intensity of contact on a touch-sensitive surface. Specifically, Figures 14A-14L illustrate exemplary user interfaces for displaying content layers. 15A-15C are flowcharts illustrating a method of displaying content layers. The user interfaces in Figures 14A-14L are used to illustrate the process in Figures 15A-15C.

• Many electronic devices include user interfaces with different representations of the same object (eg content such as email or photo). Some methods for navigating between user interfaces on devices with touch-sensitive surfaces typically require the user to position affordances (eg, keys or "buttons"). However, such methods are problematic because they are prone to inaccuracies (eg, accidental selection of an affordance, accidental selection of a different key when an affordance was intended to be selected). Such approaches also increase the cognitive load on the user by requiring an additional independent gesture. Embodiments described below provide a convenient and intuitive method for navigating between user interfaces corresponding to different representations of an object using similar gestures performed with contacts when the focus selector is over a representation of the object. In particular, FIGS. 17A-17H illustrate example user interfaces for navigating between displayed user interfaces. 18A-18C are flowcharts illustrating a method of navigating between displayed user interfaces. The user interfaces in Figures 17A-17H are used to illustrate the process in Figures 18A-18C.

exemplary device

Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are shown in order to provide a thorough understanding of various described embodiments. It will be apparent, however, to one of ordinary skill in the art that various described embodiments 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. are used herein in some embodiments 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 various described embodiments. Both the first contact and the second contact are contacts, but they are not the same contact.

The terminology used in describing the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise pointed out. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. It will also be understood that when the terms "includes", "including", "comprises" and/or "comprising" are used in this specification, they specify that stated features, integers, steps, operations, elements and The presence of/or a component does 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" is optionally interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if determined" or "if detected [the stated condition or event]" is optionally interpreted to mean "when determined" or "in response to the determination" or "when detected [ a stated condition or event]” or “in response to the detection of [a stated condition or event]”.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also contains other functionality, such as PDA and/or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Inc. (Cupertino, California) iPod and equipment. Other portable electronic devices are optionally used, such as laptops or tablets with touch-sensitive surfaces (eg, touch screen displays and/or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (eg, a touchscreen display and/or a touchpad).

In the following discussion, an electronic device is described that includes a display and a touch-sensitive surface. It should be understood, however, that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick.

Devices typically support multiple applications, such as one or more of the following: drawing applications, rendering applications, word processing applications, web page creation applications, disk editing applications, spreadsheet applications, gaming applications programs, telephony applications, video conferencing applications, e-mail applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music playback browser application and/or digital video player application.

The various applications executing on the device optionally use at least one common physical user interface device such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or changed from one application to the next and/or are adjusted and/or within the respective application Variety. In this way, the common physical architecture of the devices, such as the touch-sensitive surface, optionally supports various applications with a user interface that is intuitive and clear to the user.

Attention is now directed to an embodiment of a portable device with a touch sensitive display. Figure 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display 112, according to some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to or referred to as a touch-sensitive display system. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, Speaker 111 , microphone 113 , input/output (I/O) subsystem 106 , other input or control devices 116 , and external ports 124 . Device 100 optionally includes one or more optical sensors 164 . Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contacts on device 100 (eg, a touch-sensitive surface such as touch-sensitive display system 112 of device 100 ). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300 tactile output). These components optionally communicate via one or more communication buses or signal lines 103 .

As used in this specification and claims, the term "strength" of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a touch-sensitive surface, or Refers to a substitute (surrogate) for force or pressure of contact on a touch-sensitive surface. The contact intensity has a range of values that includes at least four different values and more typically hundreds of different values (eg, at least 256). Contact intensity is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors beneath or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some embodiments, force measurements from multiple force sensors are combined (eg, weighted average) to determine an estimated force of contact. Similarly, the pressure sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch sensitive surface. Alternatively, the detected size of the contact area on the touch-sensitive surface and/or its change, the capacitance of the touch-sensitive surface adjacent to the contact and/or its change, and/or the resistance of the touch-sensitive surface adjacent to the contact and/or The change thereof is optionally used as a surrogate for the force or pressure of contact on the touch-sensitive surface. In some embodiments, surrogate measurements of contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (eg, the intensity threshold is described in units corresponding to the surrogate measurement). In some embodiments, a surrogate measurement of contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is expressed in units of pressure measured pressure threshold).

As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a component of the device (e.g., a touch-sensitive surface) relative to another part of the device (eg, the housing), or the displacement of a part relative to the center of mass of the device. For example, where a device or part of a device comes into contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation , the tactile sensation corresponds to a perceived change in a physical property of the device or device part. For example, movement of a touch-sensitive surface (eg, a touch-sensitive display or touchpad) is optionally interpreted by the user as a "click down" or "click up" on a physical actuation button. In some cases, the user will feel a tactile sensation, such as "click down" or "click up," even when a physical button associated with the touch-sensitive surface is physically pressed (e.g., displaced) by the user's movement. When the actuation button is not moving. As another example, movement of the touch-sensitive surface is optionally interpreted or sensed by the user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such interpretation of touch by a user will be limited by the user's individual perception, there are many perceptions of touch that are common to most users. Thus, when a haptic output is described as corresponding to a particular perception of the user (e.g., "tap down," "tap up," "roughness"), unless otherwise stated, the generated haptic output corresponds to the device or its The physical displacement of a part that would generate the described perception of a typical (or average) user.

It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combining two or more components, or any Optionally have a different configuration or arrangement of these components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, the hardware or software including one or more signal processing circuits and/or application specific integrated circuits.

Memory 102 optionally includes high-speed random access memory, and also optionally includes 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 peripherals interface 118 , is optionally controlled by memory controller 122 .

Peripherals interface 118 may be used to couple the device's input and output peripherals to CPU 120 and memory 102 . The one or more processors 120 run or execute various software programs and/or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data.

In some embodiments, peripherals interface 118 , CPU 120 and memory controller 122 are optionally implemented on a single chip such as chip 104 . In some other embodiments, they are optionally implemented on separate chips.

RF (Radio Frequency) circuitry 108 receives and transmits RF signals, also called electromagnetic signals. The RF circuit 108 converts/converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, tuners, digital signal processors, codec chipsets, Subscriber Identity Module (SIM) cards, memory, one or more amplifiers, one or more oscillators, etc. RF circuitry 108 communicates with networks, such as the Internet (also known as the World Wide Web (WWW)), intranets, and/or wireless networks (such as cellular telephone networks, wireless local area networks ( LAN) and/or Metropolitan Area Network (MAN)). Wireless communications optionally use any of a variety 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), Evolution, Data Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (for example, IEEE802.11a, IEEE 802.11b, IEEE 802.11g, and/or or IEEE 802.11n), Voice over Internet Protocol (VoiP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP) and/or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging Handling Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilization Extensions (SIMPLE), Instant Messaging and Presence Services (IMPS) and/or Short Message Service (SMS), or any other suitable communication protocol, Includes communication protocols that have not been 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 . The audio circuit 110 receives audio data from the peripheral device interface 118 , converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111 . The speaker 111 converts electrical signals into human-audible sound waves. The audio circuit 110 also receives electrical signals converted from sound waves by a microphone 113 . Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is optionally 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 (eg, 212 in FIG. 2 ). The headset jack provides an interface between the audio circuitry 110 and a removable audio input/output peripheral, such as an output-only headphone or an output (e.g., monaural or both earphones) and input (e.g., a microphone). ) headsets for both.

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 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, 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 control devices 116 . Other input control devices 116 optionally include physical buttons (eg, push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, one or more input controllers 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (eg, 208 in FIG. 2 ) optionally include up/down buttons for volume control of speaker 111 and/or microphone 113 . The one or more buttons optionally include a push button (eg, 206 in FIG. 2 ).

The touch-sensitive display 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives electrical signals from the touch screen 112 and/or sends electrical signals to the touch screen 112 . The touch screen 112 displays visual output to the user. Visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from a user based on tactile sensation and/or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and/or instruction sets in memory 102) detect contact on touchscreen 112 (and any movement or interruption of that contact) and convert the detected contact to Interaction with user interface objects (eg, one or more soft keys, icons, web pages, or images) displayed on the touch screen 112 . In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although in other embodiments other display technologies are used. Touch screen 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed and other proximity sensor arrays or for determining one or more points of contact with touch screen 112 Various touch sensing technologies including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies are used to detect contact and any movement or interruption thereof. In an exemplary embodiment, using projected mutual capacitance sensing technology, such as from Apple Inc. (Cupertino, California) iPod and discovered technology.

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. A user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of the finger on the touchscreen. In some embodiments, the device translates rough finger-based inputs into precise pointer/cursor positions or commands for performing user-desired actions.

In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, a touchpad is a touch-sensitive area of a device that, unlike a touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

Device 100 also includes a power system 162 for powering various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., , Light Emitting Diodes (LEDs)) and any other components associated with the generation, management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164 . FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106 . Optical sensor 164 optionally includes a Charge Coupled Device (CCD) or Complementary Metal Oxide Semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the rear of device 100, opposite touch screen display 112 on the front of the device, enabling the touch screen display to be used as a viewfinder for still image and/or video image capture. In some embodiments, another optical sensor is located on the front of the device, allowing the user to optionally capture an image of the user for videoconferencing while viewing other videoconferencing participants on the touch screen display.

Device 100 optionally also includes one or more contact intensity sensors 165 . FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106 . Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., for measuring touch-sensitive A contact force (or pressure) sensor on a surface). The contact intensity sensor 165 receives contact intensity information (eg, pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated or adjacent to a touch-sensitive surface (eg, touch-sensitive display system 112 ). In some embodiments, at least one contact intensity sensor is located on the rear of device 100 , opposite touchscreen display 112 located on the front of device 100 .

Device 100 optionally also includes one or more proximity sensors 166 . FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118 . Alternatively, proximity sensor 166 is coupled to input controller 160 in I/O subsystem 106 . In some embodiments, the proximity sensor turns off and disables the touchscreen 112 when the multifunction device is placed near the user's ear (eg, when the user is on a phone call).

Device 100 optionally also includes one or more haptic output generators 167 . FIG. 1A shows a haptic output generator coupled to haptic feedback controller 161 in I/O subsystem 106 . Haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and/or electromechanical devices that convert energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric Actuators, electrostatic actuators, or other tactile output generating components (eg, components that convert electrical signals into tactile outputs on the device). The contact intensity sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be sensed by a user of the device 100 . In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112 ), and is optionally connected vertically (e.g., into/into the surface of device 100 ). outside) or laterally (eg, back and front in the same plane as the surface of device 100) to generate tactile output. In some embodiments, at least one tactile output generator sensor is located on the rear of device 100 , opposite touchscreen display 112 located on the front of device 100 .

Device 100 optionally also includes one or more accelerometers 168 . FIG. 1A shows accelerometer 168 coupled to peripherals interface 118 . Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I/O subsystem 106 . In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on analysis of data received from the one or more accelerometers. In addition to one or more accelerometers 168, device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about device 100 position and orientation (eg, portrait or landscape) information.

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or instruction set) 128, contact/motion module (or instruction set) 130, graphics module (or instruction set) 132, text input Module (or set of instructions) 134 , Global Positioning System (GPS) module (or set of instructions) 135 , and application (or set of instructions) 136 . Additionally, in some embodiments, memory 102 stores device/global internal state 157, as shown in FIGS. 1A and 3 . Device/global internal state 157 includes one or more of the following states: active application state, which is used to indicate which applications (if any) are currently active; display state, which Used to indicate what applications, views, or other information occupy various areas of the touchscreen display 112; sensor status, which includes information obtained from the device's various sensors and input control devices 116; and information about the device's position and/or attitude location information.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes tools for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) various software components and/or drivers, and facilitates communication between various hardware and software components.

Communications module 128 facilitates communicating with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and/or external ports 124 . External port 124 (eg, Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling to other devices directly or indirectly through a network (eg, Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (eg, 30-pin) connector the same or similar to and/or compatible with the 30-pin connector used on an iPod (trademark of Apple Inc.) device.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156 ) and other touch-sensitive devices (eg, a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining contact strength (e.g., force or pressure, or the force of a contact or a surrogate for pressure), determine whether there is movement of a contact and track movement on a touch-sensitive surface (e.g., detect one or more finger drag events), and determine whether a contact has ceased (e.g. , to detect finger lift events or contact breaks). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the velocity (magnitude), velocity (magnitude and direction) and/or acceleration (change in magnitude and/or direction) of the contact point, the movement of the contact point being determined by a series of contact data To represent. These operations are optionally applied to a single contact (eg, one finger contact) or multiple simultaneous contacts (eg, "multi-touch"/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (eg, to determine whether the user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined from software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be determined without changing the physical hardware of the device 100 is adjusted). For example, the mouse "click" threshold for a touchpad or touchscreen can be set to any of a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with the ability to adjust one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by utilizing a system-level click on the "intensity" parameter once). Adjust software settings for multiple intensity thresholds).

The contact/motion module 130 optionally detects gesture input by the user. Different gestures on touch-sensitive surfaces have different contact patterns and intensities. Thus, gestures are optionally detected by detecting specific contact patterns. For example, detecting a single-finger tap gesture includes detecting a finger-down event and then detecting a finger-up (lift-off) at the same location (or substantially the same location) as the finger-down event (e.g., at the icon location) event. As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger down event, then detecting one or more finger drag events, and then 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 for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual impact) of displayed graphics. features) components. As used herein, the term "graphics" includes any object that may 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 representation graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes specifying graphics to be displayed from an application program or the like, together with coordinate data and other graphics attribute data if necessary, and then generates screen image data to output to the display controller 156 .

Haptic feedback module 133 includes various software components for generating instructions that are used by one or more haptic output generators 167 to be generated at one or more locations on device 100 in response to user interaction with device 100 Haptic output.

Text input module 134, optionally part of graphics module 132, provides for use in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input) Soft keyboard for entering text.

The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for location-based dialing, to the camera 143 as picture/video metadata), and to provide to applications that provide location-based services such as Weather widgets, Local Yellow Pages widgets, and Maps/Navigation widgets).

Application programs 136 optionally include the following modules (or sets of instructions) or a subset or superset thereof:

· Contacts module 137 (sometimes called address book or contact list);

· Telephone module 138;

· Video conferencing module 139;

• Email client module 140;

• Instant Messaging (IM) module 141;

· Fitness support module 142;

· Camera module 143 for still images and/or video images;

· image management module 144;

· Browser module 147;

· Calendar module 148;

A widget module 149, which optionally includes one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock Applets 149-4, Dictionary Applets 149-5, and other Applets acquired by users and Applets created by users 149-6;

- an applet creator module 150 for forming user-created applets 149-6;

· Search module 151;

A video and music player module 152, optionally consisting of a video player module and a music player module;

Notepad module 153;

• Map module 154; and/or

· Online video module 155 .

Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA enabled applications, encryption, digital rights management, speech recognition and voice reproduction.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 is optionally used to manage an address book or list of contacts (e.g., stored in memory 102 or memory 370). In the application internal state 192 of the contacts module 137), including: adding one or more names to the address book; deleting one or more names from the address book; adding one or more phone numbers, one or more emails Associate an address, one or more physical addresses, or other information with a name; associate an image with a name; classify and categorize a name; provide a phone number or email address to initiate and/or facilitate a conference by telephone 138, video 139, email 140 or IM 141 communication;

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, telephony module 138 is optionally used to input text corresponding to a telephone number. character sequence, access one or more phone numbers in the address book 137, modify the phone number that has been entered, dial the corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As noted above, wireless communications optionally employ any of a variety of communications standards, protocols, and techniques.

In conjunction with RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, touch module 130, graphics module 132, text input module 134, contact list 137 As with the telephony module 138, the videoconferencing module 139 includes executable instructions for initiating, conducting, and terminating a videoconference between the user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch module 130, graphics module 132, and text input module 134, email client module 140 includes an executable program to create, send, receive, and manage email in response to user instructions. instruction. In conjunction with the image management module 144 , the email client module 140 makes it very easy to create and send emails with still images or video images captured by the camera module 143 .

In combination with RF circuit 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant message module 141 includes functions for inputting character sequences corresponding to instant messages, modifying previously entered characters, transmitting corresponding Instant messaging (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and Executable instructions for viewing received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files, and/or other attachments supported in MMS and/or Enhanced Message Service (EMS). As used herein, "instant messaging" refers to both phone-based messages (eg, messages sent using SMS or MMS) and Internet-based messages (eg, 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, fitness support module 142 includes functions for creating fitness (e.g., with time, distance, and/or calorie burn goals); communicate with fitness sensors (exercise devices); receive fitness sensor data; calibrate sensors for monitoring fitness; select and play music for fitness; and display , store and transmit fitness data.

In conjunction with touch screen 112, display controller 156, optical sensor controller 158, contact module 130, graphics module 132, image management module 144, and one or more optical sensors 164, camera module 143 includes functions for capturing still images or video (including video streams) And store them into the memory 102 , modify the characteristics of the still image or video, or delete the executable instruction of the still image or video from the 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 arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting , present (eg, in a digital slide show or photo album), and store executable instructions for still images and/or video images.

Combined with RF circuit 108, touch screen 112, display system controller 156, touch module 130, graphics module 132, and text input module 134, browser module 147 includes browsing the Internet (including searching, linking to, receiving and displaying web pages or other section, as well as attachments and other files linked to web pages).

Combined with RF circuit 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes functions to create, display , executable instructions to modify and store a calendar and data (eg, calendar entries, to-dos, etc.) associated with the calendar.

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, applet module 149 is a miniature application that is optionally downloaded and used by the user (e.g., Weather widget 149-1, Stock Market widget 149-2, Calculator widget 149-3, Alarm Clock widget 149-4, and Dictionary widget 149-5) or a micro Application programs (eg, user-created applets 149-6). In some embodiments, the applet includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, an applet includes an XML (Extensible Markup Language) file and a JavaScript file (eg, Yahoo! Applet).

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 creator module 150 is optionally used by a user to create widgets (eg, turning user-specified portions of a web page into a desktop applet).

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 functions that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions. Executable instructions for text, music, sound, images, video, and/or other files in memory 102 of words).

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, video and music player module 152 includes a or various file formats (such as MP3 or AAC files) to store recorded music and other sound files, and to display, present, or otherwise play back video (e.g., on touch screen 112 or via external port 124 executable commands on a connected external display). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notepad module 153 includes executable instructions to create and manage notepads, to-do lists, etc. according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, touch module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally configured to receive, Display, modify, and store maps and data associated with maps (e.g., driving directions; data about stores and other points of interest at or near a particular location; and other location-based data).

In conjunction with touch screen 112, display system controller 156, touch module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 Include instructions that allow the user to access, browse, receive (e.g., by streaming and/or downloading), playback (e.g., on a touch screen or external display connected via external port 124), send information to specific online video Linked emails, and otherwise manage online video in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a particular online video.

Each of the modules and applications identified above corresponds to a program for performing one or more functions described above and the methods described in this application (for example, the computer-implemented methods and other information processing methods described herein) A set of executable instructions. These modules (ie sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures described above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device on which operation of a predefined set of functions is performed exclusively through a touch screen and/or a touch pad. By using a touchscreen and/or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, etc.) on device 100 is optionally reduced.

The predefined set of functions performed exclusively through the touchscreen and/or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main menu, a home menu, or a root menu. In such embodiments, the "menu button" is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touchpad.

Figure IB is a block diagram illustrating exemplary components for event handling, according to some embodiments. In some embodiments, memory 102 (in FIG. 1A ) or memory 370 (FIG. 3 ) includes event sorter 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., the aforementioned application 137- 151, 155, any of 380-390).

The event sorter 170 receives the event information and determines the application 136-1 and the application view 191 of the 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 that indicates one or more current application views displayed on touch-sensitive display 112 while 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) are currently active, and application internal state 192 is used by event sorter 170 to determine which application(s) are currently active. The application view 191 to which the event information is delivered.

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, 1 Information displayed or user interface state information ready for information displayed by the application 136-1, a state queue for enabling the user to return to a previous state or view of the application 136-1, and previous actions taken by the user The repeat/undo queue.

Event monitor 171 receives event information from peripherals interface 118 . Event information includes information about sub-events (eg, user contact with the touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or sensors (such as proximity sensor 166 ), microphone 113 , and/or one or more accelerometers 168 (via 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 peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (eg, receiving input above a predetermined noise threshold and/or receiving input for longer than a predetermined duration).

In some embodiments, the event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173 .

When touch-sensitive display 112 displays more than one view, hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. Views consist of controls and other elements that the user can see on the display.

Another aspect of the user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which the touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy. For example, the lowest level view in which a touch is detected is optionally called a hit view, and the set of events identified as correct input is optionally determined based at least in part on the hit view starting with the initial touch of the touch-based gesture.

Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle sub-events. In most cases, the hit view is the lowest level view in which an initiating sub-event (ie, the first sub-event in a sequence of sub-events forming an event or potential event) occurs. Once a 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.

The active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognizer determination module 173 determines that only hit views should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events are completely confined to the area associated with a particular view, views higher in the hierarchy will still remain actively participating views.

Event dispatcher module 174 dispatches event information to event recognizers (eg, event recognizer 180 ). In embodiments that include active event recognizer determination module 173 , event dispatcher module 174 delivers event information to the event recognizers determined by active event recognizer determination module 173 . In some embodiments, the event dispatcher module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver module 182 .

In some embodiments, operating system 126 includes event sorter 170 . Alternatively, application 136 - 1 includes event sorter 170 . In another embodiment, event classifier 170 is a stand-alone module, or 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 a function for handling touch events that occur within a corresponding view of the application's user interface. instructions. Each application view 191 of application 136 - 1 includes one or more event recognizers 180 . Typically, a corresponding 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 toolkit (not shown) or a higher level module from which application 136-1 inherits methods and other features. horizontal objects. In some embodiments, corresponding 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 optionally utilizes or invokes data updater 176 , object updater 177 or GUI updater 178 to update application internal state 192 . Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190 . Additionally, in some embodiments, one or more of data updater 176 , object updater 177 , and GUI updater 178 are included in respective application views 191 .

A corresponding event recognizer 180 receives event information (eg, event data 179 ) from event classifier 170 and recognizes 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 (optionally including sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170 . Event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the motion of a touch, the event information optionally also includes the velocity and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation and vice versa), and the event information includes information about the device's current orientation (also referred to as the device pose). corresponding information.

The event comparator 184 compares the event information to predefined event or sub-event definitions, and based on the comparison, determines the event or sub-event, or determines or updates the status of the event or sub-event. In some embodiments, event comparator 184 includes event definitions 186 . Event definitions 186 contain definitions of events (eg, a predefined sequence of sub-events), such as event 1 ( 187 - 1 ), event 2 ( 187 - 2 ), and other events. In some embodiments, sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multiple touches. In one example, event 1 (187-1) is defined as a double click on the displayed object. For example, the double-click includes a first touch (touch start) for a predetermined duration on the displayed object, a first lift (touch end) for a predetermined duration, and a second touch (touch start) for a predetermined duration on the displayed object. ) and a second lift (touch end) for a predetermined duration. In another example, event 2 (187-2) is defined as a drag on the displayed object. For example, dragging includes a touch (or contact) on a displayed object for a predetermined duration, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch-off). In some embodiments, an event also includes information for one or more associated event handlers 190 .

In some embodiments, event definitions 187 include definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs hit testing to determine which user interface object is associated with the sub-event. For example, in an application view where three user interface objects are displayed on touch 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 Which one is associated with that touch (subevent). If each displayed object is associated with a corresponding 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 the event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, the definition of the corresponding event 187 also includes a delay action that delays the delivery of the event information until after it has been determined whether the sub-event sequence corresponds to the event recognizer's event type.

After it disregards the subsequent sub-event of the touch-based gesture, when the corresponding event recognizer 180 determines that the string of sub-events does not match any event in the event definition 186, then the corresponding event recognizer 180 enters an event not possible, an event failed, or Event end state. In this case, other event recognizers (if any) that remain active for tapping the view continue to track and handle sub-events of the ongoing contact-based gesture.

In some embodiments, a corresponding event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists indicating how the event delivery system should perform delivery of sub-events to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact or are capable of interacting with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in a view or programmatic hierarchy.

In some embodiments, when one or more specific sub-events of an event are recognized, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the respective event recognizer 180 delivers event information associated with the event to the event handler 190 . Activating an event handler 190 is distinct from sending (and deferred sending) a sub-event to the corresponding hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with that flag receives the flag and executes 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, subevent delivery instructions deliver event information to event handlers associated with subevent strings or to actively participating views. Event handlers associated with sub-event strings or with actively involved views receive event information and perform predetermined procedures.

In some embodiments, data updater 176 creates and updates data used in application program 136-1. For example, the data updater 176 updates a phone number used in the contacts module 137 , or stores a video file used in the 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 new user interface objects, or updates the location of user interface objects. The 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, one or more event handlers 190 include or have access to data updater 176 , object updater 177 , and GUI updater 178 . In some embodiments, the data updater 176, the object updater 177, and the GUI updater 178 are included in a single module of the respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It should be understood that the above discussion on event handling of user touches on a touch-sensitive display is also applicable to other forms of user input using input devices to operate the multifunction device 100, and not all user inputs are initiated on the touch screen. For example, mouse movements and mouse button presses, optionally coordinated with single or multiple keyboard presses or presses; contact movements on a touchpad, such as tapping, dragging, scrolling, etc.; stylus input; Movements; verbal commands; detected eye movements; biometric inputs; and/or any combination thereof are optionally used as inputs corresponding to sub-events defining the event to be recognized.

Figure 2 illustrates a portable multifunction device 100 with a touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200 . In this embodiment, as well as in other embodiments described below, the user can, for example, use one or more fingers 202 (not drawn to scale in the drawings) or use one or more stylus 203 (in the accompanying drawings). not drawn to scale) gestures over the figures to select one or more of the figures. In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up and/or down) and/or has been in contact with device 100 finger movement (right to left, left to right, up and/or down). In some implementations or in some cases, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, such as a “home” button or menu button 204 . As previously mentioned, menu button 204 is optionally used to navigate to any application 136 of a set of applications optionally executing on device 100 . Alternatively, in some embodiments, the menu buttons are implemented as soft keys in a GUI displayed on the touch screen 112 .

In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on and off and locking the device, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, a docking/ Charging external port 124 and one or more volume adjustment buttons 208 . The push button 206 is optionally used to power on and off the device by depressing the button and holding the button in the depressed state for a predefined time interval; Release the button before to lock the device; and/or unlock the device or initiate the unlock process. In alternative embodiments, device 100 also accepts verbal input through microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting contact intensity on touch screen 112 and/or one or more tactile output generators 167 for generating tactile output for a user of device 100 .

3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home or industrial control device). device). Device 300 generally includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes an input/output (I/O) interface 330 having a display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, a tactile output generator 357 for generating tactile output on device 300 (e.g., similar to 1A, one or more tactile output generators 167), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and/or one or more contact intensities similar to those described above with reference to FIG. Sensor 165 is a contact intensity sensor). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from one or more CPUs 310 . In some embodiments, memory 370 stores programs, modules and data structures similar to those stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules and data structures not present in memory 102 of portable multifunction device 100 . For example, memory 370 of device 300 optionally stores drawing module 380, rendering module 382, word processing module 384, website creation module 386, disk editing module 388, and/or spreadsheet module 390, while portable multifunction device 100 (FIG. 1A ) memory 102 optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is optionally stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing the functions described above. The modules or programs (i.e., sets of instructions) identified above need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are optionally combined or otherwise rearrange. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

Attention is now turned to an embodiment of a user interface (“UI”) optionally implemented on portable multifunction device 100 .

Figure 4A illustrates an exemplary user interface for an application menu on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300 . In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

• One or more signal strength indicators 402 for one or more wireless communications, such as cellular and Wi-Fi signals;

time 404;

· Bluetooth indicator 405;

· Battery status indicator 406;

• A tray 408 with icons for frequently used applications, such as:

o Icon 416 of the phone module 138 labeled "Phone", which optionally includes an indicator 414 of the number of missed calls or voicemail messages;

o an icon 418 of the email client module 140 labeled "Mail", which optionally includes an indicator 410 of the number of unread emails;

o Icon 420 of the browser module 147 labeled "Browser"; and

o the icon 422 of the video and music player module 152 (also called the iPod (trademark of Apple Inc.) module 152 ) labeled "iPod"; and

· Icons for other applications, such as:

o Icon 424 of the IM module 141 labeled "Text";

o Icon 426 of calendar module 148 labeled "Calendar";

o Icon 428 of Image Management Module 144 labeled "Photos";

o Icon 430 of the camera module 143 labeled "Camera";

o Icon 432 of the online video module 155 labeled "Online Video";

○ icon 434 of the stock market applet 149-2 labeled "stock market";

o Icon 436 of the map module 154 labeled "Map";

o Icon 438 of Weather widget 149-1 labeled "Weather";

○ The icon 440 of the alarm clock applet 149-4 labeled "clock";

o Icon 442 of Fitness Support Module 142 labeled "Fitness Support";

o Icon 444 of Notepad module 153 labeled "Notepad"; and

o Settings application or module icon 446 that provides access to settings for the device 100 and its various applications 136;

It should be noted that the icon labels shown in FIG. 4A are exemplary only. For example, the icon 422 for the video and music player module 152 is labeled "Music" or "Music Player." Other tags are optionally used for various application icons. In some embodiments, the label of the corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

FIG. 4B shows a touch-sensitive surface 451 (eg, tablet or touchpad 355 in FIG. 3 ) separate from a display 450 (eg, touchscreen display 112 ) on a device (eg, device 300 in FIG. 3 ). Exemplary user interface. Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of a contact on touch-sensitive surface 451, and/or for providing a user of device 300 with One or more haptic output generators 359 that generate haptic output.

Although some of the examples that follow will be given with reference to input on touchscreen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as shown in Figure 4B. In some embodiments, the touch-sensitive surface (eg, 451 in FIG. 4B ) has a major axis (eg, 452 in FIG. 4B ) that corresponds to a major axis (eg, 453 in FIG. 4B ) on the display (eg, 450 ). . According to these embodiments, the device detects contact with touch-sensitive surface 451 (eg, 460 in FIG. 4B corresponds to 468 and 462 corresponds to 470) at a location corresponding to a corresponding location on the display (eg, 460 and 462). In this way, when the touch-sensitive surface (eg, 451 in FIG. 4B ) is separated from the display (450 in FIG. 4B ) of the multifunction device, user input (eg, contacts 460 and 462 ) detected by the device on the touch-sensitive surface and their movement) are used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

Additionally, while the examples below are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one of these finger inputs One or more finger inputs are replaced by input from another input device (eg, mouse-based or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (eg, instead of a contact) followed by movement of the cursor along the path of the swipe (eg, instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (eg, instead of detection of a contact followed by terminating detection of the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously or a mouse and multiple finger contacts are optionally used simultaneously.

As used herein, the term "focus selector" refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element) the When an input (eg, a press input) is detected on a touch-sensitive surface (eg, touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B ), that particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display that enables direct interaction with user interface elements on the touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. A contact acts as a "focus selector" such that when an input (e.g., a press input by a contact) is detected on the touchscreen display at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) , to adjust that particular UI element based on the detected input. In some implementations, moving focus from one area of the user interface to another area of the user interface does not require a corresponding movement of the cursor or movement of contact on the touch screen display (e.g., by using the tab or arrow keys to move the focus to another area of the user interface). from one button to another); in these implementations, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the particular form that a focus selector takes, a focus selector is typically a user interface element (or a touch on a touchscreen display) that is controlled by the user in order to communicate the user's desired interaction with the user interface (e.g., by indicating to the device that the user is The element of the user interface with which you intend to interact). For example, the position of a focus selector (e.g., cursor, contact, or select box) over a corresponding button when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) will indicate that the user is intending to activate the corresponding button (as opposed to other user interface elements shown on the device's display).

The user interface graphs described below include various intensity graphs that show a contact on a touch-sensitive surface relative to one or more intensity thresholds (e.g., contact detection intensity threshold IT ₀ , light press intensity threshold IT _L , deep press intensity threshold IT _D and/or the current intensity of one or more other intensity thresholds). This intensity graph is usually not part of the displayed user interface, but is provided to aid in interpreting the graph. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an action typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations other than those normally associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected with an intensity below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold IT ₀ , below which contacts are no longer detected), the device will, according to Movement of the contact on the touch-sensitive surface moves the focus selector without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise stated, these intensity thresholds are consistent across different sets of user interface diagrams.

An increase in contact intensity from an intensity below the light press intensity threshold IT _L to an intensity between the light press intensity threshold IT _L and the deep press intensity threshold IT _D is sometimes referred to as a "light press" input. An increase in contact intensity from an intensity below the deep press intensity threshold IT _D to an intensity above the deep press intensity threshold IT _D is sometimes referred to as a "deep press" input. An increase in contact intensity from an intensity below the contact detection intensity threshold IT ₀ to an intensity between the contact detection intensity threshold IT ₀ and the light press intensity threshold IT _L is sometimes referred to as a detected contact on the touch surface. A decrease in contact intensity from an intensity above the contact detection intensity threshold IT ₀ to an intensity below the contact intensity threshold IT ₀ is sometimes referred to as a detected lift-off of the contact from the touch surface. In some embodiments, IT ₀ is zero. In some embodiments, IT ₀ is greater than zero. In some illustrations, shaded circles or ellipses are used to represent contact intensity on the touch-sensitive surface. In some illustrations, unshaded circles or ellipses are used to represent corresponding contacts on the touch-sensitive surface without specifying corresponding contact strengths.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture comprising a corresponding press input or in response to detecting a corresponding press input performed with a corresponding contact (or contacts), wherein at least A corresponding press input is detected based in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in intensity of the corresponding contact above a press input intensity threshold (eg, a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in intensity of the corresponding contact above a press input intensity threshold and a subsequent decrease in the intensity of the contact below the press input intensity threshold, and in response to detecting the corresponding contact intensity subsequently decreases to low The corresponding operation is performed upon a press input threshold (eg, an "up stroke" of the corresponding press input).

In some embodiments, the device employs an intensity hysteresis to avoid accidental inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is greater than the press input intensity threshold). The threshold is X intensity units lower, or the hysteresis intensity threshold is 75%, 90%, or some reasonable ratio of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact above a press input intensity threshold and a subsequent decrease in the contact intensity below a hysteresis intensity threshold corresponding to the press input intensity threshold, and in response to detecting The corresponding contact intensity then decreases below the hysteresis intensity threshold (eg, an "up stroke" of the corresponding press input) to perform the corresponding action. Similarly, in some embodiments, only if the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold, and optionally a subsequent decrease in the contact intensity to A press input is detected at or below the intensity of the hysteresis intensity, and a corresponding action is performed in response to detecting the press input (eg, an increase in contact intensity or a decrease in contact intensity, depending on the circumstances).

For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input are optionally triggered in response to detection of either: an increase in the intensity of a contact greater than the press input intensity threshold, an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of the contact below the press input intensity threshold, and/or an intensity of the contact Decreases below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in instances where an operation is described as being performed in response to a detected intensity of a contact being decreased below a press input intensity threshold, optionally in response to a detected intensity of a contact being decreased below a value corresponding to and less than a press Enter the hysteresis intensity threshold for the intensity threshold to perform the action on.

User Interface and Associated Processes

Perform user interface operations

Many electronic devices have user interfaces for performing operations such as viewing user interface objects (photos, email messages, etc.) and deleting user interface objects. Some user interface operations, such as deleting a user interface object from a device or stand-alone server, are destructive, meaning that the operation is difficult or impossible to reverse. For example, in some cases, a user who has inadvertently deleted an email message will have a limited amount of time to restore the email message from the trash folder before it is permanently deleted. To prevent such inadvertent operations from occurring, some existing methods have the electronic device request confirmation from a user who has entered an input (eg, into the electronic device) requesting such a destructive operation. A disadvantage of these existing methods is that they are time consuming and require additional input from the user to confirm that the operation should be performed.

In the embodiments described below, improved methods for performing user interface operations are provided. A gesture associated with a corresponding user action on the touch-sensitive surface (eg, swiping over an email message to delete the email message) is detected. In response to detecting the gesture, if the gesture has a maximum intensity on the touch-sensitive surface above the first intensity threshold, the device performs the action without requesting confirmation from the user (e.g., a deep press swipe is understood by the device as Indicates that the request to perform an action was genuinely intended). On the other hand, if the maximum intensity of the gesture is below the first intensity threshold, the device requests confirmation that the user intends to perform the action, and thus still prevents unintentional destructive actions from being performed. Some operations, such as scrolling, are performed without requesting confirmation from the user, regardless of the strength of the gesture associated with the request to perform the operation.

5A-5I illustrate exemplary user interfaces for performing user interface operations, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 6A-6B. Where applicable, FIGS. 5A-5I include an intensity map showing current contact intensity on the touch-sensitive surface relative to a plurality of intensity thresholds including a first intensity threshold (eg, “IT _D ”). In some embodiments, operations similar to those described below with reference to "IT _D " are performed with reference to a different intensity threshold (eg, "IT _L ").

In some embodiments, the device is an electronic device with a separate display (eg, display 450 ) and a separate touch-sensitive surface (eg, touch-sensitive surface 451 ). In some embodiments, the device is portable multifunction device 100, the display is touch-sensitive display system 112, and the touch-sensitive surface includes tactile output generator 167 on the display (FIG. 1A). For ease of explanation, the embodiments described with reference to FIGS. 5A-5I and 6A-6B will be discussed with reference to the touch screen 112, however, when the user interface shown in FIGS. 5A-5I is displayed on the display 450, in response to Detecting the contact described in FIGS. 5A-5I on touch-sensitive surface 451 optionally performs a similar operation on a device having display 450 and a separate touch-sensitive surface 451; in such embodiments, the focus selector either Optionally is a cursor or pointer displayed at a location corresponding to (eg, at or near) the location of the contacts (eg, 1806, 1808, and 1810) shown in Figures 5A-5I.

FIG. 5A illustrates an exemplary user interface for performing user interface operations on electronic device 300 having touch screen display 112 . In some embodiments, the device displays one or more user interface objects (eg, user interface objects 1804-1 through 1804-4 correspond to email sessions 1 through 4, respectively). In particular, Figures 5A-5I illustrate an example of deleting an email message from a list of email messages, and also illustrate examples of other user interface operations, such as scrolling through a list of emails, according to some embodiments.

FIG. 5B shows detection of contact 1806 . In some embodiments, particular gestures are associated with particular corresponding actions. For example, contact 1806 is included in a swipe gesture over user interface object 1804-1. Figure 5B shows an example of an embodiment in which a swipe gesture over an email message (user interface item 1804-1) is interpreted as a request to delete or archive the message. In some embodiments, a swipe gesture is considered to be over an email message if the gesture starts within the predefined boundaries of the email message. In some embodiments, a swipe gesture is considered to be over an email message if a substantial portion of the gesture occurs within the predefined boundaries (or within the predefined area in which a representation of the email message is displayed).

In the example shown in FIG. 5B , contact 1806 has an intensity below a corresponding intensity threshold (eg, IT _D ). In this instance, the device detects the gesture and, based on predefined criteria, requests confirmation that the user wants to delete the email message (e.g., if the criteria are not met) or deletes the email message without asking the user for confirmation (e.g., if the criteria are met). standard). In some embodiments, the predefined criteria include that the respective intensity (eg, maximum intensity) of the gesture is above a predefined threshold (eg, IT _D ). It is contemplated that when a gesture is detected over an email message, the strength of contact 1806 may be defined and measured in any number of ways. For example, in some embodiments, intensity is measured at the beginning of a gesture. In some embodiments, the average intensity of the gesture is used. Other metrics for measuring and defining the strength of a gesture will be apparent to those skilled in the art.

FIG. 5C shows the continuation of contact 1806 forming a swipe gesture on user interface object 1804-1. Contact 1806 in both Figures 5B and 5C has an intensity below the deep press intensity threshold. Accordingly, the device requests confirmation that the user wants to delete the email message (eg, displays an affordance with the word "Delete?"). Requesting confirmation to perform an operation such as a destructive operation (such as deleting a user interface object) for a low-intensity gesture enables the device to prevent unintentional operations that are difficult or impossible to reverse. In some embodiments, the user optionally selects an affordance (using a single contact or a continuation of the same gesture) to inform the device to proceed with the operation. In some embodiments, a separate gesture than the selection of the affordance cancels the operation. For example, in some embodiments, a second swipe over an email cancels the request to delete the email. In some embodiments, any one of a plurality of gestures other than the gesture of selection that includes the affordance cancels the delete operation. In this example, contact 1806 is also below the light press intensity threshold. In this example, no additional functionality is associated with the light press intensity threshold. However, in some other embodiments, additional functionality is associated with the tap input (e.g., a tap intensity threshold is used to identify an affordance for activating an affordance in response to detecting a tap input on a user interface object 1804). Intensity thresholds for light press inputs such as the delete affordance in FIG. 5B , the edit affordance in FIG. 5B , and/or opening a session that include increasing from an intensity below IT _L to above contact strength of IT _L ).

5D is similar to FIG. 5B, except that contact 1808 shown in FIG. 5D has an intensity above the deep press intensity threshold IT _D (eg, contact 1806 in FIG. 5B has an intensity below IT _D ). FIG. 5E shows a continuation of the gesture including contact 1808 . Figure 5E is similar to Figure 5C, except that contact 1808 shown in Figure 5E has an intensity above the deep press intensity threshold (eg, contact 1806 in Figure 5C). For the sake of brevity, other details already described with reference to FIGS. 5B and 5C are not repeated here with reference to FIGS. 5D and 5E , respectively. In some embodiments, the email message is deleted without requesting confirmation from the user because contact 1808 has a maximum intensity higher than IT _D when over the email message. In this instance, the device determines that the gesture is not unexpected based on the high intensity of the contact, and therefore proceeds with the operation (e.g., delete) without requesting the user to enter more user input (e.g., confirmation input), saving user time and increase efficiency. In some embodiments, contact 1808 has a higher intensity than IT _D throughout the gesture shown in FIGS. 5D-5E . In some embodiments, contact 1808 has an intensity higher than IT _D at the beginning of the gesture shown in FIGS. 5D-5E and has an intensity lower than IT _D at the end of the gesture shown in FIGS. 5D-5E . strength. In some embodiments, contact 1808 has an intensity lower than IT _D at the beginning of the gesture shown in FIGS. 5D-5E and has an intensity higher than IT _D at the end of the gesture shown in FIGS. 5D-5E .

In some embodiments, it is helpful to display a dramatic animation that grabs the user's attention (eg, an animation of glass being shattered or a representation of an email message being "crumpled") to notify the user that a destructive action has been performed. In some embodiments, after displaying the animation corresponding to the destructive operation, the user is provided with an option to undo the destructive operation (eg, display an "undo" affordance or an instruction to shake to undo). Figure 5F shows a still frame illustration of such an animation. In this case, the animation dramatically displays the word "deleting".

Figure 5G shows the email message being removed from the list after the animation described with reference to Figure 5F. In some embodiments, one or more additional email messages that were previously invisible (e.g., the user would have to scroll through the email message column to see them) are now invisible due to the removal of user interface object 1804-1. is visible. For example, user interface object 1804-5 is now visible to the user without scrolling.

In some embodiments, certain inputs associated with certain operations may be performed without requesting confirmation from the user, regardless of the intensity of contact corresponding to the input. For example, FIG. 5H shows a vertical swipe input that includes an upward movement of contact 1810 . In this example, a vertical swipe input performed with contact 1810 is interpreted by the device as a request to scroll through a list of email messages. Figure 5I shows the resulting change in the displayed email message (the list has been scrolled so that user interface objects 1804-5 through 1804-7 are now displayed). The maximum intensity of the vertical swipe gesture performed with contact 1810 is below the deep press intensity threshold (and for that matter, the light press intensity threshold). However, in this instance, the list is scrolled without requesting user confirmation because the scrolling operation does not require user confirmation. In some embodiments, an operation associated with a tap gesture is classified as one that requires user confirmation or does not require user confirmation based on the ease with which the operation can be reversed (e.g., whether it is a destructive or non-destructive operation). operation.

6A-6B are flowcharts illustrating a method 1900 of performing user interface operations, according to some embodiments. Method 1900 is performed at an electronic device (eg, device 300 , FIG. 3 , or portable multifunction device 100 , FIG. 1A ) having a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 1900 are optionally combined and/or the order of some operations is optionally changed.

As described below, method 1900 provides an intuitive way to perform user interface operations. The method reduces the cognitive load on the user when performing user interface operations, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling users to perform user interface operations faster and more efficiently saves power and increases the time between battery charges.

The device displays ( 1902 ) a user interface on a display of the device (eg, the user interface displayed on touch screen 112 of device 300 , FIG. 5A ). The device detects (1904) a gesture by the user on the touch-sensitive surface that includes a contact corresponding to a focus selector at a corresponding location in the user interface (eg, contact 1806, FIG. 5B). Gestures are associated with corresponding actions.

In some embodiments, the gesture is (1906) a swipe gesture of a contact corresponding to the focus selector's representation of an item in a list of items (e.g., a message or conversation in an email inbox) on the move. In some embodiments, the user interface includes (1908) a plurality of user interface objects, and the respective locations correspond to respective ones of the plurality of user interface objects. In some embodiments, the corresponding operation is ( 1910 ) a destructive operation (eg, a delete operation).

In response to detecting the gesture, based on determining that the contact has a maximum intensity below the first intensity threshold, the device requests (1912) confirmation that the user intended the device to perform the corresponding action (eg, to confirm that the user did not perform the gesture by accident). For example, FIGS. 5C-5D illustrate an example of a gesture having a maximum intensity below IT _D and a subsequent request for confirmation to delete an email message. In response to the gesture, upon determining that the maximum intensity of the contact is above the first intensity threshold, the device performs the corresponding operation without requesting confirmation that the user wants the device to perform the corresponding operation. For example, Figures 5D-5E illustrate an example of a gesture with a maximum intensity above IT _D and subsequent deletion of an email message without requesting confirmation. In some embodiments, the first intensity threshold is a higher intensity threshold than the input detection intensity threshold at which the contact was initially detected. In some embodiments, the device determines whether to request confirmation or perform an operation without requesting confirmation based on whether the gesture satisfies confirmation criteria. In some embodiments, the validation criteria are met when the contact (eg, contact 1808 in FIGS. 5D-5E ) has an intensity that is maintained (eg, sustained) above IT _D throughout the gesture. In some embodiments, this validation criterion is met when the contact (e.g., contact 1808 in FIGS. 5D-5E ) has an intensity higher than IT _D at the beginning of the gesture (or before detection of movement of the contact), regardless of Whether the contact has an intensity higher than IT _D at the end of the gesture. In some embodiments, the validation criteria are met when a contact (eg, contact 1808 in FIGS. 5D-5E ) has an intensity higher than IT _D at the end of the gesture (or after ceasing to detect movement of the contact), regardless of Whether the contact had an intensity higher than IT _D at the start of the gesture.

In some embodiments, requesting confirmation that the user wants the device to perform the corresponding operation includes (1914) displaying a confirmation message including an option to continue performing the corresponding operation. In some embodiments, the confirmation message includes an explicit option to cancel execution of the corresponding operation. In some embodiments, the confirmation message does not include an explicit option to cancel performance of the corresponding operation, but a tap/press when the focus selector is outside the confirmation message cancels performance of the corresponding operation. In some embodiments, the confirmation identifies (1916) the corresponding action to be performed (e.g., a dialog that displays "Do you want to delete this message? Yes/No" or an affordance that simply displays "Delete?", as shown in Figure 5C).

In some embodiments, it is helpful to display a dramatic animation that grabs the user's attention to inform the user that a destructive action has been performed. In some embodiments, the corresponding operation is ( 1918 ) a delete operation, and performing the operation includes displaying an animation that crumples the corresponding user interface object (eg, crumpling the object like a piece of paper). In some embodiments, the operation is ( 1920 ) a delete operation, and performing the operation includes displaying an animation that shatters the corresponding user interface object (eg, shatters the object like a sheet of glass). For example, Figure 5F shows a still frame of an animation of the word "deleting" being shattered like glass. In some embodiments, after displaying the animation corresponding to the destructive operation, the user is provided with an option to undo the destructive operation (eg, display an "undo" affordance or an instruction to shake to undo). In some embodiments, the operation is a delete operation, and performing the operation includes displaying that the corresponding user interface object is collapsed (e.g., collapsing the corresponding user interface object with itself and/or collapsing multiple user interface objects that include the corresponding user interface object interface object) animation. In some embodiments, the operation is a delete operation, and performing the operation includes displaying an animation of the corresponding user interface object moving back into the display (eg, the corresponding user interface object moves back and fades out).

In some embodiments, the device detects (1922) one or more inputs including a contact having a maximum intensity below the first intensity threshold. In response to detecting the one or more inputs, the device performs ( 1924 ) one or more corresponding operations (eg, non-destructive operations such as scrolling operations or email viewing operations) without requesting confirmation from the user. For example, a user may view or scroll through a list of email messages using one or more contacts having an intensity below a first intensity threshold, as shown in FIGS. 5H-5I.

It should be understood that the particular order in which the operations have been described in FIGS. 6A-6B is exemplary only and is not intended to indicate that the described order is the only order in which these operations may be performed. Various ways will occur to those of ordinary skill in the art to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in paragraph [0057]) also apply in a similar manner to those described above with respect to Figure 6A - The method 1900 depicted in Figure 6B. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, animations described above with reference to method 1900 optionally have other methods described herein with reference to them (e.g., those listed in paragraph [0057] ) describes one or more properties of a contact, gesture, user interface object, intensity threshold, focus selector, animation. For brevity, these details are not repeated here.

According to some embodiments, Fig. 7 shows a functional block diagram of an electronic device 2000 configured according to the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software that carry out the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in FIG. 7 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Accordingly, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. As shown in FIG. 7 , the electronic device 2000 includes a display unit 2002 configured to display a user interface; a touch-sensitive surface unit 2004 configured to detect user gestures on the touch-sensitive surface unit, the touch-sensitive surface unit 2004 configured to a gesture comprising a contact corresponding to a focus selector at a corresponding location in the user interface, wherein the gesture is associated with a corresponding operation; one or more sensor units 2006 configured to detect contact with the touch-sensitive surface contact intensity unit 2004; and a processing unit 2008 coupled to the display unit 2002, the touch-sensitive surface unit 2004, and the one or more sensor units 2006. In some embodiments, the processing unit 2008 includes a confirmation request unit 2010 , an operation execution unit 2012 and an animation unit 2014 .

In some embodiments, the user interface includes a plurality of user interface objects; and the respective locations correspond to respective ones of the plurality of user interface objects.

The processing unit 2008 is configured to: in response to detecting the gesture: request confirmation (e.g., using the confirmation request unit 2010) that the user wants the device to perform the corresponding operation based on determining that the contact has a maximum intensity below the first intensity threshold; Determining that the maximum intensity of the contact is above the first intensity threshold, the corresponding operation is performed without requesting confirmation that the user wants the device to perform the corresponding operation (eg, using the operation performing unit 2012).

In some embodiments, the gesture is a swipe gesture of contact corresponding to movement of the focus selector over the representation of the item in the list of items.

In some embodiments, requesting confirmation (eg, using confirmation requesting unit 2010 ) that the user intends to perform the corresponding operation includes displaying a confirmation message including an option to continue performing the corresponding operation.

In some embodiments, the confirmation identifies a corresponding operation to be performed.

In some embodiments, the corresponding operation is a destructive operation.

In some embodiments, the processing unit 2008 is further configured to: detect one or more inputs including a contact having a maximum intensity below the first intensity threshold; and respond to detecting one or more input and perform one or more corresponding actions without asking for confirmation from the user.

In some embodiments, the corresponding operation is a delete operation; and performing the operation includes displaying an animation that puckers the corresponding user interface object (eg, using animation unit 2014 ).

In some embodiments, the operation is a delete operation; and performing the operation includes displaying an animation that shatters the corresponding user interface object (eg, using animation unit 2014).

The operations in the above-mentioned information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to FIG. 1A and FIG. 3 ) or application-specific silicon.

The operations described above with reference to FIGS. 6A-6B are optionally implemented by components depicted in FIGS. 1A-1B or 7 . For example, display operation 1902 , detection operation 1904 , and wrinkle animation operation 1918 are optionally implemented by event classifier 170 , event recognizer 180 , and event handler 190 . Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event, Such as the selection of objects on the user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses a corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be apparent to those skilled in the art how other processes can be implemented based on the components shown in Figures 1A-1B.

Display additional information in response to user touch

Many electronic devices have a graphical user interface that includes user interface objects displayed at specific locations on a display. In some cases, one or more user interface objects are associated with hidden information that when the user places the cursor or contact over the user interface object for a predefined period of time (e.g., a tooltip) or clicks and holds Revealed when persisted on a user interface object for a predefined period of time (for example, the back button on a browser). These situations require the user to wait for a predefined period of time to see the initially hidden information. It would be advantageous to provide the user with the option to avoid waiting and get an immediate display of additional information. In some cases, a single activation area or user interface object is associated with multiple operations of the device (eg, a back button on a browser is associated with both navigating to a previous web page and displaying a pop-up list of previously visited web pages). In these cases, time delays are sometimes introduced as a way to determine which of multiple operations to perform in response to user input associated with an activation region or user interface object. However, such delays disrupt the user's workflow. Providing an intuitive way to perform specific actions immediately can make the user's interaction with the device more efficient.

Embodiments described below provide new and improved methods of displaying additional information (or activating user interface objects) using touch-sensitive surfaces and sensors that detect contact intensity (eg, pressure) on the touch-sensitive surfaces. To avoid waiting a predefined delay time in order to view additional information associated with a user interface object or area of the user interface, the user has the option to apply a contact intensity (e.g., pressure) greater than a predefined intensity threshold to immediately see the additional information option. For example, a user may immediately display a tooltip or popup menu without having to wait for a delay time by pressing the touch-sensitive surface with an intensity above an intensity threshold. Similarly, for the back button on a browser, a user can immediately display a list of previously visited web pages by pressing the touch-sensitive surface with an intensity above an intensity threshold. On the other hand, if the user does not press with sufficient strength, the additional information is not displayed until the delay time has elapsed. Thus, the described embodiments provide a more efficient way for users to interact with user interface objects.

8A-8N illustrate example user interfaces for displaying additional information associated with a location on a display based on contact intensity (eg, pressure) and contact timing (eg, duration), according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 9A-9B. 8A-8N include intensity graphs showing the current intensity of a contact on a touch-sensitive surface relative to a plurality of intensity thresholds including respective thresholds (eg, "IT _D "). In some embodiments, operations similar to those described below with reference to IT _D are performed with reference to a different intensity threshold (eg, "IT _L ").

FIG. 8A illustrates a user interface (eg, a web page) displayed on display 450, the user interface having a plurality of selectable objects (eg, 3606-1 and 3606-2). FIGS. 8A-8C illustrate responding to the detection of a contact (e.g., by scroll the page) to display additional information.

In FIG. 8A, at a time prior to T0, no contact is present or detected on touch-sensitive surface 451, and focus selector 3607-a is moved away from scroll arrow 3606-4 in scroll bar 3606-3. In FIG. 8B, at time T0, a contact is detected on touch-sensitive surface 451 (eg, contact 3605 in FIG. 8B). In response to detecting contact on touch-sensitive surface 451, device instructs display 450 to position a focus selector (e.g., focus selector 3607-a in FIG. 8B ) at a location on display 450 (e.g., scroll above scroll arrow 3606-4 in bar 3606-3). In FIG. 8C, after time T1 and before time T2, when focus selector 3607-a is still positioned at a position on display 450 (e.g., scroll arrow 3606-a in scroll bar 366-3 in FIG. 8C 4 above), the intensity of a contact on touch-sensitive surface 451 (eg, contact 3605 in FIG. 8C ) exceeds intensity threshold IT _D . When the contact has an intensity above a predefined intensity threshold, delaying without waiting for a predefined delay time elapses (for example, without waiting until time T2 or without waiting until a predefined _delay time T has elapsed) =T2-T0 case) Additional information (eg, additionally selectable objects 3606-6 and 3606-7) is displayed on the display 450 (eg, by scrolling a web page). In other words, when focus selector 3607-a is over scroll arrow 3606-4, if the user places a contact with an intensity above the intensity threshold, the user interface is scrolled, even if the delay time has not elapsed. In some embodiments, the portion of the user interface that controls scrolling of the user interface includes a displayed scrolling user interface (eg, as shown in FIG. 8A ). In some embodiments, the portion of the user interface that controls scrolling of the user interface is a hidden hit area that is not displayed but exists at the edge of the scrollable window of the application. For example, if the user moves the cursor 3607 to the bottom edge of the display when moving the corresponding icon or other user interface object or when selecting text, the device responds to detecting that the cursor remains in the hidden hit area for more than the delay time or responds to detecting The intensity of the contact increases above a predefined intensity threshold while scrolling the user interface.

8D-8G illustrate that when a contact has an intensity below (eg, less than) an intensity threshold (eg, "IT _D "), waiting until the time the contact is detected on the touch-sensitive surface 451 (or from A predefined delay time has elapsed to display additional information (eg, by scrolling a web page) in response to a detected contact (starting from the time the contact reaches a lower intensity threshold, such as IT _L ).

In FIG. 8D, at a time prior to T0, no contact is present or detected on touch-sensitive surface 451 and focus selector 3607-a is moved away from scroll arrow 3606-4 in scroll bar 3606-3. In FIG. 8E, at time T0, a contact is detected on touch-sensitive surface 451 (eg, contact 3608 in FIG. 8E). In response to detecting contact on touch-sensitive surface 451, device instructs display 450 to position a focus selector (e.g., focus selector 3607-b in FIG. 8E ) at a corresponding location on display 450 (e.g., in FIG. 8E edge 3606-4 of the scroll bar 3606-3). In FIG. 8F, at a time prior to time T2, when focus selector 3607-b is still positioned at the corresponding location on display 450 (e.g., above scroll arrow 3606-4 in scroll bar 3606-3 in FIG. 8F ), the intensity of a contact on touch-sensitive surface 451 (eg, contact 3608 in FIG. 8F ) is below intensity threshold IT _D . When the contact 3608 has an intensity below the intensity threshold and while the focus selector 3607-b is still positioned at the corresponding location on the display 450, the device delays until a predefined delay time has elapsed (e.g., a predefined _delay time T). =T2-T0) or until time T2 to display the additional information associated with the corresponding position of the focus selector 3607-b. In FIG. 8G, after a predefined delay time (T _delay = T2-T0) has elapsed or after time T2, when the intensity of the contact (e.g., contact 3608 in FIG. 8G ) on the touch-sensitive surface 451 is still below the intensity threshold IT _D , and while focus selector 3607-b is still positioned at a position on display 450 (e.g., above scroll arrow 3606-4 in scroll bar 3606-3 in FIG. 8G ), on display 450 (e.g., , by scrolling the web page) to display additional information (eg, additionally selectable objects 3606-6 and 3606-7). For example, if the user places a contact with an intensity below the intensity threshold over a scroll arrow in the scroll area and waits for more than the delay time, scroll the UI accordingly. In some embodiments, the delay time T _delay = T2-T1, and the contact reaches a lower intensity threshold (e.g., "IT _L ") at time T1, and waits until the contact intensity has been maintained from time T1 until time T2 Additional information is shown on the display after the intensity threshold IT _L is exceeded.

In other words, in some embodiments, the device determines whether the intensity of the contact is above an intensity threshold when the focus selector is located at the corresponding location on the display. If the contact intensity is above the intensity threshold, the device does not wait a predefined delay time to display the additional information on the display, but displays the additional information immediately. On the other hand, if the contact intensity is lower than the intensity threshold, the device waits until a predefined delay time to display the additional information on the display, thus displaying the additional information at a later time (e.g. determined according to the predefined delay time) . Therefore, if the user increases the intensity of the contact above the intensity threshold, the user can display additional (eg, not initially displayed) information associated with the location corresponding to the contact earlier on the display without having to wait for a preview. Defined delay time.

In some embodiments, when the focus selector is displayed at the corresponding location, the device determines whether a predefined delay time has elapsed from the time the contact was detected. The device displays additional information on the display 450 if a predefined delay time has elapsed since the contact was detected. On the other hand, if the predefined delay time has not elapsed, the device determines (eg, checks repeatedly, iteratively, or multiple times) whether the contact intensity is higher than the predefined threshold. If the device determines that the contact intensity is above a predefined threshold, the device displays additional information without waiting until a predefined delay time has elapsed.

FIG. 8H shows a user interface (eg, a web page) displayed on the touch screen 112 . 8H-8J also show that when a contact has an intensity (eg, pressure) above (eg, greater than) an intensity threshold (eg, IT _D ), without waiting a predefined delay from the time the contact is detected Additional information (eg, browsing history, including a list of previously visited web pages) is displayed in response to contact detected directly on the touch screen 112 in the event of time.

In FIG. 8H , at a time prior to T0, no contact is present or detected on touch screen 112 at a location corresponding to browser back button 3610 (however, contact optionally exists at another location on touch screen 112 place). In FIG. 81 , at time T0, a contact (eg, contact 3609 in FIG. 81 ) is detected on touch screen 112 at a corresponding location (eg, at the location of back button 3610 in FIG. 81 ). In some embodiments, when the device has a touchscreen display and a contact is detected on the touchscreen, the location of the focus selector coincides with the location of the contact on the touchscreen. In FIG. 8J , after time T1 and before time T2 , while contact 3609 is still positioned at the corresponding location on touchscreen 112 (eg, at the location of back button 3610 in FIG. 8J ), the contact on touchscreen 112 (eg, contact 3609 in FIG. 8J ) has an intensity that exceeds the intensity threshold IT _D . When the contact has an intensity above the predefined intensity threshold, without waiting for the predefined delay time to have elapsed (for example, without waiting until time T2 or without waiting until the predefined delay time has elapsed In the case of T _delay =T2-T0) additional information (for example, browsing history, including a list 3611 of previously visited web pages) is displayed on the touch screen 112 . In other words, if the user places a touch on the browser back button with an intensity higher than the intensity threshold IT _D , the browser history is displayed even if the delay time has not elapsed.

8K-8N illustrate that when a contact has an intensity below (eg, less than) the intensity threshold IT _D , waiting until a predefined delay time has elapsed from the time the contact is detected at the corresponding location on the touch screen 112 to display additional information corresponding to the detected contact (eg, browsing history, including a list 3611 of previously visited web pages, sometimes referred to as browser history).

In FIG. 8K , at a time prior to T0, no contact is present or detected on touch screen 112 at a location corresponding to browser back button 3610 (however, contact optionally exists at another location on touch screen 112 place). In FIG. 8L , at time T0 , a contact (eg, contact 3613 in FIG. 8L ) is detected on touch screen 112 at a location corresponding to browser back button 3610 . In some embodiments, the location of the contact on touchscreen 112 coincides with the location of the focus selector on touchscreen 112 (eg, at the location of back button 3610 in FIG. 8L ). In FIG. 8M, at a time prior to time T2, while the contact (or focus selector) is still positioned at the corresponding location on the touchscreen 112 (e.g., at the location of the back button 3610 in FIG. 8M), the touchscreen 112 The intensity of the contact on (eg, contact 3613 in FIG. 8L ) is below the intensity threshold IT _D . When the contact has an intensity below the intensity threshold and the contact (or focus selector) is still positioned at the corresponding location on the touch screen 112, the device waits until a predefined delay time has elapsed (e.g., a predefined _delay time Tdelay=T2 -T0) or no additional information is displayed until time T2. In FIG. 8N, after a predefined delay time (T _delay = T2-T0) elapses or after time T2, when the contact (or the focus selector corresponding to the contact) is still positioned at the corresponding position on the touch screen 112 ( For example, at the position of the back button 3610 in FIG. 8N ), additional information (eg, browsing history, including a list 3611 of previously visited web pages) is displayed on the touch screen 112 . In other words, if the user places a touch on the browser back button with an intensity lower than the intensity threshold IT _D and waits longer than the delay time, the browser history is displayed.

9A-9B are flowcharts illustrating a method 3700 of displaying additional information associated with a location on a display based on contact intensity (eg, pressure) and contact timing (eg, duration), according to some embodiments. Method 3700 is performed at an electronic device (eg, device 300 , FIG. 3 , or portable multifunction device 100 , FIG. 1A ) that has a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. The device includes one or more sensors for detecting the intensity of contact with the touch-sensitive surface. Some operations in method 3700 are optionally combined, and/or the order of some operations is optionally changed.

As described below, method 3700 provides an intuitive way to display additional (eg, not initially displayed) information associated with a location on a display based on contact intensity (eg, pressure) and contact timing (eg, duration). The method reduces the cognitive load on the user when additional (eg, not initially displayed) information is displayed by enabling the user to skip the delay time and immediately access the additional information, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to display additional (eg, not initially displayed) information more quickly and efficiently saves power and increases the time between battery charges.

Additional information that is not initially displayed on the display when the focus selector corresponding to the contact is located on the display (e.g., the additional information is detected on the touch screen when the focus selector is moved to the corresponding position on the display or detected The device detects ( 3702 ) a contact on the touch-sensitive surface when at a corresponding location associated with the contact not immediately preceding). In some embodiments, the additional information is "associated" with the corresponding location in that the additional information is displayed on the display when a predefined gesture (eg, finger press input) is performed at the corresponding location.

In some embodiments, the device detects a gesture that includes movement of a contact on a touch-sensitive surface that corresponds to movement of a focus selector to a corresponding location on the display (e.g., a cursor moves in response to movement of a contact on a touchpad). movement on the display). In such embodiments, the additional information is not displayed immediately prior to detecting movement of the focus selector to a corresponding position on the display. For example, as explained with reference to FIGS. 8A-8G , the device detects contact 3605 on touch-sensitive surface 451 that is separate from display 450 . In this example, a focus selector (e.g., cursor 3607 in FIGS. 8A-8G ) corresponding to contact 3608 on touch-sensitive surface 451 is positioned at a corresponding location on display 450 (e.g., the scroll button in FIG. 8B ). scroll arrow 3606-4 in bar 3606-3), and moves according to the movement of contact 3605. Additional information associated with the location of focus selector 3607-a (eg, additional selectable objects 3606-6 and 3606-7 displayed on display 450, FIG. 8C) is not initially displayed on display 450.

In some embodiments, the contact is a finger contact. In some embodiments, the additional information is not displayed immediately prior to detection of contact on the touch screen at the corresponding location. In some embodiments, the device detects a contact on a portion of the touch-sensitive surface that corresponds to a corresponding location (eg, the device detects a contact at the location of a button on a touchscreen display that is associated with additional information). For example, the device detects a contact 3609 on the touch screen 112 at a corresponding location (eg, at the location of the back button 3610 in FIG. 8I ), as explained with reference to FIGS. 81-8N . In some embodiments, as shown in FIG. 8I , when the device has a touchscreen display (eg, touchscreen 112 ) and a contact is detected on the touchscreen (eg, contact 3609 , FIG. 8I ), the position of the focus selector is related to the location of the contact. coincide. Additional information associated with the location of the focus selector (eg, browsing history, including a list 3611 of previously visited web pages, FIG. 8J ) is not initially displayed on the touchscreen 112 .

In some embodiments, the device displays (3704) the user interface object on the display. In some embodiments, the user interface object (3706) is associated with additional information that was not initially displayed on the display; and the corresponding location corresponds to the location of the user interface object on the display (e.g., the additional information is associated with an icon of the user interface or other components shown). In some embodiments, the corresponding location is not associated with a particular user interface object on the display (e.g., the device detects a contact or cursor in an active area or hidden hit area of the touch-sensitive surface and/or display, the contact or cursor in Display of additional information is triggered when activated by waiting a delay time or increasing the intensity of a contact above an intensity threshold).

In some embodiments, the additional information includes (3708) help for the user interface object (e.g., information describing the user interface object and one or more options for retrieving further help related to the user interface object, such as a hyperlink or search bar). In some embodiments, the additional information includes ( 3710 ) a description of one or more functions of the user interface object. In some embodiments, the additional information includes a brief description of the user interface object and/or a description of the functionality associated with the user interface object. For example, if the user interface object is a "create bookmark" icon in a browser, the additional information is optionally: "This creates a new bookmark; bookmarks are a way to save your favorite sites."

In some embodiments, the additional information includes (3712) a menu with selectable options related to the user interface object. For example, if the user interface object is a file icon, the additional information includes a menu with selectable options such as "Open", "Edit", "Print", "Copy", "Delete", "Rename" and the like.

In some embodiments, the user interface object is ( 3714 ) a back button. For example, the user interface object is a back button of a web browser or file browser, such as back button 3610 shown in FIGS. 8H-8N . In some embodiments (eg, where the user interface object is a back button), the additional information includes a browsing history that includes a list of previously visited representations of the information. For example, as shown in FIGS. 8J and 8N , the additional information includes a browsing history that includes a list 3611 of previously visited web pages. In this instance, when the focus _selector is over the back button, the device displays the previously visited list of sites or folders. In some embodiments, the device displays a list 3611 of previously visited websites or folders on the touchscreen 112 in response to detecting that the intensity of the contact 3609 on the touchscreen 112 is above a corresponding intensity threshold, as described with reference to FIG. 8J . In some embodiments, when the focus selector (coincident with the contact 3613 on the touch screen 112) is over the back button 3610, when the focus selector (coincident with the contact 3613 on the touch screen 112) is over the back button 3610, in response to detecting the contact 3613 for more than a predefined _delay time (Tdelay =T2-T0), the device displays a list 3611 of previously visited websites or folders.

In some embodiments, the respective locations correspond to ( 3718 ) edges of the user interface for navigating in the electronic document. In some embodiments, the edge of the user interface used to navigate within the electronic document is a scroll bar. For example, as shown in FIGS. 8A-8E , the respective positions correspond to scroll arrows 3606-4 in scroll bar 3606-3 for navigating through the electronic document, where scroll bar 3606-3 is located at the position shown on display 450. at the bottom edge of the user interface. In some embodiments, the edge of the user interface used to navigate within the electronic document is a portion of the electronic document that is adjacent to the edge of the application window displaying the electronic document. For example, in some cases, a user selecting a portion of an electronic document (eg, by dragging a cursor or touch over text in a word processing document or on a web page) will reach the edge of the electronic document on the display. In this example, if the device would otherwise wait for a delay period (eg, 0.1, 0.2, 0.3, 0.4, or 0.5 seconds) to elapse before scrolling the electronic document, the device will instead respond to the intensity increase before the delay period has elapsed. is greater than a corresponding intensity threshold (eg, IT _D ) to start scrolling the electronic document.

In some embodiments (e.g., where the respective locations correspond to hidden hit areas at the edges of the user interface for navigating in the electronic document), the additional information includes the electronic document's focus selector at the respective location part of the display that is not displayed immediately before the contact is detected. For example, when the user is selecting objects (for example, a file icon in a file manager application) or content (for example, text in a word processing document) within the application window or moving a user interface object within the application window (for example, file icon in a file manager application), when the focus selector is at or near the edge of the application window, when the focus selector is paused at the edge of the user interface for longer than a predefined delay, or if the focus selector is When the selector is at or near an edge of the application window and a press input above a corresponding intensity threshold is detected, the application window is scrolled. Scrolling the application window in this manner enables the user to keep moving the UI object or alternatively enables the user to move the UI object without interruption (for example, without dropping the currently selected UI object or without deselecting a previously selected UI object). In the case of content) keep selecting the object or content.

For example, when the focus selector is located at an edge of the user interface for navigating in an electronic document, the device scrolls the electronic document. Specifically, as explained with reference to FIG. 8C , when focus selector 3607-a is positioned over scroll arrow 3606-4 in scroll bar 3606-3, in response to detecting that the intensity of contact 3605 is above a corresponding intensity threshold IT _D , With scroll bar 3606-3 located at the bottom edge of the user interface shown on display 450, the device scrolls the electronic document to display additional information (eg, additionally selectable objects 3606-6 and 3606-7). Similarly, when focus selector 3607-b is positioned over scroll arrow 3606-4 in scroll bar 3606-3, as explained with reference to FIG. Over a predefined _delay time Tdelay = T2-T0), the device scrolls the electronic document.

As another example, when the focus selector is adjacent to a scroll bar or near the edge of an application window in which an electronic document is displayed, when the focus selector is paused in that position for longer than a predefined delay time or if a higher than the corresponding The device scrolls the document with a press input of a threshold intensity. In some embodiments, when the press input is detected, the electronic document is scrolled based on a determination that the user interface object is currently selected and is moving according to movement of the focus selector. For example, if the user is in a file manager application (e.g., a system file manager such as Finder from Apple Inc. (Cupertino, California), or a media manager such as iPhoto from Apple Inc. (Cupertino, California) or iTunes from Apple Inc. (Cupertino, California) drags a representation of a file or program (e.g., a file or program icon) in a window, and the user drags the representation of the file or program to the file manager application's window and when at the edge of the virtual desktop and pause for more than a predefined delay time or increase the intensity of the contact above the corresponding intensity threshold, the device will scroll the window of the file manager program.

In some embodiments, the respective locations correspond to ( 3720 ) edges of the display. For example, the corresponding location is located on an area or strip within a predefined distance (eg, 0.1, 0.5 or 1.0 mm, or 5, 10 or other suitable number of pixels) of the edge of the display. In some embodiments (e.g., where the respective location corresponds to an edge of the display), the additional information includes a virtual desktop that was not displayed immediately before contact was detected when the focus selector was at the respective location (e.g., when the focus selector switching between virtual desktops in response to detecting a contact intensity exceeding a corresponding intensity threshold or detecting a contact lasting longer than a predefined delay time when the monitor is located at an edge of the display). For example, if a user is dragging a window on an operating system's workspace or virtual desktop with multiple virtual desktops, and the user drags the application's window to the edge of the virtual desktop and pauses or If the intensity of the contact increases beyond a respective intensity threshold, the device will optionally switch from the current/first virtual desktop to a different/second virtual desktop associated with a respective edge of the current virtual desktop. In this example, the edge of the display is associated with the virtual desktop because pressing the input when the focus selector is adjacent to the edge of the display causes a different virtual desktop to be displayed. In some embodiments, when the press input is detected, a different virtual desktop is displayed based on a determination that a user interface object is currently selected and moving according to movement of the focus selector. In other words, a different virtual desktop is displayed based on determining that the user has performed a gesture associated with moving a user interface object from the current virtual desktop to the different virtual desktop.

In some embodiments, the corresponding location corresponds (3722) to a hyperlink (eg, a hyperlink in a webpage), and the additional information includes content associated with the hyperlink. For example, in response to detecting that the intensity of a contact on a hyperlink in a web page displayed in the web browser exceeds a corresponding intensity threshold or detecting that the contact lasts for more than a predefined delay time, the device opens a new application window of the web browser or the current A web page associated with the hyperlink is loaded in the application window (eg, immediately after detecting an increase in contact intensity or after detecting a lift-off of the contact after detecting an increase in contact intensity).

When the focus selector is located (3724) at the corresponding position: upon determining (3726) that the contact has a value above the corresponding intensity threshold (e.g., FIG. 8A ) before a predefined delay time has elapsed with the focus selector at the - Intensity of "IT _D " in FIG. 8N ), the device displays additional information associated with the corresponding location without waiting until a predefined delay time has elapsed. For example, as explained with reference to FIG. 8C, when the focus selector (eg, cursor 3607-a) is located at a corresponding position (eg, located at scroll arrow 3606-4 in scroll bar 3606-3), the focus selection is performed according to the determination. If the device 3607-a is located at the corresponding location, the contact 3605 has an intensity above the corresponding intensity threshold before a predefined _delay time (e.g., Tdelay=T2-T0) elapses, the device displays additional information associated with the corresponding location (eg, additionally selectable objects 3606-6 and 3606-7) without waiting until a predefined delay time has elapsed (eg, waiting until time T2).

When the focus selector is at (3724) the corresponding location: Upon determining (3730) that the contact has an intensity below the corresponding intensity threshold, the device waits until a predefined delay time has elapsed to display the Additional information associated with the location. For example, as explained with reference to FIGS. 8F-8G , when the focus selector (e.g., cursor 3607-b) is located at a corresponding position (e.g., scroll arrow 3606-4 in scroll bar 3606-3), according to the determined contact 3608 has an intensity below the corresponding intensity threshold, when the focus selector (e.g., cursor 3607-b) is located at the corresponding location, the device waits until a predefined _delay time has elapsed (e.g., Tdelay=T2-T0) to display the same Additional information associated with the corresponding location (eg, additional selectable objects 3606-6 and 3606-7). For example, the device waits until time T2 to display additional information associated with the corresponding location.

In some embodiments, the device detects ( 3734 ) a tap gesture on the touch-sensitive surface when the focus selector is located at the corresponding location. For example, the device detects a contact on a touch-sensitive surface that has a duration less than a predefined maximum tap gesture duration and/or is between a minimum contact detection intensity (e.g., IT ₀ ) and a corresponding intensity threshold IT _D (e.g., Maximum strength between short regular press gestures that are not "deep press" inputs. In some embodiments, in response to detecting the tap gesture, the device performs ( 3736 ) an operation associated with the user interface object (eg, without displaying additional information associated with the corresponding location). In other words, in some embodiments, a regular press input corresponding to a user interface object (eg, a non-deep press interaction) performs an operation that immediately displays additional information associated with the corresponding location, unlike a deep press input, (eg, , a non-deep press interaction results in navigating "back" in the browser by loading the most recently previously visited webpage in the browser instead of displaying a list of previously visited websites).

It should be understood that the particular order in which the operations have been described in FIGS. 9A-9B is exemplary only and is not intended to indicate that the described order is the only order in which the described operations may be performed. Various ways will occur to those of ordinary skill in the art to reorder the operations described herein. In addition, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in paragraph [0057]) also apply in a similar manner to those described above with respect to Figure 9A - The method 3700 described in Figure 9B. For example, the contacts, gestures, user interface objects, intensity thresholds, and focus selectors described above with reference to method 3700 optionally have the same features described herein with reference to other methods described herein (e.g., those listed in paragraph [0057]). One or more properties of the touch, gesture, user interface object, intensity threshold, and focus selector described above. For brevity, these details are not repeated here.

According to some embodiments, Figure 10 shows a functional block diagram of an electronic device 3800 configured in accordance with the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software that carry out the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in FIG. 10 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Accordingly, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 10 , an electronic device 3800 includes a display unit 3802 configured to display additional information associated with a corresponding location; a touch-sensitive surface unit 3804 configured to receive a message on the touch-sensitive surface unit contact; one or more sensor units 3805 configured to detect the intensity of contact with the touch-sensitive surface unit 3804; and a processing unit 3806 coupled to the display unit 3802, the touch-sensitive surface unit 3804 and sensor unit 3805. In some embodiments, the processing unit 3806 includes a detection unit 3808 , a waiting unit 3810 and a display enabling unit 3814 .

The processing unit 3806 is configured to detect a contact on the touch-sensitive surface unit 3804 when a focus selector corresponding to the contact is located at a corresponding location on the display unit 3802 associated with additional information not initially displayed on the display unit 3802 ( For example, using detection unit 3808); and when the focus selector is at the corresponding position: upon determining that the contact has an intensity above the corresponding intensity threshold before the predefined delay time has elapsed with the focus selector at the corresponding position , enabling the display of additional information associated with the corresponding location (eg, utilizing the display enabling unit 3814) without waiting until a predefined delay time has elapsed; and according to determining that the contact has an intensity below the corresponding intensity threshold, when the focus The selector waits while at the corresponding location until a predefined delay time has elapsed (eg, using wait unit 3810 ) to enable display of additional information associated with the corresponding location (eg, using display enabling unit 3814 ).

In some embodiments, processing unit 3806 is further configured to enable display of a user interface object on display unit 3802 (e.g., using display enabling unit 3814), wherein the user interface object is not originally displayed on display unit 3802 and the corresponding position corresponds to the position of the user interface object on the display unit 3802.

In some embodiments, the additional information is information selected from the group consisting of help for the user interface object, a description of one or more functions of the user interface object, and information with available information related to the user interface object. Select a menu of options.

In some embodiments, the processing unit 3806 is further configured to detect a tap gesture on the touch-sensitive surface unit (e.g., using the detection unit 3808) when the focus selector is located at the corresponding position; and in response to detecting the tap gesture, Performs the action associated with the user interface object.

In some embodiments, the user interface object is a back button; and the additional information includes a browsing history including a list of representations of previously accessed information.

In some embodiments, the respective location corresponds to an edge of the user interface used for navigating in the electronic document; and the additional information includes a portion of the electronic document that was not displayed immediately before the contact was detected when the focus selector was positioned at the respective location .

In some embodiments, the corresponding location corresponds to an edge of the display unit 3802; and the additional information includes a virtual desktop that was not displayed immediately before the contact was detected when the focus selector was located at the corresponding location.

In some embodiments, the respective locations correspond to hyperlinks; and the additional information includes content associated with the hyperlinks.

The operations in the above-mentioned information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to FIG. 1A and FIG. 3 ) or application-specific silicon.

The operations described above with reference to FIGS. 9A-9B are optionally implemented by components depicted in FIGS. 1A-1B or 10 . For example, detect operation 3702 , display operations 3704 and 3726 , and wait operation 3730 are optionally implemented by event sorter 170 , event recognizer 180 and event handler 190 . Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event, Such as the selection of objects on the user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be apparent to those skilled in the art how other processes can be implemented based on the components shown in Figures 1A-1B.

Remove icons from predefined areas

Many electronic devices have graphical user interfaces that include application task bars or launch bars. The application taskbar or launch bar includes an application icon that the user can activate to launch the application. Users can add application icons corresponding to their favorite or frequently used applications to the application tray for quick access, and remove application icons from the application tray. Users can also rearrange application icons within the application taskbar. Some methods require multiple inputs for removing the application icon from the application tray, or sometimes result in accidental removal of the icon from the application tray. Embodiments described below improve these methods by allowing a user to make gestures on a touch-sensitive surface and move application icons based on the contact intensity in the gesture for rearrangement or removal of application icons from the application taskbar based on intensity . When the user performs a gesture with a heavy touch, the user can remove the application icon from the application taskbar. When the user performs a gesture with a light touch, the application icon remains in the application taskbar. The user thus has a more convenient way for removing the application icon from the application taskbar and reduces the likelihood of accidental removal of the icon from the application taskbar.

11A-11U illustrate example user interfaces for removing icons from predefined areas, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 12A-12B. FIGS. 11A-11U include intensity maps showing contact on a touch-sensitive surface relative to multiplicity including light press intensity thresholds (eg, “IT _L ”) and deep press intensity thresholds (eg, “IT _D ”). The current intensity of an intensity threshold. In some embodiments, operations similar to those described below with reference to IT _D are performed with reference to a different intensity threshold (eg, "IT _L ").

FIG. 11A shows user interface 3904 displayed on display 450 of a device (eg, device 300 ). Displayed in user interface 3904 is an application taskbar or tray area 3916 . One or more icons are optionally displayed in application taskbar area 3916. For example, in FIG. 11A , application icons 3906 , 3908 , 3910 , 3912 , and 3914 are displayed in application taskbar 3912 . Each application icon 3906, 3908, 3910, 3912, and 3914 is associated with a respective application. For example, icon 3908 is associated with a media player or an audio application. In some embodiments, application taskbar or tray area 3916 is a predefined area displayed on display 450 in which one or more application icons (such as icons 3906, 3908, 3910, 3912, and 3914) are optionally placed to for quick access.

Also displayed on the display 450 is a cursor 3922 . Cursor 3922 is an example of a focus selector. The user optionally moves cursor 3922 on display 450 (e.g., using touch-sensitive surface 451 of the device) to point to a user interface object (e.g., icon 3906, 3908, 3910, 3912, or 3914) and select and manipulate the object with additional input .

11B-11C illustrate gestures detected on the touch-sensitive surface 451 of the device when the cursor 3922 is positioned over the icon 3908 . The gesture is performed with contact 3920. The gesture includes movement 3924 of contact 3920 on touch-sensitive surface 451, as shown in Figure 11C. Movement 3924 corresponds to movement of cursor 3922 outside application taskbar area 3916 ; cursor 3922 moves outside application taskbar area 3916 according to movement 3924 .

The intensity of contact 3920 is detected by one or more sensors in the device. The intensity is detected for the entire duration of the gesture. In response to detecting a gesture that includes contact 3920, and based on a determination by the device that contact 3920 had a maximum intensity during the gesture that was below a deep press intensity threshold (e.g., " _ITD "), displaying an indication that the gesture is being performed during the gesture, And icon 3908 (the icon over which cursor 3922 was positioned when the gesture was detected) remains in application taskbar area 3916 after the gesture ends. The indication is optionally the display of movement of icon 3908, eg, according to movement of cursor 3922, as shown in FIG. 11C. Icon 3908 remains on the application taskbar after detecting the end of the gesture (e.g., detecting a lift off of contact 3920 or detecting a decrease in intensity of contact 3920 from an intensity above IT _L to an intensity below IT _L ) In region 3916, as shown in FIG. 11D.

In some embodiments, displaying an indication that the gesture is being performed includes changing the appearance of the icon 3908 to, for example, display a ghost image 3926 of the icon 3908, as shown in FIGS. 11E-11F . While phantom 3926 is displayed, a representation of icon 3908 is displayed to move according to movement 3924 of contact 3920 . The representation of icon 3908 moved according to movement 3924 is optionally a ghost image 3926 (as shown in FIG. 11F ) or a duplicate icon 3928 of icon 3908 (as shown in FIG. 11G ). After the gesture ends, the icon 3908 is displayed again in the application taskbar area 3916, as shown in Figure 11D.

In some embodiments, displaying an indication that the gesture is being performed includes displaying movement of cursor 3922 while leaving icon 3908 in place in application taskbar area 3916 . For example, FIG. 11H shows cursor 3922 moving out of application taskbar area 3916 in accordance with movement 3924 of contact 3920 , while icon 3908 remains fixed at its position in application task bar area 3916 .

In some embodiments, displaying an indication that the gesture is being performed includes displaying movement of the icon 3908 during the gesture, but constraining the movement of the icon 3908 to the application taskbar area 3916, as shown in FIG. 111 . In other words, icon 3908 does not move completely out of application taskbar area 3916 (or, optionally, does not move out of application taskbar area 3916 at all). After the gesture ends, icon 3908 is again displayed in its original location in application taskbar area 3916, as shown in Figure 11D. In some embodiments, icon 3908 is moved to the left or right within application taskbar area 3916 .

FIG. 11J shows user interface 3904, icons 3906, 3908, 3910, 3912, and 3914, application taskbar area 3916, and cursor 3922 displayed on display 450 of the device, as shown in FIG. 11A. A gesture performed with contact 3930 and movement 3934 of contact 3930 are detected on touch-sensitive surface 451 . In FIG. 11J , the device detects that contact 3930 reached a strength above a deep press strength threshold (eg, "IT _D ") during the gesture.

In response to detecting a gesture that includes contact 3930, and based on a determination by the device that contact 3930 reached a strength above a deep press strength threshold (e.g., "IT _D ") during the gesture, icon 3908 (with cursor 3922 positioned there when the gesture was detected) icon above) moves according to movement 3934 of contact 3930, as shown in FIG. _L ) Icon 3908 is then removed from application taskbar area 3916, as shown in FIG. 11M . Icons 3908 removed from application taskbar area 3916 are optionally displayed outside of application taskbar area 3916 or deleted. In some embodiments, when icon 3908 is moved, an indication that icon 3908 is to be removed from application taskbar area 3916 is displayed prior to actual removal. The indication is optionally that icon 3936 replaces icon 3908 in application taskbar area 3916, as shown in Figure 11L.

FIG. 11N shows a gesture performed with contact 3938 detected on touch-sensitive surface 451 when cursor 3922 is positioned over icon 3908 . The gesture performed with contact 3938 is optionally a tap gesture or a press input (or a rest press input) that includes an increase in the intensity of the contact above a light press intensity threshold (e.g., “IT _L ”) followed by a decrease . In response to detecting the gesture performed with contact 3938 in FIG. 11N , an application corresponding to icon 3908 ( FIG. 11N ) is launched, as shown in FIG. 11O .

11P-11U illustrate examples of the user interface described above with reference to FIGS. 11A-11O implemented on the touch screen 112 of a device (eg, device 100). FIG. 11P shows user interface 3944 displayed on touch-sensitive display 112 of the device. Displayed in user interface 3944 is application taskbar or tray area 3916 . One or more icons are optionally displayed in application taskbar area 3916. For example, in FIG. 11P , application icons 3906 , 3908 , 3910 , 3912 , and 3914 are displayed in application taskbar 3916 .

11P-11Q illustrate gestures detected on the touch-sensitive display 112 of the device. The gesture is performed with contact 3946 detected on icon 3908 . The gesture includes movement 3948 of contact 3946 on touch-sensitive display 112, as shown in FIG. 11Q. Movement 3948 includes movement outside of application taskbar area 3916.

The intensity of contact 3946 is detected by one or more sensors in the device. The intensity is detected for the entire duration of the gesture. In response to detecting a gesture that includes contact 3946, and based on a determination by the device that contact 3946 had a maximum intensity during the gesture that was below a deep press intensity threshold (e.g., "IT _D "), displaying an indication that the gesture is being performed during the gesture, And the icon 3908 (the icon on which the contact 3946 was detected when the gesture was detected) remains in the application taskbar area 3916 after the gesture ends. The indication is optionally the display of, for example, icon 3908 according to the movement of movement 3948, as shown in FIG. 11Q. Icon 3908 remains in application taskbar area 3916 after the gesture ends (e.g., a lift off of contact 3946 is detected or a drop in intensity of contact 3946 from an intensity above IT _L to an intensity below IT _L is detected), As shown in Figure 11R.

11S-11T illustrate gestures detected on the touch-sensitive display 112 of the device. The gesture is performed with contact 3950 detected on icon 3908 . The gesture includes movement 3952 of contact 3950 on touch-sensitive display 112, as shown in Figure 11T. Movement 3952 includes movement outside of application taskbar area 3916.

The intensity of contact 3950 is detected by one or more sensors in the device. The intensity is detected for the entire duration of the gesture. In response to detecting a gesture that includes contact 3950, and based on a determination by the device that contact 3950 reached a strength above a deep press strength threshold (e.g., "IT _D ") during the gesture, icon 3908 (where contact 3950 was located when the gesture was detected) Icon above) moves according to movement 3952 of contact 3950, as shown in FIG. 11T , and icon 3908 is removed from application taskbar area 3916 after the gesture ends, as shown in FIG. 11U .

12A-12B are flowcharts illustrating a method 4000 of removing an icon from a predefined area, according to some embodiments. Method 4000 is performed at an electronic device having a display and a touch-sensitive surface (eg, device 300, FIG. 3, or portable multifunction device 100, FIG. 1A). In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 4000 are optionally combined, and/or the order of some operations is optionally changed.

As described below, method 4000 provides an intuitive way to remove icons from predefined areas. The method reduces the cognitive load on the user when removing icons from predefined areas, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to remove icons from a predefined area more quickly and efficiently saves power and increases the time between battery charges.

The device displays a plurality of icons in a predefined area on the display (eg, an application taskbar or a quick launch tray), wherein the plurality of icons includes ( 4002 ) corresponding icons. For example, in FIG. 11A or 11P , icons 3906 , 3908 , 3910 , 3912 , and 3914 are displayed in application taskbar region 3916 .

The device detects a gesture that includes (4004) a contact (e.g., a finger contact) on the touch-sensitive surface while the focus selector is over the corresponding icon and subsequent movement of the contact on the touch-sensitive surface, the subsequent movement corresponding to the focus selector Movement outside a predefined area. For example, FIGS. 11B-11C illustrate gestures including contact 3920 and movement 3924 of contact 3920 detected on touch-sensitive surface 451 . A gesture is detected when cursor 3922 is positioned over icon 3908 . Movement 3924 corresponds to movement of cursor 3922 outside application taskbar area 3916 . As another example, FIGS. 11J-11K illustrate gestures including contact 3930 and movement 3934 of contact 3930 detected on touch-sensitive surface 451 . A gesture is detected when cursor 3922 is positioned over icon 3908 . Movement 3934 corresponds to movement of cursor 3922 outside of application taskbar area 3916 .

As a further example, FIGS. 11P-11Q illustrate a gesture including a contact 3946 and a movement 3948 of the contact 3946 detected on the touch-sensitive display 112 . Contact 3946 is detected over icon 3908 and movement 3948 includes movement of contact 3946 outside application taskbar area 3916 . 11S-11T illustrate gestures including contact 3950 and movement 3952 of contact 3950 detected on touch-sensitive display 112 . Contact 3950 is detected over icon 3908 and movement 3952 includes movement of contact 3950 outside application taskbar area 3916 . In these examples, the location of the contact (contact 3946 or 3950) is similar to the location of the focus selector.

In response (4006) to detecting the gesture, and based on determining (4008) that the contact had a maximum intensity during the gesture that was below a corresponding intensity threshold, the device displays (4010) an indication during the gesture that the gesture is being performed (e.g., displaying a corresponding icon's move or a ghost of the corresponding icon), and retain (4018) the corresponding icon in the predefined area after the gesture ends (e.g., the corresponding icon bounces or otherwise returns to its original position in response to detecting lift-off of the contact , or stop movement at the boundary of a predefined area). In response to detecting a gesture performed with contact 3920 and upon determining that contact 3920 had a maximum intensity during the gesture that was below a defined intensity threshold, the device displays, for example, movement of icon 3908 ( FIG. 11C ) or phantom 3926 ( FIG. 11F ) or duplicate icon 3928 (FIG. 11G ) and leave icon 3908 in application taskbar area 3916 after the gesture ends, as shown in FIG. 11D . As another example, in response to detecting a gesture performed with contact 3946 (FIG. 11P), icon 3908 moves according to movement 3948 of contact 3946 and then remains in application taskbar area 3916 after the gesture ends, as shown in FIG. 11R .

In some embodiments, displaying an indication that the gesture is being performed includes (4012) changing the appearance of the corresponding icon in the predefined area (e.g., replacing the corresponding icon with a ghost image of the icon), and when the icon with the changed appearance is displayed on the display, When the corresponding icon is selected, the representation of the corresponding icon is moved according to the movement of the contact during the gesture. For example, in response to detecting a gesture performed with contact 3920, icon 3908 optionally changes to ghost 3926, and while ghost 3926 is displayed, a representation of icon 3908 (e.g., copy icon 3928 or ghost 3926) moves according to movement 3924 , as shown in Figure 11E-Figure 11G.

In some embodiments, displaying an indication that the gesture is being performed includes (4014) moving a cursor on the display in accordance with the movement of the contact while holding the corresponding icon in a fixed position in the predefined area (e.g., unless the user is pushing hard enough Press firmly, otherwise the icon in the taskbar is static or "stuck" in place). For example, in response to detecting a gesture performed with contact 3920, while icon 3908 remains in place, cursor 3922 is optionally moved according to movement 3924, as shown in Figure 11H.

In some embodiments, displaying an indication that the gesture is being performed includes (4016) moving the corresponding icon according to the movement of the contact during the gesture (e.g., the icon can still be moved during the gesture) while constraining movement of the corresponding icon to a predefined area Repositions within the taskbar, but cannot be moved outside the taskbar unless the user presses harder). In some embodiments, if the icon is constrained to a predefined area, the icon moves along the edge of the predefined area closest to the contact. For example, if the predefined area is a horizontal strip near the bottom edge of the display, and the focus selector is above the predefined area, the movement of the icon will track the horizontal movement of the contact, but not the vertical movement of the contact, unless The focus selector moves into a predefined area. For example, movement of icon 3908 according to movement 3924 of contact 3920 is optionally constrained within application taskbar region 3916, as shown in FIG. 111 .

In response (4006) to detecting the gesture, and upon determining (4020) that the contact reached an intensity above a corresponding intensity threshold during the gesture, the device moves (4022) the corresponding icon according to the movement of the contact during the gesture (e.g., moving The corresponding icon moves out of the predefined area such that it follows the movement of the contact), and the corresponding icon is removed (4024) from the predefined area after the gesture ends (e.g., deleting the icon or removing the icon in response to detecting lift-off of the contact Icon moves to a position outside the predefined area). For example, in FIGS. 11J-11K , in response to detecting a gesture performed with a contact 3930 and upon determining that the contact 3930 reached an intensity above a defined intensity threshold during the gesture, the device displays, for example, an icon 3908 according to a movement 3934 of the contact 3930 . Move, and icon 3908 is removed from application taskbar area 3916 after the gesture ends, as shown in FIG. 11M . As another example, in FIGS. 11S-11T , in response to detecting a gesture performed with contact 3950 , icon 3908 moves according to movement 3952 of contact 3950 and is then removed from application taskbar area 3916 after the gesture ends. Icon 3908, as shown in Figure 11U.

In some embodiments, prior to detecting the end of the gesture, the device displays (4026) that the corresponding icon will be removed from the task prior to removing the corresponding icon from the predefined area based on determining that the contact reached an intensity above the corresponding intensity threshold during the gesture. Visual indication of bar removal (for example, displaying that the corresponding icon moves out of the predefined area before the end of the gesture is detected and/or displaying an icon removal symbol such as " cloud" or red "X"). FIG. 11L shows that icon 3936 (eg, an application icon deletion indication) is displayed in application taskbar area 3916 in place of icon 3908 , eg, before the gesture performed with contact 3930 ends.

In some embodiments, the device detects (4028) a tap gesture on the touch-sensitive surface when the focus selector is over the corresponding icon, and in response to detecting the tap gesture, the device initiates (4030) the corresponding application. In some embodiments, the corresponding icon is a document icon that opens a particular document with a default application. In some embodiments, the corresponding icon is an application icon that opens the application without a document or with a default/blank document initially displayed. For example, in FIGS. 11N-11O , in response to detecting tap gesture 3938 on touch-sensitive surface 451 while cursor 3922 is positioned over icon 3908 , an application associated with icon 3908 is launched and corresponding interface 3940 is displayed.

In some embodiments, instead of determining whether to remove a corresponding icon from a predefined area based on whether the contact has a maximum intensity above or below a corresponding intensity threshold during a gesture corresponding to movement outside the predefined area, the device bases the contact on having The maximum intensity above or below the corresponding intensity threshold is used to determine whether to rearrange multiple icons in a predefined area. Accordingly, in some embodiments, the device displays a plurality of icons in a predefined area on the display, wherein the plurality of icons includes a corresponding icon. The device detects a gesture comprising contact on the touch-sensitive surface when the focus selector is over a corresponding icon; and subsequent movement of the contact on the touch-sensitive surface corresponding to movement of the focus selector within the predefined area . In response to detecting a gesture: based on determining that the contact had a maximum intensity during the gesture that was below a corresponding intensity threshold, the device displays an indication during the gesture that the gesture is being performed; and does not rearrange (e.g., rearrange) in the predefined area after the gesture ends. Sort) corresponding icons. Conversely, based on determining that the contact reached an intensity higher than a corresponding intensity threshold during the gesture, the device moves the corresponding icon according to the movement of the contact during the gesture; The icons rearrange (eg, reorder) the corresponding icons. For example, in Figure 11P, if the device detects that contact 3946 with a maximum intensity below IT _D moves to a location between icon 3910 and icon 3912, icon 3908 will return when the contact intensity falls below IT _L to its original position, and the icons in the predefined area 3916 will not be rearranged, as shown in FIG. 11R (eg, because contact 3946 has a maximum intensity lower than IT _D ). Conversely, in FIG. 11S , if the device detects that contact 3950 with a maximum intensity above IT _D moves to a location between icon 3910 and icon 3912, then icon 3908 will be removed when the contact intensity falls below IT _L. Placed between icon 3910 and icon 3912, and the icons in predefined area 3916 will be rearranged accordingly (eg, because contact 3950 has a maximum intensity higher than IT _D ). Inadvertently rearranging icons in a predefined area can be frustrating to users who may not realize that the icons have been rearranged and then have difficulty finding the icon that has been removed from its usual location. Using a higher intensity threshold (e.g., IT _D ) to control whether user gestures rearrange icons in a predefined area helps prevent users from inadvertently rearranging icons within a predefined area, improving user interface efficiency and predictability .

It should be understood that the particular order in which the operations have been described in FIGS. 12A-12B is exemplary only and is not intended to indicate that the described order is the only order in which these operations may be performed. Various ways will occur to those of ordinary skill in the art to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in paragraph [0057]) also apply in a similar manner to those described above with respect to Figure 12A - The method 4000 depicted in Figure 12B. For example, the contacts, gestures, user interface objects, intensity thresholds, and focus selectors described above with reference to method 4000 optionally have other methods described herein with reference to this text (e.g., those listed in paragraph [0057]) One or more properties of the described contact, gesture, user interface object, intensity threshold, and focus selector. For brevity, these details are not repeated here.

According to some embodiments, Figure 13 shows a functional block diagram of an electronic device 4100 configured according to the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software that carry out the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in FIG. 13 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Accordingly, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 13 , the electronic device 4100 includes a display unit 4102 configured to display a plurality of icons in a predefined area on the display unit 4102, wherein the plurality of icons include corresponding icons; a touch-sensitive surface unit 4104 , the touch-sensitive surface unit is configured to receive gestures; one or more sensor units 4105, the one or more sensor units are configured to detect contact intensity with the touch-sensitive surface unit 4104; and processing unit 4106, the processing unit coupled connected to the display unit 4102 , the touch-sensitive surface unit 4104 and the sensor unit 4105 . In some embodiments, the processing unit 4106 includes a detection unit 4108 , a display enabling unit 4110 , a retention unit 4112 , a movement unit 4114 , a removal unit 4116 and an activation unit 4118 .

The processing unit 4106 is configured to: detect a gesture comprising a contact on the touch-sensitive surface unit 4104 when the focus selector is over a corresponding icon and a subsequent movement of the contact on the touch-sensitive surface unit 4104 corresponding to Movement of the focus selector outside the predefined area (e.g., using the detection unit 4108), and in response to detecting the gesture: enabling the gesture to be active during the gesture based on a determination that the contact had a maximum intensity below a corresponding intensity threshold during the gesture The display of the instruction being carried out (for example, utilize display enabling unit 4110) and keep the corresponding icon in the predefined area (for example, utilize retaining unit 4112) after the gesture ends; The intensity of the intensity threshold, moving the corresponding icon according to the movement of the contact during the gesture (eg, with the move unit 4114) and removing the corresponding icon from the predefined area after the gesture ends (eg, with the use remove unit 4116).

In some embodiments, displaying the indication that the gesture is being performed includes: changing the appearance of the corresponding icon in the predefined area, and when the corresponding icon with the changed appearance is displayed on the display unit 4102, according to the movement of the contact during the gesture to move the representation of the corresponding icon.

In some embodiments, displaying an indication that the gesture is being performed includes moving a cursor on the display unit 4102 according to the movement of the contact while holding the corresponding icon in a fixed position in the predefined area.

In some embodiments, displaying an indication that the gesture is being performed includes moving the corresponding icon according to movement of the contact during the gesture while constraining movement of the corresponding icon to a predefined area.

In some embodiments, processing unit 4106 is configured to detect a tap gesture on touch-sensitive surface unit 4104 (e.g., using detection unit 4108) when the focus selector is over a corresponding icon, and respond to detecting the tap gesture , launch the corresponding application associated with the corresponding icon (eg, using launch element 4118).

In some embodiments, the processing unit 4106 is configured to, prior to detecting the end of the gesture, enable the corresponding Display of a visual indication that the icon is to be removed from the taskbar (eg, with display enabling unit 4110).

The operations in the above-mentioned information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to FIG. 1A and FIG. 3 ) or application-specific silicon.

The operations described above with reference to FIGS. 12A-12B are optionally implemented by components depicted in FIGS. 1A-1B or 13 . For example, detect operation 4004 , display operation 4010 , retain operation 4018 , move operation 4022 , and remove operation 4024 are optionally implemented by event sorter 170 , event recognizer 180 , and event handler 190 . Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface (or whether the rotation of the device) corresponds to a predefined event. An event or sub-event, such as selection of an object on a user interface, or rotation of the device from one orientation to another. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be apparent to those skilled in the art how other processes can be implemented based on the components shown in Figures 1A-1B.

show content layer

Many electronic devices include applications or user interfaces in which different corresponding content, such as layers of content, can be displayed. For example, the corresponding content may be images of the location at different times or different types of maps of the location. In some approaches, in order to display different content layers, the user must open a menu and select the desired content layer, which can be tedious and time consuming. The examples described below improve upon these methods. When the focus selector is over the content layer, the user increases the intensity of the contact on the touch-sensitive surface. If the intensity increases above the threshold, the corresponding portion of the different content layer is displayed. Different content layers can also be revealed gradually based on contact intensity, or panned by moving the focus selector. These features enable more efficient display and manipulation of content layers.

14A-14L illustrate example user interfaces for displaying content layers, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 15A-15C. FIGS. 14A-14L include intensity graphs showing contact on a touch-sensitive surface relative to an intensity threshold including a light press intensity (eg, “IT _L ”) and a transition onset intensity threshold (eg, “IT ₁ ”). Current intensity for multiple intensity thresholds. In some embodiments, operations similar to those described below with reference to "IT _L " are performed with reference to a different intensity threshold (eg, "IT _D ").

In some embodiments, the device is an electronic device with a separate display (eg, display 450 ) and a separate touch-sensitive surface (eg, touch-sensitive surface 451 ). In some embodiments, the device is portable multifunction device 100, the display is touch-sensitive display system 112, and the touch-sensitive surface includes tactile output generator 167 on the display (FIG. 1A). For ease of explanation, the embodiments described with reference to FIGS. When the user interface is shown, similar operations are optionally performed on a device having a touch-sensitive display system 112 in response to detecting the contact described in FIGS. 14A-14L on the touch-sensitive display system 112; in such embodiments , the focus selector is optionally: the corresponding contact, a representative point corresponding to the contact (e.g., the centroid of the corresponding contact or a point associated with the corresponding contact), or detected on the touch-sensitive display system 112 instead of the cursor 6904 Two or more touching centroids of .

FIG. 14A shows the device displaying content 6902 on the display 450 . In some embodiments, content 6902 is an image (eg, aerial or satellite imagery of the location) of the location at a first time (eg, at a particular date and time). In some other embodiments, the content 6902 is a map of a first type of location (eg, a street map).

The device also displays a focus selector (eg, cursor 6904 ) on display 450 . In some embodiments, cursor 6904 is a pointer (eg, a mouse pointer). In FIG. 14A , cursor 6904 is positioned above content 6902 at location 6904 - a. Cursor 6904 is associated with the portion of content 6902 over which cursor 6904 is located. For example, in Figure 14A, cursor 6904 at location 6904-a is associated with section 6902-1. As the cursor 6904 moves over the content 6902, the associated portion of the content 6902 also changes with the position of the cursor 6904 (e.g., the portion of the content 6902 associated with the focus selector corresponds to within a predefined radius or distance of the cursor 6904 or within the predefined area centered on the cursor 6904).

When the cursor 6904 of content has a finite size to which it is associated, the extent (e.g., size and bounds) of that portion is not displayed to the user, so until the device begins replacing the portion of the first content with the corresponding portion of the second content. section, the demarcation of the section from the rest of the content 6902 is optionally only apparent to the user, as described below. For example, in FIG. 14A , the boundaries of portion 6902 - 1 are not displayed to the user on display 450 .

In FIG. 14A, the device detects contact 6906 on touch-sensitive surface 451 when cursor 6904 is positioned over portion 6902-1. When cursor 6904 is positioned over portion 6902-1, the device detects that the intensity of contact 6906 increases from below a light press intensity threshold (eg, IT _L ) to above a light press intensity threshold (eg, IT _L ), as shown in FIG. 14B - as shown in Figure 14C. In response to detecting an increase in intensity of contact 6906 (e.g., from an intensity below IT _L in FIG. 14B to an intensity above IT _L in FIG. 14C ), the device stops displaying portion 6902-1 and displays content 6908 Part 6908-1 of , as shown in Figure 14C. Section 6908-1 has the same size and location as section 6902-1. In FIG. 14C, the entirety of content 6908 is not displayed; only portion 6908-1 is displayed. In some embodiments, portion 6908-1 is displayed to give the visual appearance of being viewed through a virtual magnifying glass or viewport, as if the user were looking through a hole in content 6902 to view content 6908 located "below" content 6902.

In some embodiments where content 6902 is an image at a location at a first time, content 6908 is an image at the same location at a second time different from the first time (eg, a different time and date). In some embodiments where content 6902 is a map of a first type of location, content 6908 is a map of a second type (eg, a public transit map) different from the first type for the same location. Portions of content 6908 are related to corresponding portions of content 6902 . Accordingly, portion 6908-1 corresponds to portion 6902-1. For example, if content 6902 and 6908 are different types of maps for the same location, then portions 6902-1 and 6908-1 are portions of the corresponding map near the same street intersection. In some embodiments, content 6902 is a first image and content 6908 is a second image corresponding to the first image (e.g., an image of the same object or group of objects based on media capture settings such as exposure, white balance, focus, etc. , or different from the first image based on image capture conditions such as time of day, lighting, etc.). In some embodiments, content 6902 is a first document and content 6908 is an earlier version of the first document (eg, an earlier version of a word processing, spreadsheet, presentation, or PDF document). Although many examples have been provided, these examples are not limiting, and similar operations are optionally performed on either set of first content and second content, for which the second content is used while continuing to display other parts of the first content. It is advantageous for the content to replace a specific portion of the first content.

In some embodiments, in response to detecting that the intensity of contact 6906 falls below a light press intensity threshold (e.g., IT _L ), content 6908-1 is ceased to be displayed, and content 6902-1 is generally recreated as part of content 6902 display (eg, stop displaying the first portion 6908-1 of the second content if the contact 6906 falls back to an intensity below the IT _L shown in FIG. 14B ).

In FIG. 14C, portion 6908-1 has a first size that is the same as the size of portion 6902-1 in FIGS. 14A-14B. In some embodiments, the first size is based on the intensity of the contact 6906 (e.g., when the intensity of the contact 6906 increases above a predefined intensity threshold, the replacement of the first content 6902 with the second content 6908 is correspondingly increased the size of the region). In response to detecting an increase in the intensity of contact 6906, device increases the size of portion 6902-1 to a second size. If an increase in intensity is detected when portion 6908-1 is displayed, the size of portion 6908-1 is increased to a second size to match the increase in size of portion 6902-1.

For example, Figure 14D shows that the intensity of contact 6906 increases above that shown in Figure 14C. The size of portion 6902 - 1 and portion 6908 - 1 is increased in response to detecting an increase in intensity by an amount corresponding to the amount of increase in intensity of contact 6906 . The increased size of portion 6908-1 is shown on display 450, but the increased size of portion 6902-1 is displayed as the size of the hole in content 6902 in Figure 14D. Similarly, Figure 14E shows that the intensity of contact 6906 increases above that shown in Figure 14D. In response to detecting an increase in intensity, the size of portion 6902-1 and portion 6908-1 is further increased from the size shown in Figure 14D. Likewise, the increased size of portion 6908-1 is shown on display 450, but the increased size of portion 6902-1 is displayed as the size of the hole in content 6902 in Figure 14E. In some embodiments, portions 6902-1 and 6908-1 are reduced in size in response to a decrease in intensity of contact 6906 (e.g., device inversion performed in response to an increase in intensity as shown in FIGS. 14C-14E ). increase in size).

FIG. 14F shows content 6902 displayed on display 450 including portion 6902-1 and cursor 6904, as shown in FIG. 14A. The device detects contact 6910 on touch-sensitive surface 451 with an intensity below a light press intensity threshold (eg, IT _L ) and below a transition initiation intensity threshold (eg, IT ₁ ). In FIGS. 14A-14L , the transition onset intensity threshold (eg, IT ₁ ) is lower than the light press intensity threshold (eg, IT _L ).

The device detects that the intensity of the contact 6910 increases to a higher intensity that is still below the transition initiation intensity threshold (eg, IT ₁ ), as shown in Figure 14G. Based on a determination that the new intensity is below the transition initiation intensity threshold (eg, IT ₁ ), portion 6902-1 continues to be displayed without displaying portion 6908-1.

In FIG. 14H , the device detects a further increase in the intensity of contact 6910 to an intensity above the transition onset intensity threshold (eg, IT ₁ ) and below the light press intensity threshold (eg, IT _L ). Upon determining that the new intensity is above the transition onset intensity threshold (and below the light press intensity threshold IT _L ), portion 6908-1 is displayed, and a reduced opacity (e.g., more visually transparent) version of portion 6902-1 Shown as overlaid on top of Section 6908-1. Thus, from a user's perspective, both portion 6908-1 and portion 6902-1 are viewable, with portion 6908-1 being seen through the more transparent portion 6902-1.

In some embodiments, the opacity of the reduced-opacity portion 6902-1 is based on the intensity of the contact 6910 between a transition onset intensity threshold (eg, IT ₁ ) and a light press intensity threshold (eg, IT _L ). . The opacity is decreased in response to the intensity of the contact 6910 increasing, and the opacity is increased in response to the intensity of the contact 6910 decreasing. Accordingly, portion 6908-1 optionally has the appearance of being gradually revealed on display 450 and gradually replacing portion 6902-1.

In FIG. 14I , the device detects that the intensity of contact 6910 has increased above a light press intensity threshold (eg, IT _L ). In response to detecting that the intensity of contact 6910 has increased above a light press intensity threshold (eg, IT _L ), the device stops displaying portion 6902-1 (with reduced opacity or otherwise) and displays content portion 6908-1. While the preceding examples of phasing out display of the first portion of the first content 6902 have been described with reference to the transition initiation threshold IT ₁ and the light press intensity threshold IT _L , in some embodiments IT _L is the first portion of the first content 6902 beginning The intensity threshold at which to fade away to reveal the first portion of the second content 6908, and the deep press intensity threshold IT _D is the intensity threshold at which the first portion of the first content fades away completely to reveal the first portion of the second content 6908.

Figure 14J shows cursor 6904 at location 6904-1 over portion 6908-1, and contact 6910 at location 6910-a. As shown in FIGS. 14J-14L , the device detects movement 6912 of contact 6910 on touch-sensitive surface 451 from location 6910-a toward location 6910-b (FIGS. 14K-14L ). In response to detecting movement of contact 6926, cursor 6904 moves from location 6904-a (FIG. 14J) to location 6904-b (FIGS. 14K-14L) over portion 6902-2 (shown in FIG. 14K) of content 6902. . The device stops displaying portion 6902-2 and displays portion 6908-2 corresponding to portion 6902-2, as shown in Figure 14L.

In FIGS. 14J-14L , the cursor 6904 moves in response to the movement 6912 of the contact 6910, a portion of the content 6908 is still displayed and the displayed portion of the content 6908 changes as the cursor 6904 moves over the new portion of the content 6902; the content 6908 The displayed portion of follows the cursor 6904. For example, if a portion of content 6908 is displayed as if viewed through a virtual magnifying glass, viewport, or hole in content 6902, the virtual magnifying glass, viewport, or hole in content 6902 is moved along with cursor 6904 and through the virtual magnifying glass or viewport The portion of the content viewed 6908 has changed. In FIG. 14K , the displayed portion of content 6908 is not shown to facilitate understanding of the movement of cursor 6904 over different portions of content 6902 . Additionally, as shown in Figure 14K, portions 6902-1 and 6902-2 optionally at least partially overlap.

15A-15C are flowcharts illustrating a method 7000 of displaying content layers according to some embodiments. Method 7000 is performed at an electronic device having a display and a touch-sensitive surface (eg, device 300, FIG. 3, or portable multifunction device 100, FIG. 1A). In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 7000 are optionally combined, and/or the order of some operations is optionally changed.

As described below, method 7000 provides an intuitive way to display content layers. The method reduces the cognitive load on the user when displaying content layers, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling users to display content layers faster and more efficiently saves power and increases the time between battery charges.

The device displays (7002) the first content on the display, where portions of the first content are related to corresponding portions of the second content (initially) not displayed on the display (e.g., upon detecting an increase in contact intensity on a touch-sensitive surface The corresponding part of the second content was not shown before, as described below). For example, FIGS. 14A and 14F illustrate displaying content 6902 on display 450 , where portions of content 6902 relate to corresponding portions of content 6908 that were not initially displayed.

When the focus selector is positioned over the first portion of the first content, the device detects (7014) that the intensity of the contact onto the touch-sensitive surface increases above a corresponding intensity threshold (eg, IT _L ). For example, FIGS. 14A-14B show that when cursor 6904 is positioned over portion 6902-1 , the intensity of contact 6906 is detected to increase above a corresponding intensity threshold (eg, IT _L ). Figures 14G-14I show that the intensity of contact 6910 is detected to increase above a corresponding intensity threshold (eg, IT _L ) while cursor 6904 is positioned over portion 6902-1.

In response to detecting (7018) an increase in the intensity of the contact on the touch-sensitive surface above a corresponding intensity threshold (e.g., IT _L ), the device stops (7020) displaying the first portion of the first content, and displays (7022) the second portion of the content. A first portion of the content corresponding to the first portion of the first content. For example, in FIGS. 14A-14C , in response to detecting that the intensity of contact 6906 has increased above a corresponding intensity threshold (eg, IT _L ), the device stops displaying portion 6902-1 ( FIGS. 14A and 14B ), and displays Portion 6908-1 corresponds to portion 6902-1 (FIG. 14C). In FIGS. 14G-14I , in response to detecting that the intensity of contact 6910 has increased above a corresponding intensity threshold (e.g., IT _L ), the device stops displaying portion 6902-1 (FIG. 14G ) and displays portion 6908-1 (FIG. 14I).

In some embodiments, prior to displaying (7004) the first portion of the second content, the device detects (7006) that the contact intensity increases from a first intensity below a corresponding intensity threshold (e.g., IT _L ) to below a corresponding intensity Second strength of the threshold (eg IT _L ). In response to detecting (7008) that the intensity of the contact has increased to a second intensity below a corresponding intensity threshold (e.g., IT _L ), upon determining that the second intensity is below a transition initiation intensity threshold (e.g., IT ₁ ), the device continues (7010) displaying the first portion of the first content without displaying the first portion of the second content; and upon determining that the contact intensity is above a transition initiation intensity threshold (e.g., IT ₁ ), the device displays (7012) an overlay on the second content A reduced-opacity version of the first portion of the first content above the first portion. In some embodiments, the opacity of the first portion of the first content decreases as the intensity increases to a corresponding threshold. As shown in FIGS. 14F-14G , for example, prior to displaying portion 6908-1 , the device detects that the intensity of contact 6910 increases to an intensity below a corresponding intensity threshold (eg, IT _L ). Upon determining that the new intensity is below the transition initiation intensity threshold IT ₁ , as shown in FIG. 14G , the device continues to display portion 6902-1 without displaying portion 6908-1. Conversely, upon determining that the new intensity is above the transition initiation intensity threshold IT ₁ , as shown in FIG. 14H , the device displays a reduced opacity version of portion 6902-1 overlaid on portion 6908-1.

In some embodiments, the size (eg, area) of the first portion of the first content (and the corresponding first portion of the second content) is determined based on the contact intensity (7016). After displaying (7028) the first portion of the second content, the device detects (7030) an increase in the intensity of the contact, and in response to detecting an increase in the intensity of the contact, increases (7032) the first portion of the second content (and The size of the corresponding first part of the first content). For example, in Figures 14C-14E, after displaying portion 6908-1, the device detects an increase in the intensity of contact 6906. In response to detecting an increase in intensity, the device increases the size of portion 6902-1 (in the background), and increases the size of portion 6908-1 to match the new size of portion 6902-1, as shown in Figure 14E.

In some embodiments, the first content includes (7024) an image of a location (e.g., a physical location) at a first time, the second content includes an image of the location at a second time different from the first time, and the second The first portion of one content and the first portion of the second content correspond to the same portion of the location. For example, content 6902 includes an image at a location at a first time, and content 6908 includes an image at a second time different from the first time. Section 6902-1 corresponds to section 6908-1; they show the same section at different times.

In some embodiments, the first content includes (7026) a first map of a location (e.g., a physical location), the second content includes a second map of the location, wherein the first map is different from the second map, and the first content The first part of and the first part of the second content correspond to the same part of the location. For example, the first map includes different map features than those included in the second map (e.g., a 1902 map of San Francisco instead of a 2012 map of San Francisco or a San Francisco map overlaid on top of a San Francisco public transit map). Francisco street map). For example, content 6902 includes a map of a first type of location (eg, a street map), and content 6908 includes a map of a second type of location different from the first type (eg, a public transit map). Section 6902-1 corresponds to section 6908-1; they show different map types for the same section of location.

In some embodiments, after displaying (7028) the first portion of the second content, the device detects (7034) movement of the contact. In response to detecting (7036) the movement of the contact, the device moves (7038) the focus selector over the second portion of the first content, stops (7040) displaying the second portion of the first content, and displays (7042) the second portion of the first content. A second portion of the content corresponds to a second portion of the first content (eg, a "revealed" area of the second content moves according to movement of the contact on the touch-sensitive surface). For example, in FIGS. 14J-14L , after displaying portion 6908 - 1 , the device detects movement 6912 of contact 6910 on touch-sensitive surface 451 . In response to detecting movement 6912 of contact 6910, the device moves cursor 6904 on display 450 and then stops displaying portion 6902-2 and displays portion 6908-2, which is first content 6902 and second content 6908 The portion of the corresponding to the new location of the cursor 6904 on the display 450.

In some embodiments, the second portion of the first content at least partially overlaps with the first portion of the first content (7044). In some embodiments, the second portion of the second content at least partially overlaps with the first portion of the second content (e.g., the "revealed" area of the second content changes smoothly according to the movement of the contact such that when in the "revealed" area When a row of pixels is revealed on the right edge of the , stop revealing the corresponding row of pixels on the left edge of the "revealed" area). For example, as shown in Figure 14K, portions 6902-1 and 6902-2 overlap.

It should be understood that the particular order in which the operations have been described in FIGS. 15A-15C is exemplary only and is not intended to indicate that the described order is the only order in which these operations may be performed. Various ways will occur to those of ordinary skill in the art to reorder the operations described herein. In addition, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in paragraph [0057]) also apply in a similar manner to those described above with respect to Figure 15A - The method 7000 depicted in Figure 15C. For example, the contact, intensity thresholds, and focus selectors described above with reference to method 7000 optionally have the contact, intensity thresholds described herein with reference to other methods described herein (e.g., those listed in paragraph [0057]). and one or more properties of the focus selector. For brevity, these details are not repeated here.

According to some embodiments, Figure 16 shows a functional block diagram of an electronic device 7100 configured in accordance with the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software that carry out the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in FIG. 16 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Accordingly, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 16 , the electronic device 7100 includes a display unit 7102 configured to display the first content on the display unit 7102, wherein the part of the first content corresponds to the part of the second content that is not displayed on the display unit 7102 partially related; a touch-sensitive surface unit 7104 configured to receive contact; one or more sensors 7106 configured to detect the intensity of contact with the touch-sensitive surface unit 7104; and a processing unit 7108 , the processing unit is coupled to the display unit 7102 , the touch-sensitive surface unit 7104 and the sensor 7106 . In some embodiments, the processing unit 7108 includes a detection unit 7110 , a stop unit 7112 , a display enable unit 7114 , an increase unit 7116 and a move unit 7118 .

The processing unit 7108 is configured to detect an increase in the intensity of the contact on the touch-sensitive surface unit 7104 above a corresponding intensity threshold (eg, IT _L ) when the focus selector is positioned over the first portion of the first content (eg, utilizing detection unit 7110); and in response to detecting that the intensity of the contact on touch-sensitive surface unit 7104 increases above a corresponding intensity threshold: stop displaying the first portion of the first content (e.g., using stop unit 7112), and enable Display of a first portion of the second content corresponding to the first portion of the first content (eg, using the display enabling unit 7114).

In some embodiments, the size of the first portion of the first content is determined based on the intensity of the contact; and the processing unit 7108 is configured to, after enabling display of the first portion of the second content: detect an increase in the intensity of the contact (e.g., Using detection unit 7110 ), and in response to detecting an increase in the intensity of the contact, increasing the size of the first portion of the second content (eg, using increasing unit 7116 ).

In some embodiments, the processing unit 7108 is configured, prior to enabling display of the first portion of the second content: to detect an increase in contact intensity from a first intensity below a corresponding intensity threshold to a second intensity below a corresponding intensity threshold; Intensity (e.g., using detection unit 7110); and in response to detecting that the intensity of the contact increases to a second intensity below a corresponding intensity threshold: continuing to enable the first content based on determining that the second intensity is lower than the transition initiation intensity Display of the first portion without enabling display of the _first portion of the second content (e.g., using display enabling unit 7114); Display of a reduced-opacity version of the first portion of the first content over the first portion of the second content (eg, using the display enable unit 7114).

In some embodiments, processing unit 7108 is configured to, after enabling display of the first portion of the second content: detect movement of the contact (e.g., using detection unit 7110); and in response to detecting movement of the contact: focus The selector is moved over the second portion of the first content (e.g., using the move element 7118); the display of the second portion of the first content is stopped (e.g., using the stop element 7112); and the second content is enabled with The display of the second portion corresponds to the second portion of the first content (eg, using the display enabling unit 7114).

In some embodiments, the second portion of the first content at least partially overlaps the first portion of the first content.

In some embodiments, the first content includes an image at a location at a first time, the second content includes an image at a second time different from the first time, and the first portion of the first content and the second content The first part of corresponds to the same part of the location.

In some embodiments, the first content includes a first map of the location, the second content includes a second map of the location, wherein the first map is different from the second map, and the first portion of the first content and the second portion of the second content A part corresponds to the same part of the location.

The operations in the above-mentioned information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to FIG. 1A and FIG. 3 ) or application-specific silicon.

The operations described above with reference to FIGS. 15A-15C are optionally implemented by components depicted in FIGS. 1A-1B or 16 . For example, detect operation 7014 , stop operation 7020 and display operation 7022 are optionally implemented by event sorter 170 , event recognizer 180 and event handler 190 . Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event, Such as selecting an object on the user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be apparent to those skilled in the art how other processes may be implemented based on the components shown in FIGS. 1A-1B .

Navigate between displayed user interfaces

Many electronic devices include user interfaces with different representations of the same object (eg, content such as an email or a photo). In some cases, different representations of the same object are organized into hierarchies (eg, a conversation including multiple messages or an album including multiple photos). Such groups require a convenient method for navigating between user interfaces corresponding to levels of the hierarchy. Some methods for navigating between user interfaces on devices with touch-sensitive surfaces typically require the user to position affordances (eg, keys or "buttons"). However, such methods are problematic because they are prone to inaccuracies (eg, accidental selection of an affordance, accidental selection of a different key when an affordance was intended to be selected). Such approaches also increase the cognitive load on the user by requiring an additional independent gesture. The embodiments described below provide a convenient and intuitive method for navigating between user interfaces corresponding to different representations of an object using similar gestures performed with contacts when the focus selector is over a representation of the object. In embodiments described below, an improved method for navigating between a first user interface comprising at least a first representation of an object and a second user interface is provided, the second user interface At least a second representation of the object is included. When the first user interface is displayed, the device replaces the first user interface with the second user interface when the device detects a gesture that satisfies certain navigation criteria for the object. When the second user interface is displayed, the device replaces the second user interface with the first user interface when the device detects a gesture that satisfies certain navigation criteria.

17A-17H illustrate example user interfaces for navigating between displayed user interfaces, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 18A-18C. 17A-17H include intensity graphs showing the current intensity of a contact on a touch-sensitive surface relative to a plurality of intensity thresholds including respective thresholds (eg, "IT _L "). In some embodiments, operations similar to those described below with reference to "IT _L " are performed with reference to a different intensity threshold (eg, "IT _D ").

In some embodiments, the device is an electronic device with a separate display (eg, display 450 ) and a separate touch-sensitive surface (eg, touch-sensitive surface 451 ). In some embodiments, the device is portable multifunction device 100, the display is touch-sensitive display system 112, and the touch-sensitive surface includes tactile output generator 167 on the display (FIG. 1A). For ease of explanation, the embodiments described with reference to FIGS. 17A-17H and 18A-18C will be discussed with reference to the touch screen 112, however, when the user interface shown in FIGS. 17A-17H is displayed on the display 450, in response to the Touch-sensitive surface 451 detects the contact described in Figures 17A-17H and optionally performs a similar operation on a device having display 450 and a separate touch-sensitive surface 451; in such embodiments, the focus selector optionally Ground is a cursor or pointer displayed at a location corresponding to (eg, at or near) the location of the contacts (eg, 8406, 8410, and 8412) shown in Figures 17A-17H.

17A shows an exemplary user interface (e.g., a first user interface) on an electronic device 300 with a touchscreen display 112, which is replaced with a second user interface in response to certain gestures described below, which The second user interface is different from the first user interface which is not currently shown in FIG. 17A. In some embodiments, the device displays representations of objects (eg, media objects such as songs, pictures, and/or electronic documents). In some embodiments, some or all of the objects are electronic messages (eg, email messages, SMS messages, instant messages, etc.) or groups of messages (eg, conversations). In some embodiments, the device displays a list having a plurality of entries, and the entries are representations of objects. The example shown in FIG. 17A shows a displayed list of representations of sessions (user interface objects 8404-1 through 8404-4 represent sessions 1 through 4, respectively). Each session contains one or more messages. In some cases, it may be desirable to change the display shown in FIG. 17A to a different display that includes a list of messages within a particular conversation (eg, navigating from an inbox view to a conversation view). Figures 17A-17H illustrate examples of improved user interfaces for navigating between, for example, these different views.

Figure 17B illustrates the detection of contact 8406 when the focus selector is positioned over user interface object 8404-1. In some embodiments, contact 8406 is part of a gesture, which optionally includes, for example, other movement and press inputs on the touch-sensitive surface.

In some embodiments, the device displays the second user interface when the navigation criteria are met. In some embodiments, the navigation criteria include that the gesture has an intensity threshold greater than a corresponding intensity threshold (e.g., greater than a nominal intensity measure indicating that the contact refers to touching the touch-sensitive surface, such as greater than the contact detection intensity threshold IT ₀ The maximum intensity of IT _L ), as shown by contact 8406 in Figure 17B. In some embodiments, the navigation criteria include detecting an increase in intensity from below a corresponding intensity threshold (eg, IT _L ) to above a corresponding intensity when the focus selector (eg, when a gesture) is continuously positioned over a representation of an object Threshold (e.g. "downstroke" detected). In some embodiments, the navigation criteria include a decrease in detected intensity from above a corresponding intensity threshold (e.g., IT _L ) to below a corresponding intensity threshold (e.g., detected "upstroke"). In some embodiments, the navigation criteria include detecting an increase in intensity from below a corresponding intensity threshold (e.g., IT _L ) to above a corresponding intensity threshold (e.g., IT _L ) when the focus selector is continuously positioned over a representation of the object. ), and subsequently detects a decrease in intensity from above a corresponding intensity threshold (eg, IT _L ) to below a corresponding intensity threshold (eg, both upstroke and downstroke are detected without leaving the representation).

Figures 17A-17H illustrate instances where detecting a contact with a maximum intensity above IT _L when the focus selector is over a particular representation of an object is sufficient to satisfy the navigation criteria. So Contact 8406 meets the criteria. Thus, contact 8406 in Figure 17B will initiate display of the second user interface. However, it will be apparent to those skilled in the art that other additional and/or alternative criteria are optionally used in place of or in addition to the criteria described herein.

In some embodiments, the device optionally displays an animated transition between the first user interface and the second user interface. Figure 17C shows an example of such a transition. In the example shown, a first set of messages (e.g., user interface objects 8404-1 and 8404-3) slides aside in one direction, and a second set of messages (e.g., user interface objects 8404-2 and 8404-4 ) slide aside in the opposite direction, revealing a second user interface (eg, a conversation view) "below" the first user interface.

Figure 17D illustrates an example of an animation that includes a visual cue indicating that a particular representation is expanding to become a corresponding document, message, or list of messages, according to an embodiment. Figure 17D shows an example of a selected conversation expanded to reveal a list of messages corresponding to the selected conversation. In some embodiments, an "expand message" animation, such as the animation shown in Figure 17D, follows a "slide message" animation (eg, such as the animation shown in Figure 17C). In some embodiments, the expanding message animation or sliding message animation occurs independently of each other. Furthermore, it is contemplated that any number of possible animations can optionally be utilized, and different animations for different types of objects and/or different situations are sometimes appropriate. An additional specific example of animation, a "trampoline" animation, is described with respect to method 8500 in FIGS. 18A-18C.

Figure 17E shows the result of navigating from the first user interface to the second user interface in Figure 17B. Specifically, Figure 17E shows that the user has now navigated to the conversation view. Additionally, Figure 17E shows a contact 8410 that is included in the gesture and meets the navigation criteria.

In some embodiments, since the conversation view is not an instance of the user interface on either extreme of the user interface hierarchy (e.g., the user can navigate up the hierarchy to return to the inbox view or to Navigate down to view individual messages), so the device is configured to respond independently to the up and down navigation criteria. For example, in some embodiments, up navigation criteria include a gesture with a deep press (e.g., a press input with an intensity above a deep press intensity threshold IT _D ) and down navigation criteria include a gesture with a key between IT _L and IT _D . Gestures of maximum intensity. In some embodiments, navigation down criteria includes a gesture with a deep press (e.g., a press input with an intensity higher than the deep press intensity threshold IT _D ) and navigation up criteria includes a gesture with a key between IT _L and IT _D . Gestures of maximum intensity. In some embodiments, other gestures, movements, gestures with multiple fingers, or a combination of light and deep press inputs are used alone and/or in combination to differentiate up and down navigation inputs.

For purposes of providing an example, assume that the gesture comprising contact 8410 in Figure 17E is a down navigation input. In some embodiments, the same or a different animation is displayed than that displayed in a previously described transition (eg, transition from inbox view to conversation view with reference to FIGS. 17B-17E ).

FIG. 17F continues the example by showing that contact 8410 in FIG. 17E (due to satisfying the navigation criteria and/or up navigation criteria) has caused the device to respond by displaying a third user interface (ie, a message view). FIG. 17F includes contacts 8412 . In this example, the gesture including contact 8412 satisfies the Up Navigation Criteria by at least having a maximum intensity above IT _L.

Figure 17G shows an example of some embodiments where the device displays a first set of messages "sliding in" from a first direction and a second set of messages "sliding in" from a second direction (e.g., the opposite direction), thereby "overlaying upwards". ” previously displayed message and return to the animation of the second user interface (or in some cases, the first user interface).

Figure 17H shows the result of navigating up from the message view shown in Figure 17F. In this instance, the session view is displayed again.

18A-18C are flowcharts illustrating a method 8500 of navigating between displayed user interfaces, according to some embodiments. Method 8500 is performed at an electronic device having a display and a touch-sensitive surface (eg, device 300, FIG. 3, or portable multifunction device 100, FIG. 1A). In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 8500 are optionally combined, and/or the order of some operations is optionally changed.

As described below, method 8500 provides an intuitive way to navigate between displayed user interfaces. The method reduces the cognitive load on the user when navigating between displayed user interfaces, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to navigate between displayed user interfaces more quickly and efficiently saves power and increases the time between battery charges.

The device displays (8502) a first user interface (eg, an inbox view, FIG. 17A ) on the display. When the focus selector is positioned over a first representation of an object (e.g., user interface object 8404-1, FIG. 17B ) in the first user interface, the device detects (8504) a first gesture on the touch-sensitive surface, the first gesture A first contact (eg, contact 8406, FIG. 17B ) that has a maximum intensity above a corresponding intensity threshold during the first gesture is included.

In some embodiments, the respective intensity threshold (e.g., IT _L ) corresponds (8506) to an intensity measurement that is greater than a nominal intensity measurement (e.g., IT ₀ ) indicating that a contact is a touch on the touch-sensitive surface . In some embodiments, where N is the lowest intensity quantification value (eg, corresponding to contact In the case of an intensity value present on the touch-sensitive surface), the corresponding intensity threshold is at least one level higher than N. For example, if there are 4 intensity quantization values and 1 is the lowest level, then the corresponding intensity threshold is 2 or a level greater than 2. As another example, if there are 256 intensity quantization values and 1 is the lowest level, then the corresponding intensity threshold is 2 or a level greater than 2, such as 5, 10, or 15.

In response to detecting the first gesture, the device (8508) replaces the first user interface with a second user interface comprising a second representation of the object (eg, conversation view, Figure 17E, or message view, Figure 17F).

In some embodiments, the object is ( 8510 ) an electronic document (e.g., a word processing document, a spreadsheet document, a rendered document, or a PDF), the first representation is an icon corresponding to the electronic document, and the second representation is a view of the electronic document (eg, an application window for viewing and/or responding to the electronic document, a document editing user interface for editing the electronic document, or another interface for interacting with the electronic document).

In some embodiments, the object is (8512) an electronic message (e.g., email, text message, instant message, or SMS, MMS, or social networking message), and the first representation is a message list entry in an electronic message list (e.g., , a representation of an email in an inbox, such as user interface object 8404-1, FIG. 17A ), and a second representation is a view of an electronic message corresponding to a message list entry (eg, a message view, FIG. 17F ). While many of the embodiments described herein have been illustrated with the example of a session/message hierarchy, where a first representation of an object is a representation of a message within a session and a second representation of an object is a view of the full message, the text described herein The principles apply in a similar manner to items in other hierarchies. Specifically, an object can be another hierarchical item, such as a discussion thread (e.g., with a first representation of a top-level discussion and a second representation of a sub-discussion), an album (e.g., with a first representation of a song in an album view and the song's a second extended representation), or a news story (eg, having a first representation as a headline with an associated summary or image and a second representation with a full news story).

In some embodiments, the first user interface includes (8514) a list with a plurality of entries representing corresponding objects (e.g., a list of electronic messages as described with reference to operation 8512, or alternatively, a list of songs in an album, etc.) , wherein the first representation of the object is one of the items in the list, and replacing the first user interface with the second user interface includes sliding the first set of one or more of the items in a first direction away from the object and sliding a second set of one or more of the items away from the first representation of the object in a second direction different from the first direction. In some embodiments, replacing the first user interface with the second user interface further includes displaying an animation of the first representation (list entry) expanding to become a corresponding document or message (eg, message list expansion, FIG. 17D ). In some embodiments, the first direction is to the right and the second direction is to the left, or vice versa. In some embodiments, the first direction is up and the second direction is down, or vice versa.

When the focus selector is positioned over a second representation of an object in a second user interface, the device detects (8516) a second gesture on the touch-sensitive surface, the second gesture comprising having an intensity higher than the corresponding intensity during the second gesture The second contact of maximum intensity for the threshold (eg, contact 8412, FIG. 17F ). In response to detecting the second gesture, the device (8518) replaces the second user interface with the first user interface (eg, displaying the session view, Figure 17G).

In some embodiments, the second gesture is ( 8520 ) a repetition of the first gesture (e.g., the second gesture includes the same basic movement and/or intensity-changing components as the first gesture, although the second gesture is performed at a later appears at the time).

In some embodiments, the first user interface includes (8522) a list having a plurality of entries representing corresponding objects, wherein the first representation of the object is one of the entries in the list, and the first user interface replaces the first The user interface includes sliding a first set of one or more of the items toward the first representation of the object in a first direction and sliding a first set of one or more of the items in a second direction different from the first direction. The two sets slide toward the first representation of the object (eg, slide the list entry in Figure 17G). In some embodiments, replacing the second user interface with the first user interface further includes displaying an animation of the document or message collapsing to become the corresponding first representation (list entry).

In some embodiments, prior to replacing the first user interface with the second user interface, the device detects (8524) that the intensity of the first contact has increased above a corresponding intensity threshold. In response to detecting the first contact intensity increase, the device displays (8526) a first animation of the first representation distorted according to the first contact intensity increase (e.g., stretching backwards like a trampoline with weights placed on it to display). In some embodiments, the first user interface is replaced with the second user interface in response to detecting a decrease in intensity and/or lift-off of the first contact, and this includes displaying an animation of a twisted inverse of the first representation ( For example, the first representation bounces back like a trampoline after lifting the weight off the trampoline). In some embodiments, prior to replacing the second user interface with the first user interface, the device detects (8528) that the intensity of the second contact increases above a corresponding intensity threshold. In response to detecting the second contact intensity increase, the device displays (8530) a second animation of the second representation distorted according to the second contact intensity increase (e.g., stretching backwards like a trampoline with weights placed on it to display). In some embodiments, the second user interface is replaced with the first user interface in response to detecting a decrease in intensity and/or lift-off of the second contact, and this includes displaying an animation of a twisted inverse of the second representation ( For example, the second representation bounces back like a trampoline after lifting the weight off the trampoline).

In some embodiments, the first animation includes (8532) adjusting the display of the first representation (e.g., changing the The center of a representation moves downward and shows distortion of the edges of the first representation to indicate that the first representation is stretching downward according to the first contact intensity). The second animation includes adjusting the display of the second representation (e.g., moving the center of the second representation down) by displaying a plurality of visual cues (e.g., visual cues associated with the same corresponding physical metaphor) according to the second contact intensity. and shows distortion of the edge of the second representation to indicate that the second representation is stretching downward according to the second contact intensity). In some embodiments, the first animation and the second animation include similar distortions of corresponding user interface elements displayed on the display. It is intended that many other transitions and/or animations fall within the scope of the present disclosure. For example, several alternative animations are discussed herein with reference to FIGS. 17A-17H .

It should be understood that the particular order in which operations have been described in Figures 18A-18C is exemplary only, and is not intended to indicate that the described order is the only order in which these operations may be performed. Various ways will occur to those of ordinary skill in the art to reorder the operations described herein. In addition, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in paragraph [0057]) also apply in a similar manner to those described above with respect to Fig. 18A-The method 8500 depicted in FIG. 18C. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, animations described above with reference to method 8500 optionally have other methods described herein with reference to them (e.g., listed in paragraph [0057] One or more properties of a contact, gesture, user interface object, intensity threshold, focus selector, animation described by those methods). For brevity, these details are not repeated here.

According to some embodiments, Figure 19 shows a functional block diagram of an electronic device 8600 configured in accordance with the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software that carry out the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in FIG. 19 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Accordingly, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 19 , the electronic device 8600 includes a display unit 8602 configured to display a first user interface comprising a first representation of an object and a second user interface comprising a second representation of an object; a touch-sensitive surface unit 8604 , the touch-sensitive surface unit configured to detect a first gesture on the touch-sensitive surface unit when the focus selector is positioned over a first representation of an object in a first user interface, the first gesture comprising having a high a first contact of maximum intensity at a corresponding intensity threshold, and detect a second gesture on the touch-sensitive surface unit when the focus selector is positioned over a second representation of an object in a second user interface, the second gesture comprising the A second contact having a maximum intensity above a corresponding intensity threshold during the second gesture; one or more sensor units 8606 configured to detect the intensity of the contact with the touch-sensitive surface unit 8604; and processing unit 8608 , the processing unit is coupled to the display unit 8602 , the touch-sensitive surface unit 8604 and the one or more sensor units 8606 . In some embodiments, the processing unit 8608 includes a replacement unit 8610 , an animation unit 8612 and a display enabling unit 8614 .

The processing unit 8608 is configured to: in response to detecting the first gesture, replace the first user interface with the second user interface (e.g., using replacement unit 8610); and in response to detecting the second gesture, replace the first user interface with the first user interface to replace the secondary user interface.

In some embodiments, the respective intensity threshold corresponds to an intensity measurement that is greater than a nominal intensity measurement indicating that the contact refers to touching the touch-sensitive surface unit 8604 .

In some embodiments, the second gesture is a repetition of the first gesture.

In some embodiments, the object is an electronic message; the first representation is a message list entry in an electronic message list; and the second representation is a view of the electronic message corresponding to the message list entry.

In some embodiments, the object is an electronic document; the first representation is an icon corresponding to the electronic document; and the second representation is a view of the electronic document.

In some embodiments, the first user interface includes a list having a plurality of entries representing corresponding objects, wherein the first representation of the object is one of the entries in the list; and the first user interface is replaced with a second user interface comprising: sliding a first set of one or more of the items away from the first representation of the object in a first direction; and sliding a second set of one or more of the items in a second direction different from the first direction; The collection slides away from the first representation of the object.

In some embodiments, the first user interface includes a list having a plurality of entries representing corresponding objects, wherein the first representation of the object is one of the entries in the list; and replacing the second user interface with the first user interface comprising: sliding a first set of one or more of the items toward a first representation of the object along a first direction; and sliding a second set of one or more of the items along a second direction different from the first direction. The collection slides towards the first representation of the object.

In some embodiments, the processing unit 8608 is further configured to: prior to replacing the first user interface with the second user interface: detect that the intensity of the first contact has increased above a corresponding intensity threshold; An increase in intensity of a contact, displaying a first animation of the first representation distorted according to the increase in intensity of the first contact; prior to replacing the second user interface with the first user interface: detecting an increase in intensity of the second contact to above the corresponding intensity threshold; and in response to detecting an increase in the intensity of the second contact, displaying a second animation of the second representation distorted according to the increase in intensity of the second contact.

In some embodiments, the first animation includes adjusting the display of the first representation by displaying a plurality of visual cues based on a first contact intensity; and the second animation includes adjusting the display of the first representation by displaying a plurality of visual cues based on a second contact intensity. Two representations of the display.

The operations in the above-mentioned information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to FIG. 1A and FIG. 3 ) or application-specific silicon.

The operations described above with reference to FIGS. 18A-18C are optionally implemented by components depicted in FIGS. 1A-1B or 19 . For example, detect operation 8504 , replace operation 8508 , and animate operation 8532 are optionally implemented by event classifier 170 , event recognizer 180 and event handler 190 . Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event, Such as selecting an object on the user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be apparent to those skilled in the art how other processes can be implemented based on the components shown in Figures 1A-1B.

It should be understood that the particular order in which operations have been described above is exemplary only, and is not intended to imply that the described order is the only order in which these operations may be performed. Various ways will occur to those of ordinary skill in the art to reorder the operations described herein. In addition, it should be noted that various processes described independently herein (eg, those listed in paragraph [0057]) may be combined with each other in different arrangements. For example, the contact, user interface object, haptic, intensity threshold, and/or focus described above with reference to any of the various processes described independently herein (e.g., those listed in paragraph [0057]). The selector optionally has a touch, gesture, user interface object, haptic, intensity as described herein with reference to one or more of the other methods described herein (e.g., those listed in paragraph [0057]). One or more of the threshold, and focus selector properties. For the sake of brevity, all possible combinations are not specifically enumerated here, but it should be understood that the claims described above may be combined in any manner not excluded by mutually exclusive claim features.

The foregoing description, for purposes of explanation, has been described with reference to specific embodiments. However, the above exemplary discussions are not intended to be exhaustive or to limit the various described embodiments to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiment was chosen and described in order to best explain the principles of the various described embodiments and their practical application, to thereby enable others skilled in the art to best utilize the various embodiments with various modifications as are suited to the particular use contemplated. kind of said embodiment.

Claims (9)

1. a kind of method for showing content, including：

At the electronic equipment with touch-sensitive display, wherein the electronic equipment includes for detecting and the touch-sensitive display Contact intensity one or more sensors：

First content is shown on the touch-sensitive display；

It is detected when at the first position having on the associated touch-sensitive display in the region on boundary with the first content When contact, the intensity for detecting the contact on the touch-sensitive display increases to above respective strengths threshold value；

In response to detecting that the intensity of the contact on the touch-sensitive display increases to above the respective strengths threshold value, generation For the part of the first content once shown in the region for having boundary, shown in the region for having boundary logical Cross the visual appearance that virtual magnifying glass is checked；

It detects the contact and is moved to the second position on the touch-sensitive display on the touch-sensitive display：

It is mobile according to the movement of the contact in response to detecting movement of the contact on the touch-sensitive display It is described to have the region on boundary and as the contact is moved and changes the institute shown in the region for having boundary State content so that the content in the region for having boundary continues to be given by what the virtual magnifying glass was checked The visual appearance；

The reduction for detecting the intensity of the contact is lifted away from without detecting the contact from the touch-sensitive display；And

Reduction in response to the intensity for detecting the contact is shown in institute again before the contact is moved to the position State the part of the first content once shown at the region on boundary.

2. according to the method described in claim 1, wherein in response to detect the intensity of the contact be reduced to correspond to and Less than the lag intensity threshold of the respective strengths threshold value, the step of showing the part of the first content again, is held Row.

3. according to the method described in claim 1, wherein：

The size for having the region on boundary is determined based on the intensity of the contact；And

The method includes after display is given by the content for the visual appearance that virtual magnifying glass is checked：

Detect the increase of the intensity of the contact；And

Increase in response to the intensity for detecting the contact has the size in the region on boundary described in increase.

4. the method according to any one of claim 1 to 2, including, it is given by the virtual magnifying glass in display Before the content for the visual appearance checked：

The intensity for detecting the contact is increased to from the first intensity less than the respective strengths threshold value less than the respective strengths Second intensity of threshold value；And

In response to detecting that the intensity of the contact increases to second intensity less than the respective strengths threshold value：

According to determination second intensity less than transformation initial intensity threshold value, continue in the region for having boundary described in display The part of first content；And

According to the intensity of the determination contact be higher than the transformation initial intensity threshold value, with the contact intensity increase and by Gradually show the content for the visual appearance for being given by that virtual magnifying glass is checked.

5. method according to any one of claim 1 to 2, wherein described have the region on boundary in the first content It is border circular areas.

6. method according to any one of claim 1 to 2, wherein when being given by what virtual magnifying glass was checked The content of visual appearance has that when being shown in the region on boundary, the first content is in the region for having boundary described The display of part in addition is maintained.

7. method according to any one of claim 1 to 2, wherein the first content is the figure of object/object set Picture, and it is the object/object set to be given by the content for the visual appearance that virtual magnifying glass is checked Image.

8. a kind of computer readable storage medium storing one or more program, one or more of programs include referring to It enables, when by with touch display and for detecting and the one or more sensors of the intensity of the contact of the touch-sensitive display Electronic equipment when executing so that the electronic equipment perform claim requires the method described in any one of 1 to 7.

9. a kind of electronic equipment, including：

Touch-sensitive display；

For detecting and the one or more sensors of the intensity of the contact of the touch-sensitive display；And

The device of the method described in any one of 1 to 7 is required for perform claim.