Patent Grant
12321589
The present disclosure relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that allow a user to annotate content.
The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Example touch-sensitive surfaces include touchpads and touch-screen displays. Such surfaces are widely used to manipulate user interface objects on a display. Such manipulations include adjusting the position and/or size of one or more user interface objects or activating buttons or opening files/applications represented by user interface objects, as well as associating metadata with one or more user interface objects or otherwise manipulating user interfaces. Example user interface objects include digital images, video, text, icons, control elements such as buttons and other graphics. A user will, in some circumstances, need to perform such manipulations on user interface objects in a file management program (e.g., Finder from Apple Inc. of Cupertino, California), an image management application (e.g., Aperture, iPhoto, Photos from Apple Inc. of Cupertino, California), a digital content (e.g., videos and music) management application (e.g., iTunes from Apple Inc. of Cupertino, California), a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, California), a word processing application (e.g., Pages from Apple Inc. of Cupertino, California), a website creation application (e.g., iWeb from Apple Inc. of Cupertino, California), a disk authoring application (e.g., iDVD from Apple Inc. of Cupertino, California), or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, California).
Some user interfaces display content and allow a user to annotate the content, e.g., to add drawings or hand-written text to portions of the content. However, methods for adding annotations to the content are cumbersome and inefficient. For example, using a sequence of mouse based inputs to select one or more user interface objects and perform one or more actions on the selected user interface objects is tedious and creates a significant cognitive burden on a user. In addition, these methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for electronic devices with faster, more efficient methods and interfaces for annotating content. Such methods and interfaces optionally complement or replace conventional methods for annotating content. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at a device with one or more processors, non-transitory memory, a display, and an input device. The method includes displaying, on the display, a drawing user interface including a plurality of drawing objects. While a drawing tool that is associated with a predefined operation is selected, the method includes detecting, via the one or more input devices, a user input moving to define a path within the drawing user interface. In response to detecting the user input moving to define the path within the drawing user interface, the method includes performing the predefined operation with respect to two or more of the plurality of drawing objects that intersect the path.
In accordance with some embodiments, a method is performed at a device with one or more processors, non-transitory memory, a display, and an input device. The method includes displaying, on the display, first content and a representation of second content associated with the first content. The method includes detecting, via the one or more input devices, a user input at a location of the representation of the second content. In response to detecting the user input at the location of the representation of the second content and in accordance with a determination that the user input includes a stylus contact, the method includes displaying, on the display, a drawing user interface including the second content and a toolbar region with a plurality of drawing tool selection affordances. In response to detecting the user input at the location of the representation of the second content and in accordance with a determination that the user input does not include a stylus contact, the method includes forgoing display of the drawing user interface.
In accordance with some embodiments, a method is performed at a device with one or more processors, non-transitory memory, and a touch-sensitive display. The method includes displaying, on the touch-sensitive display, a content creation region that includes typed text and one or more blank areas that do not include content. The method includes detecting a user input on the touch-sensitive display that includes movement of a contact in the content creation region. In response to detecting the user input and in accordance with a determination that the user input includes movement of a stylus contact in a respective blank area, the method includes drawing a mark based on movement of the stylus contact during the user input. In response to detecting the user input and in accordance with a determination that the user input includes movement of a finger contact in the respective blank area, the method includes scrolling the content creation region based on movement of the finger contact during the user input.
In accordance with some embodiments, a method is performed at a device with one or more processors, non-transitory memory, and a touch-sensitive display. The method includes displaying, on the touch-sensitive display, a content creation region. While displaying the content creation region, the method includes detecting one or more typed inputs. In response to detecting the one or more typed inputs, the method includes editing content in the content creation region to create a blank area that does not include visible content and is a text insertion region. While displaying the content creation region with the text insertion region, the method includes detecting a contact on the touch-sensitive display in the text insertion region. In response to detecting the contact on the touch-sensitive display in the text insertion region and in accordance with a determination that the contact is a stylus contact, the method includes converting at least a portion of the text insertion region into a drawing insertion region including a mark based the stylus contact. In response to detecting the contact on the touch-sensitive display in the text insertion region and in accordance with a determination that the contact is a finger contact, the method includes converting at least a portion of the text insertion region into a blank drawing insertion region.
In accordance with some embodiments, an electronic device includes a display one or more input devices, and one or more processors. The one or more processors are configured to display, on the display, a drawing user interface including a plurality of drawing objects. While a drawing tool that is associated with a predefined operation is selected, the one or more processors are configured to detect, via the one or more input devices, a user input moving to define a path within the drawing user interface. In response to detecting the user input moving to define the path within the drawing user interface, the one or more processors are configured to perform the predefined operation with respect to two or more of the plurality of drawing objects that intersect the path.
In accordance with some embodiments, an electronic device includes a display, one or more input devices, and one or more processors. The one or more processors are configured to display, on the display, first content and a representation of second content associated with the first content. The one or more processors are configured to detect, via the one or more input devices, a user input at a location of the representation of the second content. In response to detecting the user input at the location of the representation of the second content and in accordance with a determination that the user input includes a stylus contact, the one or more processors are configured to display, on the display, a drawing user interface including the second content and a toolbar region with a plurality of drawing tool selection affordances. In response to detecting the user input at the location of the representation of the second content and in accordance with a determination that the user input does not include a stylus contact, the one or more processors are configured to forgo display of the drawing user interface.
In accordance with some embodiments, an electronic device includes a touch-sensitive display and one or more processors. The one or more processors are configured to display, on the touch-sensitive display, a content creation region that includes typed text and one or more blank areas that do not include content. The one or more processors are configured to detect a user input on the touch-sensitive display that includes movement of a contact in the content creation region. In response to detecting the user input and in accordance with a determination that the user input includes movement of a stylus contact in a respective blank area, the one or more processors are configured to draw a mark based on movement of the stylus contact during the user input. In response to detecting the user input and in accordance with a determination that the user input includes movement of a finger contact in the respective blank area, the one or more processors are configured to scroll the content creation region based on movement of the finger contact during the user input.
In accordance with some embodiments, an electronic device includes a touch-sensitive display and one or more processors. The one or more processors are configured to display, on the touch-sensitive display, a content creation region. While displaying the content creation region, the one or more processors are configured to detect one or more typed inputs. In response to detecting the one or more typed inputs, the one or more processors are configured to edit content in the content creation region to create a blank area that does not include visible content and is a text insertion region. While displaying the content creation region with the text insertion region, the one or more processors are configured to detect a contact on the touch-sensitive display in the text insertion region. In response to detecting the contact on the touch-sensitive display in the text insertion region and in accordance with a determination that the contact is a stylus contact, the one or more processors are configured to convert at least a portion of the text insertion region into a drawing insertion region including a mark based the stylus contact. In response to detecting the contact on the touch-sensitive display in the text insertion region and in accordance with a determination that the contact is a finger contact, the one or more processors are configured to convert at least a portion of the text insertion region into a blank drawing insertion region.
In accordance with some embodiments, an electronic device includes a display, one or more input devices, one or more processors, non-transitory memory, and one or more programs; the one or more programs are stored in the non-transitory memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a non-transitory computer readable storage medium has stored therein instructions which when executed by one or more processors of an electronic device with a display and an input device, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, an input device, a memory, and one or more processors to execute one or more programs stored in the non-transitory memory includes one or more of the elements displayed in any of the methods described above, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display, an input device; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and an input device, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with displays, touch-sensitive surfaces and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for annotating content, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for annotating content.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Many electronic devices have graphical user interfaces that display content, such as an image or text. Some applications allow a user to add or otherwise manipulate annotations associated with content. In embodiments described below, an application allows a user to manipulate hand-drawn annotations associated with content. For example, in some embodiments, when a tool is selected, a predefined operation associated with that tool is performed on annotations intersecting a drawn path. As another example, when a user input upon displayed content is provided with a stylus (as opposed to a finger), a drawing user interface is provided for annotating the content (as opposed to a viewing user interface for viewing the content). As another example, when a user input within a blank space of content is provided with a stylus (as opposed to a finger), an annotation is added to the content (as opposed to scrolling the content). As another example, when a user input within a blank text insertion region of content is provided with a stylus (as opposed to a finger), an annotation is added to the content (as opposed to providing a drawing insertion region for the addition of an annotation by subsequent user input).
Below, a description of example devices illustrates in
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as a “down click” or an “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 122 and the peripherals interface 118, is, optionally, controlled by memory controller 120.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 122 and memory 102. The one or more processors 122 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 122, and memory controller 120 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user-interface objects.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic/tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In an example embodiment, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In an example embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 163.
Device 100 optionally also includes one or more accelerometers 167, gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertial measurement unit (IMU)) for obtaining information concerning the position (e.g., attitude) of the device.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts and/or stylus contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 163 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail client 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone module 138 for use in location-based dialing, to camera module 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone module 138, video conference 139, e-mail client 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 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 executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 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 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in a respective event, such as event 1 (187-1) or event 2 (187-2), include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, the event definition for a respective event, such as event 1 (187-1) or event 2 (187-2), includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event, such as event 1 (187-1) or event 2 (187-2), also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch-sensitive display system 112 and/or one or more tactile output generators 163 for generating tactile outputs for a user of device 100.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
Attention is now directed towards embodiments of user interfaces (“UP”) and associated processes that may be implemented on an electronic device, such as portable multifunction device (PMD) 100 or device 300, with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface.
The content region 512 includes content that can be edited via the drawing user interface 501. For example, in
The toolbar region 513 includes a plurality of drawing tool selection affordances respectively associated with a plurality of drawing tools. In
The toolbar region 513 includes an undo affordance 531A that can be used to reverse the last action taken by the user (e.g., undo insertion of a drawing object) and a redo affordance 531B that can be used to retake an undone action (e.g., redo insertion of the drawing object). In various circumstances, the undo affordance 531A and/or the redo affordance 531B are not displayed or a grayed out if there is no action to undo or redo.
The toolbar region 513 includes color selection affordances 533 for selecting a color of drawing objects inserted via the drawing user interface 501. The toolbar region 513 includes a toolbar menu affordance 534 for displaying a toolbar menu.
In various implementations, in accordance with a determination that a speed of a contact drawing the path within the drawing user interface 501 exceeds a speed threshold, the device 100 ceases to display drawing objects that intersect the path and, in accordance with a determination that the speed of the contact does not exceed the speed threshold, the device 100 continues to display the drawing objects that intersect the path. Accordingly, a quick swipe through a drawing object (even with the deletion tool selected) does not delete the object. In some embodiments, the speed of the contact is determined separately for each drawing object intersecting the path. Thus, if the speed of the contact while moving over a first object is above the speed threshold (e.g., the path meets object deletion criteria), the first object is deleted and if the speed of the contact while moving over a second object is below the speed threshold (e.g., the path does not meet the object deletion criteria), then the second object is not deleted.
The selection path graphic 522B provides a visual indication to a user as to which drawing objects are selected by the selection tool. In various implementations, drawing objects intersecting the selection path are selected. In various implementations, drawing objects intersecting those intersecting the selection path are also selected. In various implementations, drawing objects encompassed by the selection path are also selected. Thus, in
The notes user interface 505 includes an options bar 555A, a content creation region 555B, and a toolbar region 555C. The options bar 555A includes a share affordance 556A for sharing the content in the content creation region 555B with other users, e.g., emailing a copy of the content or sending a text message including a copy of the content. The options bar 555A includes a delete affordance 556B for deleting the content in the content creation region 555B. The options bar 555A includes a new-note affordance 556C for saving (and clearing) the content in the content creation region 555B.
The content creation region 555B includes first content in the form of typed text 557A. The content creation region 555B includes a blank area 557B beneath the typed text 557A. The toolbar region 555C includes an undo affordance 531A that can be used to reverse the last action taken by the user (e.g., undo insertion of content into the content creation region 555B) and a redo affordance 531B that can be used to retake an undone action (e.g., redo insertion of the drawing object). In various circumstances, the undo affordance 531A and/or the redo affordance 531B are not displayed or a grayed out if there is no action to undo or redo.
The toolbar region 555C includes a plurality of content insertion affordances 558A-558C for inserting content into the content creation region 555B. The plurality of content insertion affordances include a checkbox insertion affordance 558A for inserting a checkbox into the content creation region 555B. The plurality of insertion affordances include an image insertion affordance 558B for inserting an image into the content creation region 555B. In various implementations, upon detecting selection of the image insertion affordance 558B, the device 100 displays an image selection user interface for assisting a user in selecting an image for insertion into the content creation region 555B. The plurality of content insertion affordances include a drawing insertion affordance 558C for inserting a drawing into the content creation region 555B. In various implementations, upon detecting selection of the drawing insertion affordance 558C, the notes user interface 505 is replaced with a drawing user interface for assisting a user in creating a drawing. When the drawing is complete, the drawing user interface is replaced with the notes user interface 505 including the drawing in the content creation region 555B. The toolbar region 555C includes a show drawing tools affordance 558D for displaying drawing tool selection affordances in the toolbar region and allowing insertion of an in-line drawing into the content creation region 555B as described further below.
Thus,
The toolbar region 555C is displayed in the keyboard mode. In the keyboard mode, the toolbar region 555C include the undo affordance 531A that can be used to reverse the last action taken by the user (e.g., undo insertion of text) and the redo affordance 531B that can be used to retake an undone action (e.g., redo insertion of the text). In various circumstances, the undo affordance 531A and/or the redo affordance 531B are not displayed or a grayed out if there is no action to undo or redo. The toolbar region 555C includes the checkbox insertion affordance 558A for inserting a checkbox into the content creation region 555B, the image insertion affordance 558B for inserting an image into the content creation region 555B, and the drawing insertion affordance 558C for inserting a drawing into the content creation region 555B. The toolbar region 555C includes the show drawing tools affordance 558D for displaying drawing tool selection affordances in the toolbar region 555C. The toolbar region 555C includes a keyboard with a plurality of character affordances 558G for inserting text into the content creation region 555B. The toolbar region 555C includes the font options affordance 558F for changing a size or font of the text inserted into the content creation region 555B. The toolbar region 555C includes the hide keyboard affordance 558H for changing the toolbar region 555C into the generic content insertion mode.
Among the character affordances 558G for inserting text into the content creation region 555B is an enter affordance 558I for inserting a carriage return into the content creation region 555B.
As described below, the method 600 provides an intuitive way to manipulate drawing objects. The method reduces the cognitive burden on a user when manipulating drawing objects, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to manipulate drawing objects faster and more efficiently conserves power and increases the time between battery charges.
The device displays (602), on the display, a drawing user interface including a plurality of drawing objects. For example, in
In some embodiments, the drawing user interface includes (604) a toolbar region including a plurality of drawing tool selection affordances respectively associated with a plurality of drawing tools. For example, in
In some embodiments, the device detects (606), via the one or more input devices, a selection user input at a location of one of the plurality of drawing tool selection affordances associated with one of the plurality of drawing tools that is associated with a predefined operation. For example, in
In some embodiments, the drawing user interface includes (608) content marked up the plurality of drawing objects. For example, in
In some embodiments, the plurality of drawing objects includes (610) a stroke drawing object defined by a continuous user input within the drawing user interface while a drawing tool that is associated with a stroke operation is selected. For example, in
In some embodiments, the plurality of drawing objects includes (612) at least one of a shape drawing object, a stroke drawing object, a magnifier drawing object, or a text drawing object. For example, in
While a drawing tool that is associated with a predefined operation is selected, the device detects (614), via the one or more input devices, a user input moving to define a path within the drawing user interface. For example, in
In response to detecting the user input moving to define the path within the drawing user interface, the device performs (616) the predefined operation with respect to two or more of the plurality of drawing objects that intersect the path. For example, in
In some embodiments, in performing the predefined operation, the device ceases (618) to display the two or more of the plurality of drawing objects that intersect the path. For example, in
In some embodiments, in performing the predefined operation, the device, in accordance with a determination that a speed of the user input moving to define the path within the drawing user interface exceeds a speed threshold, ceases (622) to display the two or more of the plurality of drawing objects that intersect the path and, in accordance with a determination that the speed does not exceed the speed threshold, continues to display the two or more of the plurality of drawing objects that intersect the path. For example, in
In some embodiments, in performing the predefined operation, the device selects (624) the two or more of the plurality of drawing objects that intersect the path. For example, in
In some embodiments, in selecting the two or more of the plurality of drawing objects that intersect the path, the device selects (626) an additional one of the plurality of objects that intersects one or more of the two of more of the plurality of drawing objects that intersect the path. In some embodiments, in selecting the two or more of the plurality of drawing objects that intersect the path, the device selects (628) an additional one of the plurality of objects that is encompassed by the path. For example, in
In some embodiments, after selecting the two or more of the plurality of drawing objects that intersect the path, the device detects (630) a relocation user input moving with the drawing user interface. For example, in
In some embodiments, in selecting the two or more of the plurality of drawing objects that intersect the path, the device displays (634) a selection path graphic corresponding to the path. For example, in
In some embodiments, in performing the predefined operation with respect to two or more of the plurality of drawing objects that intersect the path, the device erases (644), from the two or more of the plurality of drawing objects that intersect the path, portions that intersect the path without erasing one or more portions that do not intersect the path. For example, in
In some embodiments, in performing the predefined operation with respect to two or more of the plurality of drawing objects that intersect the path, the device changes (646) a color of the two or more of the plurality of drawing objects that intersect the path, changes a size of the two or more of the plurality of drawing objects that intersect the path, or changes an opacity of the two or more of the plurality of drawing objects that intersect the path. For example, in
It should be understood that the particular order in which the operations in
As described below, the method 700 provides an intuitive way to markup content. The method reduces the cognitive burden on a user when marking up content, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to markup content faster and more efficiently conserves power and increases the time between battery charges.
The device displays (702), on the display, first content and a representation of second content associated with the first content. For example, in
In some embodiments, the representation of the second content includes (704) an image. For example, in
In some embodiments, the representation of the second content includes an icon. For example, in
The device detects (708), via the one or more input devices, a user input at a location of the representation of the second content. For example, in
In response to detecting the user at the location of the representation of the second content and in accordance with a determination that the user input includes a stylus contact, the device displays (712), on the display, a drawing user interface including the second content and a toolbar region with a plurality of drawing tool selection affordances. For example, in
In some embodiments, when the user input defines a path from a first location within an image to a second location within an image, the device displays (714), in the drawing user interface, a drawing object corresponding to the path. For example, in
In response to detecting the user at the location of the representation of the second content and in accordance with a determination that the user input does not include a stylus contact, the device forgoes (720) display of the drawing user interface. For example, in
In some embodiments, in forgoing to display the drawing user interface, the device displays (722) a viewer user interface including the second content without the plurality of drawing tool selection affordances. For example, in
In some embodiments, while displaying the viewer user interface, the device detects (724), via the one or more input devices, a user input selecting a drawing affordance of the viewer user interface. For example, in
In some embodiments, while displaying the viewer user interface, the device detects (728), via the one or more inputs devices, a user input at a location of the second content. For example, in
In some embodiments, in accordance with a determination that the user input at the location of the second content includes a stylus contact, the device displays (730), on the display, the drawing user interface including the second content and the toolbar region with the plurality of drawing tool affordances. For example, in
In some embodiments, in accordance with a determination that the user input at the location of the second content does not include a stylus contact, the device forgoes (732) display of the drawing user interface. For example, in
In some embodiments, while displaying the first content and the representation of the second content, in forgoing display of the drawing user interface, the device moves (736) display of the first content and the representation of the second content in accordance with movement of the user input at the location of the representation of the second content. For example, in
It should be understood that the particular order in which the operations in
As described below, the method 800 provides an intuitive way to manipulate a content creation region. The method reduces the cognitive burden on a user when manipulating a content creation region, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to manipulate a content creation region faster and more efficiently conserves power and increases the time between battery charges.
The device displays (802), on the touch-sensitive display, a content creation region that includes typed text and one or more blank areas that do not include content. For example, in
The device detects (804) a user input on the touch-sensitive display that includes movement of a contact in the content creation region. For example, in
In response to detecting the user input and in accordance with a determination that the user input includes movement of a stylus contact in a respective blank area, the device draws (806) a mark based on movement of the stylus contact during the user input. For example, in
In some embodiments, in drawing the mark, the device displays (810), on the touch-sensitive display, a toolbar region including a plurality of drawing tool selection affordances for selecting respective drawing tools. For example, in
In some embodiments, in drawing the mark, the device displays (814), on the touch-sensitive display between the respective blank area and the typed text, a visual separator. For example, in
In accordance with a determination that the user input includes movement of a finger contact in a respective blank area, the device scrolls (816) the content creation region based on movement of the finger contact during the user input. For example, in
In some embodiments, the device detects (820) a contact at a location in the typed text. For example, in
In some embodiments, the device detects (824) movement of a contact at a location within the typed text. For example, in
In some embodiments, the device detects (828) a contact at a location in the typed text for at least a predefined threshold amount of time. For example, in
In some embodiments, the device detects (832) at contact at a location of the affordance for inserting a drawing insertion region. For example, in
In some embodiments, the device detects (840) movement of a contact in the drawing insertion region. For example, in
In some embodiments, the device detects (844) movement of a contact from a location of the second visual separator. For example, in
It should be understood that the particular order in which the operations in
As described below, the method 900 provides an intuitive way to insert a drawing insertion region. The method reduces the cognitive burden on a user when inserting a drawing insertion region, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to insert a drawing insertion region faster and more efficiently conserves power and increases the time between battery charges.
The device displays (902), on the touch-sensitive display, a content creation region. For example, in Figure CL, the device 100 displays a content creation region 555B as part of a notes user interface 505.
The device detects (904) on or more typed inputs. For example, in
In response to detecting the one or more typed inputs, the device edits (906) content in the content creation region to create a blank area that does not include visible content and is a text insertion region. For example, in
In some embodiments, the device detects (908) a contact at a location of the text insertion region. For example, in
In some embodiments, in response to detecting the contact at the location of the text insertion region, the device displays (910), on the touch-sensitive display, a keyboard including a plurality of character affordances for inserting text into the text insertion region and including a show drawing tools affordance. For example, in
In some embodiments, the device detects (912) a user input requesting insertion of a drawing insertion region. In some embodiments, the device detects (914) a contact at a location of the show drawing tools affordance. For example, in
In some embodiments, in response to detecting the contact at the location of the show drawing tools affordance, the device displays (916) a toolbar region including a plurality of drawing tool selection affordances for selecting respective drawing tools. For example, in
While displaying the content creation region with the text insertion region, the device detects (918) a contact on the touch-sensitive display in the text insertion region. For example, in
In response to detecting the contact in the text insertion region and in accordance with a determination that the contact is a stylus contact, the device converts (920) at least a portion of the text insertion region into a drawing insertion region including a mark based on the stylus contact. For example, in
In response to detecting the contact in the text insertion region and in accordance with a determination that the contact is a finger contact, the device converts (924) at least a portion of the text insertion region into a blank drawing insertion region. For example, in
In some embodiments, the device detects (928) movement of a contact on the touch-sensitive display in the content creation region. For example, in
In some embodiments, in response to detecting movement of the contact on the touch-sensitive display in the content creation region and in accordance with a determination that the movement of the contact is in typed text, the device selects (930) text covered by the movement. For example, in
In some embodiments, the device displays (934), on the touch-sensitive display, a first visual separator between the drawing insertion region and typed text in the content creation region. For example, in
In some embodiments, in accordance with a determination that the drawing insertion region is between first typed text in the content creation region and second typed text in the content creation region, the device displays (936) the first visual separator between the drawing insertion region and the first typed text and displays a second visual separator between the drawing insertion region and the second typed text. For example, in
In some embodiments, the device detects (940) movement of a contact from a location of the first visual separator. For example, in
In some embodiments, in response to detecting movement of a contact from a location of the first visual separator, the device converts (942) at least an additional portion of the text insertion region into an additional portion of the drawing insertion region. For example, in
In some embodiments, the device detects (944) movement of a contact from a first location within the drawing insertion region to a second location within an additional portion of the text insertion region. For example, in
In some embodiments, in response to detecting movement of the contact from the first location within the drawing insertion region to the second location within an additional portion of the text insertion region, the device converts (946) at least an additional portion of the text insertion region into an additional portion of the drawing insertion region. For example, in
In some embodiments, in response to detecting movement of the contact from the first location within the drawing insertion region to the second location within an additional portion of the text insertion region, the device draws (948) a mark in the additional portion of the drawing insertion region based on the movement of the contact from the first location to the second location. For example, in
It should be understood that the particular order in which the operations in
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. Nonprovisional patent application Ser. No. 15/978,125, filed on May 12, 2018, which claims priority to U.S. Provisional Patent Application No. 62/514,206, filed on Jun. 2, 2017, both of which are herein incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5155813 | Donoghue et al. | Oct 1992 | A |
| 5367353 | Amanuma et al. | Nov 1994 | A |
| 5367453 | Capps et al. | Nov 1994 | A |
| 5483261 | Yasutake | Jan 1996 | A |
| 5488204 | Mead et al. | Jan 1996 | A |
| 5591945 | Kent | Jan 1997 | A |
| 5825352 | Bisset et al. | Oct 1998 | A |
| 5835079 | Shieh | Nov 1998 | A |
| 5880411 | Gillespie et al. | Mar 1999 | A |
| 5956020 | D'Amico et al. | Sep 1999 | A |
| 6188391 | Seely et al. | Feb 2001 | B1 |
| 6310610 | Beaton et al. | Oct 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6327011 | Kim | Dec 2001 | B2 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6611258 | Tanaka et al. | Aug 2003 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6690387 | Zimmerman et al. | Feb 2004 | B2 |
| 6856259 | Sharp | Feb 2005 | B1 |
| 7015894 | Morohoshi | Mar 2006 | B2 |
| 7028253 | Lieberman | Apr 2006 | B1 |
| 7079118 | Benard et al. | Jul 2006 | B2 |
| 7184064 | Zimmerman et al. | Feb 2007 | B2 |
| 7218040 | Toda | May 2007 | B2 |
| 7259752 | Simmons | Aug 2007 | B1 |
| 7489306 | Kolmykov-Zotov et al. | Feb 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7633076 | Huppi et al. | Dec 2009 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7957762 | Herz et al. | Jun 2011 | B2 |
| 8006002 | Kalayjian et al. | Aug 2011 | B2 |
| 8131026 | Benkley et al. | Mar 2012 | B2 |
| 8159501 | Rao | Apr 2012 | B2 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8279180 | Hotelling et al. | Oct 2012 | B2 |
| 8379047 | Diverdi | Feb 2013 | B1 |
| 8381135 | Hotelling et al. | Feb 2013 | B2 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8493340 | Tremblay | Jul 2013 | B2 |
| 8587526 | Engelhardt et al. | Nov 2013 | B2 |
| 8638320 | Harley et al. | Jan 2014 | B2 |
| 8638385 | Bhogal | Jan 2014 | B2 |
| 8736575 | Kasahara et al. | May 2014 | B2 |
| 8743091 | Bernstein | Jun 2014 | B2 |
| 8847983 | Ranganathan | Sep 2014 | B1 |
| 8910253 | Johnson | Dec 2014 | B2 |
| 8928635 | Harley et al. | Jan 2015 | B2 |
| 8963890 | Raif et al. | Feb 2015 | B2 |
| 8994698 | Diverdi et al. | Mar 2015 | B2 |
| 9058595 | Coffman et al. | Jun 2015 | B2 |
| 9063563 | Gray et al. | Jun 2015 | B1 |
| 9075464 | Mankowski et al. | Jul 2015 | B2 |
| 9223464 | Mandre | Dec 2015 | B2 |
| 9268997 | Sheth et al. | Feb 2016 | B2 |
| 9348458 | Hotelling et al. | May 2016 | B2 |
| 9354728 | Yilmaz et al. | May 2016 | B2 |
| 9430141 | Lu et al. | Aug 2016 | B1 |
| 9557833 | Sundara-Rajan et al. | Jan 2017 | B2 |
| 9753556 | Bernstein et al. | Sep 2017 | B2 |
| 9933937 | Lemay et al. | Apr 2018 | B2 |
| 9959037 | Chaudhri et al. | May 2018 | B2 |
| 10079786 | Yamakawa et al. | Sep 2018 | B2 |
| 10120561 | Stewart et al. | Nov 2018 | B2 |
| 10126877 | Lynn et al. | Nov 2018 | B1 |
| 10168899 | Feiszli et al. | Jan 2019 | B1 |
| 10209821 | Roberts-Hoffman et al. | Feb 2019 | B2 |
| 10241627 | Yoon | Mar 2019 | B2 |
| 10338783 | Barrus et al. | Jul 2019 | B2 |
| 10338793 | Fisher | Jul 2019 | B2 |
| 10445703 | Atkins et al. | Oct 2019 | B1 |
| 10664070 | Lipman et al. | May 2020 | B2 |
| 10860788 | Foss et al. | Dec 2020 | B2 |
| 10969873 | Tan et al. | Apr 2021 | B2 |
| 11042230 | Kochura et al. | Jun 2021 | B2 |
| 11287917 | Dahl et al. | Mar 2022 | B2 |
| 11422669 | Ravasz et al. | Aug 2022 | B1 |
| 11429274 | Missig et al. | Aug 2022 | B2 |
| 11775168 | Vignau | Oct 2023 | B1 |
| 20010003452 | Linge | Jun 2001 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020048404 | Fahraeus et al. | Apr 2002 | A1 |
| 20020059350 | Iwema et al. | May 2002 | A1 |
| 20020107885 | Brooks et al. | Aug 2002 | A1 |
| 20030071850 | Geidl | Apr 2003 | A1 |
| 20030214539 | Iwema et al. | Nov 2003 | A1 |
| 20040070573 | Graham | Apr 2004 | A1 |
| 20040085301 | Furukawa et al. | May 2004 | A1 |
| 20040252888 | Bargeron et al. | Dec 2004 | A1 |
| 20050156915 | Fisher | Jul 2005 | A1 |
| 20050183005 | Denoue et al. | Aug 2005 | A1 |
| 20050190059 | Wehrenberg | Sep 2005 | A1 |
| 20050262164 | Guiheneuf et al. | Nov 2005 | A1 |
| 20060010396 | Beezer et al. | Jan 2006 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060071910 | Kim et al. | Apr 2006 | A1 |
| 20060092138 | Kim et al. | May 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060200759 | Agrawala et al. | Sep 2006 | A1 |
| 20060267967 | Hinckley et al. | Nov 2006 | A1 |
| 20070011651 | Wagner | Jan 2007 | A1 |
| 20070097421 | Sorensen | May 2007 | A1 |
| 20070157076 | Lin et al. | Jul 2007 | A1 |
| 20070214407 | Bargeron et al. | Sep 2007 | A1 |
| 20080042978 | Perez-Noguera | Feb 2008 | A1 |
| 20080094369 | Ganatra | Apr 2008 | A1 |
| 20080100998 | Sansom et al. | May 2008 | A1 |
| 20080114251 | Weymer et al. | May 2008 | A1 |
| 20080201438 | Mandre | Aug 2008 | A1 |
| 20080225007 | Nakadaira et al. | Sep 2008 | A1 |
| 20080228007 | Hoshino et al. | Sep 2008 | A1 |
| 20080259090 | Rao | Oct 2008 | A1 |
| 20090073144 | Chen et al. | Mar 2009 | A1 |
| 20090161958 | Markiewicz et al. | Jun 2009 | A1 |
| 20090167728 | Geaghan et al. | Jul 2009 | A1 |
| 20090187860 | Fleck et al. | Jul 2009 | A1 |
| 20100020036 | Hui et al. | Jan 2010 | A1 |
| 20100095205 | Kinoshita | Apr 2010 | A1 |
| 20100107099 | Frazier et al. | Apr 2010 | A1 |
| 20100181121 | Tremblay | Jul 2010 | A1 |
| 20100293460 | Budelli | Nov 2010 | A1 |
| 20100306705 | Nilsson | Dec 2010 | A1 |
| 20110012856 | Maxwell et al. | Jan 2011 | A1 |
| 20110050601 | Son et al. | Mar 2011 | A1 |
| 20110096036 | Mcintosh et al. | Apr 2011 | A1 |
| 20110140847 | Schafer et al. | Jun 2011 | A1 |
| 20110164376 | Tabasso et al. | Jul 2011 | A1 |
| 20110239146 | Dutta et al. | Sep 2011 | A1 |
| 20110254806 | Jung et al. | Oct 2011 | A1 |
| 20120032925 | Sekiya | Feb 2012 | A1 |
| 20120036927 | Sanders et al. | Feb 2012 | A1 |
| 20120068941 | Arrasvuori et al. | Mar 2012 | A1 |
| 20120169646 | Berkes et al. | Jul 2012 | A1 |
| 20120182271 | Wu et al. | Jul 2012 | A1 |
| 20120206330 | Cao et al. | Aug 2012 | A1 |
| 20120216150 | Wernecke | Aug 2012 | A1 |
| 20120229471 | Takai | Sep 2012 | A1 |
| 20120233270 | Lee et al. | Sep 2012 | A1 |
| 20120242603 | Engelhardt et al. | Sep 2012 | A1 |
| 20120262407 | Hinckley et al. | Oct 2012 | A1 |
| 20120263381 | Yoshida | Oct 2012 | A1 |
| 20120306778 | Weeldreyer et al. | Dec 2012 | A1 |
| 20120306927 | Lee et al. | Dec 2012 | A1 |
| 20120311422 | Weeldreyer et al. | Dec 2012 | A1 |
| 20120311499 | Dellinger et al. | Dec 2012 | A1 |
| 20130019208 | Kotler et al. | Jan 2013 | A1 |
| 20130046544 | Kay et al. | Feb 2013 | A1 |
| 20130088465 | Geller et al. | Apr 2013 | A1 |
| 20130106731 | Yilmaz et al. | May 2013 | A1 |
| 20130106766 | Yilmaz et al. | May 2013 | A1 |
| 20130127757 | Mann et al. | May 2013 | A1 |
| 20130136377 | Luo et al. | May 2013 | A1 |
| 20130167086 | Kim et al. | Jun 2013 | A1 |
| 20130229390 | Diverdi | Sep 2013 | A1 |
| 20130229391 | Diverdi | Sep 2013 | A1 |
| 20130242708 | Cadiz et al. | Sep 2013 | A1 |
| 20130257777 | Benko et al. | Oct 2013 | A1 |
| 20130263027 | Petschnigg et al. | Oct 2013 | A1 |
| 20130300719 | Wang | Nov 2013 | A1 |
| 20130314337 | Asano | Nov 2013 | A1 |
| 20130326582 | Kruzeniski et al. | Dec 2013 | A1 |
| 20130328810 | Li et al. | Dec 2013 | A1 |
| 20130342729 | Kim | Dec 2013 | A1 |
| 20140019855 | Kim et al. | Jan 2014 | A1 |
| 20140022193 | Kim et al. | Jan 2014 | A1 |
| 20140028634 | Krah et al. | Jan 2014 | A1 |
| 20140035845 | Kameyama | Feb 2014 | A1 |
| 20140055427 | Kim et al. | Feb 2014 | A1 |
| 20140059487 | Baumann et al. | Feb 2014 | A1 |
| 20140067965 | Yamakawa et al. | Mar 2014 | A1 |
| 20140068493 | Moon et al. | Mar 2014 | A1 |
| 20140068504 | Sun et al. | Mar 2014 | A1 |
| 20140081610 | Diverdi et al. | Mar 2014 | A1 |
| 20140108004 | Sternby et al. | Apr 2014 | A1 |
| 20140108976 | Steiner et al. | Apr 2014 | A1 |
| 20140108979 | Davidson et al. | Apr 2014 | A1 |
| 20140108989 | Bi et al. | Apr 2014 | A1 |
| 20140152589 | Komoda et al. | Jun 2014 | A1 |
| 20140187318 | Gallizzi et al. | Jul 2014 | A1 |
| 20140194162 | Tsudik | Jul 2014 | A1 |
| 20140210097 | Chen et al. | Jul 2014 | A1 |
| 20140210730 | Mankowski et al. | Jul 2014 | A1 |
| 20140210744 | Song et al. | Jul 2014 | A1 |
| 20140210797 | Kreek et al. | Jul 2014 | A1 |
| 20140210979 | Richter et al. | Jul 2014 | A1 |
| 20140219564 | Demiya | Aug 2014 | A1 |
| 20140245139 | Lee et al. | Aug 2014 | A1 |
| 20140253462 | Hicks | Sep 2014 | A1 |
| 20140253465 | Hicks et al. | Sep 2014 | A1 |
| 20140253521 | Hicks | Sep 2014 | A1 |
| 20140253522 | Cueto | Sep 2014 | A1 |
| 20140267064 | Lu | Sep 2014 | A1 |
| 20140267078 | Kukulski et al. | Sep 2014 | A1 |
| 20140267184 | Bathiche et al. | Sep 2014 | A1 |
| 20140280603 | Rideout et al. | Sep 2014 | A1 |
| 20140331187 | Hicks et al. | Nov 2014 | A1 |
| 20140334732 | Jung et al. | Nov 2014 | A1 |
| 20140337705 | Glover et al. | Nov 2014 | A1 |
| 20140340318 | Stringer | Nov 2014 | A1 |
| 20140354553 | Dai et al. | Dec 2014 | A1 |
| 20140354555 | Shahparnia et al. | Dec 2014 | A1 |
| 20140359410 | Lee | Dec 2014 | A1 |
| 20150007061 | Mandre | Jan 2015 | A1 |
| 20150009155 | Tsao et al. | Jan 2015 | A1 |
| 20150029162 | Harris et al. | Jan 2015 | A1 |
| 20150058718 | Kim et al. | Feb 2015 | A1 |
| 20150058789 | Namgung et al. | Feb 2015 | A1 |
| 20150067469 | Shuto | Mar 2015 | A1 |
| 20150067483 | Demiya et al. | Mar 2015 | A1 |
| 20150069204 | Daniels et al. | Mar 2015 | A1 |
| 20150082217 | Tumwattana | Mar 2015 | A1 |
| 20150089389 | Cohen-Zur et al. | Mar 2015 | A1 |
| 20150106714 | Jeong et al. | Apr 2015 | A1 |
| 20150109257 | Jalali | Apr 2015 | A1 |
| 20150127403 | Petty | May 2015 | A1 |
| 20150138127 | Kurita | May 2015 | A1 |
| 20150169069 | Lo et al. | Jun 2015 | A1 |
| 20150186348 | Hicks et al. | Jul 2015 | A1 |
| 20150205398 | Le | Jul 2015 | A1 |
| 20150212692 | Hyun et al. | Jul 2015 | A1 |
| 20150221106 | Winnemoeller et al. | Aug 2015 | A1 |
| 20150248235 | Offenberg et al. | Sep 2015 | A1 |
| 20150293687 | Seong | Oct 2015 | A1 |
| 20150338949 | Westerman | Nov 2015 | A1 |
| 20150347987 | Ali | Dec 2015 | A1 |
| 20150363035 | Hinckley et al. | Dec 2015 | A1 |
| 20150365306 | Chaudhri et al. | Dec 2015 | A1 |
| 20150370350 | Hunt et al. | Dec 2015 | A1 |
| 20160070686 | Yu et al. | Mar 2016 | A1 |
| 20160070688 | Yao et al. | Mar 2016 | A1 |
| 20160098186 | Sugiura | Apr 2016 | A1 |
| 20160162048 | David | Jun 2016 | A1 |
| 20160170505 | Jordan | Jun 2016 | A1 |
| 20160179222 | Chang | Jun 2016 | A1 |
| 20160188017 | Bell | Jun 2016 | A1 |
| 20160259766 | Ivanov | Sep 2016 | A1 |
| 20160299585 | Lee et al. | Oct 2016 | A1 |
| 20160349897 | Ishikawa | Dec 2016 | A1 |
| 20160364025 | Bernstein et al. | Dec 2016 | A1 |
| 20160364026 | Bernstein et al. | Dec 2016 | A1 |
| 20160364027 | Bernstein et al. | Dec 2016 | A1 |
| 20160364091 | Bernstein et al. | Dec 2016 | A1 |
| 20170024178 | Jeong et al. | Jan 2017 | A1 |
| 20170091153 | Thimbleby | Mar 2017 | A1 |
| 20170097746 | Doray et al. | Apr 2017 | A1 |
| 20170109032 | MÉlinand et al. | Apr 2017 | A1 |
| 20180050592 | Bouaziz et al. | Feb 2018 | A1 |
| 20180081536 | Ueno et al. | Mar 2018 | A1 |
| 20180121074 | Peron et al. | May 2018 | A1 |
| 20180129391 | Files et al. | May 2018 | A1 |
| 20180239444 | Siddiqui et al. | Aug 2018 | A1 |
| 20180284946 | Yousefpor et al. | Oct 2018 | A1 |
| 20180329589 | Sonnino | Nov 2018 | A1 |
| 20180335932 | Ta | Nov 2018 | A1 |
| 20180349020 | Jon et al. | Dec 2018 | A1 |
| 20190212809 | Tzou et al. | Jul 2019 | A1 |
| 20190220109 | Bernstein et al. | Jul 2019 | A1 |
| 20190220507 | Foss et al. | Jul 2019 | A1 |
| 20190324562 | Mn et al. | Oct 2019 | A1 |
| 20190339795 | Rebeschi et al. | Nov 2019 | A1 |
| 20190354205 | Rakshit et al. | Nov 2019 | A1 |
| 20190369754 | Roper et al. | Dec 2019 | A1 |
| 20190369755 | Roper et al. | Dec 2019 | A1 |
| 20200293125 | Bernstein et al. | Sep 2020 | A1 |
| 20200356254 | Missig et al. | Nov 2020 | A1 |
| 20200371629 | Hauenstein et al. | Nov 2020 | A1 |
| 20200401796 | Chateigner | Dec 2020 | A1 |
| 20210049321 | Foss et al. | Feb 2021 | A1 |
| 20210132787 | Jung | May 2021 | A1 |
| 20210271338 | Dahl et al. | Sep 2021 | A1 |
| 20210349606 | Chang et al. | Nov 2021 | A1 |
| 20210349627 | Chang et al. | Nov 2021 | A1 |
| 20220197493 | Missig et al. | Jun 2022 | A1 |
| 20240004532 | Soli et al. | Jan 2024 | A1 |
| 20240103654 | Owens et al. | Mar 2024 | A1 |
| 20240329757 | Bernstein et al. | Oct 2024 | A1 |
| 20240393941 | Missig et al. | Nov 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 101667100 | Mar 2010 | CN |
| 103135915 | Jun 2013 | CN |
| 103164158 | Jun 2013 | CN |
| 103853491 | Jun 2014 | CN |
| 103870028 | Jun 2014 | CN |
| 104142782 | Nov 2014 | CN |
| 104298551 | Jan 2015 | CN |
| 104423820 | Mar 2015 | CN |
| 104487928 | Apr 2015 | CN |
| 104487929 | Apr 2015 | CN |
| 104679379 | Jun 2015 | CN |
| 108845757 | Nov 2018 | CN |
| 109791465 | May 2019 | CN |
| 2071436 | Jun 2009 | EP |
| 2325804 | May 2011 | EP |
| 2385446 | Nov 2011 | EP |
| 2530561 | Dec 2012 | EP |
| 2704408 | Mar 2014 | EP |
| 2778864 | Sep 2014 | EP |
| 2818998 | Dec 2014 | EP |
| 2843917 | Mar 2015 | EP |
| 2912540 | Sep 2015 | EP |
| H09-171378 | Jun 1997 | JP |
| H09-305306 | Nov 1997 | JP |
| H11-110119 | Apr 1999 | JP |
| 2000-163031 | Jun 2000 | JP |
| 2002-342033 | Nov 2002 | JP |
| 2003-296029 | Oct 2003 | JP |
| 2007-520005 | Jul 2007 | JP |
| 2008-027082 | Feb 2008 | JP |
| 2008-70994 | Mar 2008 | JP |
| 2010-183447 | Aug 2010 | JP |
| 2012-18644 | Jan 2012 | JP |
| 2012-238295 | Dec 2012 | JP |
| 2013-232033 | Nov 2013 | JP |
| 2014-153865 | Aug 2014 | JP |
| 2015-049901 | Mar 2015 | JP |
| 2015-056154 | Mar 2015 | JP |
| 2015-64882 | Apr 2015 | JP |
| 2015-88006 | May 2015 | JP |
| 2016177589 | Oct 2016 | JP |
| 10-2009-0100248 | Sep 2009 | KR |
| 10-2010-0059343 | Jun 2010 | KR |
| 10-2011-0088594 | Aug 2011 | KR |
| 10-2012-0092036 | Aug 2012 | KR |
| 10-2014-0053554 | May 2014 | KR |
| 10-2014-0073225 | Jun 2014 | KR |
| 10-2014-0124788 | Oct 2014 | KR |
| 10-2015-0022527 | Mar 2015 | KR |
| 10-2015-0026022 | Mar 2015 | KR |
| 10-2015-0026615 | Mar 2015 | KR |
| 10-2017-0139141 | Dec 2017 | KR |
| 201112040 | Apr 2011 | TW |
| 2005103872 | Nov 2005 | WO |
| 2005103872 | Apr 2006 | WO |
| 2010119603 | Oct 2010 | WO |
| 2013169300 | Nov 2013 | WO |
| 2013169849 | Nov 2013 | WO |
| 2014034049 | Mar 2014 | WO |
| 2014105276 | Jul 2014 | WO |
| 2014147724 | Sep 2014 | WO |
| 2016200586 | Dec 2016 | WO |
| 2020227445 | Nov 2020 | WO |
| Entry |
|---|
| PCT International Search Report and Written Opinion dated Jul. 23, 2018, International Search Report PCT/ JS2018/23484, pp. 1-18. |
| Communication pursuant to Rule 164(2)(b) and Article 94(3) EPC dated Sep. 4, 2020, EP Application No. 18716461.1, pp. 1-9. |
| International Preliminary Report on Patentability for PCT/US2018/023484 mailed Dec. 3, 2019. |
| European Search Report received for European Patent Application No. 18716461.1, mailed on Sep. 4, 2020, 5 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 17/031,844, mailed on Dec. 18, 2023, 14 pages. |
| Final Office Action received for U.S. Appl. No. 15/978,125, mailed on Mar. 26, 2020, 13 pages. |
| Final Office Action received for U.S. Appl. No. 15/978,125, mailed on May 13, 2021, 19 pages. |
| Final Office Action received for U.S. Appl. No. 16/982,532, mailed on Jul. 27, 2023, 20 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,678, mailed on Jan. 10, 2022, 30 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,844, mailed on Aug. 8, 2022, 33 pages. |
| International Search Report received for PCT Application No. PCT/US2023/021718, mailed on Nov. 3, 2023, 7 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2020/031727, mailed on Oct. 8, 2020, 10 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2021/031866, mailed on Nov. 8, 2021, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/978,125, mailed on Dec. 12, 2019, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/978,125, mailed on Jul. 5, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/978,125, mailed on Nov. 3, 2020, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/868,449, mailed on May 26, 2021, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/982,532, mailed on Jan. 4, 2023, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,678, mailed on Jul. 8, 2021, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,844, mailed on Dec. 3, 2021, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/315,251, mailed on Mar. 7, 2024, 28 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/978,125, mailed on Aug. 9, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/868,449, mailed on Apr. 14, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/868,449, mailed on Nov. 3, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/982,532, mailed on Jan. 24, 2024, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/982,532, mailed on May 8, 2024, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,678, mailed on Sep. 15, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,678, mailed on Feb. 1, 2023, 8 pages. |
| Adak et al., “Extraction of Doodles and Drawings from Manuscripts”, ICIAP, 17th International Conference, Naples, Italy, Dec. 10, 2013, pp. 515-520. |
| Fosseide et al., “Character Recognition in the Presence of Occluding Clutter”, Proceedings of SPIE, vol. 7247, Retrieved on Aug. 10, 2021, Jan. 18, 2009, 13 pages. |
| Hou et al., “An Algorithm of Calligraphy Beautification Based on Improved Velocity and Width Model”, Computer Engineering and Social Media (CSCESM), 2015 Second International Conference on Computer Science, 2015, pp. 124-127. |
| Matsushita et al., “Effect of Text/Non-text Classification for Ink Search Employing String Recognition”, IEEE, 2012 10th IAPR International Workshop on Document Analysis Systems, May 7, 2012, pp. 230-234. |
| Tianxiao, Liu, “Overview of Handwriting Input Technology”, CNKI, China Invention and Patent, vol. 12, [retrieved on Jul. 31, 2024], 2016, 5 pages (1 page of English Abstract and 4 pages of Official). |
| Toshiba Corporation, “Microsoft Windows for Pen Computing users Guide”, Version A1, Nov. 9, 1994, pp. 23-27, 70-77. See attached Communication 37 CFR § 1.98(a)(3). |
| Corrected Notice of Allowability received for U.S. Appl. No. 18/315,251 , mailed on Sep. 23, 2024, 2 Pages. |
| Notice of Allowance received for U.S. Appl. No. 18/315,251, mailed on Sep. 11, 2024, 19 Pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/862,085, mailed on Mar. 30, 2018, 3 pages. |
| Corrected Notice of Allowability received for U.S. Appl. No. 17/085,779, mailed on Aug. 5, 2024, 2 pages. |
| European Search Report received for European Patent Application No. 16727905.8, mailed on May 8, 2019, 4 pages. |
| European Search Report received for European Patent Application No. 19731090.7, mailed on Oct. 14, 2022, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/417,025, mailed on Sep. 6, 2022, 10 pages. |
| Extended European Search Report received for European Patent Application No. 24152367.9, mailed on Apr. 30, 2024, 15 pages. |
| Final Office Action received for U.S. Appl. No. 14/862,085, mailed on Sep. 10, 2018, 14 pages. |
| Final Office Action received for U.S. Appl. No. 16/417,025, mailed on Jan. 21, 2022, 18 pages. |
| Final Office Action received for U.S. Appl. No. 16/417,025, mailed on May 18, 2021, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/417,025, mailed on Oct. 8, 2020, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/886,643, mailed on Feb. 6, 2023, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/886,643, mailed on Jan. 27, 2022, 14 pages. |
| Final Office Action received for U.S. Appl. No. 17/085,779, mailed on Apr. 9, 2024, 25 pages. |
| Final Office Action received for U.S. Appl. No. 17/085,779, mailed on Aug. 7, 2023, 18 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2016/033588, mailed on Oct. 4, 2016, 6 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2017/053172, mailed on Mar. 14, 2018, 7 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2019/034524, mailed on Nov. 18, 2019, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/860,320, mailed on Jul. 19, 2016, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/862,073, mailed on Oct. 19, 2016, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/862,080, mailed on Jun. 22, 2016, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/862,085, mailed on Mar. 19, 2018, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/923,967, mailed on Aug. 12, 2019, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/333,103, mailed on Mar. 16, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/359,906, mailed on Aug. 21, 2019, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/417,025, mailed on Feb. 5, 2021, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/417,025, mailed on Jun. 29, 2020, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/417,025, mailed on Sep. 2, 2021, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/417,214, mailed on Aug. 6, 2020, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/886,643, mailed on Aug. 16, 2022, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/886,643, mailed on May 24, 2021, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/085,779, mailed on Dec. 28, 2022, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/085,779, mailed on Nov. 20, 2023, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/424,684, mailed on Aug. 14, 2024, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/333,103, mailed on Aug. 19, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/417,214, mailed on Feb. 25, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/860,320, mailed on Dec. 16, 2016, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/860,320, mailed on Mar. 7, 2016, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/862,073, mailed on Mar. 6, 2017, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/862,080, mailed on Dec. 27, 2016, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/862,085, mailed on Apr. 23, 2019, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/862,085, mailed on Jan. 9, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/923,967, mailed on Nov. 20, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/359,906, mailed on Feb. 20, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/359,906, mailed on Jan. 6, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/359,906, mailed on Mar. 26, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/417,025, mailed on Aug. 14, 2024, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/886,643, mailed on Jun. 29, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/886,643, mailed on Oct. 12, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/085,779, mailed on Jul. 17, 2024, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/315,251, mailed on Nov. 27, 2024, 19 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/461,395, mailed on Jul. 16, 2024, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/461,395, mailed on Nov. 12, 2024, 7 pages. |
| Patent Board Decision received for U.S. Appl. No. 16/417,025, mailed on May 7, 2024, 9 pages. |
| Android and Me, “Samsung Galaxy Note 3 Review”, Available Online at: <http://androidandme.com/2013/10-reviews/samsung-galaxy-note-3 review/>, 2013, 14 pages. |
| Anonymous, “How to Re-map the S-pen Button and Insert/remove to Do Anything on the Device”, Available Online at: <https://www.reddit.com/r/galaxynote4/comments/4ju5lh/how_to_remap_the_spen_button_and_insertremove_to/>, [retrieved on 2024-12-12], May 28, 2016, 8 pages. |
| Bargeron et al., “Reflowing Digital Ink Annotations”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, 2003,. |
| Basu Abhiroop, “Samsung Launches Cross-Platform Instant Messaging Service 'ChatON”, Available Online at: <https://www.androidpolice.com/2011/08/29/samsung-launches-cross-platform-instant-messaging-service-chaton/>, Aug. 29, 2011, 5 pages. |
| Christopher W, “ScribMaster Draw and Paint - with Instant Messenger”, Available Online at: <http://www.androidpit.com/scribmaster-draw-and-paint>, Oct. 8, 2013, 9 pages. |
| Color Hunter, “Create and Find Color Palettes Made From Images”, Available Online at: <http://www.colorhunter.com>, 2016, 3 pages. |
| Conroy Kevin, “Digital Document Annotation and Reflow”, Theses and Dissertations, University of Maryland at College Park, 2004,. |
| Css Drive, “Colors Pallete Generator”, Available Online at: <http:www.cssdrive.com/imgaepalette/>, 2011, 2 pages. |
| Eichner, “Ios Sensors & Core Motion”, Available Online at: <http://wwwbruegge.in.turn.de/lehrstuhl_1/home/98-teaching/tutorials/505-sgd-ws13-tutorial-core-motion>, 2016, 12 pages. |
| Farley, “Make Swatches from Photos in Photoshop”, Available Online at: <http://www.sitepoint.com/makeswatches-from-photos-in-photoshop/>, 5 pages. |
| Google, “Loklok”, Available Online at: < http://loklok.co>, 2015, 2 pages. |
| Hayakawa, “Galaxy Note 3 Perfect Manual”, vol. 1, Sotechsha Co. Ltd, Junichi Yanagisawa, May 12, 2015, 9 pages. |
| Itunes Preview, “Draw Calendar-Fun Scheduling and Events”, Fishington Studios, Available Online at: <https://itunes.apple.com/us/app/calendoodle-pen-ink-whiteboard/id815370160?mt=8>, 2014, 3 pages. |
| Jain, “Samsung Galaxy Note 3 Neo Review: Hidden Goodness”, Available Online at: <https://www.mobigyaan.com/samsung-galaxy-not-3-neo-review-2>, Apr. 17, 2014, 48 pages. |
| Kazmucha, “How to Send Someone a Sketch with Apple Works”, Available Online at: <https:/web.archive.org/web/20150525204929/http:ww.www.imore.com/how-sendsome-sketch-apple-watch>, May 7, 2015, 8 pages. |
| Lee et al., “A Multi-Touch Three Dimensional Touch-Sensitive Tablet”, CHI'85 Proceedings, Apr. 1985, pp. 21-25. |
| Lee et al., “PhantomPen: Virtualization of Pen Head for Digitial Drawing Free from Hen Occlusion & Visual Parallax”, IDEA Lab, Department of Industrial Design, KAIST, Republic of Korea, Oct. 7-10, 2012, 10 pages. |
| Lee et al., “PhantomPen: Virtualization of Pen Head for Digitial Drawing Free from Pen Occlusion & Visual Parallax”, YouTube video, Oct. 22, 2012, 2 pages. |
| Locke Ricky, “Kindle App Tips for iPad”, www.slideshare.net, Available online at: <https://www.slideshare.net/RickyLocke/kindle-app-tips-for-ipad>, [Retrieved from Internet on Dec. 6, 2017], Jun. 30, 2013, pp. 1-5. |
| Locke Ricky, “Kindle App Tips for IPad (Slides)”, www.slideshare.net, Available online at: <https://www.slideshare.net/RickyLocke/kindle-app-tips-for-ipad>, [Retrieved from Internet on Dec. 6, 2017], Jun. 30, 2013, pp. 1-57. |
| Mailchimp Email Marketing, “Pictaculous, A Color Palette Generator”, Available Online at: < http://www.pictaculous.com>, 2016, 1 page. |
| Millward, “LiiHo IM App: A New Way to Chat as You Draw Something and Doodle with Friends”, Available Online at: <http://www.techinasia.com/liiho-im-doodling-app/>, Apr. 5, 2012, 6 pages. |
| Notes Plus, “5th Anniversary”, Available Online at: < http://notesplusapp.com>, Apr. 4, 2013, 7 pages. |
| Perez, “Five Amazing Color Palette Generators”, Available Online at: <http://readwrite.com/2008/08/01/five_amazing_color_palette_generators>, Aug. 1, 2008, 3 pages. |
| Rubine Dean, “Combining Gestures and Direct Manipulation”, CHI'92, May 3-7, 1992, pp. 659-660. |
| Rubine Dean H., “The Automatic Recognition of Gestures”, CMU-CS-91-202, Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, Dec. 1991, 285 pages. |
| Rudling, “Erik Rudling - Intreprenur and Consulltannt in Speling”, Available Online at: <http://erikrudling.com/taking-digital-notes-notes-plus-ipad-app-review/>, Jan. 6, 2015, 14 pages. |
| Schwaller et al., “Improving In-game Gesture Learning with Visual Feedback”, ARXIV.ORG, Jun. 22-27, 2014, pp. 643-653. |
| Seiji et al., “Galaxy Note 3 Perfect Manual”, vol. 1, Sotechsha Co. Ltd., Junichi, Yanagisawa, May 12, 2015, 9 pages. |
| Sutherland et al., “Freeform Digital Ink Annotations in Electronic Documents: a Systematic Mapping Study”, Computers & Graphics, vol. 55, No. 2016, 2016, pp. 1-20. |
| Sutherland et al., “Who Changed My Annotation? An Investigation Into Refitting Freeform Ink Annotations”, IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC), 2016,. |
| Westerman Wayne, “Hand Tracking, Finger Identification, and Chordic Manipulation on a Multi-Touch Surface”, A Dissertation Submitted to the Faculty of the University of Delaware in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Electrical Engineering, 1999, 363 pages. |
| Wikipedia, “Calendar (application)”, Available Online at: <https://en.wikipedia.org/wiki/Calendar_(application)>, Sep. 10, 2002, 5 pages. |
| Wikipedia, “Comparison of Instant Messaging Clients”, Available Online at: <http://en.wikipedia.org/wiki/Comparison_of_instant_messaging_clients>, Mar. 1, 2016, 16 pages. |
| Windows, “Use A Pen to Draw, Write, or Highlight, Text on A Windows Tablet,”, Available Online at: <https://support.office.com/en-US/article/Use-a-pen-to-draw-write-or-highlight-text-on-a-Windows-tablet-6d76c674-7f4b-414d-b67f-b3ffef6ccf53>, 2016, 8 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/085,779, mailed on Dec. 20, 2024, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/417,025, mailed on Jan. 28, 2025, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/085,779, mailed on Dec. 18, 2024, 11 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230017201 A1 | Jan 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62514206 | Jun 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15978125 | May 2018 | US |
| Child | 17946374 | US |
