The present invention relates generally to interactive input systems and in particular to a system and method for tracking a pointer across multiple overlapping coordinate input sub-regions defining a generally contiguous input region and to an interactive touch system incorporating the same.
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 touch surface where the contacts are made. Common touch systems utilize analog resistive, electromagnetic, capacitive, acoustic or machine vision to identify pointer contacts with the touch surface.
For example, 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, discloses 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 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 convey pointer characteristic data to a master controller, which in turn processes the pointer characteristic data to determine the location of the pointer in (x,y)-coordinates relative to the touch surface using triangulation. The pointer coordinate data is conveyed to a computer executing one or more applications programs. The computer uses the pointer coordinate data to update the computer-generated image that is presented on the touch surface. Pointer contacts on the touch surface can therefore be recorded as writing or drawing or used to control execution of applications programs executed by the computer.
Although the above touch system works extremely well, since the fields of view of the cameras are arranged to encompass the entire touch surface, camera resolution has placed a limit on the size of the touch system that can be made.
In many environments such as in teaching institutions, very large scale touch systems are desired so that visible presentations can be made to large groups. A very large scale touch system created from a series of side-by-side mounted touch panels has been considered. Although this touch system provides a larger touch surface, the touch surface is not continuous due to the individual frames surrounding the touch surfaces. Also, tracking pointer movements from one touch surface to another is cumbersome and user unfriendly. As will be appreciated, improvements in very large scale touch systems are desired.
It is therefore an object of the present invention to provide a system and method for tracking a pointer across multiple overlapping coordinate input sub-regions defining a generally contiguous input region and to an interactive touch system incorporating the same.
According to one aspect of the present invention there is provided in a pointer tracking system including at least two overlapping coordinate input sub-regions defining a generally contiguous input region, each coordinate input sub-region generating pointer coordinate data in response to pointer movement therein, a method for tracking a pointer across overlapping portions of said coordinate input sub-regions comprising:
detecting pointer movements within overlapping portions of said coordinate input sub-regions; and
processing the pointer coordinate data generated by each of said coordinate input sub-regions as a result of pointer movement within said overlapping portions in accordance with defined logic to yield a single set of pointer coordinate data representing the pointer movement.
According to another aspect of the present invention there is provided in a touch system including a plurality of coordinate input sub-regions that overlap defining a generally contiguous input surface, each coordinate input sub-region generating pointer coordinate data in response to pointer contacts thereon, said pointer coordinate data being processed to update image data presented on said input surface, a method of detecting the position of a pointer contact relative to said touch surface comprising:
acquiring overlapping images of each coordinate input sub-region;
when a pointer contact is made on a portion of a coordinate input sub-region that does not overlap with an adjacent coordinate input sub-region, processing acquired images to derive pointer data and triangulating the position of the pointer using the derived pointer data thereby to determine the position of the pointer contact relative to the touch surface; and
when a pointer contact is made on a portion of a coordinate input sub-region that overlaps with an adjacent coordinate input sub-region, for each coordinate input sub-region processing acquired images to derive pointer data, and triangulating positions of the pointer using the derived pointer data, and thereafter processing the triangulated positions in accordance with defined logic thereby to determine the position of the pointer contact relative to the touch surface.
According to yet another aspect of the present invention there is provided a touch system comprising:
a plurality of coordinate input sub-regions, said input sub-regions overlapping to define a generally contiguous input surface, each coordinate input sub-region acquiring overlapping images thereof and generating pointer coordinate data in response to pointer contacts thereon, said pointer coordinate data being processed to update image data presented on said input surface, wherein:
when a pointer contact is made on a portion of a coordinate input sub-region that does not overlap with an adjacent coordinate input sub-region, said coordinate input sub-region processes acquired images to derive pointer data and triangulates the position of the pointer using the derived pointer data thereby to determine the position of the pointer contact relative to the touch surface; and
when a pointer contact is made on a portion of a coordinate input sub-region that overlaps with an adjacent coordinate input sub-region, each overlapping coordinate input sub-region processes acquired images to derive pointer data and triangulates the position of the pointer using the derived pointer data, the triangulated positions generated by the overlapping coordinate input sub-regions being processed in accordance with defined logic thereby to determine the position of the pointer contact relative to the touch surface.
The present invention provides advantages in that pointer contacts over an input region defined by multiple overlapping coordinate input sub-regions can be tracked effectively in a user friendly manner. Also, since a transition zone is provided between adjacent overlapping coordinate input sub-regions, coordinate input events can be transferred smoothly between coordinate input sub-regions. The transition zone also increases alignment tolerances between adjacent coordinate input sub-regions.
Embodiments of the present invention will now be described more fully with reference to the accompanying drawings in which:
a and 3b are front plan views of the touch surface showing the positions and orientations of cameras used to capture overlapping images looking across the touch surface;
a and 4b are front plan views of portions of an illuminated bezel surrounding the touch surface;
a to 9c show different pointer contacts on the touch surface of
Turning now to
A plurality of sets 106 of cameras, in this example three sets 106 of cameras, is associated with the touch surface 102. The sets 106 of cameras are positioned along the length of the touch surface 102. Each set 106 of cameras includes four cameras arranged to define the corners of a rectangle. The cameras of each set 106 have overlapping fields of view oriented to look across a portion of the touch surface 102 thereby to define a touch or coordinate input sub-region. Thus, in the present embodiment, the sets 106 of cameras define a series of three side-by-side coordinate input sub-regions CIR1, CIR2 and CIR3 respectively. The fields of view of the cameras are also oriented so that the coordinate input sub-regions defined by adjacent sets of cameras overlap to define two transition zones TZ1/2 and TZ2/3 respectively.
Each set 106 of cameras communicates with a master controller 108. Each master controller 108 processes pointer characteristic data received from its associated set 106 of cameras to determine the positions of pointers appearing in images captured by the cameras in (x,y)-coordinates using triangulation. The master controllers 108 transmit the pointer coordinate data to a computer 110 allowing the computer 110 either to record the pointer coordinate data as writing or drawing or use the pointer coordinate data as a mouse event to control execution of an applications program executed by the computer 110. The computer 110 provides image data to a series of projectors P1 to P3, which in turn project images onto the touch surface 102. The image data is updated by the computer 110 in response to received pointer coordinate data so that the images projected onto the touch surface 102 reflect the pointer activity.
Each projector is associated with a different coordinate input sub-region and projects an image thereon. As can be seen, projector P1 projects an image I1 onto coordinate input sub-region CIR1, projector P2 projects an image I2 onto coordinate input sub-region CIR2 and projector P3 projects an image I3 onto coordinate input sub-region CIR3. The projected images I1, I2 and I3 are aligned and joined seamlessly along vertical lines generally at the mid-points of the transition zones TZ1/2 and TZ2/3 to provide a smooth and continuous image spanning the touch surface 102. In the present embodiment, the computer 110 executes a desktop application. Each coordinate input sub-region is associated with and tied to a specific section of the desktop during an orientation procedure as will be described. As a result, the computer 110 provides image data to the projectors P1 to P3 so that the appropriate desktop sections are displayed on the coordinate input sub-regions.
A tool tray 112 is also associated with each coordinate input sub-region. Each tool tray 112 holds a number of pointers or tools (not shown) having different assigned attributes. In this case, each tool tray holds a number of colored pens as well as an eraser. When a tool is lifted from the tool tray, the tool tray provides a signal to the associated master controller 108 which in turn conveys the signal to the computer 110 to identify the selected tool. In this manner, when a colored pen is used to contact the touch surface 102 writing in the appropriate color tracking the pen movement is projected onto the touch surface. When an eraser is used to contact the touch surface 102 writing projected onto the touch surface over which the eraser is moved is erased. As is known, the desktop application can be conditioned to assign properties to pointers used to contact each coordinate input sub-region.
Turning now to
The set 106 of cameras associated with coordinate input sub-region CIR3 includes cameras C2″ and C3″ positioned at the top right and bottom right corners of the touch surface 102 and cameras C1″ and C0″ positioned at the top and bottom of the touch surface 102 intermediate its length. The camera C2″ is oriented so that its optical axis is aimed generally towards the intermediate camera C0″ and forms a 45 degree angle with respect to the vertical. The camera C3″ is oriented so that its optical axis is aimed generally towards the intermediate camera C1″ and forms a 45 degree angle with respect to the vertical. The intermediate camera C1″ is oriented so that an edge of its field of view is aimed slightly towards camera C3″ and forms a 10 degree angle with respect to the vertical. The intermediate camera C0″ is oriented so that an edge of its field of view is aimed slightly towards camera C2″ and forms a 10 degree angle with respect to the vertical.
The set 106 of cameras associated with the coordinate input sub-region CIR2 includes laterally spaced cameras C1′ and C2′ positioned along the top of the touch surface 102 and laterally spaced cameras C0′ and C3′ positioned along the bottom of the touch surface 102. The top left camera C1′ is located between cameras C1 and C2 and is oriented so that an edge of its field of view is aimed slightly towards camera C3′ and forms a 10 degree angle with respect to the vertical. The top right camera C2′ is located between cameras C1″ and C2″ and is oriented so that an edge of its field of view is aimed slightly towards camera C0′ and forms a 10 degree angle with respect to the vertical. The bottom left camera C0′ is located between cameras C0 and C3 and is oriented so that an edge of its field of view is aimed slightly towards camera C2′ and forms a 10 degree angle with respect to the vertical. The bottom right camera C3′ is located between cameras C0″ and C3″ and is oriented so that an edge of its field of view is aimed slightly towards the camera C1′ and forms a 10 degree angle with respect to the vertical.
The cameras at the corners and along the top and bottom of the touch surface 102 are accommodated by the illuminated bezel 104 as shown in
Each coordinate input sub-region is divided into four quadrants using diagonal lines extending between the cameras at opposite corners of the coordinate input sub-region. Image capture to permit pointer tracking within each quadrant is the responsibility of a different pair of cameras in the set. The top quadrant QT is the responsibility of the bottom left and bottom right cameras in the set, the bottom quadrant QB is the responsibility of the top left and top right cameras in the set, the left quadrant QL is the responsibility of the top left and bottom left cameras in the set and the right quadrant QR is the responsibility of the top right and bottom right cameras in the set.
Since each camera is only responsible for capturing images looking across two quadrants of the coordinate input sub-region, the field of view of each camera need only cover one half of the coordinate input sub-region. Using cameras with fields of view extending well beyond this requirement provides great flexibility with respect to orienting the cameras. For example, by tilting the intermediate cameras so that edges of their fields of view form 10° angles with respect to the vertical, the cameras provide coverage over the entire touch surface 102 while maintaining a 4:3 ratio and without requiring the cameras to intrude onto the touch surface thereby avoiding blind spots being created by the cameras. As will be appreciated, if the intermediate cameras intrude over the touch surface 102, they will block each others' view of portions of the touch surface. Also, by arranging the intermediate cameras so that edges of their fields of view form small angles with respect to the vertical, infrared lighting can be provided at the cameras that is generally in line with the infrared lighting provided by the illuminated bezels 104. This avoids dark spots from being introduced along the top and bottom of the touch surface at the intermediate camera locations.
The general operation of the touch system 100 will now be described. Initially an orientation procedure is performed by the computer 110 to calibrate the touch system 100 so that the coordinate systems of the coordinate input sub-regions can be mapped to the display coordinate systems and so that the overlapping portions of the coordinate input sub-regions within the transition zones can be mapped to one another.
With the touch system 100 calibrated, when a pointer contacts a quadrant within one of the coordinate input sub-regions outside of a transition zone, the images captured by the pair of cameras assigned to that quadrant are processed by the cameras and the associated master controller 108 in the manner described in U.S. patent application Ser. No. 10/294,917 to Morrison et al., assigned to SMART Technologies Inc., assignee of the present invention, the content of which is incorporated by reference. In this manner, a bounding box surrounding the pointer contact is determined allowing the location of the pointer in (x,y)-coordinates with respect to the coordinate input sub-region to be calculated. Thus, in this case only one master controller 108 reports pointer coordinate data to the computer 110. The computer 110 in turn records the pointer coordinate data as writing or drawing if the pointer contact is a write event or injects the pointer coordinate data into the active applications program being run by the computer 110 if the pointer contact is a mouse event.
In general to determine if a pointer contact is a write or mouse event, the tool type and point of first contact is examined. If a drawing tool is used to make the contact and the contact is within a designated writing area within the projected desktop section, the pointer contact is treated as a write event; otherwise the pointer contact is treated as a mouse event. At initial contact, the pointer is given a pointer identification (ID) and the pointer ID along with any assigned pointer attributes (i.e. shape, color, width etc.) are stored.
When a pointer contacts the touch surface 102 within a transition zone, the master controllers 108 associated with the two sets of cameras that observe the transition zone generate pointer coordinates in the same manner referenced above and convey the generated pointer coordinates to the computer 110. Upon receipt of the two reported pointer coordinates, the computer 110 uses defined logic, in this case a weighted averaging technique, to yield a single (x,y)-coordinate pair representing the position of the pointer contact. The computer 110 in turn records the pointer coordinate data as writing or drawing if the pointer contact is a write event or injects the pointer coordinate data into the active applications program being run by the computer 110 if the pointer contact is a mouse event.
By using a weighted averaging technique to determine pointer positions within the transition zones, a smooth pointer transition is achieved as a pointer is moved from one coordinate input sub-region to an adjacent coordinate input sub-region. When a pointer moves from one coordinate input sub-region to an adjacent coordinate input sub-region, since the attributes assigned to the pointer are stored with the pointer ID, the attributes of the pointer are maintained by the computer 110. Alternatively, when a pointer moves from one coordinate input sub-region to an adjacent coordinate input sub-region, the properties of the pointer can be changed to properties established by the desktop section associated with the new coordinate input sub-region after a pointer-up event or a certain period of pointer inactivity occurs.
Further specifics of the orientation procedure and pointer tracking will now be described with reference to
Orientation Procedure
The orientation procedure performed by the computer 110 is similar to that described in U.S. Pat. No. 5,448,263 to Martin, assigned to SMART Technologies, Inc., assignee of the present invention. Turning now to
If the coordinate input sub-region is part of a multiple overlapping coordinate input sub-region configuration, the computer 110 checks to determine whether an oriented coordinate input sub-region exists to the right of the coordinate input sub-region being oriented on which the desktop section is displayed (step 214). If such an oriented coordinate input sub-region exists, the object representing the coordinate input sub-region being oriented is updated to include the address of the right neighbour coordinate input sub-region (step 216). The computer 110 then updates the object representing the right neighbour coordinate input sub-region to include the address of the coordinate input sub-region currently being oriented i.e. its left neighbour (step 218).
Upon completion of step 218 or if an oriented coordinate input sub-region does not exist to the right as determined at step 214, the computer 110 checks to determine whether an oriented coordinate input sub-region exists to the left of the coordinate input sub-region being oriented on which the desktop section is displayed (step 220). If such an oriented coordinate input sub-region exists, the object representing the coordinate input sub-region being oriented is updated to include the address of the left coordinate input sub-region (step 222). The computer 110 then updates the object representing the left neighbour coordinate input sub-region to include the address of the coordinate input sub-region currently being oriented i.e. its right neighbour (step 224).
Upon completion of step 224 or if an oriented coordinate input sub-region does not exist to the left as determined at step 220 or if the coordinate input sub-region is not part of a multiple overlapping coordinate input sub-region configuration as determined at step 212, the pointer coordinate data determined at step 208 is stored to registry (step 226). If the orientation procedure has not been performed with respect to the other coordinate input sub-regions, another section of the desktop with targets is presented on an adjacent coordinate input sub-region and the orientation procedure reverts to step 204 (step 228). If the orientation procedure has been performed with respect to the other coordinate input sub-regions or if the coordinate input sub-region is not part of a multiple overlapping coordinate input sub-region configuration as determined at step 212, the orientation procedure is exited.
At step 204, if the desktop section is not displayed on the proper coordinate input sub-region, the desktop section can be moved to the next coordinate input sub-region by hitting the space bar (step 230). When the space bar is hit, the computer 110 provides the output image data to the next projector so that the desktop section is presented on the adjacent coordinate input sub-region (step 232).
The pointer coordinate data stored in the registry at step 226 allows pointer contacts over the entire touch surface 102 to be mapped to the display coordinates and register the overlapping portions of the coordinate input sub-regions.
Pointer Tracking
When pointer coordinate data is output by a master controller 108 in response to a pointer contact on the associated coordinate input sub-region, the pointer coordinate data is conveyed to the computer 110 (step 300). In response, the computer 110 orients the pointer coordinate data to the display coordinates using the results of the orientation procedure (step 302) and then examines the pointer coordinate data to determine whether the pointer contact represents a mouse event or a write event (step 304). If the pointer contact represents a mouse event, the mouse event is examined to determine its type (step 306). If the mouse event represents a first contact with the coordinate input sub-region, a check is made to determine whether a mouse down event exists on another coordinate input sub-region within a transition zone shared by the coordinate input sub-regions (step 308). If such a mouse down event does not exist on another coordinate input sub-region, a mouse event is created (step 310) and the created mouse event for the coordinate input sub-region is stored (step 312). The stored mouse event is then injected into the active application running on the computer 110 (step 314). At step 308, if such a mouse down event exists, a new mouse event is created by averaging the locations of all mouse down events with the location of the current mouse event (step 316). The created new mouse event similarly is stored (step 312) and is then injected into the active application running on the computer 110 (step 314).
At step 306 if the mouse event represents a move contact within the coordinate input sub-region, a new mouse event is created by averaging the locations of all mouse down events with the location of the current mouse event (step 316). The created new mouse event similarly is stored (step 312) and is then injected into the active application running on the computer 110 (step 314).
At step 306, if the mouse event represents a remove contact from the coordinate input sub-region, the mouse data associated with the coordinate input sub-region is removed (step 320). A check is then made to determine if a mouse down event exists on another coordinate input sub-region (step 322). If not a remove mouse event is created (step 324) and the created remove mouse event is injected into the active application running on the computer 110 (step 314). If a mouse down condition exists on another coordinate input sub-region, the mouse event is ignored (step 326).
At step 304, if the pointer contact on the coordinate input sub-region represents a write event, the write event is examined to determine its type (step 340). If the write event represents a first contact with the coordinate input sub-region, contact down information together with the pointer (x,y)-coordinate data is stored (step 342). A check is then made to determine whether the stored information matches a pointer contact on a neighbour coordinate input sub-region (step 344). If the stored information does not match a pointer contact on a neighbour coordinate input sub-region, contact identification for the write event is created (step 346). Pointer information for the contact identification is stored (step 348). The pointer (x,y)-coordinate data in turn is recorded by the computer 110 as writing or drawing (step 350).
At step 344, if the stored information matches a pointer contact on a neighbour coordinate input sub-region signifying a pointer contact in a transition zone, contact identification and pointer information from the neighbour coordinate input sub-region is obtained (step 352). A check is then made to determine whether the pointer contact was made on the projected desktop section associated with the current coordinate input sub-region or on the projected desktop section associated with the neighbour coordinate input sub-region (step 354). If the pointer contact was made using a pointer the neighbour coordinate input sub-region, the pointer coordinate data is ignored (step 356) since the recorded pointer (x,y)-coordinate data will be processed by the neighbour coordinate input sub-region. Otherwise, the pointer coordinate data is averaged with the pointer (x,y)-coordinate data recorded by the neighbour coordinate input sub-region (step 358) prior to being recorded by the computer 110 as writing or drawing (step 350).
During averaging of the pointer coordinate data, the computer 110 processes the reported y coordinates in accordance with defined logic to yield a single y-coordinate. Specifically, the computer 110 calculates the y-coordinate using a weighted averaging technique. The weighted averaging technique used by the computer 110 to calculate the y-coordinate from the pair of reported y-coordinates is in accordance with the following rule assuming that the pointer enters the transition zone from coordinate input sub-region CIRx and is travelling in a direction towards coordinate input sub-region CIRx+1:
y-coordinate=(100−P %)*y-coordinate of CIRx+P %*y-coordinate of CIRx+1
where:
P % is the distance travelled through the transition zone in the x-direction expressed a percentage.
As will be appreciated in this case at the first transition border i.e. the border between the coordinate input sub-region CIRx and the transition zone, the y-coordinate is equal to the y-coordinate reported by the master controller 108 associated with coordinate input sub-region CIRx. At the second transition border i.e. the border between the transition zone and the coordinate input sub-region CIRx+1, the y-coordinate is equal to the y-coordinate reported by the master controller 108 associated with coordinate input sub-region CIRx+1. At the midpoint of the transition zone, the y-coordinate is equal to the average of the y-coordinates reported by the master controllers associated with the coordinate input sub-regions CIRx and CIRx+1.
At step 340, if the write event represents a move contact over the coordinate input sub-region, the pointer (x,y)-coordinate data is stored (step 360). A check is then made to determine if the pointer (x,y)-coordinate data matches pointer (x,y)-coordinate data generated by a neighbour coordinate input sub-region (step 362). If the pointer (x,y)-coordinate data does not match pointer (x,y)-coordinate data generated by a neighbour coordinate input sub-region, the pointer (x,y)-coordinate data is recorded by the computer 110 as writing or drawing (step 350). If the pointer (x,y)-coordinate data matches pointer (x,y)-coordinate data generated by a neighbour coordinate input sub-region, a check is made to determine whether the pointer contact was made on the projected desktop section associated with the current coordinate input sub-region or on the projected desktop section associated with the neighbour coordinate input sub-region (step 354). If the pointer contact was made on the neighbour coordinate input sub-region, the pointer coordinate data is ignored (step 356) since the recorded pointer (x,y)-coordinate data will be processed by the neighbour coordinate input sub-region. Otherwise, the pointer coordinate data is averaged with the pointer (x,y)-coordinate data recorded by the neighbour coordinate input sub-region in the manner previously described (step 358) prior to being recorded by the computer 110 as writing or drawing (step 350).
At step 340, if the write event represents a lost contact with the coordinate input sub-region representing a clear contact state (step 380), a check is made to determine whether a neighbour coordinate input sub-region has generated a matching write event (step 382). If not, a clear contact state event is generated and recorded by the computer 110 at step 350. If a neighbour coordinate input sub-region has generated a matching write event, the write event is ignored (step 384).
Although each set 106 of cameras is shown communicating with an associated master controller 108, other processing configurations to triangulate pointer data derived from captured images may be used. For example, a single master controller 108 may be used to triangulate the pointer data generated by the cameras of each set 106. In this case, it is preferred that a synchronization signal be conveyed to each set of cameras simultaneously so that images of looking across the coordinate input sub-regions are captured at the same time.
Also, although the touch system 100 is described as including a projector associated with each coordinate input sub-region, it will be appreciated that other projector configurations may be used. For example, a single projector projecting an image that spans the touch surface 102 or other combinations of multiple projectors projecting overlapping images that span the touch surface 102 are suitable. In cases where multiple projectors are used, the projected images may overlap. For example, if desired, each projector may project an image spanning the entire touch surface 102, in which case each projected image fully overlaps. Alternatively, the projected images may only overlap in the transition zones. In this case, the projected images are blended at their edges within the transition zones TZ1/2 and TZ2/3 to provide a smooth and continuous image spanning the touch surface 102.
As will be appreciated by those skilled in the art, the overlapping coordinate input sub-regions need not be arranged in a horizontal row as shown. The coordinate input sub-regions may be arranged in a vertical column or arranged in an N×M matrix.
In the present embodiment, the touch surface and camera orientations are configured to maintain a 4:3 aspect ratio to conform to the shape of the coordinate input sub-regions. If the aspect ratio of the coordinate input sub-regions is equal to or less than 1, the intermediate cameras can be oriented so that the edges of their fields of view are vertical. Alternatively, in this case the orientation of the cameras can be maintained and their fields of view increased. In fact, the cameras can be oriented at virtually any angle provided their fields of view observe their assigned quadrants of the coordinate input sub-regions.
If desired, global attributes can be assigned to each pointer used to contact the touch surface 102 thereby obviating the need for tool trays associated with each coordinate input sub-region. Also, the computer 110 need not execute a desktop application that is presented in sections over the touch surface 102. Rather the computer 110 can execute and present a separate applications program on each coordinate input sub-region, while still permitting pointer properties to be carried over from one coordinate input sub-region to another.
Since the touch system 100 uses machine vision to detect pointers over the touch surface 102, the touch system 100 can support multiple users each using a pointer to contact the touch surface at different locations simultaneously. In this case writing input by different users using pointers is presented in the projected images typically using different colors or other visual differentiators although visually differentiating the user input is not necessary. When a pointer transition between coordinate input sub-regions is made resulting in multiple users contacting the same coordinate input sub-region, a decision algorithm based on proximity of last contact is used to differentiate the pointer contacts.
Turning now to
For example, as shown in
b and 9c show other positions of pointers on the touch surface 502 and the various triangulation results that can be derived from images captured by the cameras. As will be appreciated, the areas on the touch surface 502 falling within the fields of view of different pairs of cameras are similar to the transition zones described with reference to the embodiment of
Those of skill in the art will appreciate that although the above embodiments show vision-based touch systems, the present method of tracking a pointer can be used in other types of touch systems having overlapping input regions defining transition zones.
Although embodiments of the present invention have been described with reference to the figures, 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.
This application is a continuation application of U.S. patent application Ser. No. 12/098,961, filed Apr. 7, 2008, now U.S. Pat. No. 8,089,462, issued Jan. 3, 2012, which is a continuation application of U.S. patent application Ser. No. 10/750,219, filed Jan. 2, 2004, now U.S. Pat. No. 7,355,593, issued Apr. 8, 2008, the contents of which are incorporated herein by reference.
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 |
4672364 | Lucas | Jun 1987 | A |
4673918 | Adler et al. | Jun 1987 | A |
4703316 | Sherbeck | Oct 1987 | A |
4710760 | Kasday | Dec 1987 | A |
4766424 | Adler et al. | Aug 1988 | A |
4811004 | Person et al. | Mar 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 |
5140647 | Ise et al. | Aug 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 |
5422494 | West et al. | Jun 1995 | A |
5457289 | Huang et al. | Oct 1995 | A |
5581378 | Kulick et al. | Dec 1996 | A |
5591945 | Kent | Jan 1997 | A |
5698845 | Kodama et al. | Dec 1997 | A |
5729471 | Jain et al. | Mar 1998 | A |
5739479 | Davis-Cannon | 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 |
5804773 | Wilson et al. | Sep 1998 | A |
5884257 | Maekawa et al. | Mar 1999 | A |
5909210 | Knox et al. | Jun 1999 | A |
5940065 | Babb et al. | Aug 1999 | A |
5990874 | Tsumura | Nov 1999 | A |
6076041 | Watanabe | Jun 2000 | A |
6091406 | Kambara et al. | Jul 2000 | A |
6097394 | Levoy et al. | Aug 2000 | A |
6215477 | Morrison et al. | Apr 2001 | B1 |
6226004 | Nishihara | May 2001 | B1 |
6241609 | Rutgers | Jun 2001 | B1 |
6304263 | Chiabrera et al. | Oct 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 |
6471420 | Maekawa et al. | Oct 2002 | B1 |
6480187 | Sano et al. | Nov 2002 | B1 |
6504532 | Ogasahara et al. | Jan 2003 | B1 |
6532006 | Takekawa et al. | Mar 2003 | B1 |
6540366 | Keenan et al. | Apr 2003 | B2 |
6570103 | Saka et al. | May 2003 | B1 |
6590568 | Astala et al. | Jul 2003 | B1 |
6597508 | Seino et al. | Jul 2003 | B2 |
6603867 | Sugino et al. | Aug 2003 | B1 |
6624833 | Kumar et al. | Sep 2003 | B1 |
6650318 | Arnon | Nov 2003 | B1 |
6714311 | Hashimoto | Mar 2004 | B2 |
6720949 | Pryor et al. | Apr 2004 | B1 |
6738051 | Boyd et al. | May 2004 | B2 |
6803906 | Morrison et al. | Oct 2004 | B1 |
6828959 | Takekawa et al. | Dec 2004 | B2 |
6919880 | Morrison et al. | Jul 2005 | B2 |
6919892 | Cheiky et al. | Jul 2005 | B1 |
6927384 | Reime et al. | Aug 2005 | B2 |
7002555 | Jacobsen et al. | Feb 2006 | B1 |
7058204 | Hildreth et al. | Jun 2006 | B2 |
7075054 | Iwamoto et al. | Jul 2006 | B2 |
7084857 | Lieberman et al. | Aug 2006 | B2 |
7151533 | Van Iperen | Dec 2006 | B2 |
7155698 | Gennari | Dec 2006 | B1 |
7176905 | Baharav et al. | Feb 2007 | B2 |
7227526 | Hildreth et al. | Jun 2007 | B2 |
7236162 | Morrison et al. | Jun 2007 | B2 |
7236632 | Erol 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 |
7271795 | Bradski | Sep 2007 | B2 |
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 |
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 |
8089462 | Hill et al. | Jan 2012 | B2 |
8358872 | Fujioka | Jan 2013 | B2 |
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 |
20020118177 | Newton | Aug 2002 | A1 |
20020126116 | Grzeszczuk et al. | Sep 2002 | A1 |
20030043116 | Morrison et al. | Mar 2003 | A1 |
20030090473 | Joshi | May 2003 | A1 |
20030137494 | Tulbert | Jul 2003 | A1 |
20030151562 | Kulas | Aug 2003 | A1 |
20030156118 | Ayinde | Aug 2003 | A1 |
20030161524 | King | Aug 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 |
20040125086 | Hagermoser et al. | Jul 2004 | A1 |
20040160420 | Baharav et al. | Aug 2004 | A1 |
20040196282 | Oh | Oct 2004 | A1 |
20040201575 | Morrison | Oct 2004 | A1 |
20040202349 | Erol et al. | Oct 2004 | A1 |
20040204129 | Payne et al. | Oct 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 |
20050162402 | Watanachote | 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 |
20060197749 | Popovich | Sep 2006 | A1 |
20060202953 | Pryor et al. | Sep 2006 | A1 |
20060244067 | Socher et al. | Nov 2006 | A1 |
20060244734 | Hill et al. | Nov 2006 | A1 |
20060274067 | Hidai | Dec 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 |
20070205994 | van Ieperen | Sep 2007 | A1 |
20070273842 | Morrison | Nov 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 |
20080259050 | Lin et al. | Oct 2008 | A1 |
20080259052 | Lin et al. | Oct 2008 | A1 |
20080284733 | Hill et al. | Nov 2008 | A1 |
20090058832 | Newton | Mar 2009 | A1 |
20090058833 | Newton | Mar 2009 | A1 |
20090146972 | Morrison et al. | Jun 2009 | A1 |
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 |
EP001262909 | 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 |
2279823 | Sep 2007 | ES |
1575420 | Sep 1980 | GB |
2176282 | May 1986 | GB |
2263765 | Aug 1993 | GB |
62-005428 | Jan 1987 | JP |
63-223819 | Sep 1988 | JP |
03-244017 | Oct 1991 | JP |
06-110608 | Apr 1994 | JP |
11-203042 | Jul 1999 | JP |
11-212692 | Aug 1999 | JP |
2001-142642 | May 2001 | JP |
2002-055770 | Feb 2002 | JP |
2003-36142 | Feb 2003 | JP |
2003-65716 | Mar 2003 | JP |
2005-108211 | Apr 2005 | JP |
2005-182423 | Jul 2005 | JP |
2005-202950 | Jul 2005 | JP |
0124157 | Apr 2001 | WO |
0163550 | Aug 2001 | WO |
0191043 | Nov 2001 | WO |
0203316 | Jan 2002 | WO |
03104887 | Dec 2003 | WO |
2004072843 | Aug 2004 | WO |
2004090706 | Oct 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 |
20100512633 | May 2010 | WO |
Entry |
---|
International Preliminary Report on Patentability, PCT/NZ2004/000029, May 20, 2005 (21 pages). |
“International Preliminary Report on Patentability”, PCT/US2008/060102, Oct. 22, 2009 (9 pages). |
International Search Report for PCT/CA2010/001085 mailed Oct. 12, 2010 (5 pages). |
“International Application Serial No. PCT/US2008/060102, Search Report & Written opinion mailed Feb. 12, 2009” (14 pages). |
International Application Serial No. PCT/US2008/074749, Search Report & Written Opinion mailed Feb. 11, 2009 (10 pages). |
“International Application Serial No. PCT/US2008/074755, International Search Report and Written Opinion mailed Jan. 29, 2009” (14 pages). |
International Search Report for PCT/NZ05/00092 Sep. 27, 2006 (4 pages). |
Loinaz et al., “A 200-mW, 3.3-V, CMOS Color Camera IC Producing 352x288 24-B Video at 30 Frames/s,” IEEE Journal of Solid-StateCircuits,vol. 31,No. 12,Dec. 1998, pp. 2092-2103. |
Yawcheng Lo, “Solid-state image sensor: technologies and applications,” Input/Output and Imaging Technologies, Y.T. Tsai, T-M. Kung, and J. Larsen, eds. SPIE Proceedings vol. 3422, pp. 70-80 (1998). |
Touch Panel, vol. 5 No. 2-3 (Sep. 2010). |
Touch Panel, vol. 5 No. 4 (Nov. 2010). |
“Store Window Presentations”, Heddier Electronic. |
“ThruGlass”, Projected Capacitive Touchscreencs Specifications, Micro Touch. |
Benko, et al., “Precise Selection Techniques for Multi-Touch Screens”, Proc. ACM CHI 2006: Human Factors in Computer Systems, pp. 1263-1272. |
Buxton, W., “Issues and Techniques in Touch-Sensitive Tablet Input,” Computer Graphics, 19(3), Proceedings of SIGGRAPH '85, 1985, pp. 215-223. |
VGA-format CMOS Camera-on-a-Chip for Multimedia Applications, Photobit Corporation, 1999 (2 pages). |
“White Paper”, Digital Vision Touch Technology Feb. 2003. |
Sep. 8, 2011 Office Action for Canadian Patent Application No. 2,491,582. |
Rejection notice for Japanese Patent Application No. 2011-209880 with a mailing date of Feb. 5, 2013. |
Number | Date | Country | |
---|---|---|---|
20120068955 A1 | Mar 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12098961 | Apr 2008 | US |
Child | 13307588 | US | |
Parent | 10750219 | Jan 2004 | US |
Child | 12098961 | US |