Abstract: The present disclosure provides techniques for management of user interface elements based on historical configuration data. Use of historical configuration data to render user interface elements improves usability of graphical user interfaces by maintaining a consistent user experience. The states of user interface objects in a hosting environment are retained as historical configuration data and linked to a hosting environment profile. When the same or similar hosting environment is detected, the user interface elements are rendered based on the historical configuration data. For example, the last positions of windows in a particular monitor topology are stored as historical configuration data linked to that monitor topology. The windows are returned to their previous positions when a computing device is next configured with the same or similar monitor topology.

Abstract: The present disclosure provides techniques for management of user interface elements based on historical configuration data. Use of historical configuration data to render user interface elements improves usability of graphical user interfaces by maintaining a consistent user experience. The states of user interface objects in a hosting environment are retained as historical configuration data and linked to a hosting environment profile. When the same or similar hosting environment is detected, the user interface elements are rendered based on the historical configuration data. For example, the last positions of windows in a particular monitor topology are stored as historical configuration data linked to that monitor topology. The windows are returned to their previous positions when a computing device is next configured with the same or similar monitor topology.

Abstract: The present disclosure provides techniques for management of user interface elements based on historical configuration data. Use of historical configuration data to render user interface elements improves usability of graphical user interfaces by maintaining a consistent user experience. The states of user interface objects in a hosting environment are retained as historical configuration data and linked to a hosting environment profile. When the same or similar hosting environment is detected, the user interface elements are rendered based on the historical configuration data. For example, the last positions of windows in a particular monitor topology are stored as historical configuration data linked to that monitor topology. The windows are returned to their previous positions when a computing device is next configured with the same or similar monitor topology.

Abstract: In some examples, input received from an input device, such as a keyboard, is modified by a component associated with an operating system before the input is delivered to an application. For instance, a component associated with the operating system may become registered for modifying input. In some situations, the input is modified based at least in part on metadata associated with the input device. For example, a location of a fingertip on a touch-sensitive display may be used to modify the input before delivery to an application.

Abstract: In some examples, input received from an input device, such as a keyboard, is modified by a component associated with an operating system before the input is delivered to an application. For instance, a component associated with the operating system may become registered for modifying input. In some situations, the input is modified based at least in part on metadata associated with the input device. For example, a location of a fingertip on a touch-sensitive display may be used to modify the input before delivery to an application.

Abstract: Disclosed are techniques and systems for obtaining contextual information at least in part from a keyboard, to improve typing efficiencies and user experience. The contextual information may include keyboard attributes, typing metadata, user actions, and the like. The keyboard may be configured to detect an input event at the keyboard. A human interface device (HID) stack is configured to receive the contextual information, and a keyboard manager is configured to determine an output based at least in part on the input event and the contextual information. The output may be a most probable function (non-text-based output), or character or word (text-based output) that can be suggested or used to auto-correct application data. In some embodiments, the user action received in the contextual information may be translated to a gesture to manipulate application data.

Abstract: A voice-activated user interface for an application is described. The voice activated user interface invokes a speech recognition component to recognize audio input from a user. If the audio input is a command, then a validation component is invoked to determine whether to validate the command prior to execution.

Abstract: A method and system for tracking client software use is disclosed. User data, specifically user interaction with a client-installed software application, is collected in data files and the data files are dynamically uploaded over a global computer system, such as the Internet, to a remote analysis system. The data files are parsed for on-going analysis of feature usage. Typically, for any action that a user performs in the software application, several items are recorded in a data file, such as a user ID, an absolute time-stamp, the method invoked including application source (if the software application includes more than one application), and details such as the dialog invoked, button pressed, menu used, menu item selected, application launch, application termination, as well as environment variables, such as operating system, screen resolution, etc.