Gesture recognition method and touch system incorporating the same

Information

  • Patent Grant
  • 8325134
  • Patent Number
    8,325,134
  • Date Filed
    Monday, January 31, 2011
    14 years ago
  • Date Issued
    Tuesday, December 4, 2012
    12 years ago
Abstract
A gesture recognition method includes detecting multiple pointers in close proximity to a touch surface to determine if the multiple pointers are being used to perform a known gesture. When the multiple pointers are being used to perform a known gesture, executing a command associated with the gesture. A touch system incorporating the gesture recognition method is also provided.
Description
FIELD OF THE INVENTION

The present invention relates generally to touch systems and in particular to a gesture recognition method and touch system incorporating the same.


BACKGROUND OF THE INVENTION

Touch systems are well known in the art and typically include a touch screen having a touch surface on which contacts are made using a pointer in order to generate user input. Pointer contacts with the touch surface are detected and are used to generate corresponding output depending on areas of the contact surface where the contacts are made. There are basically two general types of touch systems available and they can be broadly classified as “active” touch systems and “passive” touch systems.


Active touch systems allow a user to generate user input by contacting the touch surface with a special pointer that usually requires some form of on-board power source, typically batteries. The special pointer emits signals such as infrared light, visible light, ultrasonic frequencies, electromagnetic frequencies, etc. that activate the touch surface.


Passive touch systems allow a user to generate user input by contacting the touch surface with a passive pointer and do not require the use of a special pointer in order to activate the touch surface. The pointer can be a finger, a cylinder of some material, or any suitable object that can be used to contact some predetermined area of interest on the touch surface.


Passive touch systems provide advantages over active touch systems in that any suitable pointing device, including a user's finger, can be used as a pointer to contact the touch surface. As a result, user input can easily be generated. Also, since special active pointers are not necessary in passive touch systems, battery power levels and/or pointer damage, theft, or misplacement are of no concern to users.


For example, U.S. patent application Ser. No. 09/610,481 filed on Jul. 5, 2000 and International PCT Application No. PCT/CA01/00980 filed on Jul. 5, 2001 and published under No. WO 02/03316 on Jan. 10, 2002, assigned to SMART Technologies Inc., assignee of the present invention, disclose a camera-based touch system comprising a touch screen that includes a passive touch surface on which a computer-generated image is presented. A rectangular bezel or frame surrounds the touch surface and supports digital cameras at its corners. The digital cameras have overlapping fields of view that encompass and look across the touch surface. The digital cameras acquire images looking across the touch surface from different locations and generate image data. Image data acquired by the digital cameras is processed by digital signal processors associated with the digital cameras to determine if a pointer exists in the captured image data. When it is determined that a pointer exists in the captured image data, the digital signal processors generate pointer information packets (PIPs) and convey the PIPs to a master controller. Each PIP includes a header portion, a data portion and a checksum. The data portion includes a pointer ID field that stores a pointer identifier to allow multiple pointers to be tracked. The data portion also includes a pointer location parameter that identifies a pointer x-position and a pointer tip parameter that identifies a pointer z-position. A contact state field stores a value indicating whether the pointer is in or out of contact with the touch surface allowing pointer hover to be detected.


Upon receipt of the PIPs, the master controller processes the PIPs using triangulation to determine the location of each pointer in the captured images relative to the touch surface in (x,y) coordinates. In this manner, as PIPs are generated in response to captured images, the position and movement of pointers over the touch surface can be tracked. The pointer location data generated by the master controller is conveyed to a computer executing one or more application programs. The computer uses the pointer location data to update the computer-generated image that is presented on the touch surface. Pointer contacts on and pointer movement over the touch surface can therefore be recorded as writing or drawing or used to control execution of application programs executed by the computer.


As will be appreciated, since digital cameras at the corners of the bezels are used to capture image data, the touch system is able to determine when multiple pointers contact and move across the touch surface. This of course provides for enhanced functionality as compared to analog resistive touch systems that are only able to track a single pointer. Although enhanced functionality is provided by the above-described camera-based touch system, to-date, this enhanced functionally has not been fully exploited. It is therefore an object of the present invention to provide a novel gesture recognition method and touch system incorporating the same.


SUMMARY OF THE INVENTION

According to one aspect of the present invention there is provided a gesture recognition method comprising the steps of:


displaying an image on a touch surface;


detecting pointer contacts on said touch surface and examining said pointer contacts to recognize multiple pointer contacts representing a gesture; and


when multiple pointer contacts representing a gesture occur, updating the displayed image in accordance with said gesture.


Multiple pointer contacts representing a gesture include multiple finger contacts on the touch surface, a finger contact on the touch surface and an object contact on the touch surface and multiple object contacts on the touch surface.


In one aspect, the gesture is a right-click event and is represented by a first pointer contact on a displayed application, and a subsequent second pointer contact that occurs within a threshold distance of the first pointer contact and while the first pointer contact is maintained. In another aspect, the gesture is a scroll event and is represented by simultaneous pointer contacts on the touch surface.


According to another aspect of the present invention there is provided a gesture recognition method comprising the steps of:


detecting multiple pointers in close proximity to a touch surface to determine if said multiple pointers are being used to perform a known gesture; and


when said multiple pointers are being used to perform a known gesture, executing a command associated with said gesture.


Preferably, during the detecting, pointer contacts with or close pointer hovers over the touch surface are detected to determine if a known gesture is being performed and specifically if one of a number of known gestures is being performed, each known gesture being associated with a different command. In a preferred embodiment, the movement of the multiple pointers relative to the touch surface and/or the pointer type determines the gesture being performed.


According to yet another aspect of the present invention there is provided an input detection method in an interactive system capable of detecting movement of multiple pointers generally simultaneously within an input region, said method comprising the steps of:


capturing images looking generally across said input region;


analyzing said images to detect multiple pointers within said input region;


when multiple pointers are detected, examining data associated with said multiple pointers to determine if the data represents an input gesture; and


when the data represents an input gesture, executing a command corresponding to the recognized input gesture.


According to still yet another aspect of the present invention there is provided a touch system comprising:


a touch surface to be contacted by at least one pointer;


at least one imaging device having a field of view looking generally across said touch surface; and


at least one processor communicating with said at least one imaging device and analyzing images acquired by said at least one imaging device to determine the location on said touch surface where pointer contacts are made, when said touch surface is contacted by multiple pointers, said processor examining said multiple pointer contacts to determine if said multiple pointer contacts represent a gesture and when said multiple pointer contacts represent a gesture, said processor executing a command associated with said gesture.


According to still yet another aspect of the present invention there is provided an interactive input system comprising:


at least one imaging device having an input region within its field of view into which one or more pointers is moved to generate user input; and


at least one processor communicating with said at least one imaging device and analyzing each image acquired by said at least one imaging device to determine the action of pointers in said input region, said at least one processor determining when multiple pointer actions within said input region represent a gesture, when said multiple pointer actions represent a gesture, said at least one processor executing a command corresponding to said gesture.


According to still yet another aspect of the present invention there is provided in an interactive touch system, a method of simulating a right-click mouse event comprising the steps of:


detecting a first pointer contact on a touch surface over a displayed application that represents a left-click mouse event;


detecting a second pointer contact on said touch surface that occurs within a threshold period of time following said first pointer contact and within a threshold distance of said first pointer contact; and


generating a right-click mouse event in response to said detected second pointer contact.


The present invention provides advantages in that since gestures represented by multiple pointer contacts on and/or movement over the touch surface are detected and corresponding commands generated, enhanced touch system functionality is provided.





BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described more fully with reference to the accompanying drawings in which:



FIG. 1 is a schematic diagram of a camera-based touch system in accordance with the present invention;



FIG. 2 is a front elevation view of a touch screen forming part of the touch system of FIG. 1;



FIGS. 3
a to 3d are front perspective views of the touch screen of FIG. 2 showing an input right-click gesture; and



FIGS. 4
a to 4f are front perspective views of the touch screen of FIG. 2 showing input up/down and left/right scroll gestures.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Turning now to FIG. 1, a camera-based touch system in accordance with the present invention is shown and is generally identified by reference numeral 50. Camera-based touch system 50 is similar to that disclosed in International PCT Application Serial No. WO 02/03316, assigned to SMART Technologies Inc., assignee of the present invention, the contents of which are incorporated herein by reference. As can be seen, touch system 50 includes a touch screen 52 coupled to a digital signal processor (DSP) based master controller 54. Master controller 54 is also coupled to a computer 56. Computer 56 executes one or more application programs and provides computer-generated image output that is displayed on the touch screen 52. The coordinate system of the touch system 52 is mapped to the coordinate system of the computer. The touch screen 52, master controller 54 and computer 56 form a closed-loop so that pointer hover or contacts with and pointer movement over or above the touch screen 52 can be recorded as writing or drawing or used to control execution of application programs executed by the computer 56.



FIG. 2 better illustrates the touch screen 52. Touch screen 52 in the present embodiment includes a high-resolution display device such as a plasma display 58, the front surface of which defines a touch surface 60. The touch surface 60 is bordered by an illuminated bezel or frame 62 coupled to the display device. Illuminated bezel 62 is of the type disclosed in U.S. patent application Ser. No. 10/354,168 filed on Jan. 30, 2003 and includes elongate side frame assemblies 64 that are coupled to the sides of the plasma display 58. Each side frame assembly 64 accommodates a light source (not shown) that projects infrared backlighting across the touch surface 60. The ends of the side frame assemblies 64 are joined by corner pieces 68 that house DSP-based CMOS digital cameras 70. Each digital camera 70 is mounted within its respective corner piece 68 so that its field of view encompasses and looks across the entire touch surface 60.


During operation, the digital cameras 70 acquire images of the touch surface 60 and generate image data. The acquired image data is processed by digital signal processors associated with the digital cameras 70 to determine if a pointer exists in the captured images. When it is determined that one or more pointers exist in the acquired image data, the digital signal processors of the digital cameras 70 generate pointer information packets (PIPs) and convey the PIPs to the digital signal processor (DSP) based master controller 54. Each PIP includes a header portion, a data portion and a checksum. The data portion includes a pointer ID field that stores a pointer identifier to allow multiple pointers to be tracked. The data portion also includes a pointer location parameter that identifies a pointer x-position and a pointer tip parameter that identifies a pointer z-position. A contact state field stores a value indicating whether the pointer is in or out of contact with the touch surface 60 allowing pointer hover to be detected.


Upon receipt of the PIPs, the master controller 54 processes the PIPs using triangulation to determine the location of each pointer in the captured images relative to the touch surface 60 in (x,y) coordinates. In this manner, as PIPs are generated in response to captured images, the position and movement of pointers over the touch surface 60 can be tracked. Since image data is processed to detect the existence of one or more pointers, the pointers may take any suitable form such as for example, a user's finger, a cylinder of material, a passive or active pen tool or erase tool or other appropriate object. Specifics of the manner by which the image data is acquired by the digital cameras 70 and processed by the master controller 54 are described in International PCT Application No. PCT/CA01/00980 filed on Jul. 5, 2001 and published under No. WO 02/03316 on Jan. 10, 2002, the contents of which are incorporated herein by reference. Accordingly, such specifics will not be described further herein.


The master controller 54 outputs generated pointer data to the computer 56 that identifies the location of each pointer relative to the touch surface as each pointer approaches and/or contacts and moves over the touch surface 60. A driver loaded on the computer 56 receives the pointer data and examines the pointer data to determine if the pointer data has been generated in response to a known input gesture stored in a gesture library. Specifically, the driver examines the pointer data to detect the existence of multiple pointers in captured images and then examines the nature of the multiple pointers to determine if a known gesture has been performed such as for example a right-click gesture, a scroll gesture, a rotate gesture etc. When a gesture has been performed, the driver generates a command (event) that is associated with the determined gesture and conveys the command to the active application program being executed by the computer 56.


Turning now to FIGS. 3a to 4f, examples of gestures that can be recognized by the touch system and the resulting actions that are performed in response to the recognized gestures are shown.


Intuitive Right-Click Gesture



FIGS. 3
a to 3d illustrate an intuitive right-click gesture. When a user contacts the touch surface 60 with a finger over an application displayed on the touch surface, the driver recognizes the contact as a left-click mouse event and injects the left-click mouse event into the application. If the user subsequently contacts the touch surface 60 with another finger while maintaining the contact with the one finger and the subsequent contact is to the right of and close to the initial contact, the driver recognizes the second touch surface contact as a right-click gesture and injects a right-click event into the application. In response to the right-click event, the application opens and displays a drop down menu (not shown). As will be appreciated, this enables a user to invoke a right-click action using a hand gesture that is similar to the action performed when invoking a right-click action using a mouse. Although, FIGS. 3a to 3d show the intuitive right-click gesture being performed using two fingers on the same hand, it will be appreciated that the right-click gesture can be performed using a finger on different hands.


Scroll Up/Down and Left/Right Gesture



FIGS. 4
a to 4e illustrate up/down and left/right scroll gestures. If the user contacts the touch surface 60 with a pair of fingers simultaneously over an application window displayed on the touch surface and the fingers are closely and generally horizontally spaced, the driver recognizes the simultaneous finger contacts as a scroll gesture and injects a scroll event into the application. Pointer position data conveyed to the application by the driver in response to subsequent vertical movement of the fingers is interpreted by the application either as scroll up or scroll down commands. In response to the scroll up or down commands, the application moves information presented within the application window in the direction of the vertical movement. Pointer position data conveyed to the application by the driver in response to subsequent horizontal movement of the fingers is interpreted by the application as scroll to side commands. In response to the scroll to side commands, the application moves information displayed within the application window to the side corresponding to the direction of the horizontal movement. Although FIGS. 4a to 4f show the scroll gestures being performed using two fingers on the same hand, it will be appreciated that the scroll gestures can be performed using a finger on different hands.


Although not illustrated, a number of other gestures can be recognized by the driver and used to generate commands to control an application being executed by the computer 56. Examples of such other gestures will now be described.


Page Up/Down Gesture


If the user contacts the touch surface 60 with three fingers simultaneously over an application window displayed on the touch surface and the three fingers are closely and generally horizontally spaced, the driver recognizes the simultaneous finger contacts as a page gesture and injects a page event into the application. Pointer position data conveyed to the application by the driver in response to subsequent vertical movement of the fingers is interpreted by the application as page up or page down commands depending on the direction of the vertical movement. In response to the page up or page down commands, the application moves information displayed within the window in the appropriate direction.


Rotate Gesture


If the user contacts the touch surface 60 over an object displayed within an application window with one finger and then subsequently contacts the touch surface with another finger and moves that other finger in an arc while maintaining the touch surface contact with the one finger, the driver recognizes the arcuate movement of the second finger as a rotate gesture. The driver in turn injects a rotate command into the application causing the application to rotate the object about the contact point defined by the first finger in the direction of the arc and by an amount equivalent to the path of the arc.


Zoom Gesture


If the user contacts the touch surface 60 with a pair of closely spaced fingers simultaneously over an application window and expands the distance between the fingers in a generally horizontal direction, the driver recognizes the finger movement as a zoom-out gesture. The driver in turn injects a zoom-out command into the application causing the application to expand the size of the information presented in the application window. If the user contacts the touch surface 60 with a pair of spaced fingers simultaneously over an application window and moves the fingers in a generally horizontal direction towards one another, the driver recognizes the finger movement as a zoom-in gesture. The driver in turn injects a zoom-in command into the application causing the application to reduce the size of the information presented in the application window.


Alternatively, the zoom-out and zoom-in commands may be represented by other gestures. For example, if the user contacts the touch surface 60 with a clawed hand having its fingers bunched together over an application window and expands the hand by extending the fingers outwardly, the driver recognizes the finger movement as the zoom-out gesture.


If the user contacts the touch surface 60 with a generally flat hand having its fingers extended over an application window and contracts the hand by clawing the fingers inwardly to bunch them together, the driver recognizes the finger movement as the zoom-in gesture.


Expand Gesture


If the user contacts the touch surface 60 with a pair of closely spaced fingers simultaneously over an application window and expands the distance between the fingers in a generally diagonal direction, the driver recognizes the finger movement as an increase window size gesture. The driver in turn injects an increase window size command into the application causing the application to expand the size of the application window. If the user contacts the touch surface 60 with a pair of spaced fingers simultaneously over an application window and moves the fingers in a generally diagonal direction towards one another, the driver recognizes the finger movement as a decrease window size gesture. The driver in turn injects a decrease window size command into the application causing the application to reduce the size of the application window.


Icon Select and Open Gesture


If the user contacts the touch surface 60 with two closely spaced fingers simultaneously over an icon, the driver recognizes the finger contact as a double-click gesture. The driver in turn generates an open application command causing the desktop application running on the computer 56 to open the selected application.


Object/Window Move Gesture


If the user moves a pair of closely spaced fingers above the touch surface 60 and over an object displayed within an application window, the driver recognizes the hovering finger movement as a translate object gesture. The driver in turn injects a translate object command into the application causing the application to translate the displayed object in the direction of and by an amount equal to the distance the fingers are moved.


If the user moves three closely spaced fingers above the touch surface 60 and over an application window, the driver recognizes the hovering finger movement as a translate window gesture. The driver in turn generates a translate window command causing the desktop application running on the computer 56 to translate the application window in the direction of and by an amount equal to the distance the fingers are moved.


Although the above gestures are described as being recognized in response to multiple finger contacts or hovers, the same gestures can be recognized if other objects are used to perform the gestures. For example, multiple pen tools can be used to perform the gestures or alternatively a finger and a pen tool can be used to perform the gestures.


Also, recognized gestures may be enhanced using different pointer characteristics. For example, in the case of scroll gestures, the angle at which the pointers contact the touch surface 60 may be used to determine the rate at which the displayed information is scrolled. Pointers contacting the touch surface 60 at a steep angle may represent a slow scroll rate whereas pointers contacting the touch surface 60 at a shallow angle may represent a fast scroll rate.


If the touch system is able to differentiate between the type of pointers used to contact the touch surface 60 as is described in co-pending U.S. patent application Ser. No. 10/384,783 filed on Mar. 11, 2003 and/or is able to determine pointer characteristics as is described in co-pending U.S. patent application Ser. No. 10/294,917, filed on Nov. 15, 2002, the contents of which are incorporated herein by reference, different functionality can be assigned to similar gestures that are performed using different pointers. For example, in the case of the rotate gesture described above, if the same gesture is carried out using a finger to initially contact an object within the application window and a pen tool to describe the arc, the driver recognizes the finger contact and pen movement as a pattern fill gesture rather than a rotate gesture. A finger contact and subsequent closely spaced pen tool contact may represent a draw circle gesture rather than a scroll gesture and a finger contact and subsequent closely spaced eraser contact may represent an erase page gesture. As will be appreciated, being able to differentiate between multiple pointers brought into proximity with the touch surface 60 significantly increases the functions that may be invoked by performing the same gestures simply by using discrete pointers that can be differentiated.


Although the driver is described as examining the pointer data to determine if the pointer data is generated in response to a known gesture, it will be appreciated by those of skill in the art that if the active application being executed by the computer has the capability of recognizing gestures, the pointer data may be conveyed to the active application for gesture recognition.


If desired the touch surface 60 may be partitioned into multiple regions to enable multiple users to interact with the touch surface simultaneously without ambiguity between user input. In this case multiple contacts on or hovers over the touch surface that are beyond a threshold distance are treated as multiple user inputs. Multiple contacts on or hovers over the touch surface that are within the threshold distance are treated as multiple contacts made by a single user and are examined to determine if the multiple contacts represent a gesture.


Although preferred embodiments of the present invention have been described, those of skill in the art will appreciate that variations and modifications may be made without departing from the spirit and scope thereof as defined by the appended claims.

Claims
  • 1. An event generation method comprising: detecting multiple pointers brought into contact with a touch surface, the subsequent relative movement of said pointers along said touch surface and the pointer types; andgenerating an event based on the subsequent relative movement of said pointers along said touch surface and the pointer types.
  • 2. The method of claim 1 wherein said detecting comprises capturing images of the touch surface from different vantages using imaging devices that are aimed to look generally across the touch surface and processing the captured images to detect the subsequent relative movement of said pointers and the pointer types.
  • 3. The method of claim 2 wherein during said processing, the captured images are processed to detect movement of multiple pointers away from one another.
  • 4. The method of claim 2 wherein during said processing, the captured images are processed to detect movement of multiple pointers towards one another.
  • 5. The method of claim 1 wherein the event is a graphical object manipulation command.
  • 6. The method of claim 5 wherein the graphical object manipulation command is one of a graphical object resize command, a graphical object rotate command and a graphical object translate command.
  • 7. The method of claim 5 further comprising executing said graphical object manipulation command.
  • 8. The method of claim 7 wherein during said processing, the captured images are processed to detect movement of multiple pointers away from one another.
  • 9. The method of claim 7 wherein during said processing, the captured images are processed to detect movement of multiple pointers towards one another.
  • 10. The method of claim 7 wherein during said processing, the captured images are processed to detect movement of one pointer in a generally arcuate path about another pointer.
  • 11. The method of claim 1 wherein during said processing, the captured images are processed to detect movement of one pointer in a generally arcuate path about another pointer.
  • 12. An interactive input system comprising: at least one imaging device aimed to look generally across a touch surface; andprocessing structure processing image data captured by said at least one imaging device and being configured to: detect multiple pointers brought into contact with said touch surface, the subsequent relative movement of said pointers along said touch surface and the pointer types; andgenerate an event based on the subsequent relative movement of said pointers along said touch surface and the pointer types.
  • 13. The interactive input system of claim 12 wherein said processing structure generates said event when said pointers are moved along said touch surface away from one another.
  • 14. The interactive input system of claim 13 wherein the event is a graphical object manipulation command.
  • 15. The interactive input system of claim 12 wherein said processing structure generates said event when said pointers are moved along said touch surface towards one another.
  • 16. An event generation method comprising: detecting multiple pointers brought into contact with a touch surface, the relative positions of the pointer contacts, the subsequent relative movement of said pointers along said touch surface and the pointer types by processing images captured using imaging devices that are proximate to the touch surface and aimed to look generally across the touch surface to determine if a gesture has been input; andgenerating an event when an input gesture is determined.
  • 17. The method of claim 16 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if said pointers are moving towards one another.
  • 18. The method of claim 16 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if said pointers are moving away from one another.
  • 19. The method of claim 16 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if one pointer is moving in a generally arcuate path about another pointer.
  • 20. The method of claim 16 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if said pointers are moving in a generally similar direction.
  • 21. The method of claim 16 wherein said event is a graphical object manipulation command.
  • 22. The method of claim 21 wherein said graphical object manipulation command is one of a graphical object resize command, a graphical object rotate command and a graphical object translate command.
  • 23. The method of claim 21 further comprising executing said graphical object manipulation command.
  • 24. The method of claim 23 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if said pointers are moving towards one another.
  • 25. The method of claim 23 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if said pointers are moving away from one another.
  • 26. The method of claim 23 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if one pointer is moving in a generally arcuate path about another pointer.
  • 27. The method of claim 23 wherein during said detecting, the subsequent relative movement of said pointers is examined to determine if said pointers are moving in a generally similar direction.
  • 28. An event generation method comprising: capturing images of a touch surface from different vantages using imaging devices;processing the captured images to detect multiple pointers brought into contact with said touch surface and to recognize a gesture based on the pointer contact positions, the subsequent relative movement of the pointers along said touch surface and the pointer types; andgenerating an event when a gesture is recognized.
  • 29. The method of claim 28 wherein during said processing, the captured images are processed to detect movement of multiple pointers towards one another.
  • 30. The method of claim 28 wherein during said processing, the captured images are processed to detect movement of multiple pointers away from one another.
  • 31. The method of claim 28 wherein during said processing, the captured images are processed to detect movement of one pointer in a generally arcuate path about another pointer.
  • 32. The method of claim 28 wherein said event represents a graphical object manipulation command.
  • 33. The method of claim 32 wherein said graphical object manipulation command is one of a graphical object resize command, a graphical object rotate command and a graphical object translate command.
  • 34. The method of claim 33 wherein during said processing, captured the images are processed to detect movement of multiple pointers towards one another.
  • 35. The method of claim 33 wherein during said processing, the captured images are processed to detect movement of multiple pointers away from one another.
  • 36. The method of claim 33 wherein during said processing, the captured images are processed to detect movement of one pointer in a generally arcuate path about another pointer.
  • 37. The method of claim 32 further comprising executing said graphical object manipulation command.
Parent Case Info

This application is a continuation of U.S. patent application Ser. No. 12/646,081, filed Dec. 23, 2009, now U.S. Pat. No. 7,880,720, issued Feb. 1, 2011, which is a continuation of U.S. patent application Ser. No. 12/189,579, filed Aug. 11, 2008, now U.S. Pat. No. 7,643,006, issued Jan. 5, 2010, which is a continuation of U.S. patent application Ser. No. 10/662,813, filed Sep. 16, 2003, now U.S. Pat. No. 7,411,575, issued Aug. 12, 2008, the contents of all incorporated herein by reference.

US Referenced Citations (220)
Number Name Date Kind
2769374 Sick Nov 1956 A
3025406 Stewart et al. Mar 1962 A
3128340 Harmon Apr 1964 A
3187185 Milnes Jun 1965 A
3360654 Muller Dec 1967 A
3478220 Milroy Nov 1969 A
3613066 Cooreman Oct 1971 A
3764813 Clement et al. Oct 1973 A
3775560 Ebeling et al. Nov 1973 A
3857022 Rebane et al. Dec 1974 A
3860754 Johnson et al. Jan 1975 A
4243879 Carroll et al. Jan 1981 A
4420261 Barlow et al. Dec 1983 A
4459476 Weissmueller et al. Jul 1984 A
4468694 Edgar Aug 1984 A
4550250 Mueller et al. Oct 1985 A
4553842 Griffin Nov 1985 A
4558313 Garwin et al. Dec 1985 A
4639720 Rympalski et al. Jan 1987 A
4672364 Lucas Jun 1987 A
4673918 Adler et al. Jun 1987 A
4703316 Sherbeck Oct 1987 A
4710760 Kasday Dec 1987 A
4746770 McAvinney May 1988 A
4766424 Adler et al. Aug 1988 A
4811004 Person et al. Mar 1989 A
4822145 Staelin Apr 1989 A
4851664 Rieger Jul 1989 A
4868551 Arditty et al. Sep 1989 A
4888479 Tamaru Dec 1989 A
4893120 Doering et al. Jan 1990 A
4916308 Meadows Apr 1990 A
4928094 Smith May 1990 A
4943806 Masters et al. Jul 1990 A
4990901 Beiswenger Feb 1991 A
5025411 Tallman et al. Jun 1991 A
5103085 Zimmerman Apr 1992 A
5105186 May Apr 1992 A
5148015 Dolan Sep 1992 A
5162783 Moreno Nov 1992 A
5164714 Wehrer Nov 1992 A
5179369 Person et al. Jan 1993 A
5196836 Williams Mar 1993 A
5239152 Caldwell et al. Aug 1993 A
5272470 Zetts Dec 1993 A
5359155 Helser Oct 1994 A
5422494 West et al. Jun 1995 A
5448263 Martin Sep 1995 A
5457289 Huang et al. Oct 1995 A
5484966 Segen Jan 1996 A
5528263 Platzker et al. Jun 1996 A
5554828 Primm Sep 1996 A
5591945 Kent Jan 1997 A
5698845 Kodama et al. Dec 1997 A
5729704 Stone et al. Mar 1998 A
5736686 Perret, Jr. et al. Apr 1998 A
5739479 Davis-Cannon Apr 1998 A
5745116 Pisutha-Arnond Apr 1998 A
5771039 Ditzik Jun 1998 A
5784054 Armstrong et al. Jul 1998 A
5785439 Bowen Jul 1998 A
5786810 Knox et al. Jul 1998 A
5793361 Kahn et al. Aug 1998 A
5804773 Wilson et al. Sep 1998 A
5818424 Korth Oct 1998 A
5819201 Degraaf Oct 1998 A
5825352 Bisset et al. Oct 1998 A
5854491 Pryor et al. Dec 1998 A
5909210 Knox et al. Jun 1999 A
5940065 Babb et al. Aug 1999 A
5990874 Tsumura Nov 1999 A
6043805 Hsieh Mar 2000 A
6076041 Watanabe Jun 2000 A
6091406 Kambara et al. Jul 2000 A
6104387 Chery et al. Aug 2000 A
6144366 Numazaki et al. Nov 2000 A
6215477 Morrison et al. Apr 2001 B1
6222175 Krymski Apr 2001 B1
6232962 Davis et al. May 2001 B1
6320597 Ieperen Nov 2001 B1
6326954 Van Ieperen Dec 2001 B1
6346966 Toh Feb 2002 B1
6352351 Ogasahara et al. Mar 2002 B1
6362468 Murakami et al. Mar 2002 B1
6377228 Jenkin et al. Apr 2002 B1
6384743 Vanderheiden May 2002 B1
6429857 Masters et al. Aug 2002 B1
6480187 Sano et al. Nov 2002 B1
6504532 Ogasahara et al. Jan 2003 B1
6512513 Fleck et al. Jan 2003 B2
6532006 Takekawa et al. Mar 2003 B1
6540366 Keenan et al. Apr 2003 B2
6540679 Slayton et al. Apr 2003 B2
6570103 Saka et al. May 2003 B1
6587099 Takekawa Jul 2003 B2
6590568 Astala et al. Jul 2003 B1
6597508 Seino et al. Jul 2003 B2
6603867 Sugino et al. Aug 2003 B1
6614422 Rafii et al. Sep 2003 B1
6624833 Kumar et al. Sep 2003 B1
6650318 Arnon Nov 2003 B1
6654001 Su Nov 2003 B1
6714311 Hashimoto Mar 2004 B2
6720949 Pryor et al. Apr 2004 B1
6738051 Boyd et al. May 2004 B2
6760009 Omura Jul 2004 B2
6778207 Lee et al. Aug 2004 B1
6802611 Chu Oct 2004 B2
6828959 Takekawa et al. Dec 2004 B2
6829372 Fujioka Dec 2004 B2
6927384 Reime et al. Aug 2005 B2
7002555 Jacobsen et al. Feb 2006 B1
7030861 Westerman et al. Apr 2006 B1
7057647 Monroe Jun 2006 B1
7058204 Hildreth et al. Jun 2006 B2
7075054 Iwamoto et al. Jul 2006 B2
7084857 Lieberman et al. Aug 2006 B2
7084859 Pryor Aug 2006 B1
7151533 Van Ieperen Dec 2006 B2
7190348 Kennedy et al. Mar 2007 B2
7193608 Stuerzlinger Mar 2007 B2
7227526 Hildreth et al. Jun 2007 B2
7236162 Morrison et al. Jun 2007 B2
7237937 Kawashima et al. Jul 2007 B2
7242388 Lieberman et al. Jul 2007 B2
7265748 Ryynanen Sep 2007 B2
7268692 Lieberman Sep 2007 B1
7283126 Leung Oct 2007 B2
7283128 Sato Oct 2007 B2
7289113 Martin Oct 2007 B2
7302156 Lieberman et al. Nov 2007 B1
7305368 Lieberman et al. Dec 2007 B2
7330184 Leung Feb 2008 B2
7333094 Lieberman et al. Feb 2008 B2
7333095 Lieberman et al. Feb 2008 B1
7372456 McLintock May 2008 B2
7375720 Tanaka May 2008 B2
RE40368 Arnon Jun 2008 E
7411575 Hill et al. Aug 2008 B2
7414617 Ogawa Aug 2008 B2
7479949 Jobs et al. Jan 2009 B2
7492357 Morrison et al. Feb 2009 B2
7499037 Lube Mar 2009 B2
7538759 Newton May 2009 B2
7559664 Walleman et al. Jul 2009 B1
7643006 Hill et al. Jan 2010 B2
20010030668 Erten et al. Oct 2001 A1
20010050677 Tosaya Dec 2001 A1
20010055006 Sano et al. Dec 2001 A1
20020008692 Omura et al. Jan 2002 A1
20020015159 Hashimoto Feb 2002 A1
20020041327 Hildreth et al. Apr 2002 A1
20020064382 Hildreth et al. May 2002 A1
20020075243 Newton Jun 2002 A1
20020118177 Newton Aug 2002 A1
20020145595 Satoh Oct 2002 A1
20030137494 Tulbert Jul 2003 A1
20030156118 Ayinde Aug 2003 A1
20030161524 King Aug 2003 A1
20030210803 Kaneda et al. Nov 2003 A1
20030227492 Wilde et al. Dec 2003 A1
20040001144 McCharles et al. Jan 2004 A1
20040012573 Morrison et al. Jan 2004 A1
20040032401 Nakazawa et al. Feb 2004 A1
20040051709 Ogawa et al. Mar 2004 A1
20040071363 Kouri et al. Apr 2004 A1
20040125086 Hagermoser et al. Jul 2004 A1
20040201575 Morrison Oct 2004 A1
20040204129 Payne et al. Oct 2004 A1
20040218479 Iwamoto et al. Nov 2004 A1
20040221265 Leung et al. Nov 2004 A1
20050077452 Morrison et al. Apr 2005 A1
20050104860 McCreary et al. May 2005 A1
20050128190 Ryynanen Jun 2005 A1
20050156900 Hill et al. Jul 2005 A1
20050241929 Auger et al. Nov 2005 A1
20050243070 Ung et al. Nov 2005 A1
20050248539 Morrison et al. Nov 2005 A1
20050248540 Newton Nov 2005 A1
20050270781 Marks Dec 2005 A1
20060012579 Sato Jan 2006 A1
20060022962 Morrison et al. Feb 2006 A1
20060028456 Kang Feb 2006 A1
20060034486 Morrison et al. Feb 2006 A1
20060152500 Weng Jul 2006 A1
20060170658 Nakamura et al. Aug 2006 A1
20060192799 Vega et al. Aug 2006 A1
20060197749 Popovich Sep 2006 A1
20060244734 Hill et al. Nov 2006 A1
20060279558 Van Delden et al. Dec 2006 A1
20070002028 Morrison et al. Jan 2007 A1
20070019103 Lieberman et al. Jan 2007 A1
20070089915 Ogawa et al. Apr 2007 A1
20070152984 Ording et al. Jul 2007 A1
20070152986 Ogawa et al. Jul 2007 A1
20070165007 Morrison et al. Jul 2007 A1
20070167709 Slayton Jul 2007 A1
20070205994 van Ieperen Sep 2007 A1
20070269107 Iwai et al. Nov 2007 A1
20070273842 Morrison Nov 2007 A1
20070290996 Ting Dec 2007 A1
20070291125 Marquet Dec 2007 A1
20080029691 Han Feb 2008 A1
20080042999 Martin Feb 2008 A1
20080055262 Wu et al. Mar 2008 A1
20080055267 Wu et al. Mar 2008 A1
20080062140 Hotelling et al. Mar 2008 A1
20080068352 Worthington et al. Mar 2008 A1
20080083602 Auger et al. Apr 2008 A1
20080106706 Holmgren et al. May 2008 A1
20080122803 Izadi et al. May 2008 A1
20080259050 Lin et al. Oct 2008 A1
20080259052 Lin et al. Oct 2008 A1
20090058832 Newton Mar 2009 A1
20090058833 Newton Mar 2009 A1
20090109194 Weng Apr 2009 A1
20090146972 Morrison et al. Jun 2009 A1
20090303187 Pallakoff Dec 2009 A1
20100182277 Nakajima et al. Jul 2010 A1
20110234638 Hill et al. Sep 2011 A1
Foreign Referenced Citations (110)
Number Date Country
2003233728 Dec 2003 AU
2006243730 Nov 2006 AU
2058219 Apr 1993 CA
2367864 Apr 1993 CA
2219886 Apr 1999 CA
2251221 Apr 1999 CA
2267733 Oct 1999 CA
2268208 Oct 1999 CA
2252302 Apr 2000 CA
2350152 Jun 2001 CA
2341918 Sep 2002 CA
2386094 Dec 2002 CA
2372868 Aug 2003 CA
2390503 Dec 2003 CA
2390506 Dec 2003 CA
2432770 Dec 2003 CA
2448603 May 2004 CA
2453873 Jul 2004 CA
2460449 Sep 2004 CA
2521418 Oct 2004 CA
2481396 Mar 2005 CA
2491582 Jul 2005 CA
2563566 Nov 2005 CA
2564262 Nov 2005 CA
2501214 Sep 2006 CA
2606863 Nov 2006 CA
2580046 Sep 2007 CA
1310126 Aug 2001 CN
1784649 Jun 2006 CN
101019096 Aug 2007 CN
101023582 Aug 2007 CN
1440539 Sep 2009 CN
3836429 May 1990 DE
60124549 Sep 2007 DE
0125068 Nov 1984 EP
0420335 Apr 1991 EP
0897161 Feb 1999 EP
0911721 Apr 1999 EP
1059605 Dec 2000 EP
1262909 Dec 2002 EP
1739528 Jan 2003 EP
1739529 Jan 2003 EP
1420335 May 2004 EP
1457870 Sep 2004 EP
1471459 Oct 2004 EP
1517228 Mar 2005 EP
1550940 Jun 2005 EP
1611503 Jan 2006 EP
1674977 Jun 2006 EP
1741186 Jan 2007 EP
1766501 Mar 2007 EP
1830248 Sep 2007 EP
1877893 Jan 2008 EP
2 279 823 Sep 2007 ES
1575420 Sep 1980 GB
2 176 282 May 1986 GB
2 263 765 Aug 1993 GB
62-005428 Jan 1987 JP
63-223819 Sep 1988 JP
03-244017 Oct 1991 JP
06-110608 Apr 1994 JP
09-146708 Jun 1997 JP
10-105324 Apr 1998 JP
10-222646 Aug 1998 JP
11-203042 Jul 1999 JP
11-212692 Aug 1999 JP
2000-163193 Jun 2000 JP
2001-142642 May 2001 JP
2001-282456 Oct 2001 JP
2002-055770 Feb 2002 JP
2003-65716 Mar 2003 JP
2003-167669 Jun 2003 JP
2003-167759 Jun 2003 JP
2003-173237 Jun 2003 JP
2005-108211 Apr 2005 JP
2005-182423 Jul 2005 JP
2005-202950 Jul 2005 JP
9807112 Feb 1998 WO
0124157 Apr 2001 WO
0131570 May 2001 WO
0163550 Aug 2001 WO
0169365 Sep 2001 WO
0191043 Nov 2001 WO
0203316 Jan 2002 WO
0208881 Jan 2002 WO
03054681 Jul 2003 WO
03104887 Dec 2003 WO
2004072843 Aug 2004 WO
2004090706 Oct 2004 WO
2004102523 Nov 2004 WO
2004104810 Dec 2004 WO
2005031554 Apr 2005 WO
2005034027 Apr 2005 WO
2005107072 Nov 2005 WO
2006002544 Jan 2006 WO
2006092058 Sep 2006 WO
2006095320 Sep 2006 WO
2006096962 Sep 2006 WO
2006116869 Nov 2006 WO
2007019600 Feb 2007 WO
2007037809 Apr 2007 WO
2007079590 Jul 2007 WO
2007132033 Nov 2007 WO
2007134456 Nov 2007 WO
2008128096 Oct 2008 WO
2009029764 Mar 2009 WO
2009029767 Mar 2009 WO
2009146544 Dec 2009 WO
2010051633 May 2010 WO
20100512633 May 2010 WO
Related Publications (1)
Number Date Country
20110234638 A1 Sep 2011 US
Continuations (3)
Number Date Country
Parent 12646081 Dec 2009 US
Child 13017419 US
Parent 12189579 Aug 2008 US
Child 12646081 US
Parent 10662813 Sep 2003 US
Child 12189579 US