Abstract:
Systems and methods are provided for improving the latency for display of ink during user creation of ink content with a stylus, mouse, finger (or other touch input), or other drawing device for tracing a desired location for ink content in a display area. In order to reduce or minimize the time for display of ink content created by a user using a stylus/mouse/touch input/other device, a separate ink rendering process thread can be used that operates within the operating system and in parallel to other application threads. When it is desired to create ink content within an application, user interactions corresponding to creation of ink content can be handled by the separate ink rendering process thread. This can avoid potential delays in displaying ink content due to an application handling other events in a process flow.
Abstract:
User interface (UI) manipulations may be performed by eliminating noticeable process boundaries associated with or generated by different applications. The techniques herein describe dynamically splitting manipulations across multiple pieces of content without regard to various types and/or states of the user interface manipulations and/or without regard to whether the multiple pieces of content are associated with different individual processes. In at least one example, the techniques described herein enable quick, responsive, and seamless UI manipulations with complex configurations of content on a UI and/or with multiple pieces of content associated with more than one application. Additionally, the techniques described herein further enable content on a UI to "stick" to the user input manipulation or move with the user input manipulation such that the content appears to stay directly in contact with the user input manipulation.
Abstract:
A platform-level container configured to hold natively-supported ink stroke data structures is maintained. The platform-level container is accessible to a plurality of different applications. An ink stroke visual corresponding to each ink stroke data structure held by the platform-level container is rendered via a display. An ink stroke change event corresponding to an ink stroke data structure held by the platform-level container is recognized. The ink stroke data structure is changed to an updated ink stroke data structure in accordance with the ink stroke change event. An ink stroke visual corresponding to the updated ink stroke data structure is rendered via the display without re-rendering ink stroke visuals corresponding to unchanged ink stroke data structures.
Abstract:
A facility for handling input relating to electronic ink is described. In a first thread, the facility produces ink in response to at least a portion of the input. In a second thread distinct from the first thread, the facility manipulates at least a portion of the ink produced in the first thread.
Abstract:
A facility for processing ink input is described. In one example facility, the facility receives ink input from an input device. The facility generates and renders ink stroke data structures in response to received ink input in accordance with an ink input processing pipeline. The facility provides to an executing application access to information traversing the ink input processing pipeline at a selected point in the ink input processing pipeline.