Selective Touch Data Reporting via System Hook Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current touch screen devices lack fine-grained control over digital touch data and OS touch events, limiting the flexibility of touch-enhanced applications in processing user interactions.
Innovation Solution
Implementing a system hook that selectively filters OS touch events based on application location information, allowing for application-specific filtering criteria to suppress or pass emulated mouse events and other OS touch events, enhancing the control over touch data processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a system hook is implemented to selectively filter OS touch events, then application-specific control over touch data is improved, but device complexity increases
Solution Approach 1:
A system hook is introduced as an intermediary component between the OS touch event generation and application processing. The hook intercepts OS touch events, applies application-specific filtering criteria based on location information, and selectively suppresses or passes events to applications. This mediator approach enables fine-grained control without requiring modifications to the core OS touch event handling architecture.
Solution Approach 2:
The touch event processing is segmented into distinct filtering stages: (1) OS generates touch events, (2) system hook intercepts and filters events based on application-specific criteria, (3) filtered events are passed to target applications. This segmentation allows different applications to have different filtering rules applied independently, providing adaptability while maintaining a structured system architecture.
2Adaptability or versatility
If all OS touch events are reported to applications, then application functionality is improved, but processing efficiency deteriorates due to unnecessary event handling
Solution Approach 1:
The system hook extracts and suppresses unnecessary OS touch events before they reach the application layer. By filtering out events that do not meet application-specific criteria (such as emulated mouse events when real mouse events are sufficient), the system reduces the volume of data that applications must process, thereby improving processing efficiency while maintaining full functionality for relevant events.
Solution Approach 2:
Instead of reporting all OS touch events to every application (excessive action), the system hook applies partial filtering based on application-specific needs. Each application receives only the subset of events relevant to its functionality, eliminating redundant processing while ensuring that necessary events are not missed.
Data Source
AI summary
A graphical user interface is rendered on a display screen of a touch screen device. The display screen includes a display area for rendering images, and the graphical user interface of the application is rendered in a portion of the display area. Digital touch data is generated in response to user interactions with a touch-sensitive surface of the touch screen device. A module of an operating system residing on the touch screen device is used to convert the digital touch data into OS touch events. The OS touch events and application location information are received at a system hook. The application location information identifies the portion of the display area of the touch screen device in which the graphical user interface of the application is rendered. The system hook filters the OS touch events based on the application location information and provides the filtered OS touch events to the application.