Gesture API Function Calls for Scroll and Animation Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user interfaces on devices face challenges in effectively interpreting various user inputs for scrolling, gesturing, and animating operations due to limited display size, processing capability, and software limitations, leading to difficulties in providing intended functionality.
Innovation Solution
The implementation of application programming interfaces (APIs) that facilitate transferring function calls for scrolling, gesturing, and animating operations, including bounce, rubberbanding, scaling, and rotation transforms, as well as animation management through a single timer, to enhance user interface responsiveness and functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional user interface methods are used for scrolling and gesturing, then basic functionality is provided, but the device cannot effectively interpret various user inputs due to limited display size and processing capability
Solution Approach 1:
The user interface is segmented into distinct operational modes (scrolling mode, gesturing mode, animating mode) that can be independently activated and managed. Each mode has its own set of API functions and handling mechanisms, allowing the system to process different types of user inputs through specialized routines rather than a monolithic processing system, thereby overcoming software limitations.
Solution Approach 2:
An intermediary layer of API functions is introduced between the user input hardware and the core processing system. This intermediary layer provides standardized function calls for scrolling, gesturing, and animating operations, abstracting the complexity of input interpretation and enabling versatile user input handling without directly increasing core processing complexity.
2Adaptability or versatility
If multiple user input types are supported, then functionality is enhanced, but processing capability requirements increase
Solution Approach 1:
The system dynamically adjusts its processing requirements based on the active operation mode. When scrolling is detected, only scrolling-related processing is activated; when gesturing is detected, gesture processing routines are activated. This dynamic activation of processing pathways reduces overall power consumption while maintaining support for multiple input types.
Solution Approach 2:
The API uses parameter changes to control different operation modes. By passing specific parameters to function calls (e.g., scroll direction, gesture type, animation speed), the system can handle diverse user inputs by varying operational parameters rather than requiring separate processing systems for each input type, thereby reducing overall processing capability requirements.
3Ease of operation
If smooth animation operations are implemented, then user experience is improved, but software complexity increases
Solution Approach 1:
A universal animation API is created that handles multiple types of animated operations (scrolling, gesturing, transitions) through a single set of standardized functions. This universal interface provides smooth animation across different operations without requiring separate complex software systems for each animation type, thereby reducing overall software complexity while maintaining ease of operation.
Data Source
AI summary
A computer system with one or more display devices and one or more input devices displays a user interface of a software application that includes one or more views. The computer system detects a user input that comprises one or more input points directed to a respective view of the one or more views and, in response, transfers an input start event function call through an application programming interface to software associated with the respective view. The computer system detects a change in the user input, the change corresponding to input movement relative to the respective view and, in response, transfers an input changed event function call through the application programming interface to the software associated with the respective view. After transferring the input changed event function call, the computer system transfers an input end function call through the application programming interface to the software associated with the respective view.