US 20080040692 A1
A variety of commonly used gestures associated with applications or games may be processed electronically. In particular, a user's physical gesture may be detected as a gesture signature. For example, a standard gesture in blackjack may be detected in an electronic version of the game. A player may thus hit by flicking or tapping his finger, stay by waving his hand and double or split by dragging chips from the player's pot to the betting area. Gestures for page turning may be implemented in electronic applications for reading a document. A user may drag or flick a corner of a page of an electronic document to flip a page. The direction of turning may correspond to a direction of the user's gesture. Additionally, elements of games like rock, paper, scissors may also be implemented such that standard gestures are registered in an electronic version of the game.
1. A method for entering commands in an electronic blackjack game, the method comprising:
detecting an initial gesture from a player;
determining whether the initial gesture corresponds to at least one of a hit gesture, a stay gesture, a double gesture and a split gesture;
in response to determining that the initial gesture corresponds to the hit gesture, dealing a card to the player;
in response to determining that the initial gesture corresponds to the double gesture, doubling a bet associated with the player; and
in response to determining that the initial gesture corresponds to the split gesture, splitting a card hand associated with the player.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
detecting a following gesture; and
determining whether the initial gesture corresponds to the double gesture based on the detected following gesture.
10. A method for processing gestures in an electronic document application, the method comprising:
detecting a gesture of a user;
determining whether the user's gesture corresponds to a page turning command;
in response to determining that the user's gesture corresponds to the page turning command, determining a direction of the gesture; and
turning a number of pages in the electronic document in accordance with the direction of the gesture.
11. The method of
12. The method of
13. The method of
14. The method of
15. The method of
16. The method of
17. The method of
determining whether the direction of the gesture corresponds to a left direction; and
in response to determining that the direction of the gesture corresponds to the left direction, turning the number of pages forward in the electronic document.
18. A method for processing user input in an electronic rock, paper, scissors game, the method comprising:
detecting a gesture from a player; and
determining whether the gesture corresponds to at least one of a rock gesture, a scissors gesture and a paper gesture, wherein the rock gesture includes a closed fist gesture, the scissors gesture includes an extended middle and pointer fingers gesture and the paper gesture includes an open hand gesture; and
registering a selection of the player in accordance with the determined gesture.
19. The method of
20. The method of
The computing world is constantly striving to improve the realism with which users are able to interact with computing devices. Improving the realism of interaction allows a user to accomplish tasks without having to deviate from standard or accepted interactions, often increasing efficiency. In many applications, including video games, users and/or players must typically learn a new set of input rules in order to operate one or more elements of the application or game interface. For example, flipping a page in an electronic document often involves selecting a flip button using an input device such as a mouse. In another example, electronic blackjack games include a number of option buttons for hitting, standing/staying, doubling and splitting. However, having to learn new rules may discourage and/or dissuade users from using computing devices to accomplish everyday tasks and to engage in common activities.
Aspects are directed to a method and system for implementing standard or commonly used gestures in corresponding applications. For example, a hit, stand/stay and double or split gestures may be implemented in a blackjack game application or program. A hit gesture may correspond to a flick toward a player or a tapping motion while a stand/stay gesture may include a waving motion by a player's hand. Doubling or splitting may be initiated by dragging a number of chips from a user's chip pot to a predefined area in the user interface. Determining whether a player wants to double or split may involve detecting an additional gesture that corresponds to one action or the other. Default rules may also be used in the event the user does not enter an additional gesture input. A player's gesture and corresponding action may be confirmed by an interface to insure appropriate processing. Gestures may be captured in a variety of ways including using motion capture devices and touch sensitive input systems.
In another aspect, gestures associated with flipping pages of a document or book may be implemented in electronic applications for reading a document or book. The gestures may include dragging a user's finger across a page or flicking the user's finger in a specified area of the document. In one example, a page of a document may include one or more curled or folded corners that indicate a gesture input area. The curled or folded corners may further provide indication to a user as to whether the document may be turned or flipped in that direction. By detecting flicking or dragging of the curled or folded corners, the interface may determine that the user wishes to turn the page. The direction of a user's gesture may be relevant in determining whether a document should be turned forward or backward. For example, a user may drag her finger from the bottom right corner of a document toward the left. This may correspond to a forward turning or flipping action. In some instances, the entire document and/or interface may receive gesture inputs. The direction of flipping or turning may be configurable and customizable by a user.
In yet another aspect, an electronic version of the game rock, paper, scissors may recognized gestures corresponding to each element of the game (i.e., rock, paper and scissors). A rock may be represented by a clenched fist while a paper gesture may include flattening a player's hand with the palm facing up or down. Scissors, on the other hand, may be represented by a player making a fist while extending the middle and pointer fingers. Additional elements that may be added into the game may also be similarly imitated by a commonly used or standard gesture.
In yet another aspect, gestures may be detected using an optical input device. The optical input device may translate physical gestures into gesture signatures. Gesture signatures may include a pattern of light and dark that corresponds to the gesture entered. Pre-stored and/or predefined gesture signatures and/or characteristics thereof may be used to determine whether a user's gesture corresponds to a specific command and/or function.
According to yet another aspect, a magnitude and/or speed of a gesture may affect the resulting action. For example, in flipping a page, the magnitude, i.e., displacement of a user's gesture may correspond to a number of pages to turn. Thus, the greater the magnitude of the gesture, the more pages that are turned and vice versa. The speed of a user's gesture may also be used to determine the number of pages to turn. Faster motions or gestures may correspond to a greater number of pages to turn while slower gestures may indicate a smaller number of pages. An interface may also use a combination of speed and magnitude to determine the number of pages to turn.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Aspects of the invention are illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:
In the following description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration various embodiments. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope of the present disclosure.
A basic input/output system 160 (BIOS), which contains the basic routines that help to transfer information between elements within the computer 100, is stored in the ROM 140. The computer 100 also may include a hard disk drive 170 for reading from and writing to a hard disk (not shown), a magnetic disk drive 180 for reading from or writing to a removable magnetic disk 190, and an optical disk drive 191 for reading from or writing to a removable optical disk 199, such as a CD ROM or other optical media. The hard disk drive 170, magnetic disk drive 180, and optical disk drive 191 are connected to the system bus 130 by a hard disk drive interface 192, a magnetic disk drive interface 193, and an optical disk drive interface 194, respectively. These drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules, and other data for the personal computer 100. It will be appreciated by those skilled in the art that other types of computer-readable media that 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 memories (ROMs), and the like, may also be used in the example operating environment.
A number of program modules can be stored on the hard disk drive 170, magnetic disk 190, optical disk 199, ROM 140, or RAM 150, including an operating system 195, one or more application programs 196, other program modules 197, and program data 198. A user can enter commands and information into the computer 100 through input devices, such as a keyboard 101 and pointing device 102 (such as a mouse). Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices often are connected to the processing unit 110 through a serial port interface 106 that is coupled to the system bus 130, but they also may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB), and the like. Further still, these devices may be coupled directly to the system bus 130 via an appropriate interface (not shown).
A monitor 107 or other type of display device also may be connected to the system bus 130 via an interface, such as a video adapter 108. In addition to the monitor 107, personal computers typically include other peripheral output devices (not shown), such as speakers and printers. In some example environments, a stylus digitizer 165 and accompanying stylus 166 are provided in order to digitally capture freehand input. Although a connection between the digitizer 165 and the serial port interface 106 is shown in
The computer 100 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 109. The remote computer 109 can be a server, a router, a network PC, a peer device or other common network node, and it typically includes many or all of the elements described above relative to the computer 100, although for simplicity, only a memory storage device 111 has been illustrated in
When used in a LAN networking environment, the computer 100 is connected to the local area network 112 through a network interface or adapter 114. When used in a WAN networking environment, the computer 100 typically includes a modem 115 or other means for establishing a communications link over the wide area network 113, such as the Internet. The modem 115, which may be internal or external to the computer 100, may be connected to the system bus 130 via the serial port interface 106. In a networked environment, program modules depicted relative to the personal computer 100, or portions thereof, may be stored in the remote memory storage device.
It will be appreciated that the network connections shown are examples, and other techniques for establishing a communications link between computers can be used.
The existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP, UDP, and the like is presumed, and the computer 100 can be operated in a user-server configuration to permit a user to retrieve web pages from a web-based server. Any of various conventional web browsers can be used to display and manipulate data on web pages.
In one or more arrangements, touch sensitive display screen 201 may further accept gesture input. That is, the system 200 may detect a user's gestures and translate them into application functions and/or commands. Gestures may be captured in a variety of ways including touch sensitive input devices and/or camera or optical input systems. Gestures generally refer to a user's motion (whether the motion is of the user's hand or a stylus or some other device) that is indicative of a particular command or request. Gestures and their corresponding meaning may be environment or application specific. For example, in blackjack, flicking or tapping one or more fingertips generally indicates that the user wants to hit (i.e., receive an additional card). Similarly, a user wishing to stay on a particular hand may wave her hand or fingers above her cards. Gestures may also correspond to desired interactions with a particular object. In one example, flipping a page of a document or book may be defined as a user's finger or hand movement from the bottom corner of one side of a document page toward the opposing side.
The display device 300 may display a computer-generated image on its display surface 301, which allows the device 300 to be used as a display monitor (such as monitor 107) for computing processes, displaying graphical user interfaces, television or other visual images, video games, and the like. The display may be projection-based, and may use a digital light processing (DLP—trademark of Texas Instruments Corporation) technique, or it may be based on other display technologies, such as liquid crystal display (LCD) technology. Where a projection-style display device is used, projector 302 may be used to project light onto the underside of the display surface 301. It may do so directly, or may do so using one or more mirrors. As shown in
In addition to being used as an output display for displaying images, the device 300 may also be used as an input-receiving device. As illustrated in
The device 300 shown in
The device 300 is also shown in a substantially horizontal orientation, with the display surface 301 acting as a tabletop. Other orientations may also be used. For example, the device 300 may be oriented to project a display onto any desired surface, such as a vertical wall. Reflective IR light may also be received from any such oriented surface.
Alternatively or additionally, blackjack interface 401 may define an input area such as regions 405 a, 405 b and/or 405 c for each player of the game. Gesture input detected in each area 405 a, 405 b and 405 c may be associated with the particular player.
Interface 401 may require that gesture input be performed within these areas 405 a, 405 b and 405 c in order to reduce the possibility that input may be ignored, left unregistered or erroneously processed. For example, a player may touch interface 301 for one or more reasons other than to express a blackjack command. However, without a specified area 405 a, 405 b or 405 c for receiving gesture input, interface 401 may interpret the touch input as, for example, a hit request. Interface 401 may also set a specified time period within which a gesture is detected and processed. That is, interface 401 may require that all gestures be completed within, for example, 2 seconds of the initial input or of some other event (e.g., beginning of a player's turn). For example, a player may begin a hit gesture by contacting the surface of device 400 at a certain point. Once this initial contact is detected, the game interface 401 may determine a gesture based on input received within a 2 second period after detection of the initial contact. The time limit allows a user to “reset” his action if he decides that, prior to completing a gesture, he does not want to perform the action associated with the contemplated gesture.
Interface 402 may provide an indicator showing a player where to move a selected amount of chips to either initiate the double or split function. For example, interface 402 may display “ghost” stack 440 next to the player's current bet 425. The “ghost” stack 440 may include a faded outline of a stack of chips and/or a dashed or segmented outline defining the doubling/splitting area. Alternatively or additionally, interface 402 may define different gestures for each of the doubling and splitting commands, or different ghost stacks for each of the doubling and splitting options. For example, a user may be required to provide an additional gesture after dragging his chips to “ghost” stack 440 to indicate whether he wants to double or split. The gesture may include one or more taps in a single location to express a desire to double and/or two simultaneous taps (i.e., with two separated fingers) in different locations to express an intent to split. In one or more arrangements, if the player does not input the additional gesture within a specified period of time after dragging his chips to “ghost” stack 440, interface 402 may perform a default action according to one or more predefined rules based on rules and conventions in blackjack.
The gestures described with respect to
Gestures 510 and 515 may be similarly identified based on corresponding gesture signatures 507 and 512, respectively. Gesture 510 may, in one or more instances, correspond to a stay/stand gesture that includes a user moving his finger side to side. To a gesture input device, gesture 510 may appear as a set of dark points that form a zig-zag line such as signature 507. In addition, gesture 515, which may include a dragging motion with a user's finger, may correspond to gesture signature 512. Gesture signature 512 registers as a line from one point to another. For example, gesture signature 512 may originate at a point within a player's pile of chips and end at a point next to the player's bet. The gesture signature 512 may thus be associated with either a double function or a split command.
If the gesture does not correspond to the hit command (e.g., gesture signature does not correspond to predefined gesture signature associated with the hit command), then the interface determines whether the gesture corresponds to a stand/stay request in step 640. The stand/stay request may be associated with a waving motion of a player's hand. If the gesture does correspond to a stand/stay request, confirmation may be requested in step 645. If the request is confirmed in step 647, the interface may set that status of the player's hand as “STAY” or “STAND” in step 648. If, however, the player does not confirm the stand/stay request, then the gesture input may be discarded in step 635.
If the gesture input does not correspond to either the hit command or a stand/stay request, the interface may determine whether the gesture input is associated with a doubling or splitting gesture in step 650 of
If, however, a player enters gesture input within the time limit, the gesture input may be compared to predefined gesture inputs associated with a double function and a split function in step 670. In step 675, the interface determines whether a double should be performed. If, based on either the default rules or the player's gesture input, the interface determines that a double should performed, the player's bet is doubled in step 680 and the player receives one more card. If, however, the interface determines that a split should be performed in step 677, the player's hand is split in step 685.
Prior to each of steps 680 and 685, the interface may request confirmation of the determined action from the player. Steps 680 and 675 might only be performed if confirmation is received. If confirmation is not received, all current gesture input may be discarded. Further, if the player's gesture does not correspond to either a double command or a split command, the input may be discarded and the player's turn reset in step 635 (
The gesture associated with flipping or turning page 715 may include a flicking or dragging action. One or both actions may register as a flip command. Flicking, as used in the description of flipping or turning page 715, may be characterized by a movement of a user's finger 710 across a specified distance and/or at a specified speed. Dragging may be characterized by a movement of a user's finger 710 across a specified distance that is greater than the specified distance associated with flicking and/or at a specified speed. The flipping gestures may be inputted using either targets/hotspots or gesture regions 721 a and 721 b. Targets and hotspots may, in one or more instances, correspond to one or more page indicators 720 a and 720 b that inform the user whether pages before or after the current pages 715 and 716 exist. Examples of page indicators 720 a and 720 b include curled or folded corners. Thus, a user may flip page 715 forward and/or backward by gesturing at page indicators 720 b and 720 a, respectively. According to one or more aspects, gesture regions 721 a and 721 b that may be defined based on the locations of hotspots/indicators 720 a and 720 b. Implementing gesture regions 721 a and 721 b may facilitate gesturing input by users who may or may not have limited fine motor skills.
Alternatively or additionally, the distance and/or velocity associated with the user's gesture may provide further parameters when flipping a page such as page 715. In one example, the distance that a user's flicks or drags may define a number of pages to flip. Thus, if a user's drag gesture extends across half of page 715, an interface 701 a, 701 b or 701 c may flip document 705 forward 15 pages. In contrast, if the user's drag gesture extends across 1/4 of page 715, only 7 pages may be flipped. Further, the speed with which the user performs the flick or drag gesture may also be indicative of a number of pages to flip. That is, the faster a user performs a flick or drag gesture, the more pages that are flipped and vice versa. The association between speed and the number of pages may alternatively be reversed. Thus, in one example, the faster a user flicks or drags a page, the fewer pages that are flipped. In one or more arrangements, both the speed and the distance of the gesture may be combined to determine a number of pages to flip. A short slow gesture may correspond to a 1 page flip while a long fast gesture may be associated with a multi-page flip.
While the page flipping methods and systems described herein correspond a forward flip to a leftward motion and a backward flip to a rightward gesture, the reverse could also be implemented. This may be provide flexibility for documents in other languages that are read from right to left rather than left to right. In addition, the gestures corresponding to forward and backward flips may be configurable by a user based preferences.
Each of the page flipping and/or turning gestures described herein may be detected and defined using gesture signatures. In
If the gesture direction does correspond to a forward flip, then the electronic document is flipped the calculated number of pages forward in step 922. If, however, the gesture direction does not correspond to a forward flip, a determination may be made in step 925 to determine whether the gesture direction corresponds to a backward flip. Again, the determination may be based on a predefined direction, e.g., right, associated with a backward flip action. If the gesture direction does correspond to a backward flip, then in step 930, the electronic document is flipped the calculated number of pages backward. If the interface is unable to determine whether the gesture direction corresponds to a forward flip or a backward flip, the gesture input may be ignored or discarded in step 935.
As with the blackjack and page turning gestures, the gestures associated with rock, paper, scissors may also be registered and predefined as gesture signatures 1105, 1110 and 1115 in
The gestures described herein relate specifically to blackjack, flipping pages and playing a game of rock, paper, scissors. However, one of skill in the art will appreciate that many other accepted or standard gestures associated with various games, applications and functions may be implemented. For example, in electronic poker games, a player may indicate a number of cards she desires by holding up a corresponding number of fingers. The different gestures associated with the different number of fingers may be identified using prestored and/or predefined gesture signatures. In addition, many aspects described herein relate to touch sensitive input devices. However, other types and forms of gesture input devices may also be used in similar fashion. For example, motion detection cameras or optical input device may serve as gesture detection devices to capture gestures that are performed in mid-air and which do not contact a touch sensitive surface. Other input devices may include position tracking sensors that may be attached to, in one example, an input glove that a player or user wears. One of ordinary skill in the art will appreciate that numerous other forms of gesture detection devices and systems may be used in place of or in addition to the systems and devices discussed herein.
In addition, while much of the description relates to flipping or turning pages in an electronic document, one of skill in the art will appreciate that the gestures associated with flipping pages forward or backwards could also be implemented in applications other than document viewers. For example, internet browsers, media/music players, wizards, or other applications that have content on multiple screens/pages could also use these gestures as a means of navigating forward and backwards.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. Numerous other embodiments, modifications and variations within the scope and spirit of the appended claims will occur to persons of ordinary skill in the art from a review of this disclosure.