Patent Publication Number: US-2022229550-A1

Title: Virtual Keyboard Animation

Description:
RELATED APPLICATIONS 
     This application is a continuation of U.S. application Ser. No. 16/410,990, filed May 13, 2019, which is a continuation of U.S. application Ser. No. 14/603,269, filed Jan. 22, 2015, now U.S. Pat. No. 10,289,302, which is a continuation of U.S. application Ser. No. 14/481,882, filed Sep. 9, 2014, now abandoned, which claims priority to U.S. Provisional Application No. 61/875,269 filed Sep. 9, 2013, entitled “Key Selection Confirmation Animation on a Virtual Keyboard”, each of which is hereby incorporated by reference in its entirety. 
    
    
     TECHNICAL FIELD 
     The disclosure herein relates to data processing systems and more particularly to detecting and responding to user input in data processing systems. 
     INTRODUCTION 
     Tablet computers, smartphones and other touchscreen devices typically emulate mechanical keyboard functionality by displaying a keyboard image beneath a featureless touch-sensitive surface, compensating for the lack of tactile feel by providing visual feedback when a key is selected. A common “virtual keyboard” technique, for example, is to display the character associated with the selected key directly above and adjacent the key as it is selected. Unfortunately, such visual feedback is often obscured by a user&#39;s hands, a problem aggravated by recent advances that enable a user&#39;s hands/fingers to be rested on the touchscreen (over the virtual keyboard) without unintended key activation. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The disclosure herein is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which: 
         FIG. 1  illustrates an embodiment of a traveling-symbol function within a touchscreen-implemented virtual keyboard; 
         FIGS. 2A and 2B  illustrate embodiments of contact-pressure and/or impact-strength indicia that may be implemented in connection with a traveling-symbol animation; 
         FIG. 3  illustrates an exemplary decay effect in which an indicia of tremor ring intensity (e.g., line-thickness) changes as the tremor ring propagates away from a struck key; 
         FIG. 4  illustrates examples of additional key-selection animation features corresponding to respective programmed animation settings; 
         FIG. 5  illustrates a key-selection animation embodiment in which initial tremor ring size is determined according to locus of a struck key; 
         FIGS. 6A and 6B  illustrate additional animation effects that may be applied in response to input from computing device sensors; 
         FIGS. 7 and 8  illustrate embodiments of a touch-emergent or transient keyboards; 
         FIG. 9  illustrates exemplary user-interface event resolution and responsive operations that may be executed within a computing device in connection with key-selection animation embodiments and other features described in reference to  FIGS. 1-8 ; and 
         FIG. 10  illustrates an exemplary conceptual diagram of a touch-screen based computing device capable of implementing the various virtual keyboard and user-interface features described in reference to  FIGS. 1-9 . 
     
    
    
     DETAILED DESCRIPTION 
     In a number of embodiments disclosed herein, user key selection in a virtual keyboard is visibly confirmed by displaying a moving image of a symbol corresponding to the selected key such that the symbol moves sufficiently away from the virtual keyboard to be readily visible by a user, despite presence of the user&#39;s hands over the virtual keyboard. In one-such “traveling symbol” implementation, the moving symbol appears to ride (sail, fly, glide or otherwise be conveyed, propelled or moved by) by a touch-induced wave, referred to herein as a tremor ring, that emanates from the user contact interpreted as the key selection or key-selection event. In other embodiments, a keyboard image may be rendered in a bowed or otherwise deformed state to signal detection of a user&#39;s rested hands or fingers. Individual key selections may then be rendered as a local deformation (e.g., modeling deformations in a stretched rubber sheet, gel or other malleable/semifluid material) such as wavelets traveling toward a symbol insertion point (e.g., text-entry field), conveying or morphing into the typed/selected symbol at the insertion point. In yet other “touch-emergent” keyboard embodiments, a keyboard image (or one or more keys thereof) is temporarily or transiently rendered on an otherwise keyboard-less display in response to user touch-input, with the keyboard image fading to the point of disappearance in the absence of continued touch or typing input. In a number of touch-emergent keyboard implementations, the keyboard image or portion thereof is rendered in a semi-transparent (i.e., non-opaque) state to enable the pre-existing screen image to remain visible to the user, thus enabling the user to quickly enter text or other information without disrupting ongoing interaction with the display (e.g., annotating a video or still image, sending a message while gaming or viewing a motion picture, etc.). These and other features and embodiments are described in further detail below. 
       FIG. 1  illustrates an embodiment of a traveling-symbol function within a touchscreen-implemented virtual keyboard. In the example shown, one or more sensor signals generated in response to a user contact at the locus of a virtual ‘T’ key (i.e., image of ‘T’ key rendered on touchscreen display) are determined by a user-interface (UI) controller to constitute a ‘T’ key-selection event. In response to detecting the ‘T’ key selection (i.e., action by the user indicating intent to activate a given key), the UI controller renders, as a graphic image on the touchscreen, a tremor ring (also referred to herein as a tremor circle or tremor wave) that emanates and propagates away from the locus of the ‘T’ key in an emulation of a wave flowing through the on-screen image, propelling an image of the typed symbol, toward a symbol destination insertion point (e.g., a text entry field). By this operation, the typed character (or more generally, typed symbol) is made visible to the user to confirm detection of the key selection, despite the otherwise obscuring presence of the user&#39;s hands over the virtual keyboard. In the particular example shown, the typed symbol grows larger as it travels away from the selected key to enhance visibility, and appears to glide to the insertion point, giving the impression that the T is being transferred from the virtual keyboard to the target text. 
       FIGS. 2A and 2B  illustrate embodiments of contact-pressure and/or impact-strength indicia that may be implemented in connection with a traveling-symbol animation, for example, to aid in user-interface training (i.e., providing feedback to a user for correcting excessive or insufficient typing impact or pressure) and/or distinguishing between different types of user input (e.g., typing vs. tapping/clicking events). In the example of  FIG. 2A , the tremor ring propagation rate (or expansion rate or travel rate) increases and decreases in accordance with impact strength (i.e., impulse force or other measure strength of user tap) and/or contact pressure (measure of how hard a user presses after impacting the touch-sensitive surface). Thus, a tremor ring generated in response to an ‘S’ key selection expands by a first radial distance over a given time interval in response to a first impact strength and/or contact pressure and expands by a second, larger radial distance over that same time interval in response to a higher impact strength/contact pressure. In one embodiment, the radial expansion rate of the ring increases in proportion to the impact/pressure level, while in other embodiments, a limited number of impact and/or pressure thresholds yield a corresponding number of ring expansion rates (i.e., impact/pressure between first and second thresholds yields a first ring expansion rate, impact/pressure between second and third thresholds yields a second ring expansion rate, etc.). 
     In the embodiment of  FIG. 2B , the intensity of the tremor ring varies in accordance with impact strength and/or contact pressure, for example ranging in color and/or line-thickness between minimum and maximum impact/pressure extremes. In the specific example shown, both color and line-thickness vary over a predetermined impact/pressure range, signaling insufficient/excessive impact strength and/or pressure via short/long color wavelength extremes (violet and red) and correspondingly thin/heavy line-thickness, and confirming impact/pressure within a desired range via a mid-range color (e.g., green) and line-thickness. In other embodiments, both ring intensity and ring expansion rate may be employed to signal impact/pressure and/or alternative typing feedback (e.g., level of ambiguity in typed keys, thus permitting a user to adjust/train his or her characteristic typing). For example, ring intensity may correspond to impact strength, while expansion rate corresponds to contact pressure or vice-versa. 
       FIG. 3  illustrates an exemplary decay effect in which an indicia of tremor ring intensity (e.g., line-thickness) changes as the tremor ring propagates away from the struck key. In the particular example shown, for instance, the line-weight of the tremor ring is progressively reduced from time t 1  to t 4 , disappearing altogether by time t 5  even as the selected symbol (the ‘x’ character in this case) continues to glide visibly toward the insertion point. This decay effect may be used, for example, to signify impact strength and/or contact-pressure intensity (e.g., lower rate of decay for higher impact strength/contact pressure) without unduly obscuring other elements of a rendered scene. 
       FIG. 4  illustrates additional key-selection animation features and configurations showing, for example, a beam-type wavelet (i.e., directional propagation indicators instead of a complete ring) for a first animation setting (“setting 1”), and a nonvisible or altogether omitted tremor ring (i.e., rendering only the gliding symbol) in a second animation setting (“setting 2”). An operational view  150  of the symbol-only setting (“setting 2”) illustrates multiple typed characters in flight simultaneously, all gliding from the virtual keyboard to a text-field insertion point. 
       FIG. 5  illustrates a key-selection animation embodiment in which initial tremor ring size is determined according to locus of the struck key. For example, keys more likely to be obscured by a user&#39;s hands yield larger initial tremor ring sizes (which size variation may also apply to initial size and/or growth rate of traveling symbols) than keys less likely to be obscured. More specifically, in the embodiment shown, keystrokes directed to bottom-row keys (e.g., deemed most likely to be obscured by the user&#39;s hands) yield larger initial tremor ring sizes than keystrokes directed to middle-row keys which, in turn, yield larger initial ring sizes than keystrokes direct to top-row keys. This location-indexed animation feature may vary according to the location and orientation of the virtual keyboard. For example, the ring-size variance shown in  FIG. 5  may be reversed for a virtual keyboard rendered in a display heading (or otherwise at the top of the display), or may progress from left to right in a virtual keyboard rendered at the side of a display (e.g., a numeric keypad or the like). In all such cases, the touch-or tap-location indexing may be applied to animation features other than ring sizes including, for example and without limitation, size, growth rate and/or rate-of-travel of traveling symbols, ring or beam intensity, ring or beam decay and so forth. 
     Characteristics of key-selection animation in addition to those described in reference to  FIGS. 1-5  include, for example and without limitation:
         the speed at which the tremor circle expands may be linear or nonlinear   the speed at which the tremor circle expands may be proportional to how hard a key is tapped   the traveling symbol displayed within or at the periphery of the tremor circle may grow or shrink as the tremor circle expands   the tremor circle of a selected key may be immediately (or more rapidly) extinguished following selection of a subsequent key, thus avoiding or limiting simultaneous display of multiple tremor circles that might otherwise clutter the user interface       

     As mentioned briefly in reference to  FIG. 4 , key-selection animation settings or configurations may be specified by a user in connection with a computing device as a whole and/or specific application programs (or “apps”) executed by the computing device. For example, a UI controller may access a programming interface (e.g., exposed by the operating system and/or executing application program) to retrieve animation settings to be applied in response to key-selection events, gestures, rested fingers and so forth. Accordingly, an application developer may specify a default set of key-selection animation characteristics to be applied by the UI controller during application execution, and may additionally permit the application user (or a system administrator in an enterprise setting) to tailor the animation characteristics via an interactive configuration display. An operating system developer may similarly specify a default set of key-selection animation characteristics to be applied in absence of application-specified settings, permitting the user to alter the characteristics according to preference in a configuration or “settings” menu. In all such cases, the configuration settings may be stored in a non-volatile memory of the host computing device and thus retained through a device power-cycle event. 
       FIGS. 6A and 6B  illustrate additional animation effects that may be applied in response to input from computing device sensors (e.g., proximity sensors, pressure sensors, vibration sensors and/or capacitive or other touch sensors as discussed below). More specifically,  FIG. 6A  illustrates a deformation of the rendered keyboard image (i.e., bowing at the center of the keyboard or anticipated input locus) that may be presented in response to determining/detecting that a user&#39;s hands or fingers have been rested on and/or are hovering above the virtual keyboard surface (e.g., as described in U.S. Pat. No. 8,325,121 entitled “Cleanable touch and tap-sensitive surface” and U.S. application Ser. No. 14/265,340 filed Apr. 29, 2014 and entitled “Finger Hover Detection for Improved Typing,” each of which is hereby incorporated by reference).  FIG. 6B  illustrates a local deformation in the rendered keyboard image (e.g., modeled as a deformation in a stretched rubber sheet, gel or other malleable material) in response to an individual key selection. As shown, the local deformation may be accompanied by (i.e., appear to trigger) a wavelet traveling away from the selected key, conveying the typed symbol or morphing into the typed symbol at or near the insertion point. 
     More generally, any large area deformation, fading, highlighting or other change in the rendered keyboard image may be used to signify resting or hovering of a user&#39;s hands or finger(s), with more focused deformations/circles/wavelets or other animation emanating from individual key selections (or combination-key selections) and transforming into a typed symbol. Such image bowing (or other deformation) effectively “advertises” the finger-resting feature, helping users learn and practice resting actions and providing feedback confirming that the feature is working. In contrast to approaches that may be misconstrued as keyboard disablement (e.g., grey-out shading in response to finger-rest detection), a downward bowing, deformation or indentation of an entire rest area indicates the hand resting weight without indicating disablement. Also, because an initial set of touches may not be confirmed as a resting event until additional touches arrive (i.e., a fraction of a second later), the UI controller may initially render an ‘ambiguous’ animation showing a slight under-finger deformation that, in the case of an eventual resting finger determination, gently diffuses or spreads the deformation over a larger area (e.g., the whole keyboard image) as if the finger energy had just dissipated into the whole surface. By contrast, if after a brief interval (e.g., few tens of milliseconds) the UI controller determines that the initial touches were non-resting key selections, the initially ambiguous animation may be morphed into a crisper, still-localized deformation (e.g., wavelet/circle) under the finger and/or traveling upwards toward the symbol insertion point. 
       FIGS. 7 and 8  illustrate embodiments of a touch-emergent or transient keyboards—virtual keyboard functions particularly useful in gaming, image-rendering and other content-rich applications that would otherwise be impaired or obscured by a statically displayed virtual keyboard. 
       FIG. 7  illustrates an touch-emergent keyboard embodiment in which a full virtual keyboard is temporarily and semi-transparently rendered over existing screen content (in this case a basketball court in a gaming application) in response to determining/detecting that:
         a user&#39;s fingers are resting on the touchscreen surface or hovering above the touchscreen surface;   the user has begun typing; and/or   the user has otherwise entered or made a gesture indicating a desire to enter data via keyboard (including a keypad or other data entry panel).
 
In one implementation, for example, when the user begins typing or rests a threshold number of fingers concurrently on the touchscreen surface, the virtual keyboard is rendered semi-transparently to enable the user to view the pre-existing content. As the user types, the typed symbols may be rendered unobstrusively (e.g., also in a semi-transparent manner) in another part of the screen while the virtual keyboard remains in view. When the user stops typing or removes his or her hands from the surface or proximity thereto, the virtual keyboard fades, eventually disappearing altogether as shown. The fade rate (or decay rate) may vary according to user gesture, fading more quickly in response to detecting removal of the user&#39;s hands than to typing cessation accompanied by resting of the user&#39;s hands on the touchscreen. Further, one or more predetermined gestures (tapping on the computing device outside the touchscreen—an event that may be detected by a vibration sensor such as an accelerometer) may be used to signal that the user has finished typing, causing the system to clear the virtual keyboard from the display without delay.
       

       FIG. 8  illustrates a touch-emergent keyboard embodiment in which only a limited set of keys are displayed (again in semi-transparent form) in response to user input (typing, resting fingers, hovering fingers, gestures, etc.) indicating user desire to enter data via keyboard. In the specific example shown, the rendered set of keys (i.e., less than the full set of keys in the virtual keyboard) are those determined to most likely follow the immediately preceding text input sequence (e.g., as determined algorithmically using linguistic or other databases within or accessible by the host computing device, including databases corresponding to events taking place in the application program itself). Thus, in the context of the tennis gaming application shown, the system may determine via one or more linguistic databases, potentially aided by contextual information following, for example, a unreturned tennis-serve, that the most likely next character following the typed expression “ha! ac” is the letter ‘e’ (to yield “ace”), with a few other less likely possibilities as shown at  181 . In the implementation shown, the keys deemed to be the most likely next-strike candidates are rendered as the subset of virtual keys (i.e., ‘E’ key and five others) without emphasizing one choice over others. In alternative embodiments, the brightness, opacity or other key characteristic may be varied from key to key to emphasize more likely next-strike candidates over less likely candidates. Further, the number of transiently rendered virtual keys may vary from one keystroke to the next according to linguistic context and/or application state. In the screen example shown at  183  in  FIG. 8 , for instance, only three keys are deemed to be linguistically viable in view of the previously entered text. In one embodiment, the UI controller may switch from transient rendering of a small number of keys (as shown in  FIG. 8 ) to rendering a complete virtual keyboard in response to a predetermined user gesture (e.g., double tapping with four or more fingers simultaneously) and/or data input context (e.g., unable to disambiguate user input or derive linguistic meaning from entered text). 
       FIG. 9  illustrates exemplary UI-event resolution and responsive operations that may be executed within a computing device in accordance with the embodiments described above. Starting at  201 , a UI controller monitors signals from various sensors (e.g., proximity sensor(s), vibration sensors(s), capacitive and/or other types of touch sensors) to determine whether a user&#39;s disposition with respect to the user interface has changed—an occurrence referred to herein as a UI event. If the sensor signals indicate a change in the user&#39;s disposition (i.e., the signals have changed), the UI controller resolves or qualifies the UI event as shown at  203  as being, for example and without limitation, a rest event (i.e., user has rested his or her hands or removed his or her hands from a resting disposition), a key selection event, or a gesture event. In one embodiment, for instance, the UI controller implements a state machine that resolves the UI event based on a current state (e.g., hands-at-rest state, active-typing state, hands approaching state, etc.) and the immediate sensor input, transitioning from state to state as UI events are resolved. 
     Continuing with  FIG. 9 , upon determining that the user has rested his or her hands on the touch-surface, the UI controller confirms the rest detection (e.g., by generating an audible and/or visible confirmation to the user, such as the keyboard image deformation described above in reference to  6 A) and outputs a corresponding UI-event code to the operating system at  205  (though not specifically shown, the UI controller may similarly confirm removal of a user&#39;s rested hands—restoring the keyboard image to a non-deformed state—and signal the OS of the removal event). Similarly, upon determining that a gesture has been entered, the UI controller confirms the gesture detection and issues a corresponding UI-event code to the operating system as shown at  207 . 
     Upon detecting that one or more keys have been pressed (or tapped or struck), the UI controller distinguishes the key input type at  209  as being a typed symbol or a non-typing function (e.g., a command as may be signaled by pressing a function key and/or a combination of keys that qualify keys otherwise used for typing input). Upon detecting command or other function-request input, the UI controller confirms the function selection and issues a corresponding UI-event code (i.e., indicating the command or requested function) to the OS as shown at  211 . By contrast, if symbol input is detected, such as typing an alphanumeric character or other symbol to be rendered at an insertion point within the display, the UI controller determines whether key-selection animation is enabled at  215  (e.g., by evaluating programmed settings associated with an executing application program or operating system) and, if so, renders the key selection animation in accordance with key-selection animation settings ( 219 ) as generally described above before displaying the symbol at the insertion point. For example, if key selection animation is enabled, the UI controller may cause traveling symbols with or without associated tremor rings or other conveyance graphics to be displayed in connection with the selected symbol. 
     Still referring to  FIG. 9 , upon resolving a particular UI event at  203 , including rested hands, specific gestures or key selections, the UI controller may display an otherwise non-visible virtual keyboard or portion thereof, and thus implement the touch-emergent keyboard operations described in reference to  FIGS. 7 and 8 . 
       FIG. 10  illustrates an exemplary conceptual diagram of a touch-screen based computing device  250  (e.g., smartphone, tablet computer, laptop computer, desktop computer etc.) capable of implementing the various virtual keyboard and user-interface features described above. In the embodiment shown, computing device  250  includes a planar (flat) transparent surface disposed over an enclosure that houses, without limitation, a set of human interface components  255 , processor  257  (which may include one or more discrete integrated circuit components or collectively packaged integrated circuit chips), and memory  259  (which may also include one or more discrete and/or collectively packaged integrated circuit chips). Though not specifically shown, computing device  255  may additionally include a power compartment into which one or more batteries or other power sources may be inserted, radio frequency transceivers (or receivers or transmitters) to enable wireless interoperability according to various standard and/or proprietary protocols, and one or more signaling interfaces to enable removable interconnection of peripheral devices such as external power delivery sources, speakers, microphones, printers, magnetic stripe card readers, storage devices or any other useful device. 
     Turning to the generalized component categories, human interface components  255  may include one or more proximity sensors  273 , one or more vibration sensors  277 , capacitive (or other types of touch) sensors  275 , audio speaker  279 , one or more visual indicators  281  (e.g., light-emitting diodes), as well as a display  285  (e.g., based on liquid crystal or other light-emitting or absorptive technology) disposed beneath the transparent planar surface of the computing device. Though not specifically shown, hardware interface components may additionally include a microphone, one or more image sensor/lens arrangements, and various other types of sensors (e.g., one or more pressure sensors). 
     Still referring to  FIG. 10 , the sensor components  273 ,  275  and  277  provide input to processor  257  which is formed, in the example shown, by a hardware or user-interface (UI) controller  291  together with one or more special purpose processor cores (e.g., graphics processor for rendering textures, images and effects on display  285 ) and/or general purposes processor cores, shown generally at  293 . In one embodiment, raw signals generated by the sensors ( 273 ,  275 ,  279 ) in response to user contact or proximity with the planar surface overlaying display  285  (the planar surface, display and capacitive sensors, at least, constituting a “touchscreen”) are interpreted by UI controller  291  and output to processor core(s)  293  in the form of UI event codes indicating key-selection events, resting hands/fingers, gestures, etc. The one or more processor cores  293  communicate with the UI controller  291  to render images on display  285 , turn on various indicators  281  (LED or otherwise), output signals for auditory expression via speaker  279  and so forth. 
     As shown, processor  257  (i.e., UI controller  291  and processor core(s)  293 ) are coupled to memory  259 , which may include a combination of volatile and nonvolatile storage, the latter including read-only and/or writeable memory (e.g., Flash memory, magnetic storage, optical storage, etc.). In the illustrated embodiment, memory  259  includes a program memory  301  (i.e., to store various executable software programs/program code such as application programs, operating system, device drivers and so forth) and data memory  303 . More specifically, UI program code  315  (software) which, when executed by UI controller  291  and/or processor core(s)  293 , enables raw signals from the proximity, vibration and/or capacitive touch sensors to be resolved or otherwise construed or interpreted as elemental user-input events (e.g., touch events, tap events, proximity events, hover events, finger/rest hand events, etc.) and, based thereon, as corresponding gestures and key selections, is stored within program memory  301 , as is operating system code  311  and other application software  317  which may further process user-input events. In one embodiment, for example, UI controller  291  detects elemental user-input events based on sensor input and outputs UI-event codes indicative of gestures, key selections, user-interface state (i.e., resting hands/fingers, hovering hands/fingers, approaching hands/fingers, etc.) to operating system  311  (i.e., to an executed instance thereof). Operating system  311 , in return delivers UI-event codes, with or without further processing (e.g., filtering) to executing instances of application programs (i.e., executing processes) to enable responsive action. The operating system and/or executing processes may, for example, revise contents of a display buffer or frame buffer  321  within data memory  303  to render various images and effects via display  285  (including the various animation effects and touch-emergent keyboard images described above), generate user-visible notifications via indicators  281 , generate audible output via speaker  279 , transmit signals via wired and/or wireless interfaces and so forth, with all such UI-event-responsive actions ultimately being effected via instruction execution within the UI controller and/or processor core(s) of processor  257 . The operating system and/or executing processes may also access (read or write) records or databases of UI events (including elemental user-input events) within a sensor history array  323 , various user or application-defined options/preferences  325  and or other application or operating system data  327  within data memory  303 . For example, records within the sensor history array  323  may be used to establish an operating state of the user-interface for purposes of detecting/interpreting subsequent UI events, transitioning computing device  250  into or out of one or more low power operating modes (e.g., to conserve battery power) and so forth. 
     As a user&#39;s fingers come into contact with the flat planar surface, capacitive touch sensors  275  generate corresponding “touch” signals (i.e., are “activated”). Processor  257  periodically or responsively samples the status of each touch sensor and stores the result in data memory  259 . Through execution of operating system software  311  and/or UI software  315 , processor  257  ascertains the location of each activated touch sensor and maps it location to a function, such as a virtual keyboard key, or other icon or construct rendered in display  285 . Similarly, the processor  257  may execute UI software and/or operating system software to monitor the status of vibration sensor(s)  277  to detect user taps (i.e., user contact that exceeds a predetermined or programmed impact threshold) on the planar surface, for example, in connection with key-selection events, gestures or other user input. When a valid tap is detected processor  257  may perform, through software execution, algorithmic analysis of the sensor data contained in memory  259  to determine which area of the planar surface was tapped on, and thus resolve the tap event and one or more temporally correlated touch events as a “tap-touch” event and thus as a higher-level user input event (e.g., key selection or gesture) or component thereof. 
     In one embodiment, at least one of the one or more vibration sensors  277  is implemented by an accelerometer capable of detecting and signaling motion of computing device  250  and thus enabling responsive operation by processor  257 . For example, upon determining that the computing device is being moved, processor  257  (through execution of UI software  315  and/or operating system software  311 ) may temporarily suspend reception of user-input via a virtual keyboard until the motion stops, thus avoiding interpretation of inadvertent user taps or touches as keystrokes or gesture input while the computing device is being moved and freeing the user to touch anywhere on the touch-sensitive surface (i.e., while moving the device). 
     Any of the various methodologies disclosed herein and/or user interfaces for configuring and managing same may be implemented by machine execution of one or more sequences instructions (including related data necessary for proper instruction execution). Such instructions may be recorded on one or more computer-readable media for later retrieval and execution within one or more processors of a special purpose or general purpose computer system or consumer electronic device or appliance, such as the computing device described in reference to  FIG. 10 . Computer-readable media in which such instructions and data may be embodied include, but are not limited to, non-volatile (non-transitory) storage media in various forms (e.g., optical, magnetic or semiconductor storage media) and carrier waves that may be used to transfer such instructions and data through wireless, optical, or wired signaling media or any combination thereof. Examples of transfers of such instructions and data by carrier waves include, but are not limited to, transfers (uploads, downloads, e-mail, etc.) over the Internet and/or other computer networks via one or more data transfer protocols (e.g., HTTP, FTP, SMTP, etc.). 
     In the foregoing description and in the accompanying drawings, specific terminology and drawing symbols have been set forth to provide a thorough understanding of the disclosed embodiments. In some instances, the terminology and symbols may imply specific details that are not required to practice those embodiments. For example, any of the specific dimensions, form factors, component circuits or devices and the like can be different from those described above in alternative embodiments. Additionally, links or other interconnection between system components or internal circuit elements or blocks may be shown as buses or as single signal lines. Each of the buses can alternatively be a single signal line, and each of the single signal lines can alternatively be buses. The terms “connected,” “interconnected” and “coupled” are used herein to express a direct connection as well as a connection through one or more intervening circuits or structures. Device “programming” can include, for example and without limitation, loading a control value into a register or other storage circuit within an integrated circuit device in response to a host instruction (and thus controlling an operational aspect of the device and/or establishing a device configuration) or through a one-time programming operation (e.g., blowing fuses within a configuration circuit during device production), and/or connecting one or more selected pins or other contact structures of the device to reference voltage lines (also referred to as strapping) to establish a particular device configuration or operation aspect of the device. The terms “exemplary” and “embodiment” are used to express an example, not a preference or requirement. Also, the terms “may” and “can” are used interchangeably to denote optional (permissible) subject matter. The absence of either term should not be construed as meaning that a given feature or technique is required. 
     Various modifications and changes can be made to the embodiments presented herein without departing from the broader spirit and scope of the disclosure. For example, features or aspects of any of the embodiments can be applied in combination with any other of the embodiments or in place of counterpart features or aspects thereof. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.