WO2017092680A1

WO2017092680A1 - Electronic device and method for deleting object

Info

Publication number: WO2017092680A1
Application number: PCT/CN2016/108076
Authority: WO
Inventors: 梁德胜
Original assignee: 华为技术有限公司
Priority date: 2015-12-03
Filing date: 2016-11-30
Publication date: 2017-06-08
Also published as: CN106843708A

Abstract

An electronic device and method for deleting an object, relating to the field of data processing. The method comprises: displaying at least one object interface element on a display screen, the at least one object interface element being associated with at least one object; detecting a gesture for the at least one object interface element on a touch-sensitive surface, the gesture comprising gesture speed information and gesture direction information; and when the gesture speed and the gesture direction satisfy pre-determined conditions, deleting the at least one object. The solution enables the interaction between an electronic device and a user to be more fluent, and improves the efficiency of processing transactions by an electronic device.

Description

Electronic device and method for deleting an object

The present application claims priority to Chinese Patent Application No. 201510883748.5, entitled "Electronic Apparatus and Method for Deleting Objects", filed on Dec. 3, 2015, the entire contents of which is incorporated herein by reference. In the application.

Technical field

This document relates to electronic devices having touch-sensitive surfaces, including but not limited to electronic devices and methods having touch-sensitive surfaces for mobile application interface elements.

Background technique

In recent years, the use of portable electronic devices with touch-sensitive surfaces has increased dramatically. Such portable electronic devices have greatly increased the number of applications or "apps". For example, image and video camera applications provide users with content generation opportunities, such as taking photos or recording videos. The Notes application allows users to read or write notes. The application corresponds to an application interface element on the graphical user interface of the portable electronic device. Such application interface elements are sometimes referred to as: app icons, app shortcuts, app buttons, app widgets, and the like. As shown in FIG. 1 , in the prior art, the method for deleting an application or a file in an electronic device is: first, the user presses an icon of an application or a file to be deleted, and the electronic device displays a trash can icon, the user's finger. Continue dragging the icon until the trash can icon is overwritten, then release your finger, and the electronic device pops up a dialog box prompting the user to delete the application or file and manually confirm it by the user. It can be seen that the above method of deleting an application is very complicated and time consuming, which seriously reduces the intelligent interaction ability between the electronic device and the user.

Summary of the invention

Therefore, there is a need for electronic devices with faster, more efficient methods and interfaces to interact with users and improve the transaction capabilities of electronic devices. Such methods and interfaces can complement or replace traditional methods of managing application interface elements. Such methods and interfaces can respond to user's individual needs more quickly and intelligently, helping users to achieve substantially the same management application interface elements in less time, and generate a more efficient human-machine interface. For battery powered devices, such methods and interfaces can save power and increase the time between battery charges.

Some embodiments herein provide the methods and user interfaces described above through the disclosed apparatus. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (eg, a laptop, tablet, or handheld device, or a wearable device). In some embodiments, the device has a trackpad. In some embodiments, the device has a touch sensitive display (also referred to as a "touch screen", a "touch screen display" or a "display with a touch-sensitive surface"). In some embodiments, a device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in memory for performing a plurality of functions. In some embodiments, the user interacts with the GUI primarily through finger contact and/or gestures on the touch-sensitive surface. In some embodiments, these functions may include image editing, drawing, rendering, word processing, web page creation, disk editing, spreadsheet creation, playing games, making calls, video conferencing, emailing, instant messaging, exercise support. , digital photography, digital video recording, web browsing, digital music playback, and/or digital video playback. Executable instructions for performing these functions can be included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.

In a first aspect, an embodiment of the present invention provides a portable electronic device. The device includes a display, wherein the display includes a touch-sensitive surface and a display screen; one or more processors; a memory; a plurality of applications; and one or more programs. The one or more programs are stored in memory and configured to be executed by one or more processors. The one or more programs include instructions. The instructions are for displaying at least one object interface element on the display screen, the at least one object interface element associating at least one object; detecting a gesture for the at least one object interface element at the touch-sensitive surface, the gesture The gesture speed and the gesture direction are included; when the gesture speed and the gesture direction satisfy a predetermined condition, the at least one object is deleted. This can respond to the user's individual needs more quickly and intelligently, reducing the manual operation of the user, greatly improving the efficiency of processing the electronic device, and saving power.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the object interface element specifically includes: an application interface element or a file interface element, the application interface element is associated with an application, and the file interface element is associated with File data.

With reference to the first implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the predetermined condition includes: the gesture speed is greater than or equal to a predetermined threshold, and the gesture direction information is To the right of the display.

With reference to the second implementation manner of the first aspect, in a third possible implementation manner of the first aspect, when the gesture speed information is less than the predetermined threshold, the at least one of the gestures is moved according to the detected gesture An object interface element.

In conjunction with the first aspect, in a fourth possible implementation of the first aspect, before the touch-sensitive surface detects a gesture for the at least one object interface element, the method includes: determining the at least one object Whether to delete: if the at least one object is erasable, detecting a gesture for the at least one object interface element on the touch-sensitive surface; prompting the user if the at least one object is not undeletable.

With reference to the first aspect, or the fourth implementation manner of the first aspect, in the fifth possible implementation manner of the first aspect, the at least one object interface element is specifically a first application interface element and a second application interface element, The first application interface element is associated with a first application, the second application interface element is associated with a second application; wherein the gesture for the at least one object interface element is detected at the touch-sensitive surface Deleting the at least one object when the gesture speed and the gesture direction satisfy a predetermined condition, specifically: detecting a gesture for the first application interface element and the second application interface element on the touch-sensitive surface When the gesture speed and the gesture direction satisfy a predetermined condition, the first application and the second application are uninstalled.

With reference to the first aspect, or the fourth implementation manner of the first aspect, in the sixth possible implementation manner of the first aspect, the at least one object interface element is specifically a first file interface element and a second file interface element, The first file interface element is associated with first file data, and the second file interface element is associated with second file data; wherein the gesture for the at least one object interface element is detected on the touch-sensitive surface Deleting the at least one object when the gesture speed and the gesture direction satisfy a predetermined condition, specifically: detecting a gesture for the first file interface element and the second file interface element on the touch-sensitive surface And erasing the first file data and the second file data when the gesture speed and the gesture direction satisfy a predetermined condition.

With reference to the first aspect, or the fourth implementation manner of the first aspect, in the seventh possible implementation manner of the first aspect, the at least one object interface element is specifically a third file interface element and a fourth application interface element, The third file interface element is associated with third file data, the fourth application interface element is associated with a fourth application; wherein the gesture for the at least one object interface element is detected on the touch-sensitive surface, when Deleting the at least one object when the gesture speed and the gesture direction satisfy a predetermined condition, specifically: detecting a gesture for the third file interface element and the fourth application interface element on the touch-sensitive surface When the gesture speed and gesture direction are satisfied When the condition is predetermined, the third file data is erased and the fourth application is unloaded.

In a second aspect, the present embodiment provides a method of deleting an object for a portable electronic device including a display and a plurality of applications, wherein the display includes a touch-sensitive surface and a display screen, the method comprising: The display screen displays at least one object interface element associated with the at least one object; a gesture for the at least one object interface element is detected at the touch-sensitive surface, the gesture including gesture speed information and gesture direction Information; deleting the at least one object when the gesture speed and the gesture direction satisfy a predetermined condition.

With reference to the second aspect, in a first possible embodiment of the second aspect, the object interface element specifically includes: an application interface element or a file interface element, the application interface element is associated with an application, and the file interface element is associated with File data.

With reference to the first embodiment of the second aspect, in a second possible embodiment of the second aspect, the predetermined condition specifically includes: the gesture speed is greater than or equal to a predetermined threshold, and the gesture direction information is To the right of the display.

With reference to the second embodiment of the second aspect, in a third possible embodiment of the second aspect, when the gesture speed information is less than the predetermined threshold, moving the at least according to the detected gesture An object interface element.

In conjunction with the second aspect or the second embodiment of the second aspect, in a fourth possible embodiment of the second aspect, before the touch sensitive surface detects a gesture for the at least one object interface element, The method includes: determining whether the at least one object is removable: if the at least one object is deletable, detecting a gesture for the at least one object interface element at the touch-sensitive surface; if the at least one object If it is not removable, the user is prompted.

With reference to the second aspect or the second embodiment of the second aspect, in a fifth possible embodiment of the second aspect, the at least one object interface element is specifically a first application interface element and a second application interface element, The first application interface element is associated with a first application, the second application interface element is associated with a second application; wherein the gesture for the at least one object interface element is detected at the touch-sensitive surface Deleting the at least one object when the gesture speed and the gesture direction satisfy a predetermined condition, specifically: detecting a gesture for the first application interface element and the second application interface element on the touch-sensitive surface When the gesture speed and the gesture direction satisfy a predetermined condition, the first application and the second application are uninstalled.

With reference to the second aspect or the second embodiment of the second aspect, in a sixth possible embodiment of the second aspect, the at least one object interface element is specifically a first file interface element and a second file interface element, The first file interface element is associated with first file data, and the second file interface element is associated with second file data; wherein the gesture for the at least one object interface element is detected on the touch-sensitive surface The gesture speed and gesture direction are satisfied Deleting the at least one object when a condition is predetermined, specifically: detecting a gesture for the first file interface element and the second file interface element on the touch-sensitive surface; when the gesture speed and gesture When the direction satisfies the predetermined condition, the first file data and the second file data are erased.

With reference to the second aspect or the second embodiment of the second aspect, in a seventh possible embodiment of the second aspect, the at least one object interface element is specifically a third file interface element and a fourth application interface element, The third file interface element is associated with third file data, the fourth application interface element is associated with a fourth application; wherein the gesture for the at least one object interface element is detected on the touch-sensitive surface, when Deleting the at least one object when the gesture speed and the gesture direction satisfy a predetermined condition, specifically: detecting a gesture for the third file interface element and the fourth application interface element on the touch-sensitive surface And erasing the third file data and unloading the fourth application when the gesture speed and the gesture direction satisfy a predetermined condition.

In a third aspect, an embodiment of the present invention provides an electronic device. The electronic device specifically includes: a touch-sensitive display unit, configured to detect a gesture of a user for an object interface element, the gesture includes a gesture speed and a gesture direction, the object interface element includes an application interface element and a file interface element; and a processing unit, And a gesture for acquiring the touch-sensitive display unit, and determining whether the gesture satisfies a predetermined condition: if the processing unit determines that the gesture satisfies a predetermined condition, deleting an object associated with the object interface element.

With reference to the third aspect, in a first possible embodiment of the third aspect, the predetermined condition specifically includes: the gesture speed is greater than or equal to a predetermined threshold, and the gesture direction information is to the display screen Right.

In conjunction with the first embodiment of the third aspect, in a second possible embodiment of the third aspect, before the touch sensitive display unit detects a gesture for the object interface element, the processing unit is further configured to: Determining whether the object is erasable: if the object is removable, the touch-sensitive display unit detects a gesture for the object interface element; if the object is non-deletable, prompts the user.

Based on the above technical solution, the electronic device can provide a more friendly method and user interface for the user, and implement the function of uninstalling a specific application or erasing a specific file. At the same time, this also helps users use less time to achieve the same effect of managing application interface elements and generate a more efficient human-machine interface. For battery powered devices, such methods and interfaces can save power and increase the time between battery charges. For battery powered devices, such methods and interfaces can save power and increase the time between battery charges.

DRAWINGS

In order to better understand the foregoing embodiments of the present invention and additional embodiments of the present invention, the following drawings should be combined With reference to the following description of the embodiments, in the drawings, the

FIG. 1 is a graphical user interface showing how to delete an application in the prior art.

2A is a block diagram showing a portable electronic device with a touch-sensitive display, in accordance with some embodiments.

2B is a block diagram showing exemplary components for event processing in accordance with some embodiments.

FIG. 3 illustrates a portable electronic device with a touch screen in accordance with some embodiments.

4 is a block diagram of an exemplary electronic device having a display and a touch-sensitive surface, in accordance with some embodiments.

FIG. 5 illustrates an exemplary graphical user interface for an application menu on a portable electronic device in accordance with some embodiments.

6A-6C illustrate an exemplary graphical user interface for uninstalling application interface elements in accordance with some embodiments.

7A, 7B illustrate an exemplary graphical user interface for deleting multiple object interface elements, in accordance with some embodiments.

FIG. 8 illustrates a functional block diagram of an electronic device in accordance with some embodiments.

detailed description

The embodiments will now be referred to in detail above, examples of which are illustrated in the accompanying drawings. Numerous specific details are set forth in the following detailed description in the claims. However, it will be apparent to those skilled in the art that the invention may be practiced without the specific details. In other instances, well-known methods, procedures, components, circuits, and networks are not described in detail so as not to unnecessarily obscure the aspects of the embodiments.

The terms used in the embodiments of the present invention are for the purpose of describing particular embodiments only and are not intended to limit the invention. The singular forms "a", "the" and "the"

It will also be understood that although the terms "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, the first application interface element can be named a second application interface element, and similarly, the second application interface element can be named the first application interface element without departing from the scope of the invention.

It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms "comprise" and "comprises", "the"," One or more other features, integers, steps, operations, elements, components, and/or Grouping.

As used herein, the term "if" may be interpreted to mean "when" or "after" or "in response to determining" or "in response to detecting", depending on the context. Similarly, depending on the context, the phrase "if determined..." or "if the stated condition or event is detected" can be interpreted to mean "when determining..." or "in response to determining... "or" when [the stated condition or event] is detected" or "in response to detecting the [condition or event stated]".

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the electronic device is a portable electronic device, such as a mobile phone, that also includes other functions, such as a personal digital assistant and/or music player functionality. Exemplary embodiments of an electronic device include, but are not limited to, piggybacking

Or a portable communication device of other operating systems. Other electronic devices can also be used, such as a laptop or tablet with a touch-sensitive surface (eg, a touch screen display and/or a touchpad). It should also be understood that in some embodiments, the electronic device is not a portable electronic device, but a desktop computer having a touch-sensitive surface (eg, a touch screen display and/or a touch pad).

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

Electronic devices typically support a variety of applications, such as one or more of the following: a drawing application, a rendering application, a word processing application, a web page creation application, a disk editing application, a spreadsheet application, a gaming application. , phone applications, video conferencing applications, email applications, instant messaging applications, workout support applications, photo management applications (ie image management applications), digital camera applications, digital video camera applications, networks Browse applications, digital music player applications, and/or digital video player applications.

Various applications that can be executed on an electronic device can use at least one shared 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 may be adjusted and/or changed from one application to the next and/or adjusted and/or varied within the respective application. In this way, the shared physical architecture of the electronic device, such as a touch-sensitive surface, can support various applications with a user interface that is intuitive to the user.

Attention is now directed to an embodiment of a portable communication device having a touch sensitive display. FIG. 2A is a block diagram showing a portable communication device 100 with a touch-sensitive display 112 in accordance with some embodiments. Touch sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and may also be referred to as or referred to as a touch sensitive display system, and may also be referred to as touch sensitive. Display system for touch-sensitive surfaces and displays. Device 100 can include memory 102 (which can include one or more computer readable storage media), memory controller 122, one or more central processing units (CPUs) 120, peripheral interface 118, RF circuitry 108, audio circuitry System 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Device 100 can include one or more optical sensors 164. These components can communicate over one or more communication buses or signal lines 103.

It should be understood that device 100 is but one example of a portable electronic device, and device 100 may have more or fewer components than shown, two or more components may be combined, or may have different components Configuration or layout. The various components shown in Figure 2A can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

Memory 102 can include high speed random access memory and can also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state memory devices. Access to memory 102 by other components of device 100, such as CPU 120 and peripheral interface 118, may be controlled by memory controller 122.

Peripheral device interface 118 can be used to couple the input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 execute or execute various software programs and/or sets of instructions stored in the memory 102 to perform various functions of the device 100 and process the data. In some embodiments, the one or more processors 120 include an image signal processor and a dual or multi-core processor.

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

RF (radio frequency) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals into/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, Decode chipset, Subscriber Identity Module (SIM) card, memory, and more. The RF circuitry 108 can communicate with the network and other devices via wireless communication, 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 (LANs), and/or Or Metropolitan Area Network (MAN). Wireless communication can use any of a variety of communication 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 Link Packet Access (HSUPA), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Blue Teeth, Wireless Fidelity (WI-Fi) (eg, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and/or IEEE 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (eg, Internet) Message Access Protocol (IMAP) and/or Post Office Protocol (POP), instant messaging (eg, Extensible Messaging Processing Site Protocol (XMPP), Session Initiation Protocol (SIMPLE) for instant messaging and field utilization extensions, instant messaging and Presence Service (IMPS), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed at the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. The speaker 111 converts the electrical signal into a human audible sound wave. The audio circuitry 110 also receives electrical signals converted by the microphone 113 based on the acoustic waves. Audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to peripheral interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripheral device interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (eg, 212 in FIG. 3). The headset jack provides an interface between the audio circuitry 110 and a removable audio input/output peripheral, such as an output only headset or with an output (eg, a monaural or binaural headset) and input (eg, Microphone) Both headsets.

I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripheral device interface 118. The I/O subsystem 106 can include a display controller 156 and one or more input controllers 160 for other input control devices. The one or more input controllers 160 receive electrical signals/transmit electrical signals from other input control devices 116 to other input control devices 116. The other input control device 116 may include physical buttons (eg, a push button, rocker button, etc.), a dial, a slide switch, a joystick, a click wheel, and the like. In some alternative embodiments, input controller 160 may be coupled to (or not coupled to) any 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. 3) may include up/down buttons for volume control of the speaker 111 and/or the microphone 113. The one or more buttons can include a push button (eg, 206 in Figure 3).

Touch sensitive display 112 provides an input interface and an output interface between the device and the user. Display controller 156 receives electrical signals from touch screen 112 and/or transmits electrical signals to touch screen 112. Touch screen 112 displays a visual output to the user. Visual output can include graphics, text, icons, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some visual output or all of the visual output may correspond to a user interface object.

Touch screen 112 has a touch-sensitive surface, sensor or group of sensors that accept input from a user based on tactile and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) Detecting contact on touch screen 112 (and any movement or interruption of the contact) and converting the detected contact to a user interface object (eg, one or more soft keys, icons, web pages, or Image) interaction. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger. The touch screen 112 referred to in the embodiment of the present invention specifically refers to a touch-sensitive display system having a touch-sensitive surface and a display screen, unless otherwise specified.

Touch screen 112 may use LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may utilize any of a variety of touch sensing techniques now known or later developed, as well as other proximity sensor arrays or other means for determining one or more points in contact with touch screen 112. Elements to detect contact and any movement or interruption thereof, including but not limited to capacitive, resistive, infrared, and surface acoustic wave techniques. In an exemplary embodiment, a projected mutual capacitance sensing technique is used.

Touch screen 112 can have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user can contact the touch screen 112 using any suitable object or add-on 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 accurate than the stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device translates the finger-based coarse input into an accurate pointer/cursor position or command to perform the action desired by the user.

In some embodiments, in addition to the touch screen, device 100 can include a touchpad (not shown) for activating or deactivating a particular function. In some embodiments, the touchpad is a touch sensitive area of the device that is different from the touchscreen in that it does not display a visual output. The touchpad can be a touch-sensitive surface that is separate from the touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

Apparatus 100 also includes a power system 162 for powering various components. The power system 162 can include a power management system, one or more power sources (eg, batteries, alternating current (AC)), a recharging system, power fault detection circuitry, power converters or inverters, power status indicators (eg, lighting) A diode (LED) and any other component associated with the generation, management, and distribution of power in a portable device.

Device 100 may also include one or more optical sensors 164. FIG. 2A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 can include a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light projected through one or more lenses from the environment 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 can capture still images or video. In some embodiments, one or more optical sensors are located The rear of device 100 is opposite the touch screen display 112 on the front of the device such that the touch screen display can be used as a viewfinder for still image and/or video image capture. In some embodiments, another or more optical sensors are located on the front of the device such that the user can view images of the user while viewing other video conferencing participants on the touch screen display for video conferencing.

Device 100 may also include one or more proximity sensors 166. FIG. 2A shows proximity sensor 166 coupled to peripheral interface 118. Alternatively, proximity sensor 166 can be coupled to input controller 160 in I/O subsystem 106. In some embodiments, when the electronic device is placed near the user's ear (eg, when the user is making a phone call), the proximity sensor turns off and disables the touch screen 112.

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

In some embodiments, the software components stored in the memory 102 include an operating system 126, a communication module (or set of instructions) 128, a contact/moving module (or set of instructions) 130, a graphics module (or set of instructions) 132, text input. A module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application (or set of instructions) 136. Moreover, in some embodiments, memory 102 stores device/global internal state 157, as shown in Figures 2A and 3. The device/global internal state 157 includes one or more of the following: an active application state indicating which applications (if any) are currently active; a display state indicating which applications, views, or other Information occupies various areas of the touch screen display 112; sensor status, including information obtained from various sensors of the device and input control device 116; and position information regarding the position and posture of the device.

Operating system 126 (eg, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, ANDROID, or an embedded operating system (such as Vx Works)) includes control and management of general system tasks (eg, memory management, storage device control, Various software components and/or drivers for power management, etc., and facilitate communication between various hardware and software components. Moreover, in some embodiments, memory 102 stores digital camera film 159 and digital image pipeline 161.

Communication module 128 facilitates communication 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 port 124. External port 124 (eg, Universal Serial Bus (USB), Firewire, etc.) is adapted to be directly coupled to other devices or indirectly through the network (for example, the Internet, wireless LAN, etc.) is coupled. In some embodiments, the external port is a multi-pin (eg, 30-pin) connector that is identical or similar to and/or compatible with a 30-pin connector used on an iPod (trademark of Apple Inc.) device.

The contact/movement module 130 can detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (eg, a touchpad or physical click wheel). The contact/movement module 130 includes a plurality of software components for performing various operations related to contact detection, such as determining if a contact has occurred (eg, detecting a finger press event), determining if there is a contact movement, and being touch sensitive throughout The movement is tracked on the surface (eg, detecting one or more finger drag events), and determining if the contact has terminated (eg, detecting a finger lift event or contact interruption). Contact/movement module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point may include determining the rate (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 caused by a series of contact data Said. These operations can be applied to a single point of contact (eg, one finger contact) or multiple points of simultaneous contact (eg, "multi-touch" / multiple finger contacts). In some embodiments, the contact/movement module 130 and the display controller 156 detect contact on the touchpad.

The contact/movement module 130 can detect a user's gesture input. Different gestures on the touch-sensitive surface have different contact patterns. Therefore, the gesture can be detected by detecting a specific contact pattern. For example, detecting a one-finger tap gesture includes detecting a finger press event, and then detecting a finger lift at a location (or substantially the same location) as the finger press event (eg, at the icon location) ( Lift off) event. As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift off) event.

Graphics module 132 includes a number of known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the strength of the displayed graphics. As used herein, the term "object" includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user interface objects including soft keys), digital images, video, animation, and the like.

In some embodiments, graphics module 132 stores data representation graphics to be used. Each graphic can be assigned a corresponding code. The graphics module 132 receives one or more codes specifying graphics to be displayed from an application or the like, and also receives coordinate data and other graphics attribute data together if necessary, and then generates screen image data for output to the display controller 156.

A text input module 134, which may be a component of the graphics module 132, is provided for use in a variety of applications (eg, contacts 137, email 140, instant message 141, browser 147, and any other application requiring text input) Enter the soft keyboard for the text.

The GPS module 135 determines the location of the device and provides this information for use in various applications (eg, for phone 138 for location based dialing, for camera 143 as picture/video metadata, and for providing) Applications for location-based services, such as the weather desktop applet, the local yellow pages desktop applet, and the map/navigation desktop applet.

Application 136 may include the following modules (or sets of instructions) or subgroups or supersets thereof:

Contact module 137 (sometimes referred to as an address book or contact list);

● telephone module 138;

● video conferencing module 139;

● email client module 140;

Instant messaging (IM) module 141;

● exercise support module 142;

a camera module 143 for still images and/or video images;

Image management module 144;

Browser module 147;

Calendar module 148;

a desktop applet module 149, which may include one or more of the following: weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm desktop applet 149-4 , the dictionary desktop applet 149-5, and other desktop applets obtained by the user, and the user-created desktop applet 149-6;

a desktop applet creator module 150 for generating a user-created desktop applet 149-6;

● search module 151;

Video and music player module 152, which may be comprised of a video player module and a music player module;

● note module 153;

Map module 154;

● online video module 155;

Sound/audio recorder module 163; and/or

Notification module 165.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA enabled applications, encryption, digital rights management, voice recognition, And sound reproduction.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contact module 137 can be used to manage contacts or contact lists (eg, stored in memory 102 or memory 370 for contact) The application internal state 192 of the person module 137) includes: adding a name to the address book; deleting the name from the address book; associating the phone number, email address, actual address, or other information with the name; associating the image with the name; Names are categorized and categorized; a phone number or email address is provided to initiate and/or facilitate communication over the phone 138, video conference 139, email 140, or IM 141;

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 can be used to input corresponding to the telephone The character sequence of the number, accessing one or more phone numbers in the address book 137, modifying the phone number that has been entered, dialing the corresponding phone number, making a call, and disconnecting or hanging up when the call is completed. As noted above, wireless communication can use any of a variety of communication standards, protocols, and technologies.

In combination with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contacts List 137, and telephony module 138, the video conferencing module 139 includes executable instructions for initiating, conducting, and ending a video conference 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, contact module 130, graphics module 132, and text input module 134, email client module 140 includes means for creating, transmitting, receiving, and managing in response to user instructions Executable instructions for email. 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 taken by the camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant messaging module 141 includes a sequence of characters for inputting an instant message, modifying previously entered characters, Transmitting corresponding instant messages (eg, using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and View executable instructions for the received instant message. In some embodiments, the transmitted and/or received instant messages may include graphics, photos, audio files, video files, and/or other attachments supported in MMS and/or Enhanced Messaging 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 transmitted using XMPP, SIMPLE, or IMPS).

In combination with the RF circuit system 108, the touch screen 112, the display controller 156, the contact module 130, the graphics module 132, Text input module 134, GPS module 135, map module 154, and music player module 146, exercise support module 142 includes executable instructions for creating an exercise (eg, having a time, distance, and/or calorie consumption target); Exercise sensor (sports equipment) communication; receiving exercise sensor data; calibrating sensors for monitoring exercise; selecting and playing music for exercise; and displaying, storing, and transmitting exercise data.

In conjunction with touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, digital image pipeline 161 (which converts raw data from the optical sensor into a final image or video), and images Management module 144, camera module 143 includes features for capturing still images or video (including video streams) and storing them in memory 102 (eg, in digital camera film 159), modifying the characteristics of still images or video, or from memory 102 (eg, from digital camera film 159) deletes executable instructions for still images or video.

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 means for arranging, modifying (eg, editing), or otherwise manipulating, adding An executable instruction to tag, delete, render (eg, in a digital slide or album), and to store still images and/or video images (including still images and/or video images stored in camera roll 159).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes means for browsing the Internet in accordance with user instructions (including searching, linking to, receiving, Executable instructions for displaying a web page or portion thereof, and attachments and other files linked to the web page.

In conjunction with RF circuitry 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 instructions for An executable instruction that creates, displays, modifies, and stores calendars and data associated with the calendar (eg, calendar entries, to-do list, etc.).

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, desktop applet module 149 is a mini-application that can be downloaded and used by a user. (eg, weather desktop applet 147-1, stock desktop applet 149-2, calculator desktop applet 149-3, alarm desktop applet 149-4, and dictionary desktop applet 149-5) or created by the user Micro-apps (for example, user-created desktop applets 149-6). In some embodiments, the desktop applet includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (Extensible Markup Language) file and a JavaScript file (eg, a Yahoo! desktop 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, desktop applet creator module 150 can be used by the user Create a desktop applet (for example, transfer the user-specified portion of a web page to the 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 means for searching in memory 102 for one or more search criteria (eg, user specified) in accordance with user instructions. One or more search terms) executable instructions for matching text, music, sound, images, video, and/or other files.

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 user download and playback Executable instructions for recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), and for displaying, rendering, or otherwise playing back video (eg, on touch screen 112 or Executable instructions on an external display connected via external port 124. In some embodiments, device 100 may include the functionality of an MP3 player.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, note pad module 153 includes executable instructions for creating and managing notes, to-do list, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 can be used to receive, according to user instructions, Display, modify, and store maps and data associated with the map (eg, driving directions; data for stores and other points of interest at or near specific locations; and other location-based data).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online Video module 155 includes allowing a user to access, browse, receive (eg, stream receive and/or download), play back (eg, on a touch screen or on an external display connected via external port 124), send with a particular online video. Linked emails, and instructions to otherwise manage online video of one or more file formats, such as H.264. In some embodiments, the instant message module 141 is used instead of the email client module 140 to send a link to a particular online video.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, and microphone 113, audio/audio recorder module 163 includes a user-allowed one or more file formats (such as An MP3 or AAC file) executable instructions that record audio (eg, sound), and executable instructions for rendering or otherwise playing back the recorded audio file.

Incorporating the touch screen 112, the display system controller 156, the contact module 130, and the graphic module 132, the notification module 165 includes executable instructions for displaying a notification or warning on touch screen 112, such as an incoming message or an incoming call, a calendar event reminder, an application event, and the like.

Each of the above modules and applications corresponds to a set of methods for performing one or more of the functions described above, as well as the methods described in this application (eg, computer implemented methods and other information processing methods described herein). Execute the instruction. These modules (ie, sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various sub-groups of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 can store a subset of the modules and data structures described above. Moreover, memory 102 can store additional modules and data structures not described above.

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

The predefined set of functions that are uniquely executable by the touch screen and/or trackpad include navigation between user interfaces. In some embodiments, device 100 is navigated from any user interface displayable on device 100 to a main menu, main menu, or root menu when the touchpad is touched by a user. In such an embodiment, the touchpad can be referred to as a "menu button." In some other embodiments, the menu button can be a physical push button or other physical input control device instead of a touchpad.

2B is a block diagram showing exemplary components for event processing in accordance with some embodiments. In some embodiments, memory 102 (in FIG. 2A) or memory 370 (in FIG. 4) includes event classifier 170 (eg, in operating system 126) and corresponding application 136-1 (eg, aforementioned application 137) - any application in -151, 155, 380-390).

The event classifier 170 receives the event information and determines the application 136-1 to which the event information is to be passed and the application view 191 of the application 136-1. The event classifier 170 includes an event monitor 171 and an event scheduler module 174. In some embodiments, application 136-1 includes an application internal state 192 that indicates a current application view that is displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, the device/global internal state 157 is used by the event classifier 170 to determine which application(s) are currently active, and the application internal state 192 is used by the event classifier 170 to determine that event information is to be passed. Go to the application view 191.

In some embodiments, the application internal state 192 includes additional information, such as one or more of: recovery information to be used when the application 136-1 resumes execution, indicating that it is being displayed by the application 136-1 of Information or user interface state information ready for information displayed by application 136-1, a status queue for enabling a user to return to a previous state or view of application 136-1, and previous actions taken by the user Repeat/deactivate the queue.

The event monitor 171 receives event information from the peripheral device interface 118. The event information includes information about sub-events (eg, user touches on the touch-sensitive display 112 as part of a multi-touch gesture). Peripheral device interface 118 transmits information it receives from I/O subsystem 106 or sensors (such as proximity sensor 166), accelerometer 168, and/or microphone 113 (via audio circuitry 110). The information that peripheral device 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 a request to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when there is a significant event (eg, an input that is above a predetermined noise threshold is received and/or an input that exceeds a predetermined duration is received).

In some embodiments, event classifier 170 also includes hit view determination module 172 and/or activity event recognizer determination module 173.

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

Another aspect of the user interface associated with the application is a 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 respective application) in which the touch is detected may correspond to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be referred to as a hit view, and the set of events identified as being correctly entered may be determined based at least in part on a hit view of the initial touch that begins with the touch based gesture.

The hit view determination module 172 receives information related to sub-events of the touch-based gesture. When the application has multiple views organized in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which the sub-event (ie, the first sub-event in the sequence of sub-events that formed the event or potential event) is initiated. Once the hit view is identified by the hit view determination module, the hit view typically receives all of the sub-events associated with the same touch or input source for which it was identified as the hit view.

The activity 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 activity event recognizer determination module 173 determines that only the hit view should be picked up. Receive a specific sequence of sub-events. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively involved views, and thus determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, the higher view in the hierarchy will remain as the active involved view.

Event scheduler module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In an embodiment that includes an activity event recognizer determination module 173, the event scheduler module 174 passes the event information to the event recognizer determined by the activity event recognizer determination module 173. In some embodiments, event scheduler module 174 stores event information in an event queue that is retrieved by respective event receiver module 182.

In some embodiments, operating system 126 includes an event classifier 170. Alternatively, application 136-1 includes event classifier 170. In another embodiment, event classifier 170 is a stand-alone module or is part of another module (such as contact/mobile module 130) stored in memory 102.

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes a touch event for processing a respective view occurring within a user interface of the application. Instructions. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a stand-alone module, such as a user interface toolkit (not shown) or from which the application 136-1 inherits methods and other features. Higher level objects. In some embodiments, the respective event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and/or event data 179 received from the event classifier 170. Event handler 190 can utilize or call 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 respective 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.

The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes at least one of the following subgroups: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Based on the sub-event, the event information also includes additional information, such as the location of the sub-event. When a sub-event involves movement of a touch, the event information may also include the rate and direction of the sub-event. In some embodiments The event includes the rotation of the device from one orientation to another (eg, from a portrait orientation to a landscape orientation, and vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as device gesture).

Event comparator 184 compares the event information to a predefined event or sub-event definition and determines an event or sub-event based on the comparison, or determines or updates the status of the event or sub-event. In some embodiments, event comparator 184 includes an event definition 186. Event definition 186 contains definitions of events (eg, predefined sub-event sequences), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event 187 include, for example, touch start, touch end, touch movement, touch cancellation, and multi-touch. In one example, the definition of event 1 (187-1) is a double click on the displayed object. For example, the double tap includes a first touch of a predetermined duration on the displayed object (touch start), a first lift of the predetermined duration (touch end), a second predetermined time duration on the displayed object The second touch (touch start) and the second lift of the predetermined duration (touch end). In another example, the definition of event 2 (187-2) is a drag on the displayed object. For example, the drag includes a predetermined duration of touch (or contact) on the displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes definitions of events for respective user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view in which three user interface objects are displayed on touch display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine among the three user interface objects. Which one is associated with the touch (sub-event). 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 an event handler associated with the object and sub-event that triggered the hit test.

In some embodiments, the definition of the respective event 187 also includes a delay action that delays the delivery of the event information until after it has been determined that the sequence of sub-events does or does not correspond to the event type of the event recognizer.

When the corresponding event recognizer 180 determines that the sub-event string does not match any of the events in the event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event end state, and then ignores the touch-based gesture. Subsequent sub-events. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, the respective event recognizer 180 includes metadata 183 having configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to the event identifiers involved in the activity. In some embodiments, the metadata 183 includes configurable attributes, flags indicating how the event recognizers can interact with each other And / or list. In some embodiments, metadata 183 includes configurable attributes, tags, and/or lists that indicate whether a sub-event is passed to a level in a view or a programmed hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the respective event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the respective event recognizer 180 passes event information associated with the event to the event handler 190. The activation event handler 190 is different from the send (and postponed) sub-event to the corresponding hit view. In some embodiments, event recognizer 180 throws a flag associated with the identified event, and event handler 190 associated with the flag receives the flag and performs a predefined process.

In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that pass event information about sub-events without activating an event handler. Instead, the sub-event delivery instruction passes the event information to an event handler associated with the sub-event string or to the active involved view. An event handler associated with a sub-event string or with an active involved view receives event information and performs a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, the data updater 176 updates the phone number used in the contact module 137 or stores the video file used in the video player module 145. In some embodiments, object updater 176 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user interface object or updates the location of the user interface object. The GUI updater 178 updates the GUI. For example, GUI updater 178 is ready to display information and send it to graphics module 132 for display on a touch sensitive display.

In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of 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 foregoing discussion of event handling of user touches on touch-sensitive displays is also applicable to other forms of user input that utilizes input devices to operate electronic device 100 (not all of which are initiated on a touch screen), such as coordination. Mouse movement and mouse button press (with or without single or multiple keyboard presses or hold), user movement on the touchpad, flick, drag, scroll, etc., stylus input, device movement, verbal command, detected Eye movements, biometric inputs, and/or any combination thereof, can be used as input corresponding to sub-events that define an event to be identified.

FIG. 3 illustrates a portable electronic device 100 having a touch screen 112 in accordance with some embodiments. The touch screen can display one or more graphics within a user interface (UI) 200. In this embodiment, as well as other In an embodiment, the user may make a graphic representation by, for example, one or more fingers 202 (not drawn to scale in the drawings) or one or more styluses 203 (not drawn to scale in the drawings). Gestures to select one or more of these graphics. In some embodiments, the selection of one or more graphics occurs when the user interrupts contact with the one or more graphics. In some embodiments, the gesture may include one or more taps, one or more swipes (from left to right, from right to left, up and/or down) and/or fingers that have been in contact with device 100 ( Toggle from right to left, left to right, up and/or down. In some embodiments, unintentional contact with the graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, the swipe gesture swiped over the application icon does not select the corresponding application.

Device 100 may also include one or more physical buttons, such as a "home screen" or menu button 204. As previously mentioned, menu button 204 can be used to navigate to any of a set of applications that can run on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key displayed in a GUI on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for device power on and lock device, volume adjustment button(s) 208, user identity module (SIM) card slot 210 The headset jack 212, and the docking/charging external port 124. The push button 206 can be used to power the device by pressing the button and holding the button in a depressed state for a predefined time interval; by pressing the button and before the predefined time interval Release the button to lock the device; and/or unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 may also accept voice input for activating or deactivating certain functions via microphone 113.

4 is a block diagram of an exemplary electronic device having a display and a touch-sensitive surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop, tablet, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (eg, home or industrial control) Device). Device 300 typically 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. In some embodiments, processing unit 310 includes an image signal processor and a dual or multi-core processor. Communication bus 320 may include circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input/output (I/O) interface 330 having a display 340, which is typically a touch screen display. The I/O interface 330 may also include a keyboard and/or mouse (or other pointing device) 350 and a trackpad 355. Device 300 also includes an optical sensor 164 and an optical sensor controller 158. The memory 370 includes a high speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state memory device; Loss of memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Optionally, memory 370 can include one or more storage devices remotely located from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to the programs, modules, and data structures stored in memory 102 of portable electronic device 100 (FIG. 2A), or a subset thereof. Moreover, memory 370 can store additional programs, modules, and data structures that are not present in memory 102 of portable electronic device 100. For example, memory 370 of device 300 can store drawing module 380, rendering module 382, word processing module 384, web page creation module 386, disk editing module 388, and/or spreadsheet module 390, while portable electronic device 100 (FIG. 2A) The memory 102 may not store these modules.

Each of the above identified components in Figure 4 can be stored in one or more of the aforementioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing the functions described above. The above identified modules or programs (ie, sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. . In some embodiments, memory 370 can store a subset of the modules and data structures described above. Moreover, memory 370 can store additional modules and data structures not described above.

Attention is now directed to an embodiment of a user interface ("UI") that can be implemented on portable electronic device 100.

FIG. 5 illustrates an exemplary user interface for an application menu on the portable electronic device 100 in accordance with some embodiments. A similar user interface can be implemented on device 300. In some embodiments, user interface 400 includes the following elements or subgroups or supersets thereof:

a signal strength indicator 402 for wireless communication, such as cell phone signals and Wi-Fi signals;

● time 404;

● Bluetooth indicator 405;

● battery status indicator 406;

● A tray 408 with common application icons, commonly used applications such as:

■ phone 138, which may include an indicator 414 of the number of missed calls or voicemail messages;

An email client 140, which may include an indicator 410 of the number of unread emails;

■ browser 147; and

■ Video and music player 152, also known as iPod (trademark of Apple Inc.) module 152;

■ Icons for other applications, other applications such as:

◆IM 141;

◆ Image Management 144;

◆ camera 143;

◆Weather 147-1;

◆Stock market 149-2;

◆ exercise support 142;

◆ calendar 148;

◆Alarm 149-4;

◆Map 154;

◆Note 153;

Setting 412, which provides access to settings of device 100 and its various applications 136;

An online video module 155, also known as the YouTube (trademark of Google Inc.) module 155.

Moreover, while the following examples are primarily given with reference to finger input (eg, single finger contact, single finger tap gesture, single finger swipe gesture), it should be understood that in some embodiments, these finger inputs are One or more of the ones are replaced by inputs from another input device (eg, stylus input).

User interface and associated processes

Embodiments of the user interface ("UI") and associated processes that can be implemented on an electronic device (such as device 300 or portable electronic device 100) having a display and a touch-sensitive surface are now turned to.

6A-6C illustrate an exemplary user interface for deleting an object (eg, an application) in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes and/or functions described below.

In the embodiment of the present invention, the object specifically refers to a target pointing object associated with the displayed icon. For example, icon A is an icon of application A displayed on touch screen 112 of the device, that is, an application interface element. Then, application A is the target pointing object associated with icon A. When a user makes contact with the icon A through the touch-sensitive surface, that is, the application A associated with the icon A is activated, the specific graphical user interface of the application A is displayed on the touch screen 112. On the other hand, the object can also be a file. For example, after the image management application 144 is activated, the graphical user interface of the application is displayed on the touch screen 112, and the image displayed as a thumbnail at this time can also be regarded as an icon, which can be referred to as a file interface element. The target point of the icon is the image file data associated with this icon (for example, an image in JPG or JEPG format). Therefore, when the user performs an operation on the icon, it is an operation performed on the associated image file data, such as modifying the naming of the icon. Activating the icon also activates its associated image file for display on touch screen 112.

In order to select an object, it can be achieved by selecting an object interface element (such as an icon) to which the object is associated. In an embodiment, the object interface element can be dragged or moved, and the object associated with it (such as an application, file, etc.) is opened when the finger is raised. The terms "select," "select," "move," "drag," "touch," "touch," and "fast move" are generally described herein with reference to a touch screen display. However, in alternative embodiments, the terms are also intended to include the required user actions with respect to other input devices. For example, in the case of a proximity screen, the user does not need to be in direct contact with the screen in order to select, move or drag object interface elements or other information. Therefore, the above terms are intended to include that the user only needs to be located near the device in order to perform the desired function. For example, when used in a scene adjacent to a screen device, the term "contact" does not imply a direct contact for activating an adjacent device, but a proximity or proximity contact.

FIG. 6A illustrates a graphical user interface (GUI) displayed on touch screen 112 of device 100.

A plurality of object interface elements (501-504) are displayed on the graphical user interface, wherein the

object interface elements

501, 502, 503 are application icons, that is, application interface elements, and each application icon is associated with an application. . Object interface element 504 bit file icon, ie file interface element, each file icon is associated with a file data. The embodiment of the present invention deletes the object associated with the object interface element by using a specific gesture on the object interface element, thereby greatly improving the intelligent interaction capability between the electronic device and the user, and improving the processing of the electronic device. The efficiency of the transaction.

Now, we will explain this embodiment in detail by taking an uninstall application as an example. As shown in FIG. 6A, the touch screen 112 can detect a first gesture 505 of the user for the application icon 503, which can be a gesture of selecting an application icon 503, which can be a selected application icon After 503, quickly move your finger and lift it up, and quickly leave the touch screen surface. The electronic device can now detect the gesture speed and gesture direction of the first gesture 505 through the touch screen 112.

The central processing unit 120 of the electronic device can determine the gesture speed of the first gesture 505 through the data about the first gesture received by the touch screen 112. Specifically, it is determined that it belongs to the prior art, and details are not described herein again. When the central processing unit 120 determines that the gesture speed meets the predetermined condition, the application associated with the application icon 503 is uninstalled. The user may pre-store a threshold of a gesture speed in the memory 102. When it is determined that the detected gesture speed is greater than or equal to the threshold, the central processing unit 120 may determine that the first gesture belongs to a gesture that moves rapidly on the touch screen, that is, The first gesture 505 can be used as an instruction to trigger an application uninstallation. After the central processing unit 120 compiles the first gesture into an unloading instruction, the application associated with the application icon 503 to which the first gesture 505 is applied is unloaded. It can be understood that before the associated application is uninstalled, it can be displayed on the touch screen 112 in the form of a dynamic GUI to indicate to the user that the application is about to be uninstalled. As shown in FIG. 6B, the icon 507 can be an animation. Display, indicating that the application tweet is about to be uninstalled. Of course, you can also use it In a user-perceivable manner, the user is indicated that the application is about to be uninstalled, and the embodiment is not limited herein.

Of course, before executing the uninstall command, the user can be prompted in a user-aware manner to indicate whether the application will be uninstalled or not. The uninstallation operation can be performed after receiving an instruction from the user to confirm the consent.

As shown in Figure 6C, the current graphical user interface can be re-arranged after the application is uninstalled.

In still other embodiments, the electronic device can erase the file associated with the file interface element based on the detected gesture. As shown in FIG. 6A, the touch screen 112 can detect a second gesture of the user for the file icon 504 (ie, the file interface element), which can be a gesture of selecting the file icon 504, which can be After selecting the file icon 504, quickly move the finger and lift it up, quickly leaving the touch screen surface. The electronic device can now detect the gesture speed of the second gesture through the touch screen 112.

The central processing unit 120 of the electronic device can determine the gesture speed of the second gesture through the data about the second gesture received by the touch screen 112. Specifically, it is determined that it belongs to the prior art, and details are not described herein again. When the central processing unit 120 determines that the gesture speed satisfies the predetermined condition, the file associated with the file icon 504 is erased. The user may pre-store a threshold of a gesture speed in the memory 102. When it is determined that the detected gesture speed is greater than or equal to the threshold, the central processing unit 120 may determine that the second gesture belongs to a gesture that moves quickly on the touch screen. That is, the second gesture can be used as an instruction to trigger file erasure. When the central processing unit 120 compiles the second gesture into an erase command, the file associated with the file icon 504 to which the second gesture is applied is erased. It will be appreciated that the associated file data may be displayed on the touch screen 112 in the form of a dynamic GUI to indicate to the user that the file is about to be erased before the associated file data is erased. It is of course possible to indicate to the user that the file is to be erased in a manner that is sensible to other users. This embodiment is not limited herein.

In still other embodiments, if the gesture speed information detected by the central processing unit 120 is less than the threshold, the object interface element may be moved according to the detected gesture (eg, the first gesture or the second gesture described above) (eg, The location of icon 503, icon 504).

In still other embodiments, the touch screen 112 can detect the gesture direction in addition to detecting the gesture speed, that is, detecting which direction the user's finger is moving toward the touch screen 112. Further, in the embodiment, a condition may be added: the central processing unit 120 selects an application selected for the first gesture when the gesture speed is greater than or equal to a predetermined threshold, and the gesture direction is to the right of the touch screen 112. Unload or erase the file selected by the second gesture. As shown in FIG. 6A, icon 506 represents the direction of gesture 505.

In still other embodiments, before the touch-sensitive surface of the touch screen 112 detects a gesture for the application icon 503 or the file icon 504, the central processing unit 120 may further determine whether the object corresponding to the icon is erasable: The object is erasable, then detecting an object interface element (ie, an icon) on the touch-sensitive surface The gesture of 503 or icon 504); if it is not erasable, the user is prompted.

In still other embodiments, the gestures described above may also operate for two or more object interface elements, ie, the gestures detected by touch screen 112 are selected for two or more icons. The following embodiment is illustrated with two object interface elements as an example.

For example, the object interface element selected by the above gesture (including the first gesture or the second gesture) may specifically be a first application interface element and a second application interface element, where the first application interface element is associated with the first application. a program, the second application interface element associated with the second application. As shown in FIG. 7A, the first application interface element (icon 502) is associated with an image management application, and the second application interface element (icon 503) is associated with a Twitter application. The touch screen 112 detects a gesture 605 that begins on the icon 503 and then passes the icon 502 along the gesture direction shown by the icon 606, and then the finger quickly lifts off the touch screen 112. We can assume that the gesture 605 is for the first application interface element (icon 502) and the second application interface element (icon 503). The central processing unit 120 of the electronic device receives the data of the gesture 605 through the touch screen 112, and the gesture speed of the gesture 605 can be determined. When the central processing unit 120 determines that the gesture speed meets a predetermined condition, for example, determining that the gesture speed is greater than or equal to a predetermined threshold, the image management application and the second application associated with the first application interface element (icon 502) The tweet application associated with the interface element (icon 503) is unloaded. It will be appreciated that the associated application may be displayed on the touch screen 112 in the form of a dynamic GUI to indicate to the user that the application is about to be uninstalled before the associated application is uninstalled. It is of course possible to indicate to the user that the application is about to be uninstalled in a manner that is sensible to other users. This embodiment is not limited herein.

In some other embodiments, the object interface element selected by the gesture (including the first gesture or the second gesture) may specifically be a first file interface element and a second file interface element. The first file interface element is associated with first file data, and the second file interface element is associated with second file data. As shown in FIG. 7B, the user activates the open gallery graphical user interface upon selection of the icon 502 in FIG. 6A. In the interface, the photo or video in the gallery is displayed in the form of a thumbnail icon. For example, the icon 601 is associated with the image file data of the name 4, the icon 602 is associated with the video file data of the name 5, and the icon 603. Associated with the image file data named 6. The specific format of the picture or video is not limited here.

The touch screen 112 detects a gesture 607 that begins on the icon 601 and then passes the icon 602 along the gesture direction shown by the icon 606, and then the finger quickly lifts off the touch screen 112. We can assume that the gesture 607 is for the first file interface element (icon 601) and the second file interface element (icon 602). The central processing unit 120 of the electronic device receives the data of the gesture 607 through the touch screen 112, and the gesture speed of the gesture 607 can be determined. When the central processing unit 120 determines that the gesture speed meets a predetermined condition, for example, it is determined that the gesture speed is large. At or equal to the predetermined threshold, the image file associated with the first file interface element (icon 601) and the video file associated with the second file interface element (icon 602) are erased. It will be appreciated that the associated file may be displayed on the touch screen 112 in the form of a dynamic GUI to indicate to the user that the image file and video file are about to be erased before the associated file is erased. It is of course possible to indicate to the user that the file is about to be erased in a manner that is sensible to other users. This embodiment is not limited herein.

In some other embodiments, the object interface element selected by the above gesture (including the first gesture or the second gesture) may specifically be a third file interface element and a fourth application interface element. The third file interface element corresponds to the third file data, and the fourth application interface element corresponds to the fourth application. The same as the above embodiment, after the touch sensitive surface of the touch screen 112 detects the gestures for the third file interface element and the fourth application interface element, the central processing unit 120 determines whether the gesture speed is satisfied. a predetermined condition, when the predetermined condition is satisfied, the third file data is erased and the fourth application is uninstalled.

In still other embodiments, the touch screen 112 can detect the gesture direction in addition to detecting the gesture speed, that is, detecting which direction the user's finger is moving toward the touch screen 112. Further, in the embodiment, a condition may be added: the central processing unit 120 selects an application selected for the first gesture when the gesture speed is greater than or equal to a predetermined threshold, and the gesture direction is to the right of the touch screen 112. Unload or erase the file selected by the second gesture. For example, icon 608 in Figure 7B is used to indicate the gesture direction of gesture 607.

In this article, unless otherwise specified, the user's gestures are flexible and can be click, double click, circle, draw line, single finger touch, or multi finger touch, and so on. One of ordinary skill in the art will appreciate that the selection of a particular gesture is flexible as long as substantially the same effect is achieved. In this document, unless otherwise specified, the position or area of the user's gesture acting on the touch-sensitive surface is flexible, and may be the area of an application interface element displayed on the display screen or a nearby area, and the display does not display the blank of the application interface element. Area, the display shows the area of a function setting, and so on. One of ordinary skill in the art will appreciate that the specific location or area of the gesture acting on the touch-sensitive surface can be flexibly set as long as substantially the same effect can be achieved.

In still other embodiments, a computer readable storage medium storing one or more programs, the instructions including instructions, when included in a portable electronic device including a display and a plurality of applications, can be provided The device, when executed, causes the portable electronic device to perform an event, wherein the display includes a touch-sensitive surface and a display screen. The above computer readable storage medium can be used to perform the events in the above embodiments.

In still other embodiments, a graphical user interface on an electronic device can be provided, the electronic device including a display, a memory, a plurality of applications, and one or more programs for executing in the memory One or more processors, wherein the display includes a touch-sensitive surface and a display screen, the graphical user community The facets include the graphical user interface introduced and displayed in the above embodiments.

In accordance with some embodiments, FIG. 8 illustrates a functional block diagram of an electronic device 700 configured in accordance with the principles of the present invention described above. Functional blocks of a device may be implemented by hardware, software, or a combination of hardware and software to perform the principles of the invention. Those skilled in the art will appreciate that the functional blocks described in FIG. 8 can be combined or separated into sub-blocks to implement the principles of the invention described above. Accordingly, the description herein may support any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 8, the electronic device 700 includes a touch-sensitive display unit 701 configured to display a screen interface and configured to receive gestures, and a processing unit 702 coupled to the touch Sensitive display unit 701. In an embodiment, the touch-sensitive display unit 701 receives a gesture of the user for the object interface element, and the gesture may include a gesture speed and a gesture direction; the processing unit 702 acquires a gesture of the touch-sensitive display unit 701, and determines whether the gesture speed is greater than or equal to The predetermined threshold, if the processing unit 702 determines that the gesture speed is greater than or equal to a predetermined threshold, the processing unit 702 deletes the object associated with the object interface element. The meanings of terms such as objects, object interface elements, and the like in this embodiment are referred to the above embodiments. The electronic device 700 can be used to implement the technical solutions in the above embodiments.

In some embodiments, the processing unit 702 may specifically include a touch screen receiving unit 7021, a motion interpretation unit 7022, an event distribution unit 7023, a home screen receiving unit 7024, an event determining unit 7025, an application unloading unit 7026, and a file erasing unit 7027. .

The functions of the electronic device 700 are described below, and those skilled in the art can understand the following functions and the electronic devices, systems, devices, methods, graphical user interfaces, information processing devices (eg, processor chips or processors) described herein. The various embodiments of the computer-readable storage medium are echoed, and the various combinations and/or combinations of the various aspects are combinations that can be directly and unambiguously contemplated by those of ordinary skill in the art after understanding this document.

The touch screen receiving unit 7021: the touch sensitive display receives a signal of the user gesture touch screen operation, and the operation may include pressing, moving, lifting, and the like.

The action interpretation unit 7022 is configured to interpret the original actions such as pressing, moving, lifting, etc. as events such as clicking, long pressing, fast moving, and the like;

The event distribution unit 7023: the event in the system action interpretation unit is delivered to the upper layer application (such as the home screen receiving unit 7024);

The main screen receiving unit 7024: the main screen receives the above event, and sends it to the following processing unit corresponding to the event, and executes a process corresponding to the event;

The event judging unit 7025: determining whether the current event satisfies a predetermined condition, for example, whether the gesture speed of the gesture is greater than or equal to a predetermined threshold, and starting the corresponding processing unit after the judgment is completed;

The application unloading unit 7026: according to the event determining unit 7025, determining that the gesture speed of the gesture is greater than or equal to a predetermined threshold, uninstalling the application clicked by the gesture;

The file erasing unit 7027: according to the event determining unit 7025, determining that the gesture speed of the gesture is greater than or equal to a predetermined threshold, erasing the file clicked by the gesture.

In the above embodiment, the file may specifically be a picture, a video in the image management application, or a contact in the contact application.

It will be appreciated that those of ordinary skill in the art will appreciate that the operations described above with reference to Figures 6A-6C, 7A-7B can be implemented by the components illustrated in Figures 2A-2B. For example, event monitor 171 in event sorter 170 detects contact on touch-sensitive display 112, and event scheduler module 174 passes 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. Event detector 180 activates event handler 190 associated with detecting the event or sub-event when a corresponding predefined event or sub-event is detected. Event handler 190 can utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses 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 illustrated in Figures 2A-2B.

For the purposes of explanation, the foregoing description has been described by reference to the specific embodiments. However, the above illustrative discussions are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. The embodiment was chosen and described in order to explain the embodiment of the invention and the embodiments of the invention example.

Claims

A portable electronic device comprising:

a display, wherein the display comprises a touch sensitive surface and a display screen;

One or more processors;

Memory

Multiple applications; and

One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for to:

Displaying at least one object interface element on the display screen, the at least one object interface element associating at least one object;

Detecting a gesture for the at least one object interface element at the touch-sensitive surface, the gesture including a gesture speed and a gesture direction;

The at least one object is deleted when the gesture speed and the gesture direction satisfy a predetermined condition.
The portable electronic device of claim 1, wherein the object interface element comprises: an application interface element or a file interface element, the application interface element associating an application, the file interface element associating file data.
The method of claim 2, wherein the predetermined condition specifically comprises: the gesture speed is greater than or equal to a predetermined threshold, and the gesture direction information is to a right side of the display screen.
The method of claim 3, wherein when the gesture speed information is less than the predetermined threshold, the at least one object interface element is moved according to the detected gesture.
The method of claim 1 wherein before the touch sensitive surface detects a gesture for the at least one object interface element, the method includes determining whether the at least one object is erasable: if The at least one object is erasable, the gesture for the at least one object interface element is detected at the touch-sensitive surface; and the user is prompted if the at least one object is non-deletable.
The method according to claim 1 or 5, wherein the at least one object interface element is specifically a first application interface element and a second application interface element, and the first application interface element is associated with the first application, The second application interface element is associated with the second application;

among them,

The detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, when the gesture speed and the gesture direction satisfy a predetermined condition, deleting the at least one object, specifically:

Gestures for the first application interface element and the second application interface element are detected at the touch sensitive surface;

When the gesture speed and the gesture direction satisfy a predetermined condition, the first application and the second application are uninstalled.
The method according to claim 1 or 5, wherein the at least one object interface element is specifically a first file interface element and a second file interface element, and the first file interface element is associated with the first file data. The second file interface element associates the second file data;

among them,

The detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, when the gesture speed and the gesture direction satisfy a predetermined condition, deleting the at least one object, specifically:

Gestures for the first file interface element and the second file interface element are detected on the touch sensitive surface;

The first file data and the second file data are erased when the gesture speed and the gesture direction satisfy a predetermined condition.
The method according to claim 1 or 5, wherein the at least one object interface element is specifically a third file interface element and a fourth application interface element, and the third file interface element is associated with the third file data. The fourth application interface element is associated with the fourth application;

among them,

The detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, when the gesture speed and the gesture direction satisfy a predetermined condition, deleting the at least one object, specifically:

Gestures for the third file interface element and the fourth application interface element are detected on the touch sensitive surface;

When the gesture speed and the gesture direction satisfy a predetermined condition, the third file data is erased and the fourth application is unloaded.
A method of deleting an object for a portable electronic device comprising a display and a plurality of applications, wherein the display comprises a touch-sensitive surface and a display screen, wherein the method comprises:

Displaying at least one object interface element on the display screen, the at least one object interface element associating at least one object;

Detecting a gesture for the at least one object interface element at the touch-sensitive surface, the gesture including gesture speed information and gesture direction information;

The at least one object is deleted when the gesture speed and the gesture direction satisfy a predetermined condition.
The method of claim 9, wherein the object interface element comprises: an application interface element or a file interface element, the application interface element associating an application, the file interface element associating file data.
The method of claim 10, wherein the predetermined condition specifically comprises:

The gesture speed is greater than or equal to a predetermined threshold, and the gesture direction information is to the right of the display screen.
The method of claim 11 wherein when said gesture speed information is less than said predetermined threshold, said at least one object interface element is moved in accordance with said detected gesture.
The method of claim 9 or 11, wherein before the touch sensitive surface detects a gesture for the at least one object interface element, the method comprises:

Determining whether the at least one object is removable: if the at least one object is erasable, detecting a gesture for the at least one object interface element on the touch-sensitive surface; if the at least one object is undeletable , then prompt the user.
The method according to claim 9 or 11, wherein the at least one object interface element is specifically a first application interface element and a second application interface element, and the first application interface element is associated with the first application, The second application interface element is associated with the second application;

among them,

The detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, when the gesture speed and the gesture direction satisfy a predetermined condition, deleting the at least one object, specifically:

Gestures for the first application interface element and the second application interface element are detected at the touch sensitive surface;

When the gesture speed and the gesture direction satisfy a predetermined condition, the first application and the second application are uninstalled.
The method according to claim 9 or 11, wherein the at least one object interface element is specifically a first file interface element and a second file interface element, and the first file interface element is associated with the first file data, The second file interface element associates the second file data;

among them,

The detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, when the gesture speed and the gesture direction satisfy a predetermined condition, deleting the at least one object, specifically:

Gestures for the first file interface element and the second file interface element are detected on the touch sensitive surface;

The first file data and the second file data are erased when the gesture speed and the gesture direction satisfy a predetermined condition.
The method according to claim 9 or 11, wherein the at least one object interface element is specifically a third file interface element and a fourth application interface element, and the third file interface element is associated with the third file data. The fourth application interface element is associated with the fourth application;

among them,

The detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, when the gesture speed and the gesture direction satisfy a predetermined condition, deleting the at least one object, specifically:

Gestures for the third file interface element and the fourth application interface element are detected on the touch sensitive surface;

When the gesture speed and the gesture direction satisfy a predetermined condition, the third file data is erased and the fourth application is unloaded.
An electronic device, the electronic device specifically includes:

a touch-sensitive display unit for detecting a gesture of a user for an object interface element, the gesture includes a gesture speed and a gesture direction, and the object interface element includes an application interface element and a file interface element;

And a processing unit, configured to acquire a gesture of the touch-sensitive display unit, and determine whether the gesture satisfies a predetermined condition: if the processing unit determines that the gesture satisfies a predetermined condition, deleting an object associated with the object interface element.
The electronic device according to claim 17, wherein the predetermined condition specifically comprises: the gesture speed is greater than or equal to a predetermined threshold, and the gesture direction information is to a right side of the display screen.
The electronic device according to claim 18, wherein the processing unit is further configured to: before the touch sensitive display unit detects a gesture for the object interface element:

Determining whether the object is erasable: if the object is removable, the touch-sensitive display unit detects a gesture for the object interface element; if the object is non-deletable, prompts the user.