Static Widget Rendering for Lower Memory and Power Use
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Electronic devices with numerous widget subcomponents experience increased memory occupation and power consumption due to continuous running and refreshing of these components, leading to inefficient resource usage.
Innovation Solution
A widget display method that renders a plurality of components into a static image, reducing the need for continuous component refresh and rendering, thereby minimizing memory usage and power consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple subcomponents are continuously rendered and refreshed in a widget, then the widget functionality and interaction are maintained, but memory occupation and power consumption increase
Solution Approach 1:
The patent implements periodic rendering by capturing widget components at specific intervals (e.g., when data changes) rather than continuous rendering. The captured components are stored as images and displayed until the next capture event, creating a periodic action pattern that reduces power consumption while maintaining widget functionality.
Solution Approach 2:
The patent creates image copies of widget components instead of continuously rendering the actual components. These image copies (bitmaps) are stored in memory and displayed in place of the original components, reducing the computational overhead and power consumption associated with continuous component rendering and refreshing.
2Reliability
If multiple subcomponents are continuously rendered and refreshed in a widget, then the widget functionality and interaction are maintained, but memory occupation increases
Solution Approach 1:
The patent creates image copies of widget components instead of continuously rendering the actual components. These image copies (bitmaps) are stored in memory and displayed in place of the original components, reducing the computational overhead and power consumption associated with continuous component rendering and refreshing.
Solution Approach 2:
The patent implements periodic rendering by capturing widget components at specific intervals (e.g., when data changes) rather than continuous rendering. The captured components are stored as images and displayed until the next capture event, creating a periodic action pattern that reduces power consumption while maintaining widget functionality.
3Use of energy by moving object
If a static image is used to replace multiple rendered components, then memory usage and power consumption are reduced, but interaction functionality must be preserved
Solution Approach 1:
The patent segments the widget into multiple independent components, each with its own image capture and interaction handling. Each component can be independently rendered, captured as an image, and have its interaction areas defined separately, allowing the static image to maintain full interaction functionality while reducing power consumption.
Solution Approach 2:
The patent introduces interaction area definitions as an intermediary layer between the static image display and the underlying component functionality. By defining specific areas in the static image that correspond to interactive elements, the system preserves touch and click functionality without requiring continuous rendering of the actual components.
Data Source
AI summary
A widget display method includes receiving a first trigger operation of a user, where the first trigger operation is used to add a first static widget, and the first static widget corresponds to a plurality of components. The widget display method further includes rendering the plurality of components corresponding to the first static widget, and generating and displaying a first static image based on the plurality of rendered components, where the first static image is used to display first resource content corresponding to the first static widget.


