|Publication number||US7602382 B2|
|Application number||US 11/210,699|
|Publication date||Oct 13, 2009|
|Filing date||Aug 25, 2005|
|Priority date||Sep 14, 1998|
|Also published as||EP1241557A2, EP1241557A3, US7256770, US20010015718, US20050275637|
|Publication number||11210699, 210699, US 7602382 B2, US 7602382B2, US-B2-7602382, US7602382 B2, US7602382B2|
|Inventors||Kenneth P. Hinckley, Steven N. Bathiche, William Vong, James H. Cauthorn, Corey M. Ladas, Kenneth V. Fry|
|Original Assignee||Microsoft Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (93), Non-Patent Citations (30), Referenced by (30), Classifications (46), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a divisional application of prior U.S. patent application Ser. No. 09/804,496, filed Mar. 13, 2001, which application is a continuation-in part of commonly assigned, U.S. patent application entitled “Proximity Sensor in a Computer Input Device” to Hinckley et al., filed Sep. 14, 1998 and assigned Ser. No. 09/152,434, now U.S. Pat. No. 6,456,275, issued Sep. 24, 2002, which is herein incorporated by reference. Also, prior U.S. patent application Ser. No. 09/804,496, filed Mar. 13, 2001 is a continuation-in part of commonly assigned, U.S. patent application entitled “A Technique For Implementing a Two-Handed Desktop Use Interface For a Computer” to Hinckley, filed Sep. 14, 1998 and assigned Ser. No. 09/152,432, now abandoned, which is herein incorporated by reference. Further, prior U.S. patent application Ser. No. 09/804,496, filed Mar. 13, 2001 is a continuation-in part of commonly assigned, U.S. patent application entitled “Method of Interacting With a Computer Using a Proximity Sensor in a Computer Input Device” to Hinckley et al., filed Sep. 14, 1998 and assigned Ser. No. 09/152,443, now U.S. Pat. No. 6,396,477, issued May 28, 2002, which is herein incorporated by reference.
In addition, prior U.S. patent application Ser. No. 09/804,496, filed Mar. 13, 2001 is a continuation-in part of commonly assigned, copending U.S. patent application entitled “A Technique For Implementing an On-Demand Display Widget Through Controlled Fading Initiated By User Contact With a Touch Sensitive Input Device” to Hinckley, filed Nov. 25, 1998 and assigned Ser. No. 09/200,325, now U.S. Pat. No. 6,333,753, issued Dec. 25, 2001, which is herein incorporated by reference and which claims priority to U.S. provisional patent application entitled “Toolglass Improvements—On-Demand Tool Sheet; Gesturing Through Tool Sheets”, filed Sep. 14, 1998 and assigned Ser. No. 60/100,261. The prior U.S. patent application Ser. No. 09/804,496, filed Mar. 13, 2001 is also a continuation-in part of commonly assigned, copending U.S. patent application entitled “A Technique For Implementing an On-Demand Tool Glass For Use in a Desktop User Interface” to Hinckley, filed Nov. 25, 1998 and assigned Ser. No. 09/200,321, now U.S. Pat. No. 6,232,957, issued May 15, 2001, which is herein incorporated by reference and which claims priority to U.S. provisional patent application entitled “Toolglass Improvements—On-Demand Tool Sheet; Gesturing Through Tool Sheets”, filed Sep. 14, 1998 and assigned Ser. No. 60/100,261.
The prior U.S. patent application Ser. No. 09/804,496, filed Mar. 13, 2001 is related to commonly assigned, copending U.S. patent application entitled “Method of Interacting With a Computer Using a Proximity Sensor in a Computer Input Device” to Hinckley et al., filed Apr. 5, 2000, and assigned Ser. No. 09/543,723, now U.S. Pat. No. 6,559,830, issued May 6, 2003, which is herein incorporated by reference and which is a continuation of U.S. patent application Ser. No. 09/152,443, now U.S. Pat. No. 6,396,477, issued May 28, 2002, identified above.
A. Technical Field
The present invention relates to input devices for computer systems. More particularly, the present invention relates to the use of touch sensitive input devices in computer systems.
B. Related Art
Input devices for computerized systems such as keyboards, touchpads, trackballs, game controllers and mice, often include one or more auxiliary controls such as joysticks, touchpads, trackballs, headsets, microphones, buttons, knobs, rocker switches, triggers, sliders, wheels, biometric sensors, etc. Auxiliary controls may be used alone or in conjunction with input devices and other auxiliary controls.
Most input devices create input signals using transducers, or switches. Switches are typically found in the buttons of mice, joysticks, and game controllers, as well as in the keys of keyboards. Transducers are found in mice and trackballs and create electrical signals based on the movement of balls in those devices or by optically detecting movement of the device across a surface. Transducers are also found in headsets where they convert speech signals into electrical signals. Touchpads create input signals using sensors that provide an electrical signal when the user contacts the touchpad that signal including the location within the touchpad where contact is made.
Although it is desirable to increase the amount of information that an input device and its auxiliary controls can provide to the computer, the number of transducers and switches that can be added to an input device is limited by the user's ability to remember all of the functions that a particular transducer or switch performs and by the practicalities of the available or at least feasibly available real estate for the switches and transducers on the input device (e.g., keyboard or mouse). The ability of a user to determine the functionality of each auxiliary control is also generally limited to a static label on or near the auxiliary control, activating each auxiliary control, clicking a button to select a menu option to request help file or reading a user manual. Furthermore, the functionality of an auxiliary control may vary from one game or application to another game or application. Thus, a static label on an auxiliary control is of little value when the function and status of the input device and its auxiliary controls change from application to application. In this regard, even if a user learns the assignment of the buttons and other controls in one game or application, another game or application may assign the same buttons or controls different features. Similarly, the status of the feature controlled by the auxiliary control generally can only be determined by activating the control.
Thus, there is a need to provide a user with the ability to better determine the functionality and status of auxiliary controls regardless of their context, (e.g., active application or game).
To address this need, indicators such as LEDs or small LCDs may be integrated directly with the input device and its auxiliary controls to provide feedback or state information. However, association of LEDs or LCDs with each auxiliary control increases both the amount of power consumed and the cost of the input device. Furthermore, LEDs and LCDs have very limited output forms and are separated from the main display (e.g., a computer monitor) causing the user to constantly have to look away from the screen and at the auxiliary control to determine the functionality or status of the control. Such constant shifts of attention can mentally tire the user as he or she is forced to repetitively reacquire the current context. Accordingly, there is a need to provide a more efficient, convenient and/or cost effective way to determine the functionality and/or status of auxiliary controls of input devices in a computer system.
The present invention overcomes many of the shortcomings of existing input devices by providing touch sensitive input devices which have touch sensitive auxiliary controls that sense a physical presence and provide visual feedback on an on-screen display or on the control itself, acoustic feedback (e.g., voice or music) or tactile feedback (e.g., vibration).
In an aspect of the present invention, keys, buttons, knobs, rocker switches or other auxiliary controls of an input device such as a keyboard, touchpad, trackball, game controller, monitor, joystick, steering wheel, headset or mouse can be augmented with sensors that detect contact or extreme proximity of a user's hand. According to another aspect, a sensed signal of the auxiliary control can provide the user with an on-screen display of status, state information, tool tips, help text or other feedback relevant to the control the user has touched without the user having activated (e.g., depress, turn, roll or otherwise activate) the control. Alternatively, acoustic or tactile feedback may be provided to the user instead of or in addition to the feedback provided by the on-screen display. Hence, a user can simply touch different buttons or other controls to explore their function assignment or status, or obtain other feedback. Such feedback can allow the user to better understand the consequences of their action, should he or she subsequently chooses to activate the control. Also, a user may quickly and casually be able to view status information.
Aspects of the invention include providing context sensitive feedback for an auxiliary control in an on-screen display, such as a display widget (e.g., graphical user interface (GUI)), responsive to detection of a user's hand. Hence, touch sensitive controls can be used to predict the context of a user's action. The context of the situation can be established by preparatory actions by the user such as grabbing, touching or approaching a control. Knowing the context of the action, the computer can begin to execute and predict the will of the user.
According to another aspect of the invention, contexts of an auxiliary control may include, but are not limited to, different types of applications such as games, utility, and productivity applications. Also, contexts may change within various portions of an application or game.
In another aspect of the invention, when a GUI is displayed responsive to detection of a physical presence proximate to or contacting an auxiliary control, a user may interact with the GUI using another auxiliary control or an input device including, but not limited to, a mouse, touchpad or keypad. For example, if a volume control GUI is displayed, a user may adjust the volume with a mouse.
In another aspect of the invention, input devices including their auxiliary controls may have a touch sensor which directly detects when a physical presence (e.g., user) touches the device or its controls, so as to provide display and dismissal of feedback on an “on-demand” basis, e.g., whenever the user establishes or breaks physical hand contact with the device.
For example, a transition in a touch indication provided by the device reflective of the user then making contact with the device or control, such as by touching the device with a finger may cause a tool tip to be displayed. A transition indicative of a user breaking physical contact with the device, such as by lifting his finger off the device, can cause the tool tip to be dismissed from the display. In one aspect of the invention, to prevent user distraction, these detected transitions initiate corresponding predefined animation sequences that occur over preset time intervals in which the feedback either begins to fade into view (typically from an invisible, i.e., totally transparent state, to eventually a predefined semi-transparent state or non-transparent state) as soon as user contact begins, and then begins to fade out from view (i.e., eventually back to its invisible state) as soon as user contact with the device is broken, e.g., as soon as the user lifts his or her hand away from the device.
In another aspect of the invention, toolbars, scrollbars and the like may only be displayed on a display screen in response to detection of a physical presence. Illustratively, touching, and not activating, an auxiliary control may cause on-screen display of a toolbar and breaking contact with the control may cause dismissing of the toolbar. In one aspect of the invention, a user may interface with the toolbar using an auxiliary control or input device as desired with one hand while continuing to touch the auxiliary control which caused the on-screen display of the toolbar. According to this aspect, display clutter can be reduced and available application screen area increased at appropriate times during program execution consistent with and governed by user action but without imposing any significant cognitive burden on the user to do so. This, in turn, is likely to significantly improve the “user experience”.
These and other novel advantages, details, embodiments, features and objects of the present invention will be apparent to those skilled in the art from following the detailed description of the invention, the attached claims and accompanying drawings, listed herein, which are useful in explaining the invention.
In accordance with illustrative embodiments of the present invention, an auxiliary control of an input device may be configured to detect when a physical presence (e.g., user's hand, stylus) touches the control so as to provide display and dismissal of a display widget on an “on demand” basis. The display widget may be a graphical user interface (GUI) and include information such as functionality (e.g., tool tips) and/or status information on an “on-demand” basis. An exemplary list of display widgets includes toolbars, tool glass sheet, scroll bars, window frames and window decorations, title bars, floating tool palettes, modal and non-modal dialog boxes, list or combo boxes, setting controls, buttons, text entry areas, etc.
A transition in a touch indication provided by the input device reflective of the user then making physical contact with an auxiliary control, such as by touching the control with a finger may cause a display widget to be displayed. A transition indicative of a user breaking contact with the auxiliary control, such as by lifting his finger off the control, causes the display widget to be dismissed. To prevent user distraction, these detected transitions can initiate corresponding predefined animation sequences that occur over preset time intervals in which the display widget either begins to fade into view (typically from an invisible, i.e., totally transparent, state to eventually a predefined semi-transparent state) as soon as user contact begins, and then begins to fade out from view (i.e., eventually back to its invisible state) as soon as user contact with the auxiliary control is broken, for example, as soon as the user lifts his or her finger from the control. Furthermore, depending on a specific touch-sensitive auxiliary control used, it is sometimes preferable to begin the fading after a brief time delay or “cooling period” occurs. For example, the user may reach the edge of the touchpad and “reclutch” his or her hand (e.g., briefly lift up his or her finger and then re-center it on the pad) to continue pointer motion. It might be annoying for the display widget to begin fading immediately when this happens. A brief time delay (e.g., approximately 0.5 to 1.0 seconds), coupled with continued contact sensing of the finger, prior to the start of the fading allows brief reclutchings of this sort without any changes to the screen display. Similarly, if a user has not touched the auxiliary control for a sufficiently long period of time, a similar time delay, coupled with sensing for a release of user contact, prior to the start of a fade-in might be used to prevent a short inadvertent contact from causing the display widget from fading in and then out, and otherwise annoying the user.
Furthermore, according to the present invention, touch induced display and dismissal can also readily be used to display and dismiss a display widget (e.g., toolbar) on an “on-demand” basis by sensing contact between a user's preferred hand and another touch sensitive auxiliary control or input device, such as, e.g., a touch sensitive mouse. Displaying a display widget in response to detection of touch, specifically when a user grabs an auxiliary control or input device, can exploit a user's desire, to utilize the display widget, implicit in the user's action in reaching for and grabbing the auxiliary control or input device. The display widget would be dismissed when the user releases the auxiliary control or input device, for example, when touch contact is broken. Displaying and dismissing a display widget in this fashion advantageously places little, if any, additional cognitive burden on the user.
With reference to
Although the exemplary environment described herein employs the hard disk, the removable magnetic disk 29 and the removable optical disk 31, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memory (ROM), and the like, may also be used in the exemplary operating environment.
A number of program modules may be stored on the hard disk, magnetic disk 29, optical disk 31, ROM 24 or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37, program data 38, and device drivers 60. The device drivers 60 processes commands and information entered by a user through input devices 43, which can include a keyboard, mouse, game controller, trackball, touchpad. The input devices also can have auxiliary controls such as a joystick, game pad, touchpad, trackball, key, headset, monitor, microphone, button, knob, rocker switch, trigger, slider, wheel, lever, touch strip, biometric sensor, etc. The input devices 43 may be wired or wirelessly coupled to the personal computer 20.
According to an exemplary embodiment of the present invention, at least one of the input devices includes a touch sensor 40 and an input device such as a mouse may have both a touch sensor 40 and a movement transducer 42. Touch sensor 40 is capable of generating a signal that indicates when a physical presence, such as a user's hand, is touching one of the input devices 43 itself or an auxiliary control thereof. Movement transducer 42 is capable of generating a signal that indicates when a user causes part of the input device to move. The signals generated by touch sensor 40 and movement transducer 42 can be passed along a conductor connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus 23, but may be connected by other interfaces, such as a sound card, a parallel port, a game port or a universal serial bus (USB).
A monitor 47 or other type of display device may also be connected to the system bus 23 via an interface, such as a video adapter 48. In addition to the monitor 47, personal computers may typically include other peripheral output devices, such as a speaker 45 and printers (not shown).
The personal computer 20 may operate in a networked environment using logic connections to one or more remote computers, such as a remote computer 49. The remote computer 49 may be another personal computer, a hand-held device, a server, a router, a network PC, a peer device or other network node, and typically includes many or all of the elements described above relative to the personal computer 20, although only a memory storage device 50 has been illustrated in
When used in a LAN networking environment, the personal computer 20 is connected to the local area network 51 through a network interface or adapter 53. When used in a WAN networking environment, the personal computer 20 typically includes a modem 54 or other means for establishing communications over the wide area network 52, such as the Internet. The modem 54, which may be internal or external, is connected to the system bus 23 via the serial port interface 46. In a network environment, program modules depicted relative to the personal computer 20, or portions thereof, may be stored in the remote memory storage devices. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. For example, a wireless communication link may be established between one or more portions of the network.
In some contact sensor embodiments, a touch sensor includes a conductive film that has a capacitance that changes when it is touched. This sensor also includes a capacitive measuring circuit that generates an electrical signal based on the change in capacitance of the conductive film. Those skilled in the art will recognize that other contact sensor technologies are available such as photodiodes, piezoelectric materials, and capacitive pressure sensors. Any of these sensors may be used within the context of the present invention. In one proximity sensor embodiment, the touch sensor uses reflected light from an LED to detect when the user is proximate the sensor. A chip used to drive the LED and sense the reflected light according to this illustrative embodiment may be produced by Hamamatsu Corporation of Bridgewater, N.J. Other proximity sensor embodiments use changes in electric or magnetic fields near the input device to determine when the user is proximate to the device.
In embodiments of the present invention, the touch sensors may provide the same information regardless of where on the touch sensor the user touches the input device or the portion of the sensor to which the user is proximate. Thus, these touch sensors decouple touch data from position data.
In other embodiments, for example with touchpads, touch screens, and touch tablets, a given touch sensor may provide location information that would indicate where the user made contact within that touch sensor or where the user came closest to the touch sensor within the touch sensor. In these devices, one cannot specify positional data without touching the device, nor can one touch the device without specifying a position. Hence, touch sensing and position sensing are tightly coupled in these devices.
Those skilled in the art will also recognize that the number of input lines tied to microcontroller 120 depends on the number of sensors on the input device and the configuration of the input device. For example, for a keyboard, the microcontroller uses input lines to determine if any of the auxiliary controls have been activated. The micro controller accomplishes this using a multiplexer (not shown) to sequentially test the state of each auxiliary control on the keyboard. The techniques used to detect these auxiliary control states closures are well known in the keyboard art.
In a mouse or trackball, input lines 122 include lines for detecting the closure of switches and lines for detecting the rotation of encoder wheels. The switches are located beneath buttons on the mouse or trackball. The encoder wheels track the movement of the mouse ball or trackball. Typically, one encoder wheel tracks movement in the X direction and another encoder wheel tracks movement in the Y direction. In most embodiments, each encoder wheel has its own associated input line into microcontroller 120. In some mice, an additional encoder wheel tracks the rotation of a wheel located on top of the mouse.
In some mice, the X and Y movement of the mouse is tracked by a separate optics microcontroller that is connected to microcontroller 120 through lines 122. The optics microcontroller uses optical data to determine movement of the mouse. The optical microcontroller converts this optical data into movement values that are transmitted to microcontroller 120 along input lines 122.
In a game controller such as a game pad, input lines 122 include lines for detecting the closure of multiple switches on the game pad as well as lines for detecting the rotation of wheels on the game pad. In joysticks, input lines 122 can include lines connected to resistance wipers on the joystick as well as switches on the joystick. In headsets, lines 122 include multiple lines that carry multi-bit digital values indicative of the magnitude of the analog electrical signal generated by the microphone. An analog-to-digital converter typically produces these digital values. To reduce the weight of the headset, the analog-to-digital converter and microcontroller 120 can be found on a soundboard located within the computer. To further reduce the weight of the headset, multiplexer and A-to-D converter 116 of
Microcontroller 120 produces an output 124, which is provided to serial port interface 46 of
Output line 158 carries signals from microphone 152 and from touch sensor 156. In some embodiments, headset 150 is connected to a computer system that includes a speech recognition system. In these embodiments, the speech recognition system is inactive unless touch sensor 156 indicates that a user is touching headset 150. The activation of the speech recognition system can include loading the speech recognition system into random access memory when the user first touches headset 150. It can also include prompting a speech recognition system that resides in random access memory so that it can process input speech signals. In either case, by only activating the speech recognition system when headset 150 indicates that the user is touching the headset, the present invention reduces the likelihood that extraneous speech will be processed by the speech recognition system.
Thus, a mouse according to exemplary embodiments of the present invention is able to detect when certain areas of the mouse are being touched and when portions of the mouse or the entire mouse are being moved. Specifically, the conductive films on the palm-rest 172, left button 174, and side areas 184 and 186 indicate when the user is touching these areas. Note that even if the user does not move the mouse or press a button, the sensors associated with the conductive films of
In alternative embodiments of the present invention, trackball 190 and encoder wheels 194 and 196 are replaced by a solid-state position-tracking device that collects images of the surface that the mouse travels over to determine changes in the position of the mouse. According to these exemplary embodiments, the mouse typically includes a light source used to illuminate the surface, an optics system used to collect images of the surface, and a processor used to compare the various images to determine if the mouse has moved, and if so, in what direction. Since the solid-state position-tracking device converts movement into an electrical signal, it can be considered to be a sophisticated transducer or motion sensor.
Note that all of the exemplary embodiments of
Although various exemplary embodiments have been described with particularity with respect to touch sensor location in
In illustrative embodiments of the invention, game controllers such as those of
Additional touch sensors can be located on keyboard casing 301 at portions 306 and 307 below space bar 308, at portion 309 below arrow keys 310, and at a portion 311 below keypad 304. Arrow keys 310 are typically used by the user to move a cursor across the display. Note that although keyboard 300 is shown with touch sensors on the keys and touch sensors on portions 306, 307, 309, and 311, other exemplary embodiments of the invention may only have touch sensors on the keys or only on one of the portions 306, 307, 309, and 311. In other exemplary embodiments, different combinations of these touch sensors can be found on the keyboard 300. In addition, some or all of the touch sensors on portions 306, 307, 309, and 311 may be proximity sensors. Touch sensors 306, 307, 309 and 311 may represent many types of auxiliary controls including, but not limited to, a joystick, game pad, touchpad, trackball, button, knob, rocker switch, trigger, slider, wheel, lever, etc. The proximity sensors can detect the user's hand when it is near the sensor without requiring the hand to actually contact the sensor. Generally, one signal is provided when the user touches, but does not activate (e.g., depress, turn, roll), the auxiliary control, and a second signal is provided when the user activates the auxiliary control. In exemplary embodiments of the invention, a keyboard including its auxiliary controls can detect a physical presence (e.g., a finger) contacting a touch sensitive surface thereof, the physical presence representing an explicit user request to display a display widget on a display screen and/or to generate other feedback (e.g., acoustic, tactile). The feedback can provide information to the user such as status information, control functionality, and help text. The information may vary from application to application. In some embodiments of the invention, the position of the display widget on the display screen may track the movement of the physical presence across the touch sensitive surface.
As has been described, keys, buttons, knobs, rocker switches, or other auxiliary controls of an input device can be augmented with sensors that detect contact or extreme proximity of a physical presence including, but not limited to, a user's hand (e.g., finger, palm) or a stylus. Illustrative input devices have been shown and described previously including mice (
Serial interface 46 converts the serial binary signal from input device 43 into parallel multi-bit values that are passed to device driver 60. In many embodiments of the present invention, device driver 60 can be implemented as a software routine that is executed by CPU 21 of
Based on the designated protocol, device driver 60 converts the multi-bit values into device messages that are passed to operating system 35. These device messages indicate what events have taken place on the input device. For example if a touch sensor on a mouse has been touched, the message indicates that the particular sensor is being touched. When the touch sensor is released, a separate message is generated by device driver 60 to indicate that the touch sensor has been released.
The messages generated by device driver 60 are provided to operating system 35, which controls the routing of these messages. According to illustrative embodiments, the device messages are usually sent to a focus application 812. The focus application is typically the application that has the top-most window on the display.
In some illustrative embodiments, operating system 35 maintains a list of message hook procedures that have been registered with the operating system. In these illustrative embodiments, operating system 35 sequentially passes the device message to each message hook procedure on the list before sending the message to focus application 812. Such message hook procedures are shown generally as message hook procedures 810 of
The message hook procedures and the focus application use the device messages, especially those indicating that a touch sensor has been touched, to initiate a variety of functions that are discussed below.
In window 328, a caret 330 is positioned within a sentence of an open document. Caret 330 may be positioned by moving mouse 170 or ball 228 of trackball 220. In
The position of caret 330 within the sentence of window 328 causes a tool tip 332 to appear. Tool tip 332 indicates who entered the word that caret 330 is positioned over.
Window 328 also includes a tool bar 334 that includes drawing tools that can be used to draw pictures in the document of window 328.
According to exemplary embodiments of the present invention such as shown in
Those skilled in the art will recognize that the disappearance of caret 330, tool tip 332, and tool bar 334 when the user is not touching the input device can be controlled independently. Thus, the user may customize window 328 such that tool tip 332 and tool bar 334 disappear when the user releases the input device, but caret 330 remains visible. In addition, the rate at which items disappear and reappear can be controlled. Thus, it is possible to fade images off the display and to fade them back onto the display as the user releases and then touches the input device. In some illustrative embodiments of the invention, the fade-out period is 0.7 to 1.0 seconds to minimize distraction, and the fade-in period is 0.0 seconds for the caret, which appears instantly, and 0.3 seconds for toolbars. In certain embodiments, the fade-out time may be a variable configurable by a user with a preset default period.
In other exemplary embodiments, the user may move left and right across menu bar 358 by using the keys representing the numbers “4” and “6” on numeric keypad 304. As the user moves across menu bar 358 a different pull-down menu can be displayed for each respective menu heading. Specifically, by touching the key representing the number “4”, the user causes a keyboard message to be sent to the application, which changes the display so that the menu heading to the left of the current menu heading in header menu 358 is displayed. Thus, if the pull-down menu for the menu heading “Tools” is currently displayed in window 352, touching the key representing the number “4” causes a pull-down menu associated with the menu heading “Insert” to be displayed. Similarly, the user can cause a pull-down menu to appear for a menu heading to the right of the current menu heading by touching the key representing the number “6” on numeric keypad 304. Thus, if the current pull-down menu is associated with the menu heading “Tools”, and the user touches the key representing the number “6”, the pull-down menu associated with the menu heading “Format” in header menu 358 will be displayed. This is shown in
By touching the keys representing the numbers “2” and “8” on numeric keypad 304, the user can also move up and down within a pull-down menu such as pull-down menu 360. As the user moves through a pull-down menu, different items within the pull-down menu become highlighted. An example of a highlighted entry is entry 362 of
In the prior art, pull-down menu 360 will continue to be displayed, even if the caret is positioned outside of the pull-down menu itself. The only way to make the pull-down menu disappear is to click on an area outside of the menu itself. However, according to an illustrative embodiment of the present invention, the application that produces the pull-down menu, removes the pull-down menu as soon as it receives a mouse message that indicates that the user released the pointing device. This improves user efficiency by reducing the movements the user must make to close the pull-down windows associated with header menu 358.
Using keyboard 300, a focus application displays radial menu 370 when it receives a keyboard message indicating that a user touched one of the keys in keypad 304. To highlight a specific entry, the user touches a key in keypad 304 that is spatially related to the entry. For example, to highlight entry 373 of radial menu 370, the user touches the key representing the number “8”, which is located directly above a center key representing the number “5” because the spatial positioning of the “8” key relative to the “5” key is the same as the spatial relationship between entry 373 and cancel button 372. To select an entry, the user depresses the key that causes the entry to be highlighted. To dismiss the radial menu, the user depress the “5” key.
To manipulate the radial menu using the touch sensors of button 670 on the mouse of
According to illustrative embodiments of the invention, the use of touch sensitive controls and devices may be transparent to the user. The context of the situation may be indicated by the user's preparatory actions with the control, such as grabbing, touching, or approaching the control device. Referring to
In another illustrative embodiment of the invention, when the user approaches or touches the control knob 314, without activating the control, a display widget such as a tool tip can instantly be displayed on the display screen and identify the current functionality of the control knob 314. For example, a tool tip may indicate, but is not limited to, one of the following functions 1) tuning for a variety of different applications including audio and video applications; 2) volume control for media applications; 3) volume control for system generated sounds; and 4) control for numerous features which can have multiple settings (e.g., brightness, cropping, color, etc.). In other illustrative embodiments, as a user approaches a control, such as control knob 314, visual feedback may be provided on the actual control knob by an LED or LCD alone or in addition to the display widget on the display screen. In still further illustrative embodiments, acoustic or tactile (e.g., vibration) feedback may be provided alone, or in addition to visual feedback on the display screen, input device and/or control, or to each other. Consequently, the input device or control may be able to directly provide feedback (e.g., acoustic feedback) with or without involving or sharing the information with the host computer. In still further exemplary embodiments, one or more portions (e.g., top and side) of the control, such as control knob 314, may be able to independently detect contact or user proximity and generate unique messages for the host computer based on which portion of the control is being touched.
In another illustrative embodiment of the present invention based on the keyboard input device of
An illustrative implementation of various auxiliary controls for an exemplary keyboard input device and their context sensitive response to touch are listed below in Table 1. It should be understood that the various controls and responses may be applied to other input devices such as game controllers, trackballs, mice, touchpads, etc.
CONTEXT-SENSITIVE RESPONSE TO TOUCH
Volume Knob (e.g.,
Touching can show volume setting GUI with
control knob 314 in
clickable slider (e.g., FIG. 27) that can be used to
FIG. 18B) or
adjust the volume of audio associated with media (as
Volume Up and
opposed to the volume for other system-generated
Volume Down Keys
sounds). Touching the volume knob or at least one
of the volume up and down keys does not alter the
volume; it only brings up the display. The display
disappears at the cessation of touch (possibly after a
brief time-out). Thus, the user can touch the volume
knob or volume up and down keys to view the
current volume setting, without necessarily changing
One or more of
Touching can show a display widget including a
Play, Mute, Pause,
multimedia control panel. The multimedia control
Stop, Next Track,
panel may show graphical representation of the
Previous Track, and
controls, plus other information such as album
name, track name and length, etc.
Touching can show programmed content; with
Launch Button, or
clickable area to launch specific applications, as
as replacement or in
well as other UI for adding, removing, or
reorganizing applications that can be launched.
the behavior listed
for the controls
Touching can show number of new messages, brief
summary of recent, unread high-priority messages,
or bring an up Inbox window for the mail client.
Glance into running application: Touching the key
can bring application to the foreground, releasing
the key sends the application to the background. If
the user actually presses the key, the application can
come forward and stay in the foreground when the
user releases the key. If the application is not
already running, touching the key may or may not
launch the application.
Button or Key
tion Button or Key
tion Button or Key
Touching can show most recently used searches or
equivalent of past activities or search results.
Touching can show thumbnail or history of
previous/next websites visited. This feature can
allow the user to see if the desired page was
available on the visited list, and to see how many
times it would be necessary to press Forward or
Back to reach a desired page.
Stop or Refresh
Touching can show current page loading
Buttons or Keys
information (if any), including amount of page
loaded and expected time to complete the download,
as well as any status or error information, allowing
the user to decide whether they want to stop.
Touching can show most recently used favorites or
UI for organizing favorites.
Touching options may include: 1) Show/Hide the
Task Bar when the user touches or releases the
(e.g., Rocker Switch
Application Switch Control; 2) Change the content
(e.g., rocker switch
of Task Bar, showing more or less detail, or
315 in FIG. 18C),
emphasizing the Task Bar so it is clear how the user
Dial Switch, or
is changing applications, and the next or previous
application to appear is more predictable; 3)
App Keys, and Key
Showing a separate on-screen display of running
applications (titles, icons (e.g., FIG. 28), or thumb-
nails) so that the user can more efficiently navigate
to the desired application. For example, the current
on-screen display for the Alt-Tab key combination
can appear when the user touches the control.
Touching can cause GUI to be displayed showing
Switch or Key
options for sleep mode including Stand By, Log Off,
Restart, and Shut Down.
Touching can hide the scrollbars and/or other
ancillary UI such as toolbars and status indicators
while scrolling, or as long as the user maintains
contact with the scrolling mechanism (e.g., wheel,
Cut, Copy, Paste
Touching can show contents of the clipboard or
Stop (Esc), Help,
Touching can 1) show status of alerts; or 2) show
New, Open, Close,
macros of programmed keys.
Spell Check Key
Touching can show/hide indicators of spelling/
grammar issues, such as the “red squiggly” lines
that are used to highlight spelling errors in Microsoft
Save or Save As
Touching can show time, date, location, and file
type for most recent save.
Print Control (e.g.,
Touching can show current printer queue and job
status for default printer(s).
Touching can show log-on status. Log-on status
information can include, among other information,
log-on id, domain, status of login, and a log of any
errors or delays encountered.
Fn (function key
Touching can show 1) on-screen display of mapped
functionality of F1- F12 keys for given application;
or 2) on-screen display for each F1-F12 key if Fn
When help function is selected, context sensitive
help can be displayed on touch of controls on the
input device (e.g., mouse or keyboard).
Help finding a key
The keyboard help can direct user to a key by
sensing where the user is on the keyboard and
pointing the user to the right key.
Touching keys in combination can display the key
combination function (e.g., Ctrl key + c key =
copy). It might also show status or state information
associated with the command. For example, the Ctrl
key + c key could show the current clipboard
contents (or alternatively, the clipboard contents that
would result if the user were to execute the
Context Menu Key
Touching can show the right-click context menu for
the current cursor or pointer position, which may
change as the user moves the mouse cursor pointer.
Touching keys can show lock status, (i.e., on or
off). Touch sensitive feature may be used to replace
Caps Lock Key
Touching specific buttons or keys can show maps,
tools, views, etc.
Touching specific control can show its function.
Touching control can 1) show status of alerts; 2)
show macros of programmed keys; or 3) show other
mail status information as detailed as the Mail
application launch key described above including
number of new messages, brief summary of recent,
unread high-priority messages, or bring an up Inbox
window for the mail client. Touching the control
might also show additional information specific to a
current message that the user is contemplating
replying to, such as showing other recent messages
sent to the same recipient.
+, −, /, *, = Keys
In spreadsheet or word processing application, after
user has selected range of cells (e.g., column),
touching an operation key can perform the operation
or show what result of operation would be without
actually inserting it into the spreadsheet.
Touching can show current state of numeric keypad
Below, Table 2 describes illustrative techniques for context-sensitive response to touch on an exemplary mouse input device according to the present invention.
CONTEXT-SENSITIVE RESPONSE TO TOUCH
A small raised area in the corner of the right mouse
button can be touch sensitive. The user can use the
right mouse button as usual if he or she does not
touch this area. This raised area looks different and
invites touching, leading to discovery of right-click
functionality. If the user touches this area, the right
mouse context menu can appear. As the user moves
the mouse around while touching this area, context
menus for the different objects can appear. The user
can then click the right mouse button per usual to
interact with the menu.
Touching shows current configuration and
customization algorithms for how the wheel can be
used (e.g., lines per notch for scrolling, scrolling
acceleration, assignment of middle-button-click
functionality). Touching can also show or hide the
In addition to many of the types of visual feedback that may be provided on a screen in response to user contact with a touch-sensitive control, another possibility is to display a standard tool tip, such as those illustrated in
Typically, the on-screen display can be placed near the current cursor or pointer (e.g., caret) position regardless of the input device that the user touches. For example, a keyboard tool tip could appear next to the cursor. Popping up the on-screen display to the right of and above the current cursor position can be beneficial, since the on-screen display does not conflict with traditional tool tips which appear when the user dwells with the pointer over an icon (tool tip appears to the right of and below the pointer or cursor) in the Windows® operating system by Microsoft Corporation of Redmond, Wash. The tool tip can follow the cursor or pointer as the user moves the cursor or pointer with a pointing device (e.g., mouse), or it can remain stationary at the point where it initially appears. Maintaining the tool tip where it appears rather than moving the tool tip with the cursor is easier to implement and more efficient, and would likely be well accepted by users. According to other exemplary embodiments of the present invention, the display widget may be displayed at the center of the screen, at the center of the currently active (“focus”) application or widget (e.g. a text entry box), at the bottom of the screen, or above the system tray icons.
In another exemplary embodiment of the present invention, each hot key may be assigned a text macro, where activating the hot key causes a block of text to be inserted, for example where the cursor is located on the screen. When used in this context, touching a hot key displays at least the beginning or another portion, if not all, of the text macro assigned to the hot key as shown in
As mentioned previously, according to some exemplary embodiments of the present invention, acoustic or tactile feedback may be employed. Acoustic or tactile feedback can be used in combination with or separately from visual feedback on the display. In some cases, visual feedback may not be appropriate, or acoustic feedback may be desired because of the currently running application, the input device that is currently being used, or user preference.
According to certain embodiments of the invention, acoustic feedback, for example, appropriate cue tones or other sounds could be generated, as the user touches a control. A desired audio cue tone may be mapped to a specific function or control. Volume, pitch, and timbre could be adjusted to produce appropriate cues that mimic desired sounds, such as voice-generated announcement of a control function. Cue sounds may be generated by taking parametric sound event requests and sequencing them using MIDI wavetable synthesizer 662 through audio generator 640 (illustratively the Creative Labs AWE64 Gold card sound board) (see
Acoustic feedback to identify functionality and other information may be particularly useful for gaming applications and products such as the MS Game Voice™ by Microsoft Corporation of Redmond, Wash. For example, gaming products may include a headset microphone combination attached to a puck. A puck allows a user to selectively talk to multiple combinations of people and teams with whom he or she is playing. Each person may be automatically assigned a code (1,2,3 . . . ) and a team (A,B,C . . . ). A problem may arise when the player has to remember which code corresponds to which player and team. When the user wants a reminder to whom a button is assigned, the user may touch a control (e.g., number key) and receive acoustic feedback of the name of the person assigned that code via their headset.
In one exemplary embodiment of the present invention identified in Table 1, multiple touch areas on an input device can be used to page backwards and forwards through web pages provided by an Internet browser. Examples of input devices having multiple touch sensitive areas useful in paging backward and forward include, among others, the mice of
Note that a mouse according to an illustrative embodiment of the present invention can be configured so that paging functions are initiated simply by touching one touch sensor instead of touching a sequence of two touch sensors. Thus, in
The paging functions performed using these touch areas are shown in
It should be understood that the various responses to making contact with or being in extreme proximity to a touch sensitive control may be used in combination. For example, when a user first makes contact with a button, the button's function may be displayed. In one implementation, if the user maintains contact with the button for more than a prescribed amount of time (e.g., five seconds), more detailed status information may be displayed or a GUI may be available to the user. Alternatively, successive touches of the same button within a predetermined period of time may cause different types of information to be displayed such as the button functionality followed by a GUI. Tactile or acoustic feedback may also be provided following an initial touch with a display of the same or more detailed information following a second touch in a predetermined time period or after touching has been detected for a prescribed time period.
In responsive to detection of a user in contact with or proximate to an input device or auxiliary control of the device, the on-screen display of a display widget may occur instantaneously. Frequently, it may be desirable to delay the appearance of the display widget on the screen slightly so that if a user activates, rather than merely touches, the control or device to activate a function, for example, the display widget will not rapidly appear and disappear from the screen. Delaying the appearance of the display widget a predefined amount of time can prevent unnecessarily displaying of a display widget with tool tip information for example, to a user who is familiar with the active application and the operation of an input device and its auxiliary controls and who rapidly activates the device or its control (e.g., depresses a button) to activate a function. Several illustrative techniques according to the invention are described below that address controlling the display.
In one embodiment of the invention, a brief time period on the order of 0.3 seconds may be employed. In this instance, if a user makes contact with, but does not activate, a key or other control within the brief time period, then the on-screen display appears. If the user activates the control before the expiration of the brief time period, the on-screen display would not be displayed in response to the user contacting the control.
According to some embodiments of the invention, activation of the control (e.g., turning a knob) causes the state of the function controlled (e.g., volume) to change and may display a GUI (e.g., volume setting) as the user changes the state (e.g., volume setting). In contrast, when touching, but not activating, the control for the entire brief period, a GUI representing the existing state (e.g., current volume) of the function may be displayed without causing the state to be changed.
Similarly, according to embodiments of the present invention, a brief time period may also be used to control disappearing or fading out of the on-screen display when a user ceases contact with a control. In this instance, the on-screen display remains visible during the brief time period, at the expiration of which the on-screen display disappears or fades out. If the user again touches the control before the brief time period expires, the on-screen display remains visible. It should be understood that the same type of time periods may be applied in embodiments of the present invention in which detecting contact of a control by a user causes a display widget to be dismissed (i.e., disappear or fade-out) and ceasing contact of the control causes the display widget to reappear or fade-in.
According to illustrative embodiments of the invention, when a display widget including a tool tip or other information appears, schemes for such display can be based on a number of criteria including the control, timeout and other information such as mouse movement.
According to the timing diagram shown in
In the timing diagram depicted in
Another aspect of display schemes for the touch sensitive input control display involves the response of a tool tip or other display widget to user activation of the button or other input control. After the user activates the control, the user may no longer desire the feedback (of the resulting action or otherwise). For example, at the time that a user clicks a button (button down event), the button tool tip can instantly disappear (or fade out). Also, the button tool tip may reappear or stay hidden after a button up event occurs if the user maintains contact with the button. The computer system can also display visual feedback to associate the button click with the information displayed in the tool tip before the tool tip disappears. According to an illustrative embodiment as depicted by the timing diagram shown in
Other embodiments of the invention involve handling simultaneous contact with multiple controls on an input device. If a user touches one control while maintaining contact with a second control, the on-screen display or other feedback for the second control should be generated. Alternatively, certain functions can be defined by a combination of controls, for example, key combinations. In this instance, the tool tip of the combination (e.g., key combination) is displayed when both keys are simultaneously touched but not activated, which will override the tool tip, if any, associated with the first key contacted. If the user releases one of the controls, the on-screen display may be dismissed in its entirety, or the feedback for the other touched control can be reinstated.
In another embodiment of the present invention, once the on-screen display in the form of a GUI has appeared or faded in, the GUI may remain visible if the cursor or pointer (e.g., by movement of a mouse) has been located therein, even if the user ceases contact of the control (e.g., button of a touch sensitive mouse) that caused the display of the GUI. In this instance, the GUI may eventually disappear in response to movement of the cursor (e.g., movement of a mouse) outside of the GUI, activation of another control or after a predefined period (e.g., 5 seconds) of inactivity in which no input is received by computer such as movement of a mouse.
According to illustrative embodiments of the invention, an on-screen display may be faded-in and out using an animated transition. It should be understood that techniques for controlling appearance and disappearance of an on-screen display may be used alone or in combination. An embodiment of the invention providing animated transition is described below with respect to
The touch outputs provided by input devices 43 can be applied, as represented by leads 903 and 907, respectively, to input interfaces 46. These interfaces can produce separate signals reflective of whether contact is then being sensed or not by the contact sensor of each touch sensitive component (e.g., auxiliary control) of each input device. These signals may be routed, as represented by lead 905, to input device drivers 60 that form a component within operating system 35. The device drivers interpret the signals produced by the input devices and, in response, generate appropriate events. With respect to touch, these events can specify the particular input device and the state of the corresponding touch sensor, e.g., whether hand contact is detected. These events can be passed by operating system 35 to application 36 and, ultimately within the application, to GUI process 910. Within this process, the events are processed by fade-in/fade-out animation process 915. The animation process, in response to the occurrence of a state transition of each input device, i.e., whether that device has just started sensing hand contact or has just ceased sensing such contact, and whether a display widget (e.g., Tool Glass or toolbar(s)) is then being displayed or not, will generate a predefined animation sequence to either controllably fade-in or fade-out the display widget.
Bitmap generator 920 stores predefined patterns 922, 924 and 926, typically texture maps, for the various display widgets, including the Tool Glass sheet, predefined toolbar(s) and/or other display widgets, respectively. These patterns are typically stored as separate files within the application. As application program 36 is invoked, the application, during initialization or after any change to the widget, downloads these patterns to Graphics API 940 via line 930 which, in turn, may route these patterns to a graphics accelerator (not shown) for local storage therein as texture maps. Alternatively, this downloading may be managed by a service provided by operating system 35.
During subsequent display, the accelerator will read these maps from its local store, polygonally fill these maps as appropriate, and render resulting filled patterns on display 47. Once these maps have been downloaded, then, for either a controlled fade-in/fade-out operation, animation process 915 changes an alpha-transparency value at which the graphics accelerator will render a corresponding filled pattern for a display widget. For a toolbar, the alpha-transparency value is varied across a full range of transparency values (i.e., between approximately 0 α and 1.0 α, on a linear scale of 0-1 α where 0 α is fully transparent and 1.0 α is fully opaque). For a Tool Glass sheet, the alpha-transparency value is varied across a range of typically 0 α to approximately 0.7 α, such that, even with the Tool Glass sheet rendered at its maximum opacity, underlying document objects are still visible (which some obscuration) through the sheet.
In essence, for a fade-in or fade-out operation, animation process 915 will issue a series of instructions over a predefined interval of time, specifically one such instruction for each different display frame, to successively change the alpha-transparency value with which a particular display widget is to then be displayed. These instructions will be issued, as also represented by line 930, to operating system 35, which, in turn, will pass these instructions to Graphics API 940 and ultimately to a graphics accelerator.
Fade-in should occur over a relatively short interval of time, such as on the order of approximately 0.3 to 0.5 seconds. However, so as not to distract a user, fade-out should occur over a relatively long interval, such as on the order of approximately 0.7-1.0 seconds. During these intervals, particularly on fade-in, the alpha-transparency values are generally varied in a non-linear fashion. Empirically, to utilize a conventional slow-in/slow-out technique commonly used in screen animation has been chosen. With this technique, the opacity initially changes rather slowly from being substantially, if not, totally transparent (i.e., essentially invisible) to an intermediate value, then increases rather quickly to another intermediate value with further increases then slowing once again until a maximum opacity (either, e.g., 1 α or 0.7 α for a toolbar or Tool Glass sheet, respectively) is eventually reached. This results in an approximately “S” shaped curve for opacity as a function of time. The same transparency variations are used for fading-out a display widget (though in a reverse direction). Clearly, other time-based opacity functions, such as a linear function, can be used to vary the opacity during the fade-in and fade-out intervals. Ultimately, the particular function(s) chosen (with possibly a different function being used for fade-in versus fade-out and, in fact, different such functions can be used for different display widgets, if desired) will likely be empirically determined through appropriate user testing.
Furthermore, a human eye exhibits increased sensitivity to certain colors, such as, e.g., red tones, over others, such as blue tones, for a common luminance. Hence, fading-in a display widget that contains any of the former colors, even at relatively low luminance, could be potentially distracting and more so particularly as these colors become brighter. To avoid such distraction, the display widget could be represented by several different texture maps of different or varying coloration and luminance—particularly for color(s) to which the human eye is most sensitive—until a final map with desired coloration and luminance is displayed. In that regard, a monochrome texture map for this widget could be initially displayed, with texture maps for the same widget but having desired coloration with increasing luminance (or even different coloration for that matter) then being rendered at appropriate times during fade-in, until at the end of the fade-in period, a texture map having a final coloration and luminance is rendered. Fade-out could be accomplished in a similar, though reverse fashion. For example, a display widget could fade-out using a succession of colored texture maps, of decreasing luminance, to a monochrome map which itself then fades out to total transparency, or, at the inception of fade-out, change to a monochrome map of the widget and from there fade-out to total transparency.
If a graphics accelerator is not used, then, as symbolized by line 955, Graphics API 940 can provide graphics output directly to video adapter 48 (specifically a standard video card, not shown, therein), which, in turn, will generate appropriate video signals and apply those signals to display 692. In this instance, the computer system would need to be sufficiently fast to implement the appropriate graphics capabilities, that would have been provided by the graphics accelerator, in software. Furthermore, where fade-in and fade-out graphics capabilities are not supported, the display and dismissal of display widgets could occur through other visual techniques. These techniques include, e.g., simply translating the widget by sliding or shuffling it onto the screen from an off-screen position; instantly and completely displaying or dismissing the widget; rotating the widget (if, e.g., a toolbar is on a 3-D surface that rotates into place) and/or zooming in or out interface widgets or portions of a document. However, with these techniques, the display widgets such as the toolbars and the Tool Glass sheet are constrained to being displayed fully opaque. Any of these techniques could also be used along with fading with a graphics accelerator that supports alpha-transparency.
Although alpha-transparency capability is supported by a wide variety of currently existing graphics accelerators, this capability can be readily simulated in software, in a well-known manner, by conventional 2-D (two-dimensional) or 3-D (three-dimensional) graphics APIs, such as D3D (which is a 3-D graphics API currently produced by Microsoft Corporation as a standard component of a WINDOWS® operating system), OpenGL (which is currently available in the art) or GDI (which historically is only a 2-D low-level graphics processing layer currently produced by Microsoft Corporation and also incorporated as a standard component of a WINDOWS® operating system).
Instances can arise where a display screen is to simultaneously show both a toolbar(s) and a Tool Glass sheet (or other combinations of display widgets). In these instances, unwanted interactions can arise that would cause both widgets to fade-in or out. To prevent these interactions and attendant user frustration, an appropriate decision process, well within the skill in the art, would be incorporated into animation process 915 to then permit only one, rather than both, of these display widgets to fade-in or out. For example, if both widgets were being displayed but a user is then manipulating the Touch Mouse, then only the Tool Glass would be permitted to fade-out while the toolbars remained fully displayed. The specific decision process would be governed by the particular widgets that could be simultaneously displayed, a need to continue displaying one or more these widgets based on a current contextual setting of the application including an operation then being performed, and relative display prioritization among these widgets.
It should be understood that the present invention may employ other sensing technologies, apart from touch sensing, to invoke on-demand action, such as, e.g.: galvanic skin response, non-contact proximity sensors, pressure sensors, events from touch/proximity sensors on a keyboard, data from a GPS (global positioning system) receiver (position of the user or location of a mobile computer), video data from a camera, and audio data from a microphone.
While particular embodiments of the present invention have been described and illustrated, it should be understood that the invention is not limited thereto since modifications may be made by persons skilled in the art. The present application contemplates any and all modifications that fall within the spirit and scope of the underlying invention disclosed and claimed herein.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4028695||Jul 11, 1974||Jun 7, 1977||The Solartron Electronic Group Limited||Data terminals having interactive keyboards and displays and data processing apparatus incorporating such terminals|
|US4317956||Nov 10, 1980||Mar 2, 1982||Bell Telephone Laboratories, Incorporated||Remote chalkboard automatic cursor|
|US4403777||Jan 8, 1981||Sep 13, 1983||Mattel, Inc.||Electronic game using phototransducer|
|US4977397||Oct 13, 1989||Dec 11, 1990||Sysgration Ltd.||Touch-control computer house|
|US5208903||Sep 10, 1990||May 4, 1993||Eastman Kodak Company||Video image display for predicting color hardcopy image quality|
|US5250929||Jul 29, 1991||Oct 5, 1993||Conference Communications, Inc.||Interactive overlay-driven computer display system|
|US5252951||Oct 21, 1991||Oct 12, 1993||International Business Machines Corporation||Graphical user interface with gesture recognition in a multiapplication environment|
|US5309172||Jul 29, 1991||May 3, 1994||Fox Charles S||Computer data and command entry device|
|US5311175 *||Nov 1, 1990||May 10, 1994||Herbert Waldman||Method and apparatus for pre-identification of keys and switches|
|US5327160 *||Nov 16, 1992||Jul 5, 1994||Asher David J||Touch sensitive user interface for television control|
|US5347295||Oct 31, 1990||Sep 13, 1994||Go Corporation||Control of a computer through a position-sensed stylus|
|US5355148||Jan 14, 1993||Oct 11, 1994||Ast Research, Inc.||Fingerpoint mouse|
|US5426450||Oct 4, 1994||Jun 20, 1995||Wang Laboratories, Inc.||Hands-free hardware keyboard|
|US5457480||Oct 3, 1994||Oct 10, 1995||Dell Usa||Integrated mouse and numerical keypad device|
|US5530455||Aug 10, 1994||Jun 25, 1996||Mouse Systems Corporation||Roller mouse for implementing scrolling in windows applications|
|US5559301||Sep 15, 1994||Sep 24, 1996||Korg, Inc.||Touchscreen interface having pop-up variable adjustment displays for controllers and audio processing systems|
|US5572238||Jan 27, 1995||Nov 5, 1996||Xerox Corporation||Computer user interface for non-dominant hand assisted control|
|US5589855||Aug 14, 1992||Dec 31, 1996||Transaction Technology, Inc.||Visually impaired customer activated terminal method and system|
|US5592609 *||Oct 31, 1994||Jan 7, 1997||Nintendo Co., Ltd.||Video game/videographics program fabricating system and method with unit based program processing|
|US5598527||Apr 17, 1995||Jan 28, 1997||Sextant Avionique||Compact and ergonomic communications terminal equipped with proximity detection surfaces|
|US5635958||Dec 3, 1993||Jun 3, 1997||Matsushita Electric Industrial Co., Ltd.||Information inputting and processing apparatus|
|US5666113||Sep 5, 1995||Sep 9, 1997||Microtouch Systems, Inc.||System for using a touchpad input device for cursor control and keyboard emulation|
|US5666499||Aug 4, 1995||Sep 9, 1997||Silicon Graphics, Inc.||Clickaround tool-based graphical interface with two cursors|
|US5675361||Aug 23, 1995||Oct 7, 1997||Santilli; Donald S.||Computer keyboard pointing device|
|US5694153||Jul 31, 1995||Dec 2, 1997||Microsoft Corporation||Input device for providing multi-dimensional position coordinate signals to a computer|
|US5698822||May 15, 1995||Dec 16, 1997||Sharp Kabushiki Kaisha||Input and display apparatus for handwritten characters|
|US5751260||Apr 3, 1995||May 12, 1998||The United States Of America As Represented By The Secretary Of The Navy||Sensory integrated data interface|
|US5752254||Apr 8, 1996||May 12, 1998||International Business Machine Corp.||Method and system for controlling clipboards in a shared application progam|
|US5767457||Nov 13, 1995||Jun 16, 1998||Cirque Corporation||Apparatus and method for audible feedback from input device|
|US5793356||Jul 31, 1995||Aug 11, 1998||Microsoft Corporation||System and method for the software emulation of a computer joystick|
|US5798752||Feb 27, 1995||Aug 25, 1998||Xerox Corporation||User interface having simultaneously movable tools and cursor|
|US5805144||Jul 18, 1996||Sep 8, 1998||Dell Usa, L.P.||Mouse pointing device having integrated touchpad|
|US5805159 *||Aug 22, 1996||Sep 8, 1998||International Business Machines Corporation||Mobile client computer interdependent display data fields|
|US5812114||Jul 24, 1997||Sep 22, 1998||Hunter Digital, Ltd.||System for steering an electronically responsive device|
|US5818800||Jun 7, 1995||Oct 6, 1998||Barker; Bruce J.||Voice recording device having portable and local modes of operation|
|US5825356||Mar 18, 1996||Oct 20, 1998||Wall Data Incorporated||Help system with semitransparent window for disabling controls|
|US5828360||Jul 20, 1994||Oct 27, 1998||U.S. Philips Corporation||Apparatus for the interactive handling of objects|
|US5831597||May 24, 1996||Nov 3, 1998||Tanisys Technology, Inc.||Computer input device for use in conjunction with a mouse input device|
|US5841425||Jul 31, 1996||Nov 24, 1998||International Business Machines Corporation||Ambidextrous computer input device|
|US5844547||May 9, 1995||Dec 1, 1998||Fujitsu Limited||Apparatus for manipulating an object displayed on a display device by using a touch screen|
|US5847695||Jan 4, 1996||Dec 8, 1998||Siemens Business Communication Systems, Inc.||Method and apparatus for implementing a dialpad on the surface of a mouse input device|
|US5854624||Sep 12, 1996||Dec 29, 1998||Innovative Device Technologies, Inc.||Pocket-sized user interface for internet browser terminals and the like|
|US5877750||Sep 17, 1996||Mar 2, 1999||International Business Machines Corporation||Method and apparatus for in-place line width selection for graphics applications|
|US5905493||Nov 13, 1996||May 18, 1999||Unalink Communications, Inc.||Color coded instructional scheme for computers and the like system, method and article of manufacture|
|US5907327||Aug 15, 1997||May 25, 1999||Alps Electric Co., Ltd.||Apparatus and method regarding drag locking with notification|
|US5910798||Nov 25, 1997||Jun 8, 1999||Lg Electronics Inc.||Apparatus for moving a cursor on a screen|
|US5910800||Jun 11, 1997||Jun 8, 1999||Microsoft Corporation||Usage tips for on-screen touch-sensitive controls|
|US5910802||Jun 11, 1997||Jun 8, 1999||Microsoft Corporation||Operating system for handheld computing device having taskbar auto hide|
|US5914702||Mar 4, 1996||Jun 22, 1999||Hewlett-Packard Company||Pointing device with wrap-around buttons|
|US5914707||May 31, 1995||Jun 22, 1999||Seiko Epson Corporation||Compact portable audio/display electronic apparatus with interactive inquirable and inquisitorial interfacing|
|US5936612 *||May 30, 1997||Aug 10, 1999||Wang; Yanqing||Computer input device and method for 3-D direct manipulation of graphic objects|
|US5943052||Aug 12, 1997||Aug 24, 1999||Synaptics, Incorporated||Method and apparatus for scroll bar control|
|US5944151 *||Jul 9, 1996||Aug 31, 1999||Vdo Adolf Schindling Ag||Operating device|
|US5973622||Sep 12, 1997||Oct 26, 1999||Acer Peripherals, Inc.||Keyboard with a two-dimensional actuator for generating direction signals|
|US5973670||Dec 31, 1996||Oct 26, 1999||International Business Machines Corporation||Tactile feedback controller for computer cursor control device|
|US5973694 *||Apr 21, 1998||Oct 26, 1999||Chatham Telecommunications, Inc.,||Method of communication using sized icons, text, and audio|
|US5977952||Oct 29, 1997||Nov 2, 1999||International Business Machines Corporation||Method and system for an ambidextrous mouse|
|US5982302||Mar 7, 1994||Nov 9, 1999||Ure; Michael J.||Touch-sensitive keyboard/mouse|
|US5983245||Dec 27, 1996||Nov 9, 1999||Apple Computer, Inc.||Method and apparatus for implementing universal resource locator menus|
|US5987345 *||Nov 29, 1996||Nov 16, 1999||Arch Development Corporation||Method and system for displaying medical images|
|US5995101||Oct 29, 1997||Nov 30, 1999||Adobe Systems Incorporated||Multi-level tool tip|
|US6005496||May 12, 1997||Dec 21, 1999||Kinesis Corporation||Ergonomic keyboard apparatus|
|US6016520||Jul 14, 1995||Jan 18, 2000||Microsoft Corporation||Method of viewing at a client viewing station a multiple media title stored at a server and containing a plurality of topics utilizing anticipatory caching|
|US6020881||Feb 18, 1997||Feb 1, 2000||Sun Microsystems||Graphical user interface with method and apparatus for interfacing to remote devices|
|US6040817||Feb 3, 1994||Mar 21, 2000||Fuji Xerox Co., Ltd.||Display apparatus and method for displaying windows on a display|
|US6040821||Jan 19, 1993||Mar 21, 2000||Incontrol Solutions, Inc.||Cursor tracking|
|US6046728||Dec 5, 1997||Apr 4, 2000||Dell Usa, L.P.||Keyboard actuated pointing device|
|US6088023 *||Dec 10, 1996||Jul 11, 2000||Willow Design, Inc.||Integrated pointing and drawing graphics system for computers|
|US6097371||Mar 12, 1996||Aug 1, 2000||Microsoft Corporation||System and method of adjusting display characteristics of a displayable data file using an ergonomic computer input device|
|US6100875||Dec 28, 1993||Aug 8, 2000||Ast Research, Inc.||Keyboard pointing device|
|US6118450||Apr 3, 1998||Sep 12, 2000||Sony Corporation||Graphic user interface that is usable as a PC interface and an A/V interface|
|US6121960||Aug 28, 1997||Sep 19, 2000||Via, Inc.||Touch screen systems and methods|
|US6133916||Apr 8, 1998||Oct 17, 2000||International Business Machines Corporation||Graphical user interface providing access to files downloaded over a network|
|US6166723||Nov 7, 1997||Dec 26, 2000||Immersion Corporation||Mouse interface device providing force feedback|
|US6232968||Mar 31, 1998||May 15, 2001||International Business Machines Corporation||Data processor controlled display system with a plurality of switchable customized basic function interfaces for the control of varying types of operations|
|US6246405||Jun 6, 1997||Jun 12, 2001||Mci Communications Corporation||Method and apparatus for managing a plurality of objects on a graphical user interface|
|US6262717||Jul 2, 1998||Jul 17, 2001||Cirque Corporation||Kiosk touch pad|
|US6323846||Jan 25, 1999||Nov 27, 2001||University Of Delaware||Method and apparatus for integrating manual input|
|US6346951||Sep 23, 1997||Feb 12, 2002||Touchtunes Music Corporation||Process for selecting a recording on a digital audiovisual reproduction system, for implementing the process|
|US6489974||Jan 11, 1996||Dec 3, 2002||International Business Machines Corporation||Buoy icon notification of object interface accessibility in multitasking computer environment|
|US6680677||Oct 6, 2000||Jan 20, 2004||Logitech Europe S.A.||Proximity detector to indicate function of a key|
|US6686911||Oct 2, 2000||Feb 3, 2004||Immersion Corporation||Control knob with control modes and force feedback|
|US6710771||May 12, 2000||Mar 23, 2004||Sony Corporation||Information processing method and apparatus and medium|
|JP2000181602A||Title not available|
|JP2000250677A||Title not available|
|JP2000355256A||Title not available|
|JPH0511913A||Title not available|
|JPH1091307A||Title not available|
|JPH02153415A||Title not available|
|JPH05150925A||Title not available|
|JPH06175762A||Title not available|
|JPH09222876A||Title not available|
|JPH10289047A||Title not available|
|1||"Personal Computer Environmental Control Via a Proximity Sensor," IBM Technical Disclosure Bulletin, vol. 36, No. 08, Aug. 1993.|
|2||"The Design of a GUI Paradigm based on Tablets, Two-hands and Transparency", Proceedings of Computer-Human Interaction (CHI) 1997, Atlanta, Georgia, Mar. 22-27, 1997, pp. 35-42.|
|3||Albrecht Schmidt, "Implicit Human Computer Interaction Through Context," Telecooperation Office (TecO), University of Karlsruhe Germany.|
|4||B. Buxton, "Integrating the Periphery and Context: A New Taxonomy of Telematics", Computer Systems Research Institute (CSRI, University of Toronto & Alias Research Inc., pp. 1-10, downloaded on Mar. 23, 1999 from: http://www.dgp.toronto.edu/people/rroom/research/papers/bg-fg/b g-fg.html.|
|5||Beverly L. Harrison et al., "Squeeze Me, Hold Me, Tilt Me! An Exploration of Manipulative User Interfaces," CHI 98, Apr. 18-23, 1998, pp. 17-24.|
|6||Buxton, W., Hill, R., Rowley, P., "Issues and Techniques in Touch-Sensitive Tablet Input,"Computer Graphics, 19(3): pp. 215-224, 1985.|
|7||Computer Music Journal, vol. 4, No. 1, Spring 1980.|
|8||E. A. Bier et al., "A Taxonomy of See-through Tools", Proceedings of CHI 1994 Conferences, Apr. 1994, Boston, Massachusetts, pp. 517-523.|
|9||E.A. Bier et al. "Toolglass and Magic Lenses: The See-Through Interface", Proceedings of the Annual Conference on Computer Graphics SIGGRAPH 93, Anaheim, California, Aug. 1-6, 1993, pp. 73-80.|
|10||EP Search Report dtd Dec. 29, 2006, EP Pat. Appln. 02005645.|
|11||EPO Communication dated Aug. 14, 2008, 5 pages.|
|12||EPO Communication dated Oct. 22, 2007, 8 pages.|
|13||Herot, C., Weinzapfel, G., "One-Point Touch Input of Vector Information from Computer Displays," Computer Graphics, 12(3): pp. 210-216, 1978.|
|14||J. Mackinlay et al., "A Semantic Analysis of the Design Space of Input Devices", Human-Computer Interaction, vol. 5, 1991, pp. 145-190.|
|15||J.R. Smith, "Field Mice: Extracting Hand Geometry From Electric Field Measurements," IBM Systems Journal, vol. 35, Nos. 3 & 4, 1996, pp. 587-608.|
|16||Joshua Smith et al., "Electric Field Sensing for Graphical Interfaces,"MIT Media Laboratory-Special Issue on Input Devices, IEEE Computer Graphics and Applications, May 1998.|
|17||K. Fishkin et al., "Enhanced Dynamic Queries via Movable Filters", Proceedings of CHI 1995 Conference, pp. 415-420 (as downloaded from http://www.parc.xerox.com/istl/projects/MagicLenses/DynamicQueries.html on Sep. 25, 1998, pp. 1-13).|
|18||Ken Hinckley and Mike Sinclair, "Touch-Sensing Input Devices," To Appear in ACM CHI'99 Conf. On Human Factors in computing Systems.|
|19||Ken Hinckley et al., "Interaction and Modeling Techniques for Desktop Two-Handed Input," Proceedings of ACM UIT'98 Symposium on User Interface Software and Technology, pp. 49-58.|
|20||M.C. Stone et al., "The Movable Filter as a User Interface Tool" Proceedings of CHI 1994 Conference, Apr. 1994, Boston, Massachusetts, pp. 306-312 (as downloaded from http://www.parc.xerox.com/istl/projects/MagicLenses/94CHIFilters.html on Sep. 24, 1998, pp. 1-15).|
|21||Microsoft Windows User's Guide, 1992, Doc. No. PC21669-0492.|
|22||R. Balakrishnan et al., "The PadMouse: Facilitating Selection and Spatial Positioning for the Non-Dominant Hand", Proceedings of CHI ', Los Angeles, California, Apr. 18-23, 1998, pp. 9-16.|
|23||Rouse, P., "Touch-Sensitive joystick," Radio & Electronics World, Fe. 1985, pp. 23-26.|
|24||S. Card et al. "A Morphological Analysis of the Design Space of Input Devices", ACM Transactions on Information Systems, vol. 9, No. 2, Apr. 1991, pp. 99-122.|
|25||Thomas G. Zimmerman et al., "Applying Electric Field Sensing to Human-Computer Interfaces," CHI '95 Mosaic of Creativity, May 7-11, 1995, pp. 280-287.|
|26||Using Windows NT Workstation 4, 2nd Ed., 1998 QUE.|
|27||W. Buxton et al., "A Microcomputer-based Conducting System", Computer Music Journal, vol. 4, No. 1, Spring 1980, contents and pp. 8-21.|
|28||W. Buxton et al., "A Study in Two-Handed Input", Proceedings of CHI ', Boston, Massachusetts, Apr. 13-17, 1986, pp. 321-326.|
|29||W. Buxton et al., "A three-state model of graphical input", Proceedings of INTERACT-90, Amsterdam, Netherladns, 1990, pp. 449-456.|
|30||W. Buxton, "Living in Augmented Reality: Ubiquitous Media and Reactive Environments", Computer Systems Research Institute, University of Toronto and Alias/Wavefront Inc., pp. 1-17, downloaded on Feb, 1, 1999 from: http/www.dgp.utoronto.ca/OTP/papers/bill.buxton/augmentedReality.html.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7831923 *||Nov 28, 2006||Nov 9, 2010||International Business Machines Corporation||Providing visual keyboard guides according to a programmable set of keys|
|US7941439 *||May 10, 2011||Google Inc.||Methods and systems for information capture|
|US8099407||Jan 17, 2012||Google Inc.||Methods and systems for processing media files|
|US8155837 *||Apr 20, 2007||Apr 10, 2012||Toyota Jidosha Kabushiki Kaisha||Operating device on vehicle's steering wheel|
|US8161053||Apr 17, 2012||Google Inc.||Methods and systems for eliminating duplicate events|
|US8275839||Mar 31, 2004||Sep 25, 2012||Google Inc.||Methods and systems for processing email messages|
|US8346777||Jan 1, 2013||Google Inc.||Systems and methods for selectively storing event data|
|US8386728||Sep 14, 2004||Feb 26, 2013||Google Inc.||Methods and systems for prioritizing a crawl|
|US8543942 *||Aug 13, 2010||Sep 24, 2013||Adobe Systems Incorporated||Method and system for touch-friendly user interfaces|
|US8612213||May 23, 2013||Dec 17, 2013||Google Inc.||Correction of errors in character strings that include a word delimiter|
|US8631076||Jun 30, 2004||Jan 14, 2014||Google Inc.||Methods and systems for associating instant messenger events|
|US8643596 *||Sep 12, 2008||Feb 4, 2014||Siemens Aktiengesellschaft||Control of a scrollable context menu|
|US8713433 *||Jan 3, 2013||Apr 29, 2014||Google Inc.||Feature-based autocorrection|
|US8747225||Jan 11, 2012||Jun 10, 2014||Wms Gaming Inc.||Gaming machine chair|
|US8812515||Dec 20, 2007||Aug 19, 2014||Google Inc.||Processing contact information|
|US8886372 *||Sep 7, 2012||Nov 11, 2014||The Boeing Company||Flight deck touch-sensitive hardware controls|
|US8954420||Mar 31, 2004||Feb 10, 2015||Google Inc.||Methods and systems for improving a search ranking using article information|
|US9013267||Aug 23, 2011||Apr 21, 2015||Rhonda Enterprises, Llc||Systems and methods for position-based loaning of electronic documents to electronic device users|
|US9047472||Jan 14, 2013||Jun 2, 2015||International Business Machines Corporation||Managing sensitive content|
|US9170736||Sep 16, 2013||Oct 27, 2015||Microsoft Corporation||Hover controlled user interface element|
|US9189553||Jan 28, 2013||Nov 17, 2015||Google Inc.||Methods and systems for prioritizing a crawl|
|US9311408||Dec 12, 2013||Apr 12, 2016||Google, Inc.||Methods and systems for processing media files|
|US20080126977 *||Nov 28, 2006||May 29, 2008||Keohane Susann M||System and method for providing visual keyboard guides according to a programmable set of keys|
|US20090073114 *||Sep 12, 2008||Mar 19, 2009||Susanne Bay||Control of a scrollable context menu|
|US20090164062 *||Apr 20, 2007||Jun 25, 2009||Toyota Jidosha Kabushiki Kaisha||Operating device|
|US20090165092 *||Dec 20, 2007||Jun 25, 2009||Mcnamara Michael R||Sustained authentication of a customer in a physical environment|
|US20090172516 *||Feb 14, 2008||Jul 2, 2009||Oracle International Corporation||Providing Enhanced Information When a Pointing Device Points to a Specific Area In a Graphical User Interface|
|US20100020022 *||Jul 24, 2008||Jan 28, 2010||Dell Products L.P.||Visual Feedback System For Touch Input Devices|
|US20110164066 *||Jul 7, 2011||Todd Beals||Electronic reading device|
|USD669086 *||Oct 16, 2012||Avaya Inc.||Display screen with graphical user interface|
|U.S. Classification||345/173, 345/156|
|International Classification||G06F3/023, A63F13/06, G06F3/02, G05G9/047, G06F3/01, G06F3/038, G06F3/033, G06F3/041, H01H7/08, G09G5/00|
|Cooperative Classification||G06F2203/04805, G06F3/0489, G06F3/03549, G06F3/0219, G05G2009/04774, G05G9/047, A63F2300/1043, G06F3/033, G06F3/04812, G06F3/0202, G06F2203/04804, G06F3/03543, A63F13/06, G06F3/03547, G06F3/038, G06F3/0481, G05G2009/04766, A63F2300/1012, A63F2300/1068, G06F3/0482|
|European Classification||G06F3/02A, G05G9/047, G06F3/02A5, A63F13/06, G06F3/0482, G06F3/0481, G06F3/0354M, G06F3/0489, G06F3/0354P, G06F3/0481C, G06F3/0488, G06F3/0354T, G06F3/038, G06F3/033|
|Mar 18, 2013||FPAY||Fee payment|
Year of fee payment: 4
|Dec 9, 2014||AS||Assignment|
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034543/0001
Effective date: 20141014