Polygon-Based Hit Testing for Curve-Based UI Elements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional computing systems face difficulties in accurately defining user interface element edges when translating between different software styles, leading to inconsistencies in hit-testing processes across various applications.
Innovation Solution
A translation API that converts vector-based user interface elements into polygon-based representations, allowing for accurate hit-testing by tessellating shapes into polygons, padding lines, creating cuts for hollow areas, and identifying three-dimensional boundaries, thereby enabling precise selection of user interface elements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Shape
If curve-based user interface element boundaries are used, then visual quality and design flexibility are improved, but hit-testing accuracy and data translation compatibility deteriorate
Solution Approach 1:
The patent creates polygon-based copies of curve-based user interface elements. The translation API generates polygon representations that replicate the visual and functional properties of the original curve-based elements, enabling accurate hit-testing while preserving the design flexibility of curve-based boundaries. These polygon copies serve as intermediaries that maintain fidelity to the original curves while being compatible with polygon-based hit-testing algorithms.
Solution Approach 2:
The patent transforms the mathematical representation of user interface elements from curve-based parameters to polygon-based parameters. By changing the fundamental parameter structure from continuous curve definitions to discrete polygon vertex coordinates, the system enables precise hit-testing while maintaining the ability to represent complex shapes. This parameter transformation allows the same visual element to be processed differently for rendering versus hit-testing purposes.
2Adaptability or versatility
If curve-based boundaries are used in one application, then design flexibility is improved, but data translation to polygon-based systems deteriorates
Solution Approach 1:
The translation API serves as an intermediary layer between curve-based and polygon-based systems. It receives curve-based user interface element definitions from applications designed with curve-based boundaries and translates them into polygon-based representations that can be processed by polygon-based systems. This intermediary translation process preserves the essential geometric and topological information while converting between different representation formats, preventing data loss during translation.
Solution Approach 2:
The patent creates a universal translation mechanism that handles multiple representation formats. The translation API can process various types of curve-based boundaries (lines, arcs, Bezier curves) and convert them all to polygon representations, making the system universally compatible with different design approaches. This multi-functional translation capability ensures that data can be exchanged between curve-based and polygon-based systems without loss of essential information.
3Measurement precision
If polygon-based representations are created from curves, then hit-testing accuracy is improved, but computational complexity increases
Solution Approach 1:
The patent segments curve-based user interface elements into discrete polygon representations. By dividing continuous curves into a finite number of linear segments (polygon edges), the system transforms an infinitely complex mathematical problem into a finite, computationally manageable one. This segmentation maintains sufficient visual and functional accuracy while dramatically reducing the computational complexity of hit-testing operations, as polygon-polygon intersection tests are simpler than curve-curve intersection tests.
Data Source
AI summary
Upon receiving an input comprising an area of a user interface, a user interface element associated with the area of the user interface may be identified and a polygon-based representation of the at least one user interface element may be created. If the input is determined to comprise a selection of the user interface element according to the polygon-based representation, an operation associated with the user interface element may be performed.