Touch Gesture Recognizers for Multi-View Event Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user interface technologies require complex software and logic revisions for recognizing and responding to touch-based gestures, especially when applications are updated or new applications are added, leading to inefficiencies and additional steps in interacting with hidden applications.
Innovation Solution
A comprehensive framework for recognizing touch-based gestures and events that adapts easily to various contexts and modes, allowing seamless interaction with hidden applications without displaying them, using gesture recognizers and event handlers to process touch inputs efficiently across multiple software applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional touch gesture recognition systems are used, then gesture recognition functionality is provided, but software complexity increases and requires revision with each application update
Solution Approach 1:
The system segments gesture recognition into independent gesture recognizers that can be individually configured and updated. Each gesture recognizer is a discrete component that processes specific gesture patterns, allowing the system to maintain complexity locally rather than globally. This segmentation enables flexible adaptation without requiring system-wide software revisions.
Solution Approach 2:
The patent implements a universal gesture recognition framework that serves multiple applications and contexts through a common set of gesture recognizers. This multi-functional architecture allows the same gesture recognition infrastructure to support various applications, reducing overall software complexity while maintaining adaptability across different use cases.
2Adaptability or versatility
If comprehensive gesture recognition is implemented across all applications, then gesture functionality is enhanced, but software maintenance burden increases
Solution Approach 1:
The system enables applications to self-configure gesture recognition by selectively registering gesture recognizers based on their specific needs. Each application can independently manage its gesture recognition requirements without requiring centralized configuration or maintenance intervention, reducing the software maintenance burden while maintaining comprehensive gesture coverage.
Solution Approach 2:
The patent implements preliminary configuration of gesture recognizers that are pre-configured with gesture patterns and recognition logic. This preliminary action allows gesture recognition to be readily available when applications are added or updated, eliminating the need for complex maintenance operations and reducing the software maintenance burden.
3Ease of operation
If touch inputs are delivered to multiple applications simultaneously, then interaction flexibility is improved, but processing efficiency decreases
Solution Approach 1:
The system dynamically routes touch inputs to appropriate applications based on the current context, active application state, and gesture pattern. This dynamic routing mechanism maintains interaction flexibility by allowing multiple applications to receive relevant inputs while optimizing processing efficiency by directing each input to the most appropriate handler, avoiding unnecessary processing overhead.
Data Source
Figure 1A~1B
Figure 1C
Figure 2
AI summary
A method includes displaying one or more views of a view hierarchy, and executing software elements associated with a particular view. Each particular view includes event recognizers. Each event recognizer has one or more event definitions, and an event handler that specifies an action for a target and is configured to send the action to the target in response to event recognition. The method includes detecting a sequence of sub-events, and identifying one of the views of the view hierarchy as a hit view that establishes which views are actively involved views. The method includes delivering a respective sub-event to event recognizers for each actively involved view. A respective event recognizer has event definitions, and one of the event definitions is selected based on the internal state. The respective event recognizer processes the respective subevent prior to processing a next sub-event in the sequence of sub-events