Touch Event Processing via Segmented View Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-touch enabled devices face challenges in recognizing single and multiple touch events, leading to increased complexity and cost in software development, as well as difficulties in converting single-pointing device software to multi-point or multi-touch enabled devices.
Innovation Solution
The solution involves configuring each view within a window as either a multi-touch or single-touch view, and setting flags such as the multi-touch flag and exclusive touch flag to control how touch events are processed, allowing for selective recognition and handling of touch events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multi-touch enabled devices process all touch events simultaneously, then touch recognition capability is improved, but software complexity increases
Solution Approach 1:
The patent segments the display into multiple independent views, each capable of being configured as single-touch or multi-touch. This allows the system to process multiple touch events simultaneously in different views without requiring all software elements to handle the full complexity of multi-touch processing, thereby improving touch recognition capability while managing software complexity through division of labor
Solution Approach 2:
The patent introduces dynamic configuration flags (multi-touch flag and exclusive touch flag) that allow views to switch between single-touch and multi-touch modes based on runtime conditions. This dynamic adaptability enables the system to optimize processing complexity on a per-view basis while maintaining overall multi-touch capability across the display
2Adaptability or versatility
If existing single-pointing device software is converted to multi-touch, then device functionality is improved, but conversion difficulty increases
Solution Approach 1:
The patent creates a universal view configuration system where views can operate in multiple modes (single-touch or multi-touch) based on flags. This universality allows existing single-touch software to run unchanged in single-touch views while new multi-touch functionality is enabled in dedicated views, facilitating easier conversion of existing software to multi-touch devices without requiring complete rewrites
Solution Approach 2:
The patent introduces configuration flags as intermediary control mechanisms between the multi-touch hardware and software applications. These flags act as a translation layer that allows existing single-pointing device software to interface with multi-touch capabilities through a standardized configuration interface, reducing conversion difficulty by providing a clear migration path
3Productivity
If multiple software elements process touch events independently, then processing efficiency is improved, but coordination difficulty increases
Solution Approach 1:
The patent segments touch event processing into independent view-based units, where each view with appropriate flags can process touches independently. This segmentation improves processing efficiency by allowing parallel handling of touches in different views while reducing coordination difficulty through clearly defined boundaries and independent configuration options for each view
4Measurement precision
If all views on display are configured as multi-touch views, then touch event recognition is improved, but resource consumption increases
Solution Approach 1:
The patent applies local quality by allowing individual views to be configured with different touch processing capabilities based on their specific needs. Only views that require multi-touch processing are configured as such, while other views maintain single-touch configuration. This selective approach improves touch event recognition where needed while minimizing resource consumption in views that do not require advanced multi-touch functionality
Data Source
AI summary
A computer system detects an input that is directed, when the input starts, to a location within a view in a user interface, and consequentially: sends to a software element associated with the view a plurality of input events, wherein each input event comprises a data structure including a phase field that describes a state of the input at a respective time, and the phase field of one of the plurality of input events is set to an input phase began value indicating that the input is new; determines whether or not the input should be ignored by the electronic device; and, in accordance with a determination that the input should be ignored by the electronic device, includes in the plurality of input events an input event whose phase field is set to an input phase cancel value indicating that the input has been cancelled.