This relates generally to touch screens.
Touch screens allow the user to provide inputs to a computer system by merely touching the screen. With conventional touch screens and, particularly, those associated with mobile devices, the screen may be relatively small. This means that the display of text or other symbols on the screen may be relatively small compared to the size of the user's finger. Thus, the user may touch a symbol on a screen in order to provide an input, but the user's finger may completely overlie the item being touched. As a result, the user may actually select a different symbol, also under the user's finger, than the one the user intended to select. This results in consumer confusion and dissatisfaction with small touch screens.
Another problem with touch screens is that clickable links are not generally indicated by any kind of graphical symbol. Thus, the user must touch a link in order to determine if, in fact, it is a clickable link.
In accordance with some embodiments, the appearance of a touch selectable element on a touch screen may be changed when the user positions the user's finger over the element. For example, the element may be enlarged so that the user knows which element the computer understands has been selected. This may reduce the number of inadvertent selections in some embodiments. In some embodiments, if the indicated element is not the one the user intended to select, the user can simply slide the user's finger over to center over the desired element. Then, when the user lifts the user's finger from the screen, in one embodiment, the underlying element is then actually selected.
In some embodiments, finger touch commands can be understood to be a request to indicate which elements of a plurality of elements displayed on the screen are actually hot clickable or hot selectable elements. For example, when the user presses a particular area on the screen, all the clickable elements may have their appearance modified in one way or another.
Referring to
The processor-based system 10 may include a processor implementing a layout engine 14. The layout engine 14 may receive inputs from a browser user interface 12. The layout engine may render screen outputs to a touch screen 16. The layout engine 14 may be coupled to a storage device 18, which may store software implemented sequences 20 and 22, in some embodiments of the present invention.
Referring to
To overcome this problem, in some embodiments, as shown in
In accordance with another embodiment of the present invention, a portion 24 of the display screen 16 may include a display of four elements, labeled links 1-4, in
Thus, a star or asterisk 26 may appear through the links, the links may be highlighted or may be enlarged to indicate that the text adjacent the user's finger is actually a clickable link that can be selected by the user, as described above. In this way, clickable links may be revealed on touch screens to allow user identification of what is and is not a clickable link. In some embodiments, a region on the screen may be provided so that when the user touches that region, all the clickable links on the display are automatically indicated.
Referring to
Referring to
Otherwise, the style attributes of the targeted DOM element may be modified, as indicated in block 38. This is also illustrated in
Then, a check at diamond 42 determines whether there has been a button unpress event, for example, by lifting the user's finger or sliding the user's finger. If the user has slid the user's finger, as determined in diamond 44, the flow iterates back to block 38, recognizing that the user has changed his or her mind about selecting the element that was previously selected, perhaps because the user had inadvertently placed his or her finger over the wrong element and the user recognized the error when the element was enlarged, in accordance with one embodiment of the present invention.
Otherwise, if a slide is not detected, then a button unpress command can be understood. In other words, in one embodiment of the present invention, the touching simply indicates the user's preliminary selection and the lifting of the user's finger indicates acceptance of that selection after enlargement of the selected element, in some embodiments of the present invention. As a result, lifting the user's finger in a way other than sliding the finger may be recognized as receiving a user's selection, indicated in block 46. Other gestural commands could also be used.
Moving now to
The sequence 22 begins by receiving a gestural command, as indicated in diamond 50. The various gestural commands may be used. For example, a sweeping hard gesture across the entire display may be understood as a request to indicate which elements are clickable. Likewise, touching a blank region on the display may be understood to be a request to indicate which regions are hot clickable. If a gestural command is received, then the hot clickable links may be indicated by an appropriate visual indication on the display screen, including highlighting or magnifying the clickable elements or adding icons in association with those clickable elements, as indicated in block 52.
If no gestural command was received or the hot clickable links have already been indicated, a check at diamond 54 determines whether there has been a margin tap. In one embodiment, a gestural command, such as a margin tap adjacent a series of clickable elements, may be understood to select a group of adjacent clickable elements. The group may be, in some embodiments, a row of clickable elements adjacent the blank region tapped or a column of clickable elements, to give two examples, adjacent the region tapped. In such case, the entire group of clickable links may be indicated in the same fashion described above in connection with block 52 or as indicated in block 56.
References throughout this specification to “one embodiment” or “an embodiment” mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one implementation encompassed within the present invention. Thus, appearances of the phrase “one embodiment” or “in an embodiment” are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be instituted in other suitable forms other than the particular embodiment illustrated and all such forms may be encompassed within the claims of the present application.
While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/CN12/00002 | 1/3/2012 | WO | 00 | 6/11/2013 |