Screen Switching Control for Web-Native Display Transitions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multifunction peripherals (MFPs), the transition from a web screen to a native screen based on user operations can lead to decreased operability due to unintended display of previously operated content, especially when users intend to access different screens like status or job history displays.
Innovation Solution
An apparatus with a control unit, notification unit, determination unit, and screen switching unit is configured to display either a web screen or native screen, where the determination unit assesses user operations and switches to the native screen only when the current display is a web screen, maintaining the current display if it is not a web screen.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the web application changes the screen from web screen to native screen based on user operations, then the web application can efficiently utilize the information processing apparatus functions, but the operability decreases when users intend to access other screens like status or job history displays
Solution Approach 1:
The determination unit acts as an intermediary between the web application and the screen switching mechanism. It receives screen change requests from the web application, checks whether the current display is a web screen, and only permits switching to native screens when appropriate. This intermediary layer prevents unintended screen transitions while allowing efficient web application operation.
Solution Approach 2:
The system implements feedback by having the determination unit continuously monitor the current screen state and provide information to the screen switching unit. This feedback mechanism ensures that screen transitions occur only when the current display is indeed a web screen, preventing erroneous switches to native screens when users intend to access other functional screens.
2Reliability
If the information processing apparatus stores all menu data locally for native screen display, then the apparatus can operate independently, but the device complexity and memory requirements increase
Solution Approach 1:
The screen data is segmented into two types: web screens stored on the web server and native screens stored locally in the information processing apparatus. This segmentation allows the system to leverage external storage for web interface data while maintaining essential native screens locally, reducing overall local storage requirements while preserving independent operation capability.
Solution Approach 2:
The information processing apparatus is designed with multi-functionality, supporting both web screen display (requiring external data) and native screen display (using local data). This universal design allows the same hardware to serve multiple purposes, reducing the need for dedicated storage for each screen type while maintaining operational independence.
Data Source
AI summary
An apparatus determines whether a current display is a web screen, when a user operation performed via the web screen indicates a display of a native screen and when a web server instructs the apparatus to display the native screen. The apparatus switches the current display to the native screen when the current display is the web screen, and maintains the current display when the current display is not the web screen.