Main body of a content review graphical user interface of an electronic device

Abstract

1. Name of the product in this design: The main body of the graphical user interface for content review of electronic devices. 2. Purpose of this design: An electronic device. 3. The key design features of this product are the graphical user interface in the electronic device for which protection is sought. 4. The image or photograph that best illustrates the key design points: Design 2 Change State Diagram 4. 5. Design 2 is designated as the basic design. 6. Purpose of the graphical user interface: The graphical user interface is used for content review. The part of the graphical user interface that requests protection is the content review result display area of ​​the content review graphical user interface. 7. Human-computer interaction method of graphical user interface: In Design 1, users can save the content review results by clicking the "Save" button. In Design 2, when the user hovers the mouse over the button to the left below "Reason for Ignore" in the main view of Design 2, the graphical user interface changes from the main view of Design 2 to Design 2 Change State Diagram 1, displaying the "Ignore this risk" overlay. When the user clicks the corresponding button on the "Ignore this risk" overlay, the graphical user interface changes from Design 2 Change State Diagram 1 to Design 2 Change State Diagram 2, displaying an input box. By entering the reason for ignoring in the input box and clicking the "OK" button, the graphical user interface changes from Design 2 Change State Diagram 2 to Design 2 Change State Diagram 3, displaying the reason for ignoring. When the user hovers the mouse over the button to the left below "Reason for Recall" in Design 2 Change State Diagram 3, the graphical user interface changes from Design 2 Change State Diagram 3 to Design 2 Change State Diagram 4 to display the "Undo Ignore" overlay. When the user clicks the corresponding button in the "Undo Ignore" overlay, the graphical user interface changes from Design 2 Change State Diagram 4 to Design 2 Change State Diagram 5 to display the input box. By entering the reason for the undo and clicking the "OK" button, the graphical user interface changes from Design 2 Change State Diagram 5 to Design 2 Change State Diagram 6 to display the reason for the undo. In Design 3, when the user hovers the mouse over the button to the left below "Reason for Ignore" in the main view of Design 3, the graphical user interface changes from the main view of Design 3 to Design 3 Change State Diagram 1 to display the "Ignore this risk" overlay. When the user clicks the corresponding button in the "Ignore this risk" overlay, the graphical user interface changes from Design 3 Change State Diagram 1 to Design 3 Change State Diagram 2 to display the input box. By entering the reason for ignoring in the input box and clicking the "OK" button, the graphical user interface changes from Design 3 Change State Diagram 2 to Design 3 Change State Diagram 3 to display the reason for ignoring. In Design 4, when the user operates the mouse to hover over the button on the right side below "Prompt Reason" in the main view of Design 4, the graphical user interface changes from the main view of Design 4 to the changed state view of Design 4 to show the floating layer of "Log Record". In Design 5, when the user operates the mouse to hover over the button on the right side below "Prompt Reason" in the main view of Design 5, the graphical user interface changes from the main view of Design 5 to the changed state view of Design 5 to show the floating layer of "Log Record". In Design 6, when the user operates the mouse to hover over the lower right corner of the card in the main view of Design 6, the graphical user interface changes from the main view of Design 6 to the changed state view 1 of Design 6 to show the feedback button, and when the user clicks the feedback button in the changed state view 1 of Design 6, the graphical user interface changes from the changed state view 1 of Design 6 to the changed state view 2 of Design 6 to show the feedback information. 8. Other situations needing to be explained Other explanations: The part of the graphical user interface shown by the dashed line in each view of Design 1 to Design 6 does not constitute the part required to be protected by the appearance design.

Images