Abstract: A vehicle sliding door brake assembly configured for attachment to a sliding door mechanism of a vehicle may include a brake member connectable to the sliding door mechanism and configured to rotate about a pivot point, the brake member comprising one or more brake portions for selectively engaging a track of the vehicle so as to provide a braking force. The brake portions may be configured to form an inertial counterweight that urges the brake member to move from a neutral position in which the brake portions are not engaged with the track to an engaged position in which one or more of the brake portions are engaged with the track when a sliding door of the vehicle is subjected to an acceleration exceeding a threshold.

Abstract: A vehicle sliding door brake assembly configured for attachment to a sliding door mechanism of a vehicle may include a brake member connectable to the sliding door mechanism and configured to rotate about a pivot point, the brake member comprising one or more brake portions for selectively engaging a track of the vehicle so as to provide a braking force. The brake portions may be configured to form an inertial counterweight that urges the brake member to move from a neutral position in which the brake portions are not engaged with the track to an engaged position in which one or more of the brake portions are engaged with the track when a sliding door of the vehicle is subjected to an acceleration exceeding a threshold.

Abstract: One or more techniques and/or systems are provided for utilizing input data received from an indirect interaction device (e.g., mouse, touchpad, etc.) as if the data was received from a direct interaction device (e.g., touchscreen). Interaction models are described for handling input data received from an indirect interaction device. For example, the interaction models may provide for the presentation of two or more targets (e.g., cursors) on a display when two or more contacts (e.g., fingers) are detected by indirect interaction device. Moreover, based upon a number of contacts detected and/or a pressured applied by respective contacts, the presented target(s) may be respectively transitioned between a hover visualization and an engage visualization. Targets in an engage visualization may manipulate a size of an object presented in a user interface, pan the object, drag the object, rotate the object, and/or otherwise engage the object, for example.

Abstract: In an indirect interaction input device, z-information can be considered in defining a user interaction model for the device. Any measurement of displacement in a z-direction can be used, if such information is available from the input device. The pressure data can be used to define states of interaction, with transitions between these states determined by various thresholds. The device can provide raw or normalized data, and can provide state information or data defining its thresholds that specify state transitions. This information can be provided as an attribute of a contact point provided by the device. Data can be normalized across various similar devices. Applications can use the raw pressure data from the device for their own purposes, or rely on the device itself or host operating system software to interpret the pressure data according to thresholds and states.

Abstract: An input device is disclosed that includes keys on a first surface and a second surface of the input device. At least some of the keys are operably coupled to a matrix including a switch for each key therein. When one of the keys is pressed, the corresponding switch is activated to provide a signal indicative thereof.

Abstract: Automatic mode determination for an input device is disclosed. Depending on conditions of the input device, the input device can transition from a first mode to a transition mode and/or a second mode.

Abstract: One or more techniques and/or systems are provided for utilizing input data received from an indirect interaction device (e.g., mouse, touchpad, etc.) as if the data was received from a direct interaction device (e.g., touchscreen). Interaction models are described for handling input data received from an indirect interaction device. For example, the interaction models may provide for the presentation of two or more targets (e.g., cursors) on a display when two or more contacts (e.g., fingers) are detected by indirect interaction device. Moreover, based upon a number of contacts detected and/or a pressured applied by respective contacts, the presented target(s) may be respectively transitioned between a hover visualization and an engage visualization. Targets in an engage visualization may manipulate a size of an object presented in a user interface, pan the object, drag the object, rotate the object, and/or otherwise engage the object, for example.

Abstract: In an indirect interaction input device, z-information can be considered in defining a user interaction model for the device. Any measurement of displacement in a z-direction can be used, if such information is available from the input device. The pressure data can be used to define states of interaction, with transitions between these states determined by various thresholds. The device can provide raw or normalized data, and can provide state information or data defining its thresholds that specify state transitions. This information can be provided as an attribute of a contact point provided by the device. Data can be normalized across various similar devices. Applications can use the raw pressure data from the device for their own purposes, or rely on the device itself or host operating system software to interpret the pressure data according to thresholds and states.

Abstract: Methods and systems for controlling access of application programs to an adaptive input device are described herein. One exemplary computing system includes an application programming interface executable on a computing device for controlling said access to an adaptive input device having a plurality of display regions. The application programming interface is configured to receive a display request from one of the application programs to display formatted output on the composite display and is further configured to apply at least a display sharing policy based on application-specific policy settings received from the application program for defining an application-specific area including at least one of the display regions. Further, the application programming interface is configured to generate formatted output based on the application-specific policy settings, and to send the formatted output to the application-specific area for display.

Abstract: Methods and systems for controlling access of application programs to an adaptive input device are described herein. One exemplary computing system includes an application programming interface executable on a computing device for controlling said access to an adaptive input device having a plurality of display regions. The application programming interface is configured to receive a display request from one of the application programs to display formatted output on the composite display and is further configured to apply at least a display sharing policy based on application-specific policy settings received from the application program for defining an application-specific area including at least one of the display regions. Further, the application programming interface is configured to generate formatted output based on the application-specific policy settings, and to send the formatted output to the application-specific area for display.

Abstract: Various embodiments of systems and methods to implement a context-based state change for an adaptive input device are provided. For example, a method is disclosed that may include receiving a state input indicating a change in a system state, changing adaptive input device data in response to the state input, the adaptive input device data including one or more of image data or adaptive input device mapping data, and adjusting an adaptive input device display state using the adaptive input device data. Adjusting the adaptive input device display state may include one or more of displaying the image data on an adaptive input device display or adjusting an adaptive input device mapping state according to the adaptive input device mapping data.

Abstract: Various embodiments of systems and method to implement a state change for an adaptive device are provided. In one example, a method is disclosed that includes receiving a system state input indicating a change in a system state of a computing device, changing adaptive device data in response to the system state input to form changed adaptive device data, the adaptive device data and the changed adaptive device data each including one or more of image data and adaptive device mapping data, and adjusting an adaptive device display state using the changed adaptive device data, wherein adjusting the adaptive device display state includes one or more of displaying the image data on the keyboard display and adjusting an adaptive device mapping state according to the adaptive device mapping data.

Abstract: Keyboard gesturing on an input device of a computing system is herein provided. One exemplary computing system includes a host computing device and an input device including one or more keys. The host computing device includes a gesture-recognition engine that is configured to recognize a gesture from touch input reported from a touch-detection engine. The touch-detection engine is configured to detect a touch input directed at a key of the input device. The host computing device further includes an input engine that is configured to interpret a key-activation message based on the gesture recognized by the gesture-recognition engine, where the key-activation message is generated by a key-activation engine of the input device in response to activation of the key.

Abstract: A method for carrying out application-specific mapping of input device elements (for example, human input device buttons). The method includes, from an application matching program, determining, for an application program, whether a control element event (for example, a mouse button click event) needs to carry out an action that is specific to the application program, or to perform its default action. The application matching program is configured to execute independently of the application program. A computing system that is capable of carrying out the above method is also provided.