Virtual Input Mechanism for Non-Touch Application Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless devices with touch interfaces face challenges in executing non-touch applications, as they lack the necessary input mechanisms, leading to compatibility issues and limited functionality.
Innovation Solution
A computer-implemented method and system that dynamically generates virtual input mechanisms for non-touch applications by parsing application code to determine if key or touch inputs are required, allowing the device to support both types of inputs and enabling execution on touch-interface-only devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a wireless device uses a touch interface only, then the device structure is simplified and manufacturing cost is reduced, but non-touch applications cannot be executed due to lack of key input support
Solution Approach 1:
A virtual machine is introduced as an intermediary layer between the touch interface and non-touch applications. The virtual machine intercepts touch input events, translates them into virtual key press events, and delivers them to applications that expect traditional key inputs. This mediator enables compatibility without requiring physical key hardware.
Solution Approach 2:
The patent replaces the mechanical key input system with a software-based virtual key mechanism. Instead of using physical keys, the system uses software-generated virtual key events that simulate traditional keyboard input through the virtual machine's event translation layer.
2Adaptability or versatility
If virtual input mechanisms are dynamically generated for non-touch applications, then application execution capability is improved, but code parsing and metadata processing increase device complexity
Solution Approach 1:
The system performs preliminary analysis of application code during installation or first execution to identify whether an application requires virtual input mechanisms. Metadata is extracted and stored in advance, so when the application runs, the virtual machine can quickly retrieve the pre-analyzed information without re-parsing the entire codebase.
Solution Approach 2:
The virtual machine automatically detects whether an application needs virtual input support by analyzing its code characteristics and metadata, without requiring manual configuration or user input. The system self-determines the appropriate input mechanism based on the application's inherent properties.
3Measurement precision
If the system parses application code to identify input requirements, then input mechanism selection accuracy is improved, but processing time and computational resources increase
Solution Approach 1:
Application code parsing is performed in advance during installation or first launch, with results cached in metadata. This preliminary action eliminates the need for repeated parsing during subsequent executions, significantly reducing runtime computational overhead while maintaining accurate detection.
Solution Approach 2:
The system extracts only the essential metadata information from the full application codebase rather than processing the entire code. By identifying and storing only the critical input requirement indicators, the system achieves accurate detection with minimal processing time and computational resources.
Data Source
AI summary
A computer-implemented method, computer-readable media, and wireless device that automatically determines whether an application requires a virtual input mechanism are provided. The wireless device includes a virtual machine and database. The virtual machine executes the application and parses code associated with the application to determine whether a virtual input mechanism is necessary. The database stores metadata that indicates whether the type of input needed for the application is touch or key.