Patent ID: 12236084

DETAILED DESCRIPTION

An information handling system keyboard replaces a function key row with a touch function row to accept configurable function commands with touch inputs supported by an on-screen-display user interface presented at a system display referenceable while using the keyboard. For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.

Referring now toFIG.1, an exploded perspective view depicts a portable information handling system10having a mechanical function key row of a keyboard40replaced by a touch function row44that detects function key inputs through touch interactions. In the example embodiment, information handling system10has a portable configuration with housing12having a main portion14rotationally coupled to a lid portion16by a hinge18to rotate between open and closed positions. A display20couples in lid portion16to present visual images, such as a liquid crystal display (LCD) panel or an organic light emitting diode (OLED) film. Housing lid portion16rotates to an open position having main portion14supporting lid portion16with display20in a viewing position. Housing main portion14includes a motherboard22that couples processing components in place to process information. For example, a central processing unit (CPU)24executes instructions to process information in cooperation with a random access memory (RAM)26that stores the instructions and information. A solid state drive (SSD)28provides persistent storage of information and instructions, such as an operating system and applications that are retrieved at power up of the system to RAM26by an embedded controller30. Embedded controller30generally manages physical operating conditions within housing12, such as application of power and maintenance of thermal constraints, and interactions with peripheral devices, such as a keyboard and mouse. A graphics processing unit (GPU)32interfaces with CPU24to further process information that is presented as visual images at display20. A wireless network interface controller (WNIC)34communicates with external networks and peripherals through wireless signals, such as WIFI and BLUETOOTH. Although the example embodiment depicts a convertible portable information handling system configuration, in alternative embodiments other types of information handling systems may be supported, such as stationary configurations that use a peripheral keyboard.

In the example embodiment, housing12includes a cover portion36that couples to main portion14to cover the processing components. A touchpad38and keyboard40couple to the upper surface of cover portion36to accept end user inputs when housing12rotates to an open position. Keyboard40has plural mechanical keys42that accept end user inputs by a press of an end user finger to depress the key vertically relative to cover portion36. As an example, mechanical keys42are biased upwards by a rubber dome or other biasing mechanism and detect an input when pressed downward to contact a membrane within housing12. The membrane decodes the position of the contact and reports the mechanical key input to the embedded controller and CPU for use as an end user input. A conventional QWERTY keyboard on a portable information handling system includes a bottom row with a spacebar, three middle rows with letter input values, an upper row with number values that shift to punctuation values, and a far upper function row with function values. A conventional function row includes a far left mechanical escape key, function keys F1 through F12, and far right insert and delete keys. In addition to accepting function inputs when depressed simultaneously with an FN key input on the spacebar row, at least some of the function keys support a secondary input, such as speaker controls, display brightness controls, print controls, etc. . . . .

The example embodiment depicts keyboard40having mechanical keys of a function row replaced by a touch function row44having plural touch function locations46that accept function key inputs without a mechanical key. In one embodiment, touch function row44is unlabeled so that function inputs are coordinated with a presentation at display20when an end user interacts with a capacitive touch detection surface of touch function row44. In an alternative embodiment, touch locations46are identified with light emitting diode illumination to aid end user touch function interactions. Alternatively, a display is placed below the touch detection surface to present the input values represented by each touch location44. By replacing the standard function row with a generic capacitive touch detection strip, the available functions and their arrangement become flexible and configurable so that an end user can personalize and optimize the available touch functions. Further, gesture and other touch inputs may enhance end user interactions with the touch function row. For instance, sliding an end user finger along the touch function row provides a visual feedback at an on-screen-display user interface presented at display20to coordinate function selection, such as by highlighting functions at display20as the finger passes by a touch location associated with a function. The touch function row interactions coordinated through display20helps to keep an end user's eyes focused on the main display to reduce workflow breaks. Further, traversing options and making selections with gestures, such multiple fingers, swipes and flicks, accomplishes function key selections with rapid and blind interactions along the lines of touchpad and touchscreen interaction models familiar to end users.

In the example embodiment, touch function row44couples to housing cover portion36between the upper row of mechanical keys and display20in lid portion16. A hardware, embedded code and software architecture coordinates end user function key selection inputs with touches at touch locations and presentation of function key values at display20in a touch function on-screen-display user interface. A variety of selection options are available to adapt to end user preferences, such as lift and tap to select a function, a slide to present the on-screen-display user interface, and specific gestures associated with common function key inputs, such as speaker controls and microphone controls. In one embodiment, a long press is recognized to open menus or user interfaces with additional details, such as a pause at a selection that maintains contact for a predetermined amount of time. User configurability through a touch function menu optimizes the touch function row interactions for each end user.

Referring now toFIG.2, one example embodiment of a touch function row44and touch function on-screen-display user interface48is depicted. In the example embodiment, touch function row44includes a secondary display (such as the embodiment ofFIG.7described below) that presents an adaptive and configurable set of function input options, such as an escape key, a speaker control option, a speaker mute option, a brightness option and a delete option. An end user selects the functions that are presented and the order of the functions in a customizable manner. Interactions with touch function row44can include a hover option, in which an on-screen-display user interface is activated by a hover and pause, a haptic feedback option, in which inputs are confirmed with a vibration, and a gesture option that can provide shortcuts and automated reconfiguration of the type and order of functions presented. In one example, a task bar50may change places with touch function row44so that an end user can interact with the touch function row using a mouse or touches at the display and can interact with the task bar50through the capacitive touch surface of touch function row44. In the example embodiment, some or all of the functions available in the touch function row are simultaneously presented at on-screen-display user interface48. Alternatively, a press at a function location of touch function row44activates a function associated with the location or activates an on-screen-display user interface having a submenu for the function. For instance, a press on a speaker or microphone mute icon presentation at touch function row performs the function without further interactions, such as the long press defined above; a press on a speaker icon opens a speaker control menu to adjust volume, balance and other operating conditions. In one embodiment, when a submenu is opened the touch function row becomes a sliding control bar as an input to the function, like changing speaker volume. In another example embodiment, commonly used keys, such as the escape and delete keys, remain presented in the on-screen-display user interface independent of interactions with the touch row function, such as at all times or during times when the task bar is presented.

Referring now toFIG.3, another example embodiment of a touch function row44and touch function on-screen-display user interface48is depicted. In the example embodiment, touch function row44does not have a display underlying the touch location and instead identifies each touch location with a point light source, such as an LED. The touch locations are fixed in relation to the point light sources and the identification of each touch location function is provided by the touch function on-screen-display user interface48when an end user initiates a touch interaction with the touch function row. In the example embodiment, an end user has touched or hovered at a touch location46resulting in a speaker control on-screen-display user interface being presented at the display. Further interactions with the speaker controls may be performed by treating the touch function row touch locations as submenu inputs or by interacting directly through the display user interface with a mouse and the operating system. When touch function row44designates a submenu selection, the touch locations are reassigned input values to control the submenu instead of the touch functions until the submenu is removed from the display.

Referring now toFIG.4, another example embodiment of a touch function row44and touch function on-screen-display user interface48is depicted. In the example embodiment, touch function row44is a capacitive touch detection surface that is unlabeled so that touch locations are identified by the on-screen-display user interface when a touch is detected at touch detection row44. In the example embodiment, a vertical line45defined with an LED, light guide, or etching, separates the escape and delete keys to help identify the escape key and delete key input touch locations; in an alternative embodiment each of the touch locations may be separated by a similar vertical line. In one example embodiment, a sliding motion along touch function row44presents a user interface with all function key inputs displayed and highlighting the function key input most closely located to the touch location. Highlighting of the function key inputs is performed in a variety of ways, such as enlarging a function icon nearest a touch location, showing a different color or transitioning between translucent and fully depicted views. In another example, proximity sensing is applied to initiate presentation of the user interface without a touch at the touch function row, with a pause in movement of a proximity highlighting or selecting the function. In one embodiment, when a function value is highlighted at the display from a pause, a tap initiates the function value. In another embodiment, when sliding touch highlights a function followed by a lift of the finger from the touch function row and a tap at the capacitive surface, the function value is commanded that is highlighted at the time of the lift of the finger.

Referring now toFIG.5, another example embodiment of a touch function row44and touch function on-screen-display user interface48is depicted. In the example embodiment, an adaptive touch function row44is presented at a bottom portion of a flexible film display20, such as an OLED film that folds at the housing hinge location so that the touch function row is presented between the keyboard and hinge. The touch locations and touch input values are configurable in content, order and placement. In the example, an end user flicks up with a finger in a gesture that commands a function value at the touch location to present a submenu in the display lid portion location. Including the touch function row in a flexible display enhances configurability, such as by allowing the end user to select any of the display options shown inFIGS.2,3and4.

Referring now toFIG.6, an exploded perspective view depicts a touch function row44configured to accept touch inputs and force inputs with or without labeling the touch input values of the touch locations. In the example embodiment, a cover glass52is exposed at an upper surface of the touch function row between a keyboard and display with a label having key values of the touch function row touch locations. In alternative embodiments, cover glass52may be unlabeled with a background color to match the system housing. A force sensing membrane56couples below cover glass52with an adhesive54to support sensing of an amount of force applied at touch locations of cover glass52. Another adhesive layer58couples force sensing membrane56to a modified lightguide60and a printed circuit board62having LEDs64. Printed circuit board62includes a processing resource, such as a microcontroller unit (MCU), to detect touches at cover glass52and to sense force with force sensing membrane54. Point illumination provided by LEDs64is guided through modified lightguide60to identify touch locations at cover glass52. Touch sensing and proximity sensing may be supported with a capacitive touch sensor included in cover glass52, force sensing membrane56or printed circuit board62.

The example embodiment ofFIG.6supports a variety of different and configurable touch function row interactions. As described above, touch function key value selections are made by sliding a finger along cover glass52to bring up the touch function on-screen-display user interface, pausing to highlight a desired touch function key value, then lifting and tapping to input the highlighted key value. Force sensing membrane56offers an alternative input method of increasing force at a touch location to indicate an input selection. In yet another embodiment, proximity sensing is used to detect a finger in a hover position over cover glass52and apply the hover in a similar manner as a touch. An advantage of the hover input is that a transition from hover to touch indicates a touch function value input without a lifting motion. The touch location from the hover position is highlighted at the on-screen-display user interface, by the labels on the cover glass when present, and by the LED illumination point locations. These indications are configurable so that an end user can perform a direct touch without any other indications when desired to have more rapid inputs without the pause associated with presentation of display function input values.

Referring now toFIG.7, an exploded perspective view depicts a touch function row44configured to accept touch inputs labeled by a secondary display72having configurable touch input values for the touch locations. In the example embodiment, cover glass52includes touch sensors, such as embedded wires, and mounts to a cover glass bracket66having piezoelectric haptic vibration devices68at opposing ends. A foam seal70couples the cover glass bracket to a display frame74that holds secondary display72configured as an LED display panel. The secondary display couples to a subassembly76, which has printed circuit board62coupled at a bottom surface. An ambient light sensor78and LEDs64couple to the printed circuit board to manage illumination at the LED display panel. A touch sensor control board80interfaces with printed circuit board62to coordinate presentation of function icons and end user interactions at the LED display panel, as described in greater detail below. An end user configures the touch function row to have desired functionality, which is presented at the LED display panel and detected by the touch sensor in cover glass52. When function interactions take place, touch sensor control board80communicates the interactions through a system embedded controller to the CPU for use in managing physical components and inputs. Haptic devices68activate at each input to provide feedback to the end user as inputs are detected and applied. The use of an LCD display panel tends to increase the thickness or Z-height of the solution relative to other solutions, such as the OLED film illustrated inFIG.8below.

Referring now toFIG.8, a side sectional view of the touch function row depicts the vertical arrangement of the components within an information handling system housing. In the example embodiment, a glass cover52couples at an upper surface to an underlying touch sensor82with an adhesive54. OLED film72presents touch function row icons as visual images in cooperation with printed circuit board62, which interfaces through a connector86to an information handling system motherboard and embedded controller. In the example embodiment, an escape button88is included to manage inputs of the escape function value, such as with a pressure sensor or mechanical button. Maintaining some of the functions as physical keys can help to ensure that an end user has commonly used functions available in defined positions. Other functions remain configurable by changing the positions at which the function icons are presented at the OLED film. One important consideration for the implementation of the touch function row is that the low Z-height of the touch function row adjacent the keyboard rear where thermals exhaust improves thermal rejection, such as with additional exhaust vent structure. The use of an OLED display film over the LCD panel ofFIG.7helps to drive a low Z-height with improved thermal management.

Referring now toFIG.9, a block diagram depicts logical elements that coordinate interactions of an end user at a touch function row. In the example embodiment, touch function row44stores instructions in a non-transitory memory90that execute on a processing resource92, such as an MCU. Touch function row44processing resource92interfaces with a system motherboard through a USB HID control interface94and with a mass storage, such as an SSD, through a USB mass storage interface96. In alternative embodiments, other types of interfaces may be used. Keyboard40includes mechanical keys42that accept end user touch inputs with a vertical movement while touch function row44is a flat capacitive touch surface that detects touches at touch locations. Keyboard40communicates key inputs through a conventional interface, such as an embedded controller I2C interface98or a USB HID keyboard interface100. Keyboard40may be integrated in a portable information handling system housing as described above or in a peripheral keyboard that operates separate from an information handling system housing. A row images and mapping module110arranges presentation of function icons, such as key values for the function key row, and maps the presentation of the function icon locations to the touch function row touch locations. A key/event interrupt module108monitors the touch sensor to detect when a touch event takes place and provides the event information to the row image and mapping module to execute. A configuration and control module106manages the order and list of functions presented at the touch function row, such as based on end user preferences and context of the operating conditions. An event process module104executes to handle events as detected according to the mapped positions and configuration.

In the example embodiment, configuration and control module106accesses available touch function row configurations stored in persistent storage102to define a mapping of touch locations to functions for presentation at the touch function row display and system display. For example, a table of available functions is presented along with a list of functions assigned to touch locations. The end user can then drag and drop desired functions from the list of available functions to touch locations defined on the touch function row. The available function may include the standard function keys, such as escape, insert, delete and F1 through F12, presented in any order desired by the end user. Secondary functions that are typically shown above F1 through F12 keys may also be included in any desired order independent of the values F1 through F12. Some of the function keys may result in a command directly issued to the system, such as a mute of a speaker or microphone. Others may result in opening of a submenu that presents control inputs, such as an audio speaker control function that opens a menu on the main display to control speaker volume, balance and quality. In some instances, a function command may open a submenu to show the value selected by the input, such as a volume bar that shows a volume level when increased by a volume up function key. In one embodiment, a macro arrangement allows an end user to define and customize customs that are assignable to the function keys, such as to support applications running on the system.

Referring now toFIG.10, an example embodiment depicts hardware components that cooperate to support touch function row interactions. Motherboard22supports execution of an operating system and application on CPU24under management of an embedded controller30. CPU24and embedded controller30interface with touch function row processing resource92through I2C, UART, USB and similar interfaces operating with a clock112. In the example embodiment touch function row44has a SAM9×75 MCU as the processing resource92that receives power from a power source110and executes instructions stored in a flash memory90. Processing resource92interfaces with display116, such as an OLED film included in the touch function row, to present function icons as defined by the configuration selected by an end user. A touch detection surface118detects touch locations, and processing resource92initiates haptic feedback from a haptic device114as defined by the configuration settings when a touch input is detected. ALS78detects ambient light at the touch function row to adjust brightness of display116. In the example embodiment, a point illumination LED64indicates a fixed location for the escape and delete keys. In one example embodiment, processing resource92supports presentation of touch functions at both the secondary display included in the touch function row and in the primary system display. For instance, the processing resource supports function interactions at the main system display in preboot operations to fully interact with an end user who has a need of functions before system boot.

Referring now toFIG.11, an example embodiment depicts presentation of a touch function row44at a display20that folds over a housing hinge to support the touch function row on the housing main portion. Display20presents task bar50in a conventional manner with touch function row44presented at the bottom portion of the display where the film folds over top the housing hinge. The presentation of the touch function row44at display20is managed with a hardware solution that can also work when a separate secondary display is used. The CPU24and GPU of the motherboard manage the upper part122of the display in a conventional manner with an eDP interface, such as with the operating system and applications, while the visual images of the touch function row are presented in a lower portion124by a processing resource92of the touch function row, such as an MCU, through a MIPI interface. Similarly, the touch detection surface of display20has the upper portion120managed by CPU24while processing resource92manages the touch detection surface in a lower portion126. This arrangement uses two separate I2C interfaces to manage touch inputs at the touch detection surface plus a USB and I2C interface to communicate between processing resource92and CPU24.

Referring now toFIG.12, an alternative embodiment depicts presentation of a touch function row44at a display20that folds over a housing hinge to support the touch function row on the housing main portion by leveraging the display scalar. In the example embodiment, scalar130, such as an ASIC with PBP function, generates presentation of visual images for both upper portion122and lower portion124of display20based upon visual information provided from processing resource92and CPU24through separate eDP interfaces. The touch detection surface upper portion120is managed by CPU24and the touch detection surface lower portion126is managed by processing resource92through separate I2C interfaces. The example embodiment and that ofFIG.11provide support for separate display and touch areas where needed and also support operations in a preboot environment when a single flexible display is used.

Referring now toFIG.13, an alternative embodiment depicts presentation of a touch function row44at a display20that folds over a housing hinge to support the touch function row on the housing main portion by leveraging the display as a single entity. Display20has a single display area that presents information provide by CPU24through a single eDP interface. CPU24retrieves the touch function row configuration from the embedded controller and generates the visual images based upon the defined configuration. Similarly, the touch detection is provided by a single touch detection surface120communicated to CPU24through an I2C interface. As touch inputs are detected, CPU24adjusts the touch function row presentation to the configured response.

Referring now toFIGS.14A and14B, a flow diagram depicts a process for managing inputs at a touch function row. The process starts at step150from an idle state and determines at step152if a touch is detected at the touch function row. If not the process returns to step150and periodically checks for a touch at the touch function row. When a touch and/or hover is detected, the process continues to step154to determine if the touch involves a gesture, such as with multiple fingers. If not, the process continues to step156to bring up the on-screen-display user interface at a menu state that presents the functions for all of touch locations at the touch function row. At step158, a determination is made of whether a slide motion is detected at the touch function row capacitive touch surface. If the touch and/or hover is stationary, the process continues to step166to highlight the function associated with the touch location detected for the touch and/or hover with a selection preview presentation for the item in the menu presented by the touch function row on-screen-display. If a sliding motion is detected, the process continues to step160to interactively indicate with a selection preview the closest item to the sliding finger touch/proximity. From steps160and166, if the finger lifts away from the touch function row so that touch and/or proximity is no longer detected, the process continues to step168to indicate that no input was detected and step170to hide the on-screen-display user interface after no touch is detected within a countdown time period. From steps160and166the process continues to steps162and164to detect if an input is made at the touch function row. At step162an input is detected when a touch and/or hover is followed by a press of a predetermined pressure detect by a force detection device. At step164an input is detected as a tap, such as a contact followed by no contact then contact within a predetermined time. In an embodiment that relies upon hover, an input may be a hover followed by a contact. Detection of an input results in selection of the function menu item for the function icon highlighted at the time of the input, as is described in greater depth below.

At step154when multiple fingers are detected or other indications of a gesture input, the process continues to step170to determine if the multiple finger input has a sliding motion. If a sliding motion is detected, the process continues to step172to bring the on-screen-display user interface for speaker control onto the display, such as sound bar that the end user can interact with through the display to change speaker volume. Once the speaker volume bar is presented, the process continues to step174to interactively adjust the speaker volume based upon the sliding motion until at step176a lift of the finger is detected from the touch function row. From step176when no contact is detected the process continues to step184to countdown for removal of the on-screen-display user interface. In addition, from removal of contact at step176the process continues to step178to set the volume and play preview sound based upon the setting at contact lift and to step150to await the next input. When at step170a slide is not detected, the process continues to step182to determine if a lift is detected to remove contact of the multiple fingers from the touch function row. At step184when a lift of the contact is detected the on-screen-display user interface counts down for removal. At step182with removal of contact and no sliding motion, the process continues to step186to present the microphone function at the on-screen-display user interface and at step188to toggle the microphone between mute and non-mute states. The process then returns to step150to monitor for additional inputs. Although the example embodiment describes two finger gesture inputs at a touch function row, other types of gestures may be used. For instance, a two finger gesture may command a speaker control user interface and a three finger gesture may command a microphone control user interface. Other types of gestures may support other functions, such as drawing a circle, a rapid back and forth motion or other distinguishable inputs to command display operational menus or keyboard backlight illumination.

Referring now toFIGS.15A and15B, a flow diagram depicts a process for managing a touch input at a touch function row once the on-screen-display user interface is active. From step162or164ofFIG.14, the process starts at step200by selecting the indicated function in the menu of the on-screen-display user interface. At step202a determination is made of whether the selected function is toggle function that toggles between first and second states at each input, such as mute or audiovisual play. If the function is a toggle function, the process continues to step214to update the on-screen-display user interface presentation of the toggled value and to step216to execute the toggle command. At step218after the toggle command is executed, the process returns to an idle state. When the function is not a toggle function at step202, the process continues to step204to determine if the function is a slider function, such as audio balance or volume. If the function has a slider function, the process continues to step220to update the on-screen-display slider control presentation and to step224to interactively adjust the slider visual presentation based upon the touch positioning. At step226when the touch function row detects a lift without contact, the slider input is stopped and the process continues to step228to execute the state update for the function adjusted by the slider update. From step228, the process returns to idle at step218and initiates count down for on-screen-display user interface hide at step258.

When the function is not a slider function at step204, the process continues to step206to determine if the function has a submenu, such as an audiovisual presentation controller that manages presentation of a video. If a submenu function is selected, the process continues to step230to update the on-screen-display user interface for the submenu with presentation of the submenu at the display. At step232the user interface interactively indicates in the submenu the commands of the submenu that are highlighted by touches at the touch function row. For instance, when the submenu opens at the display the touch locations are remapped to the submenu values and the submenu presentation is adjusted to show which of the touch locations is pressed on the submenu. At step234an input is accepted by increased pressure on the touch location that is detected by a force sensor. Alternatively at step236an input is accepted by a lift and tap at the touch location to accept an input for the submenu item highlighted at the display at the time of the lift. At step238the selected submenu function is executed and the process returns to idle at step240. When the function is not a submenu function at step206, the process continues to step208to determine if a customizer function is selected, which supports the end user defining a personalized on-screen-display presentation of functions and the arrangement of the presentation of the functions, such as an order in which function key icons are presented. If yes, the process continues to step242to hide the on-screen-display user interface and to step246to bring up the customize presentation for the customized function. At step248, the process completes by performing the customizer function, such as presenting a drop and drag menu that shows all available functions and the functions that are selected from all available functions for presentation in the touch function row on-screen-display user interface. If at step208the function is not a customized function, the process continues to step210to determine if the function is to launch an application. If yes, the process continues to step250to hide the on-screen-display user interface and to step252to launch the application. If at step210the function is not an application launch, the process continues to step212to execute a virtual keypress function and step256to hide the on-screen-display user interface. The logic completes at step240by going to an idle state.

Referring now toFIG.16, a flow diagram depicts a process for hiding a touch function row on-screen-display user interface. The process starts at step280with the on-screen-display user interface presented at the display, such as after a touch, sliding motion or hover at the touch function row. At step282a determination is made of whether a touch is detected on the touch function row. If a touch is detected, the process ends at step288. If a touch is not detected, the process continues to step284to determine if the autohide countdown has elapsed, such a predetermined time period. If the countdown has not elapsed, the process returns to step280to continue the countdown. If the countdown has elapsed, the process continues to step286to hide the on-screen-display user interface and to step288to end.

Referring now toFIGS.17A and17B, a flow diagram depicts interactions at a touch function row having touch and/or hover interactions supported. The process starts at step300and at step302determines if an end user finger is in proximity to the touch function row. In an alternative embodiment, actual touch may be used instead of proximity. The process returns to step300to monitor for proximity or touch and, when touch or proximity is detected, continues to step304to bring up the touch function on-screen-display user interface for presentation at the system main display or the integrated touch function row display as described above. At step304, the touch function icon is highlighted for the touch function key value that is associated with the touch location closest to the touch or proximity detection. At step308a determination is made of whether the finger remains in proximity and/or contact with the touch location. If yes, the process returns to step306to continue monitoring for an input made by a tap from the proximity sensing or by a lift and tap by the touch sensing. Once proximity or touch is not detected and an input is not detected, the process continues to step310for proximity and step312for touch to timeout the touch function on-screen-display user interface and returns to step300. If an input is detected by a lift and tap or by a proximity to tap, the process continues to step314to determine the touch function value selected. If the touch function value is a toggle input, such as a microphone or speaker mute, the process continues to step316to perform the toggle action and then returns to step300.

At step314, if the input is a submenu selection, the process to step318to bring up the submenu based function selection for presentation, such as slider bar or a discreet interface. If the slider bar submenu is selected, the process continues to step320to present the slider bar and to step322to determine if the finger remains on the touch detection surface of the touch function row with a sliding contact. If yes, the process continues to step324to adjust slider bar value based upon the touch input to the slider bar. Once the slider bar is released at step322or324, the process continues to step326to timeout the touch function on-screen-display user interface and returns to step300. If a discreet function is selected at step328, the process continues to step330to highlight the closest touch function icon of the touch function on-screen-display user interface. At step332a determination is made of whether a finger remains on the touch detection surface, such as with a sliding contact or an input to the discreet function. Once the finger leaves the touch detection surface, the process continues to step334to detect the finger has left the contact and step336to detect a tap for an input. Although the discreet menu in the example embodiment uses a lift and tap, an input may be made by a force detection or proximity to tap instead. The process then returns to step300.

Referring now toFIG.18, a keyboard40is depicted having a touch function row44supported by haptic feedback that is isolated from the housing cover portion36by integrated dampeners. Touch function row44couples to housing cover portion36between keys42of keyboard40and the front side of the housing cover portion where the hinge couples the housing lid portion. An upper touch detection surface350couples over a gasket352to a base354that supports the touch function row. First and second haptic device assemblies356couple to the bottom side of upper surface350and include haptic devices370and372that generate vibration, such as piezoelectric devices. When a touch input is detected at the touch function row44, haptic feedback is provided by generating vibration with piezoelectric devices370and372, which translates through to upper touch detection surface350, as is described above.

Referring now toFIG.19, a top view depicts a haptic feedback device356having vibration isolated to a touch function row and from a housing cover portion. In the example embodiment, an adhesive366is applied to the upper surfaces of piezoelectric haptic devices370and372to couple directly to the upper surface of the touch function row. Adhesive364is also applied to an outer perimeter358of haptic device356so that a support plate360holding the haptic devices370and372is captured between the touch function row and housing cover portion with a resilient spring member362on each side of support plate360. As a result, vibration from haptic devices370and372translates directly to the upper contact surface of the touch function row and is dampened relative to the housing cover portion. The lateral location of the resilient member minimizes the vertical size of the haptic device assembly. In one example embodiment, support plate360is cut from stainless steel material. In alternative embodiments, other types of material may be used so that the spring shape of resilient spring member362has a desired dampening effect.

Although the present invention has been described in detail, it should be understood that various changes, substitutions and alterations can be made hereto without departing from the spirit and scope of the invention as defined by the appended claims.