Simulated Touch Event Handling for Proximity and Contact Input
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing touch-sensitive surfaces in electronic devices often struggle with seamless integration of contact-based and proximity-based inputs, leading to user confusion and incompatibility with different operating systems and peripheral input devices.
Innovation Solution
Methods and devices that facilitate and convey contact-based and proximity-based user inputs, translating other input events into simulated touch events, and merge separate event streams to enhance cross-platform compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If touch-sensitive surfaces include sensors that detect proximity-based inputs, then additional avenues for manipulating user interface objects are provided, but contact-based inputs and proximity-based inputs interfere with each other and cause user confusion
Solution Approach 1:
The patent segments the event handling process into distinct phases (hover phase and contact phase) with clear boundaries. The system determines whether an input event is a hover event or a contact event and routes it to appropriate application views, preventing interference between proximity-based and contact-based inputs while maintaining seamless operation.
2Adaptability or versatility
If conventional methods handle contact-based and proximity-based inputs separately, then implementation is straightforward, but compatibility with different operating systems and peripheral input devices is limited
Solution Approach 1:
The patent creates a universal event handling mechanism that processes both contact-based and proximity-based inputs through a common interface. The system translates different input types (mouse, trackball, stylus, finger) into standardized simulated touch events, enabling applications to work across different operating systems and peripheral devices without requiring input-specific handling code.
Solution Approach 2:
The patent introduces an intermediary layer (the operating system's event handling mechanism) that sits between various input devices and applications. This intermediary translates and normalizes inputs from different sources into a unified event format, allowing applications to interact with diverse input devices through a consistent interface while maintaining compatibility across platforms.
3Reliability
If applications expect specific input events, then application functionality is maintained, but compatibility with different operating systems and peripheral devices is reduced
Solution Approach 1:
The patent creates simulated touch events that copy the essential characteristics of actual touch inputs. When a mouse, trackball, or other peripheral device generates an input event, the system creates a simulated touch event that replicates the position, timing, and other relevant parameters, allowing applications expecting touch events to function correctly regardless of the actual input device used.
Data Source
AI summary
An electronic device, with a display and an input device separate from the display, displays a user interface that includes a representation of a first application. The device receives, at the input device, a user input event directed to a location in the user interface. In response to the user input event, when the respective location in the user interface is over the representation of the first application, the device provides, to the first application, information that describes a simulated touch event including information that describes locations of one or more simulated touches in the user interface; and displays, on the display, a change in the representation of the first application that is determined by the first application in response to the information that describes the simulated touch event.