Touch Event Mediator for Embedded Application Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Portable electronic devices with touch-sensitive displays face challenges in effectively handling touches and gestures, particularly when embedded applications are designed for indicator-based controls, leading to issues like undesired functions and loss of functionality due to incorrect conversion of touch events into mouse events.
Innovation Solution
A method is implemented where a touch is detected on a touch-sensitive display, reported as a specific type to the first application, and if not utilized within a threshold time, the touch is reported to a second application when movement is detected, maintaining the touch location to facilitate proper handling of roll-over and selection events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If touch events are converted to mouse events for embedded applications, then compatibility with existing applications is improved, but functionality is lost and undesired functions occur due to incorrect conversion
Solution Approach 1:
The patent introduces an intermediary touch event processing system that sits between the touch-sensitive display and applications. This mediator captures raw touch events, determines their actual intent based on movement patterns and timing, and translates them into appropriate application-specific commands. For embedded applications, it can simulate mouse events when needed, while for native touch applications, it passes through proper touch event structures, thus resolving the compatibility-functionality contradiction.
Solution Approach 2:
The system dynamically adapts the touch event conversion strategy based on the application type and touch characteristics. It adjusts the conversion rules in real-time: for embedded applications designed for mouse interaction, it converts touch events to mouse events; for native touch applications, it maintains touch event integrity. This dynamic adaptation allows the system to optimize for either compatibility or functionality depending on the context.
2Speed
If touch events are directly reported to the first application, then response time is improved, but touch movement is not properly handled when the application does not utilize the touch type
Solution Approach 1:
The system performs preliminary analysis of the touch event characteristics (movement pattern, duration, pressure) before reporting to the application. It pre-determines whether the touch is intentional or accidental, and whether it should be passed to the first application or redirected. This preliminary action allows for faster overall response time while ensuring proper touch handling, as the system already has the classification ready when the application needs it.
Solution Approach 2:
The system implements a feedback mechanism where it monitors whether the first application utilizes the reported touch event. If the application does not respond or does not utilize the touch type within expected parameters, the system receives feedback and adjusts by redirecting the touch event to the second application or treating it as a scroll/zoom gesture. This feedback loop ensures both rapid response and proper touch handling.
3Extent of automation
If the system waits for application response before handling touch movement, then application control is improved, but user interaction smoothness deteriorates
Solution Approach 1:
The patent segments the touch event handling into independent parallel processes: one process handles the initial touch reporting to the application, while another process independently tracks touch movement and determines gesture type. These segmented processes operate concurrently without blocking each other, allowing the system to maintain both application control and interaction smoothness. The movement handling does not wait for application response, eliminating delays while keeping the application informed.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method includes displaying, on a touch-sensitive display, information associated with a first application and information associated with a second application, detecting on the touch-sensitive display, a touch at a first location associated with the first application, reporting the touch as a first touch type to the first application, and when the first touch type is not utilized by the first application within a threshold period of time and when movement of the touch on the touch-sensitive display is detected, reporting the touch to the second application.