The disclosed embodiments relate generally to user interfaces, and more particularly to a pointer tool for a user interface.
With the increasing popularity of mobile devices, including cellphone devices, handheld devices, handheld computers, smartphones, PDAs, etc., there is a need for improving the user interface experience by increasing user input entry speed, reducing entry errors, and improving the overall user experience.
Mobile devices with capacitive or resistive touch capabilities are well known. Modern mobile phones have evolved over recent years to the point where they now possess a broad range of capabilities. They are not only capable of placing and receiving mobile phone calls, multimedia messaging (MMS), and sending and receiving email, they can also access the Internet, are GPS-enabled, possess considerable processing power and large amounts of memory, and are equipped with high-resolution color liquid crystal displays capable of detecting touch input. As such, today's mobile phones are general purpose computing and telecommunication devices capable of running a multitude of applications. For example, modern mobile phones can run web browser, navigation system, media player and gaming applications.
Along with these enhanced capabilities has come a demand for larger displays to provide a richer user experience. Mobile phone displays have increased in size to the point where they can now consume almost the entire viewing surface of a phone. To increase the size of displays any further would require an increase in the size of the phones themselves. Even with the display size being at its maximum, the content on the display remains relatively small.
Indeed, a finger touching the display can obfuscate the very content being manipulated, making precise operations difficult. For example, moving an insertion point in text often requires a user to grab and drag an insertion cursor. However, the cursor is small relative to a user's finger and often positioned amongst other characters. As a result, the touch screen needs to decide whether the user is attempting to grab the cursor or select the surrounding text. With the user's finger covering both the cursor and text simultaneously, it is impossible to know what operation is being attempted. As a result, the user interface often provides inconsistent results, which causes user frustration.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
The above deficiencies and other problems associated with interacting with touch screen displays are reduced or eliminated by the disclosed pointer tool. The claimed subject matter is not limited to implementations that solve any or all of the noted disadvantages.
The pointer tool allows an insertion point of text to be interactively changed and manipulated by a user. In one embodiment, the pointer tool can be activated (such as by a press-and-hold operation) on the user interface display. When activated, the pointer tool can be automatically positioned adjacent the user's finger regardless of the location of a current cursor. In the activated mode, the pointer tool can be free floating on the user interface and can move with the user's finger to create an insertion point for entering information. Once the user moves the pointer tool to the desired location, the user can remove his or her finger from the display and the pointer tool can persist on the user interface. As such, the user can re-grab the pointer tool (without the need to reactivate it) and move it to a different location. Once the user enters editing information or re-taps the display, the pointer tool can be automatically removed from the display.
In another embodiment, the pointer tool can be an enlarged “I” beam that is greater in size than text on the user interface. Additionally, a triangle or other symbol can be associated with the I-beam and located near the bottom thereof to weight the pointer tool and to prompt the user to grab the pointer tool at the bottom so as not to obfuscate the content being manipulated.
In yet another embodiment, the pointer tool can automatically switch between two modes of operation: a free floating mode wherein the pointer tool can move wherever the user's finger is located and independently of content (e.g., the pointer tool can float over the top of text); and a notched mode wherein the pointer tool can only move to possible cursor positions and, consequently, is dependent upon content. For example, when a user's finger is within a predetermined distance from a candidate cursor location, the pointer tool automatically changes to the notched mode wherein the pointer tool can move to potential cursor locations so it does not overlap with text.
In still a further embodiment, the user can move the pointer tool near a boundary of the display in order to initiate an auto-scrolling mode wherein text outside of a visible area can be automatically scrolled into view.
The foregoing and other features, and advantages will become more apparent from the following detailed description, which proceeds with reference to the accompanying figures.
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 embodiments described herein. However, it will be apparent to one of ordinary skill in the art that the embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
Accordingly,
At block 210 the pointer tool persists in the display after contact with the touch screen is removed, such as on a finger up. For example, the pointer tool continues to be displayed until removed. While persisting in the display the pointer tool can be re-grabbed. For example, the user can grab the pointer tool again by contacting the display near the pointer tool without re-activating the pointer tool. For example, the pointer tool can be re-grabbed by detecting contact with a touch screen within a hit target or area surrounding the pointer tool. When the pointer tool is grabbed it can be relocated. For example, after re-grabbing the pointer tool, the user's finger is dragged and the pointer tool follows the contact movement. Also, for example, the pointer tool can be relocated to an insertion point in an input data field. Additionally, the pointer tool can be moved between sections of the display. In one embodiment, the distance between the point of contact with the touch screen and the pointer tool location can be set at a certain distance (e.g. 40 pixels). Thus, the user can grab the pointer tool even though the user touches the screen within a predetermined distance from the pointer tool. In other embodiments, the pointer tool can be relocated through detecting a user command. For example, a user command could be a voice command, a camera detected gesture, or detected device movement.
The pointer tool can be placed at character level precision when relocated. For example, the pointer tool can be placed before or after any character. Also, for example, when in floating mode, upon releasing contact, such as a finger up, the pointer tool can be automatically re-positioned with character level precision, meaning the pointer tool can be automatically repositioned to a possible cursor location. After being re-positioned, the pointer tool can move in character increments.
In other embodiments, relocating the pointer tool in text allows for the generation of suggestions based on the location of the pointer tool. For example, in one embodiment, if the pointer tool is moved to the middle of a word, word suggestions can be generated based on the letters before the pointer tool location. Also, in other embodiments the suggestions can be generated in some other manner, and suggestions can be generated for multiple languages. Also, suggestions can be text strings, characters or addresses.
Removing the pointer tool from the touch screen display when data is entered or a gesture is detected is shown in block 220. For example, a gesture can be a defined and bounded motion by a user such as a tap on the screen, a flick, a pan, or some other motion. Also, for example, data can be entered by typing or selecting text. The data can be editing data. The data can be entered by a keyboard either on screen or hardware, through curve drawing, handwriting, or some other input method. An on-screen keyboard may have a variety of keys that can be selected with contact with the touch screen. Also, an on screen keyboard can be displayed simultaneously with the pointer tool. In some embodiments, the removal of the pointer tool can be animated and/or play a sound upon removal. In another example embodiment, the pointer tool can be removed if not re-grabbed in a predetermined period of time. Also, in another embodiment, the pointer tool, can be removed if an on screen keyboard is closed manually. In one embodiment, when the pointer tool is removed from the display, a cursor appears in the display where the pointer tool was located.
Attention is now directed to
Exemplary Embodiment for Detecting Contact
In alternative embodiments, for example, a press and hold gesture can be detected by detecting continuous contact with the touch screen while ignoring some slight movements of the finger within a specified tolerance range thereby interpreting a hold gesture. For example, the hold delay can be set at a duration (e.g. 500 ms). This can be achieved with a gesture engine specifying in a registry key in inch units without regard to dots per inch (DPI) differences, however this can work with various DPI. In another embodiment, upon a user gesture of press and hold, inside an editable field the pointer tool can activate near the top edge of the finger making contact with the touch screen. In a further embodiment, a press and hold on selected text can dismiss a selection and activate a pointer tool. In other embodiments, a press and hold on empty space can cause the pointer tool to activate. Also, for example, a press and hold towards the top most boundary of an edit field may cause the pointer tool to appear overlapping the edit field boundary. If a user, for example, drags a pointer tool on screen outside the edit field with text in the edit field, the pointer tool may follow the finger until finger is let up. In another embodiment, if an edit field is the topmost field in a display, a press and hold towards the top most boundary of the edit field may cause the pointer tool to appear overlapping the screen boundary. Part of a pointer tool may not be visible while overlapping the screen boundary. In another embodiment activating the pointer tool (e.g. via press and hold) in a single line edit field can display the pointer tool overflowing the boundary. If the pointer tool is overflowing the edit field, a user can, for example, drag such that the pointer tool aligns with text.
Exemplary User Scenario
In one exemplary scenario of an embodiment, a user can receive an email from a potential customer asking for a quote. The user can type out a reply with the work breakdown and quote for each item. Before she hits send, the user can re-read the reply and notice that one of the work items has the wrong quote; instead of $527 the user should have typed $5027. The user puts her finger on the figure and press and holds down. The user can then view a pointer tool appearing near her finger and follows her finger as she moves it around. The user can align the pointer tool to a cursor position that is after the digit “2”. Keeping her finger down, the user can drag it to the left and see the pointer tool move in real time and without changing the appearance of the text. As soon as the pointer tool is located before the digit “2” the user can stop dragging and lift her finger. The user can then press a Backspace key on the on-screen keyboard to delete the digit “0”. The pointer tool then can disappear and a cursor can take the position of the pointer tool in the display.
Exemplary Advantages
The following describes exemplary advantages of various embodiments. For example, the pointer tool can provide an improved way to precisely interact with touch sensitive displays. According to some embodiments, the pointer tool offers the user an intuitive way of moving a cursor or setting a target in a composition string through direct manipulation with a finger without causing occlusion of manipulated text. Another advantage, for example, of an embodiment of a pointer tool is that it enables a user to place a cursor without having to grab the existing cursor. Also, the text that can be edited with the pointer tool can be from a soft keyboard or imported from other devices, or some other text source. Furthermore, exemplary embodiments of the pointer tool can be used for precise curve drawing or handwriting in a display. In some embodiments, the pointer tool is weighted toward the bottom to encourage a user to grab it at that end so that the insertion point, where data can be entered, is viewable while the pointer tool is being used. Because the pointer tool does not need to displace or magnify surrounding text the user does not have to change their mental focus to manipulate content, and the usability of the pointer tool is not degraded on the edges of a screen or device. Also, in an exemplary embodiment, the pointer tool can persist in the display so a user can review their work or extend a task without having to reactivate the pointer tool.
Example Mobile Environment
The illustrated mobile device can include a controller or processor 1010 (e.g., signal processor, microprocessor, ASIC, or other control and processing logic circuitry) for performing such tasks as signal coding, data processing, input/output processing, power control, and/or other functions for implementing the mobile device. An operating system 1012 can control the allocation and usage of the components 1002 and support for one or more application programs 1014, and support for the pointer tool user interface 1015. The application programs typically include email applications, calendars, contact managers, web browsers, text and media messaging applications.
Memory 1020 can include non-removable memory 1022 and/or removable memory 1024. The non-removable memory 1022 can include RAM, ROM, flash memory, a hard disk, or other well-known memory storage technologies and can be used for storing data and/or code for running the operating system 1012, the applications 1014, and the pointer tool user interface 1015. Example data can include web pages, text, images, sound files, video data, or other data sets to and from one or more network servers or other mobile devices via one or more wired or wireless networks. The removable memory 1024 can include flash memory or a Subscriber Identity Module (SIM) card, which is well known in GSM communication systems, or other well-known memory storage technologies, such as “smart cards.” The memory 1020 can be used to store a subscriber identifier, such as an International Mobile Subscriber Identity (IMSI), and an equipment identifier, such as an International Mobile Equipment Identifier (IMEI). Such identifiers can be transmitted to a network server to identify users and equipment.
The mobile device can support one or more input devices 1030, such as a touch screen 1032, microphone 1034, camera 1036, physical keyboard 1038 and/or trackball 1040, joystick, mouse, and one or more output devices 1050, such as a speaker 1052 and a display 1054. Other possible output devices (not shown) can include piezoelectric or other haptic output devices. Touch screen 1032 can support, an on screen keyboard, edit controls, and the like.
A wireless modem 1060 can be coupled to an antenna (not shown) and can support two-way communications between the processor 1010 and external devices, as is well understood in the art. The modem 1060 is shown generically and can include a cellular modem for communicating with the mobile communication network 1004 and/or other radio-based modems (e.g., Bluetooth or Wi-Fi). The wireless modem 1060 is typically configured for communication with one or more cellular networks, such as a GSM network for data and voice communications within a single cellular network, between cellular networks, or between the mobile device and a public switched telephone network (PSSTN).
The mobile device can further include at least one input/output port 1080, a power supply 1082, a satellite navigation system receiver 1084, such as a Global Positioning System (GPS) receiver, an accelerometer 1086, a transceiver 1088 (for wirelessly transmitting analog or digital signals) and/or a physical connector 1090, which can be a USB port, IEEE 1094 (firewall) port, and RS-232 port. The illustrated components 1002 are not required or all-inclusive, as any components can deleted and other components can be added.
Example Computing Environment
The computing environment 1100 is not intended to suggest any limitation as to scope of use or functionality of the technology, as the technology may be implemented in diverse general-purpose or special-purpose computing environments. For example, the disclosed technology may be implemented with other computer system configurations, including hand held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The disclosed technology may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
With reference to
The storage 1140 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, CD-RWs, DVDs, or any other medium which can be used to store information and which can be accessed within the computing environment 1100. The storage 1140 stores instructions for the software 1190, which can implement technologies described herein.
The input device(s) 1150 may be a touch input device, such as a keyboard, keypad, mouse, pen, or trackball, a voice input device, a scanning device, or another device, that provides input to the computing environment 1100. The environment may also have a touch screen 1180 as an input device and display. For audio, the input device(s) 1150 may be a sound card or similar device that accepts audio input in analog or digital form, or a CD-ROM reader that provides audio samples to the computing environment 1100. The output device(s) 1160 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing environment 1100.
The communication connection(s) 1170 enable communication over a communication medium (e.g., a connecting network) to another computing entity. The communication medium conveys information such as computer-executable instructions, compressed graphics information, or other data in a modulated data signal.
Computer-readable media are any available media that can be accessed within a computing environment 1100. By way of example, and not limitation, with the computing environment 1100, computer-readable media include memory 1120, storage 1140, communication media (not shown), and combinations of any of the above.
Computer-readable media are any available media that can be accessed within a computing environment 1100. By way of example, and not limitation, with the computing environment 1100, computer-readable media include memory 1120 and/or storage 1140. As should be readily understood, the term computer-readable storage media includes the media for data storage such as memory 1120 and storage 1140, and not transmission media such as modulated data signals.
Exemplary Architecture
Furthermore, in one embodiment, a user interface framework can communicate touch input through input handlers. An edit field control can consume a handler that can be modified to communicate touch events to a text editing engine through a touch events interface. The touch events interface can contain a method that can allow the text editing hosts, such as a user interface framework, to forward touch input directly to the touch events interface without the need to directly forward window events.
In another embodiment, a method in a touch events interface to a text editing engine can be implemented to perform selection behavior. For example, selection and pointer tool placement can be modified using selection and pointer tool internal APIs of a text editing engine.
In an example embodiment, in order to place the pointer tool at the correct location on screen, a text editing engine can communicate with hosts through a client-to-screen method. This communication can allow a user interface framework host to convert between text editing engine coordinates and screen coordinates.
Furthermore in another example embodiment, a host interface can be an interface that a text editing engine exposes for hosts to implement in order for the text editing engine to communicate with the host. For example, a method of the interface can allow hosts to be notified when the pointer tool is updated. For example, it returns OK if the host handles updating the pointer tool, or returns FALSE if the host uses a default implementation of the pointer tool.
In one embodiment, for example, the pointer tool can be implemented by calling HRESULT CaretPlacementArrow (bool visible, bool interactive, int x, int y, int height). For example, the parameters can describe whether to display or hide the pointer tool, whether the pointer tool is being interacted with, screen coordinates for locating the pointer tool, and the height of the pointer tool. In one implementation, to assist in calculations, macros and constants can be defined for update of the pointer tool. For example, the amount of offset from the actual touch point to create the hotspot to be used in hit testing can be defined. Also, for example, when in floating mode or when a line height is not available, the height of the pointer tool can be defined as a default height. Additionally, for example, in one embodiment, a margin around a cursor position that transitions the pointer tool from floating mode to notched mode when the pointer tool hotspot enters the margin can be defined.
Example Alternatives and Combinations
In view of the many possible embodiments to which the principles of the disclosed invention may be applied, it should be recognized that the illustrated embodiments are only preferred examples of the invention and should not be taken as limiting the scope of the invention. Rather, the scope of the invention is defined by the following claims. We therefore claim as our invention all that comes within the scope of these claims.
Number | Name | Date | Kind |
---|---|---|---|
4190835 | Buynak | Feb 1980 | A |
4633432 | Kitamura | Dec 1986 | A |
4698625 | McCaskill et al. | Oct 1987 | A |
4739314 | McCaskill et al. | Apr 1988 | A |
RE32773 | Goldwasser et al. | Oct 1988 | E |
4786894 | Furusawa et al. | Nov 1988 | A |
5051930 | Kuwabara et al. | Sep 1991 | A |
5070478 | Abbott | Dec 1991 | A |
5122953 | Uekusa et al. | Jun 1992 | A |
5164713 | Bain | Nov 1992 | A |
5581670 | Bier et al. | Dec 1996 | A |
5583981 | Pleyer | Dec 1996 | A |
5655093 | Frid-Nielsen | Aug 1997 | A |
5666139 | Thielens et al. | Sep 1997 | A |
5666552 | Greyson et al. | Sep 1997 | A |
5714971 | Shalit et al. | Feb 1998 | A |
5754737 | Gipson | May 1998 | A |
5778404 | Capps et al. | Jul 1998 | A |
5798752 | Buxton et al. | Aug 1998 | A |
5825352 | Bisset et al. | Oct 1998 | A |
5857212 | Van De Vanter | Jan 1999 | A |
5905486 | Brittenham et al. | May 1999 | A |
5917476 | Czerniecki | Jun 1999 | A |
6049326 | Beyda et al. | Apr 2000 | A |
6057827 | Matthews | May 2000 | A |
6115482 | Sears et al. | Sep 2000 | A |
6137472 | Pekelney et al. | Oct 2000 | A |
6204848 | Nowlan et al. | Mar 2001 | B1 |
6232969 | Fawcett | May 2001 | B1 |
6310610 | Beaton et al. | Oct 2001 | B1 |
6313836 | Russell, Jr. | Nov 2001 | B1 |
6340967 | Maxted | Jan 2002 | B1 |
6360237 | Schulz et al. | Mar 2002 | B1 |
6396474 | Johnson et al. | May 2002 | B1 |
6489981 | Jones | Dec 2002 | B1 |
6661965 | Yamamoto | Dec 2003 | B2 |
6677928 | Brodey et al. | Jan 2004 | B1 |
6683627 | Ullmann et al. | Jan 2004 | B1 |
6693653 | Pauly | Feb 2004 | B1 |
6714218 | Bian | Mar 2004 | B1 |
6714221 | Christie et al. | Mar 2004 | B1 |
6854090 | Yu | Feb 2005 | B2 |
6927783 | MacInnis et al. | Aug 2005 | B1 |
6986106 | Soin et al. | Jan 2006 | B2 |
7006074 | Chesters | Feb 2006 | B2 |
7024623 | Higashiyama et al. | Apr 2006 | B2 |
7030861 | Westerman et al. | Apr 2006 | B1 |
7032171 | Carroll | Apr 2006 | B1 |
7075512 | Fabre et al. | Jul 2006 | B1 |
7091954 | Iesaka | Aug 2006 | B2 |
7098933 | Thoemmes et al. | Aug 2006 | B1 |
7113178 | Webb | Sep 2006 | B1 |
7149550 | Kraft et al. | Dec 2006 | B2 |
7177797 | Micher et al. | Feb 2007 | B1 |
7355583 | Beardsley et al. | Apr 2008 | B2 |
7356760 | Jaeger | Apr 2008 | B2 |
7380203 | Keely et al. | May 2008 | B2 |
7423659 | Pratley et al. | Sep 2008 | B1 |
7456850 | Meier et al. | Nov 2008 | B2 |
7489306 | Kolmykov-Zotov et al. | Feb 2009 | B2 |
7586481 | Paquette et al. | Sep 2009 | B1 |
7605804 | Wilson | Oct 2009 | B2 |
7761807 | Tapuska | Jul 2010 | B2 |
7856605 | Ording et al. | Dec 2010 | B2 |
7916157 | Kelley et al. | Mar 2011 | B1 |
7954054 | Iwema et al. | May 2011 | B2 |
7966578 | Tolmasky et al. | Jun 2011 | B2 |
8074181 | Zaman et al. | Dec 2011 | B2 |
8117034 | Gschwendtner | Feb 2012 | B2 |
8176438 | Zaman et al. | May 2012 | B2 |
8299943 | Longe | Oct 2012 | B2 |
8319728 | Geffin et al. | Nov 2012 | B2 |
8446392 | Wang et al. | May 2013 | B2 |
8566751 | Kelley et al. | Oct 2013 | B2 |
8614665 | Li | Dec 2013 | B2 |
8656282 | Kulas | Feb 2014 | B2 |
8656296 | Ouyang et al. | Feb 2014 | B1 |
8656315 | Kirkpatrick | Feb 2014 | B2 |
8826190 | Kirkpatrick | Sep 2014 | B2 |
8922479 | Pennington, II | Dec 2014 | B2 |
8984436 | Tseng | Mar 2015 | B1 |
20010012437 | Yamamoto | Aug 2001 | A1 |
20020032705 | Higashiyama et al. | Mar 2002 | A1 |
20020059350 | Iwema | May 2002 | A1 |
20020063740 | Forlenza et al. | May 2002 | A1 |
20020143544 | Gschwendtner | Oct 2002 | A1 |
20020156615 | Takatsuka et al. | Oct 2002 | A1 |
20030095135 | Kaasila et al. | May 2003 | A1 |
20030103082 | Carroll | Jun 2003 | A1 |
20040019849 | Weng et al. | Jan 2004 | A1 |
20040027398 | Jaeger | Feb 2004 | A1 |
20040056899 | Sinclair et al. | Mar 2004 | A1 |
20040083109 | Halonen et al. | Apr 2004 | A1 |
20040135797 | Meier et al. | Jul 2004 | A1 |
20040179001 | Morrison et al. | Sep 2004 | A1 |
20040225965 | Garside et al. | Nov 2004 | A1 |
20040249627 | Mirkin | Dec 2004 | A1 |
20050008343 | Frohlich et al. | Jan 2005 | A1 |
20050057524 | Hill et al. | Mar 2005 | A1 |
20050193321 | Iwema et al. | Sep 2005 | A1 |
20050204295 | Voorhees et al. | Sep 2005 | A1 |
20050270269 | Tokkonen | Dec 2005 | A1 |
20060005151 | Altman | Jan 2006 | A1 |
20060026536 | Hotelling et al. | Feb 2006 | A1 |
20060064640 | Forlines et al. | Mar 2006 | A1 |
20060072137 | Nishikawa et al. | Apr 2006 | A1 |
20060119588 | Yoon et al. | Jun 2006 | A1 |
20060132460 | Kolmykov-Zotov et al. | Jun 2006 | A1 |
20060197756 | Sun | Sep 2006 | A1 |
20060253803 | Backlund | Nov 2006 | A1 |
20060256088 | Kong | Nov 2006 | A1 |
20070061753 | Ng et al. | Mar 2007 | A1 |
20070125633 | Boillot | Jun 2007 | A1 |
20070229466 | Peng et al. | Oct 2007 | A1 |
20070234235 | Scott | Oct 2007 | A1 |
20070260981 | Kim et al. | Nov 2007 | A1 |
20070294644 | Yost | Dec 2007 | A1 |
20080048997 | Gillespie et al. | Feb 2008 | A1 |
20080084400 | Rosenberg | Apr 2008 | A1 |
20080148177 | Lang et al. | Jun 2008 | A1 |
20080165141 | Christie | Jul 2008 | A1 |
20080165142 | Kocienda et al. | Jul 2008 | A1 |
20080174570 | Jobs et al. | Jul 2008 | A1 |
20080184290 | Tapuska | Jul 2008 | A1 |
20080195979 | Souza et al. | Aug 2008 | A1 |
20080259040 | Ording et al. | Oct 2008 | A1 |
20080309632 | Westerman et al. | Dec 2008 | A1 |
20090049398 | Ahn | Feb 2009 | A1 |
20090058830 | Herz et al. | Mar 2009 | A1 |
20090087095 | Webb | Apr 2009 | A1 |
20090109182 | Fyke et al. | Apr 2009 | A1 |
20090113353 | Bansal et al. | Apr 2009 | A1 |
20090187846 | Paasovaara | Jul 2009 | A1 |
20090189862 | Viberg | Jul 2009 | A1 |
20090204888 | Miyamoto | Aug 2009 | A1 |
20090217158 | Bailey | Aug 2009 | A1 |
20090228792 | van Os et al. | Sep 2009 | A1 |
20090228842 | Westerman et al. | Sep 2009 | A1 |
20090237421 | Kim et al. | Sep 2009 | A1 |
20090249232 | Lundy et al. | Oct 2009 | A1 |
20090249257 | Bove et al. | Oct 2009 | A1 |
20100066764 | Refai | Mar 2010 | A1 |
20100159892 | Dunnam et al. | Jun 2010 | A1 |
20100171713 | Kwok et al. | Jul 2010 | A1 |
20100205575 | Arora | Aug 2010 | A1 |
20100235726 | Ording et al. | Sep 2010 | A1 |
20100235729 | Kocienda et al. | Sep 2010 | A1 |
20100245261 | Karlsson | Sep 2010 | A1 |
20100295798 | Nicholson et al. | Nov 2010 | A1 |
20100302281 | Kim | Dec 2010 | A1 |
20100313126 | Jung et al. | Dec 2010 | A1 |
20100328209 | Nakao | Dec 2010 | A1 |
20100328317 | Lindfors | Dec 2010 | A1 |
20110010668 | Feldstein et al. | Jan 2011 | A1 |
20110029917 | Um | Feb 2011 | A1 |
20110035209 | MacFarlane | Feb 2011 | A1 |
20110080341 | Helmes et al. | Apr 2011 | A1 |
20110109581 | Ozawa et al. | May 2011 | A1 |
20110134029 | Park et al. | Jun 2011 | A1 |
20110157028 | Stallings et al. | Jun 2011 | A1 |
20110310026 | Davis et al. | Dec 2011 | A1 |
20120306772 | Tan | Dec 2012 | A1 |
Number | Date | Country |
---|---|---|
WO 2010135127 | Nov 2010 | WO |
Entry |
---|
Hillebrand, “How to Make your Windows Mobile Touch Screen Finger-Friendly,” Published Date: Apr. 22, 2008, <http://www.mobilitysite.com/2008/04/how-to-make-your-windows-mobile-touch-screen-finger-friendly/>, 4 pages (retrieved Mar. 24, 2010). |
Stoup, “The New 12″ MacBook will have an iPhone-Like Interface,” Published Date: Jan. 17, 2007, <http://www.applematters.com/article/the-new-12-macbook-will-have-an-iphone-like-interface/>, 7 pages (retrieved Jan. 22, 2010). |
“My-T-Touch for Windows Indestructible Keyboards and Indispensable Utilites, Version 1.78, Release 4, User's Guide,” Released Date: Nov. 24, 2009, <http://www.imgpresents.com/myttouch/guide/mtta4.pdf, 187 pages (retrieved Jan. 22, 2010). |
Apple, “Vision,” <http://www.apple.com/accessibility/iphone/vision.html>, 8 pages, Accessed Aug. 9, 2011. |
“iPhone OS 3.0: How to cut, copy and paste text and images,” <http://www.iphonic.tv/2009/06/iphone—os—30—how—to—cut—copy—a.html>, accessed Jun. 18, 2010, 11 pages. |
Microsoft Office, “Select text by using the mouse,” <http://office.microsoft.com/en-us/word-help/select-text-HA010096402.aspx#BM1>, accessed Jun. 18, 2010, 4 pages. |
Olwal et al., “Rubbing and Tapping for Precise and Rapid Selection on Touch-Screen Displays,” Proceedings of CHI 2008 (SIGCHI Conference on Human Factors in Computing Systems), Florence, Italy, Apr. 5-10, 2008, pp. 295-304. |
PCWorld, “Magnifying Glass Pro description, Database Downloads List by 30 Day Change,” <http://www.pcworld.com/downloads/file/fid,71819-order,4-c,database/description.html>, Added Feb. 1, 2010, pp. 1-4, Downloaded Mar. 31, 2011. |
Ramos et al., “Zliding: Fluid Zooming and Sliding for High Precision Parameter Manipulation,” UIST '05, Oct. 23-27, 2005, pp. 143-152. |
ThomasNet News, “Touch Sensor Features Gesture Recognition Technology,” <http://news.thomasnet.com/fullstory/543504>, Published Date: Apr. 28, 2008, 3 pages. |
“Virtual On-Screen Keyboard for any Taste,” <http://hot-virtual-keyboard.com/>, Published Date: Dec. 15, 2009, 1 page. |
European Search Report received for European Patent Application No. 12822739.4, Mailed: Oct. 30, 2014, 3 Pages. |
Office Action received for European Patent Application No. 12822739.4, Mailed: Nov. 18, 2014, 5 Pages. |
Number | Date | Country | |
---|---|---|---|
20110239153 A1 | Sep 2011 | US |