Electronic devices with a graphical user interface for creating shortcuts

Abstract

1. Name of the product in this design: Electronic device with a graphical user interface for creating shortcuts. 2. Application of this design: This design is intended for use in an electronic device. 3. The key design features of this product are its graphical user interface content. 4. The picture or photo that best illustrates the key design points: Design 1 front view. 5. The electronic device described in this design is a conventional design, and the rear view, left view, right view, top view, and bottom view of Design 1-Design 6 are omitted. 6. Design 1 is designated as the basic design. 7. Purpose of the graphical user interface: This product design allows users to create shortcut commands through interactive operation, thereby increasing the diversity of button binding commands with the remote control. 8. Human-computer interaction methods of graphical user interface: User interaction operations include voice interaction commands, clicking text or icon buttons representing various programs, and operating via wired or wireless remote control. It should be noted that the "gray tiles" in the graphical user interface represent variable images, and the "XX" in the graphical user interface represent variable numbers or text. The graphical user interface (GUI) of the main view in Design 1 is the main page for remote control binding commands. When the user clicks any "X key binding" button in the GUI of the main view of Design 1, the GUI changes to the GUI shown in Design 1 Interface Change State Figure 1 when the user binds the remote control and commands for the first time. Clicking "OK" in the GUI of Design 1 Interface Change State Figure 1 then leads to the GUI of Design 1 Interface Change State Figure 2. Clicking "OK" in the GUI of Design 1 Interface Change State Figure 2 then leads to the GUI of Design 1 Interface Change State Figure 3. The user interacts by clicking the custom combination command bar in the graphical user interface (GUI) of Design 1 (Figure 3), which leads to the GUI of Design 1 (Figure 4). The user then enters a name in the command name field of the GUI of Design 1 (Figure 4). If the entered name is duplicated, the GUI of Design 1 (Figure 4) changes to the GUI of Design 1 (Figure 5). The user then re-enters a name in the command name field of the GUI of Design 1 (Figure 5). When the entered name is available, the GUI of Design 1 (Figure 5) changes back to the original Design 1 interface. The graphical user interface (GUI) in state change diagram 6 changes to state change diagram 7. After the user enters the execution command in the "Add Shortcut" section of the GUI in state change diagram 7, the GUI in state change diagram 8 changes to state change diagram 8. The user then enters the next execution command in the "Add Shortcut" section of the GUI in state change diagram 8. After executing the command, the graphical user interface in Design 1 interface change state diagram 8 changes to the graphical user interface in Design 1 interface change state diagram 9. The user clicks the "OK" button in the graphical user interface in Design 1 interface change state diagram 9 through interactive operation, and the graphical user interface in Design 1 interface change state diagram 9 changes to the graphical user interface in Design 1 interface change state diagram 10. The user clicks the "Save" button in the graphical user interface in Design 1 interface change state diagram 10 through interactive operation, and the graphical user interface in Design 1 interface change state diagram 10 changes to the graphical user interface in Design 1 interface change state diagram 11. In this graphical user interface, the created command can be added as a custom shortcut command. The graphical user interface (GUI) of Design 2's main view is the main page for remote control binding commands. When the user clicks any "X key binding" button in the GUI of Design 2's main view, the GUI changes to the GUI of Design 2's main view when binding the remote control and commands for the first time. Clicking "OK" in the GUI of Design 2's ... After the user enters the execution command in the "Shortcut" interface, the graphical user interface (GUI) in Design 2 (Figure 5) changes to the GUI in Design 2 (Figure 6). After the user enters the next execution command in the "Add Shortcut" section of the GUI in Design 2 (Figure 6), the GUI changes to the GUI in Design 2 (Figure 7). After the user enters the required execution command in the "Add Shortcut" section of the GUI in Design 2 (Figure 7), the GUI changes to the GUI in Design 2 (Figure 8). Clicking the "OK" button in the GUI in Design 2 (Figure 8) changes the GUI to the GUI in Design 2 (Figure 9). Clicking the "Save" button in the GUI in Design 2 (Figure 9) changes the GUI to the GUI in Design 2 (Figure 10). In this GUI, the created command can be added as a custom shortcut. The graphical user interface (GUI) of the main view in Design 3 is the main page for remote control binding commands. When the user clicks any "X key binding" button in the GUI of the main view in Design 3, the GUI changes to the GUI shown in Design 3 Interface Change State Figure 1 when the user first binds the remote control and commands. Clicking "OK" in Design 3 Interface Change State Figure 1 then leads to the GUI shown in Design 3 Interface Change State Figure 2. Clicking "OK" in Design 3 Interface Change State Figure 2 then leads to the GUI shown in Design 3 Interface Change State Figure 3. The user interface (GUI) features a customizable command bar, leading to the GUI in Figure 4 of the interface transition diagram. Users interact by entering a name in the command name field of Figure 4. If a name is already entered, the GUI changes to Figure 5. Users then re-enter a name in the command name field of Figure 5. When a name is available, the GUI changes to Figure 6. Users then interact by adding a shortcut in Figure 6. After the user enters the execution command in the "Shortcut Command" interface, the graphical user interface in Design 3 (Figure 6) changes to the graphical user interface in Design 3 (Figure 7). After the user enters the next execution command in the "Add Shortcut Command" section of the graphical user interface in Design 3 (Figure 7), the graphical user interface in Design 3 (Figure 8) changes to the graphical user interface in Design 3 (Figure 8). After the user enters the required execution command in the "Add Shortcut Command" section of the graphical user interface in Design 3 (Figure 8), the graphical user interface in Design 3 (Figure 9) changes to the graphical user interface in Design 3 (Figure 9). The user then selects the icon in Design 3 (Figure 9) through interactive operations. When the executable instructions created in the graphical user interface (GUI) are sorted, the GUI in Design 3, interface state diagram 9, changes to the GUI in Design 3, interface state diagram 10. After the user completes the sorting of the selected executable instructions through interactive operations in the GUI in Design 3, interface state diagram 10, and clicks the "OK" button in the GUI in Design 3, interface state diagram 10, the GUI in Design 3, interface state diagram 11 changes to the GUI in Design 3, interface state diagram 11. After the user clicks the "Save" button in the GUI in Design 3, interface state diagram 11, the GUI in Design 3, interface state diagram 12 changes to the GUI in Design 3, interface state diagram 12.Within this graphical user interface, created commands can be added as custom shortcuts. The graphical user interface (GUI) in Design 4's main view serves as the main page for remote control binding commands. When a user interacts by clicking any "X-key binding" button in the GUI of Design 4's main view, the GUI changes to the GUI shown in Design 4's interface change state diagram 1 when the user first binds the remote control and commands. Clicking "OK" in Design 4's interface change state diagram 1 then leads to the GUI in Design 4's interface change state diagram 2. Clicking "OK" again in Design 4's interface change state diagram 2 leads to the GUI in Design 4's interface change state diagram 3. Interoperability: Clicking the custom combination command bar in the graphical user interface (GUI) of Design 4 (Figure 3) allows the user to enter the GUI of Design 4 (Figure 4). The user enters a name in the command name field of the GUI of Design 4 (Figure 4). If no duplicate name is entered, the GUI of Design 4 (Figure 4) changes to the GUI of Design 4 (Figure 5). After the user enters the execution command in the "Add Shortcut" field of the GUI of Design 4 (Figure 5), the GUI of Design 4 (Figure 5) changes to the GUI of Design 4 (Figure 6). The user then... After the user enters the next execution command in the "Add Shortcut" section of the graphical user interface in Design 4 (Figure 6), the graphical user interface changes to the graphical user interface in Design 4 (Figure 7). After the user enters the desired execution command in the "Add Shortcut" section of the graphical user interface in Design 4 (Figure 7), the graphical user interface changes to the graphical user interface in Design 4 (Figure 8). When the user selects and sorts the created execution commands in the graphical user interface in Design 4 (Figure 8), the graphical user interface in Design 4 (Figure 8) changes to... The graphical user interface (GUI) in Design 4 (Figure 9) changes state. After the user completes the sorting of the selected execution instructions through interactive operations in the GUI of Design 4 (Figure 9), clicking the "OK" button in the GUI of Design 4 (Figure 9) changes the GUI to the GUI of Design 4 (Figure 10). The user then clicks the "Save" button in the GUI of Design 4 (Figure 10) changes the GUI to the GUI of Design 4 (Figure 11). In this GUI, the created instructions can be added as custom shortcuts. The graphical user interface (GUI) in Design 5's main view serves as the main page for remote control binding commands. When a user clicks any "X-key binding" button in the GUI of Design 5's main view, the GUI changes to the GUI shown in Design 5's interface change state diagram 1 upon the first time the user binds the remote control and commands. Clicking "OK" in Design 5's interface change state diagram 1 then leads to the GUI in Design 5's interface change state diagram 2. Clicking "OK" again in Design 5's interface change state diagram 2 leads to the GUI in Design 5's interface change state diagram 3. The user then clicks... The user interface (GUI) features a customizable command bar, leading to the GUI shown in Figure 4 of the interface transition diagram. Users interact by entering a name in the command name field of Figure 4. If a name is already entered, the GUI changes to Figure 5. Users then re-enter a name in the command name field of Figure 5. When a name is available, the GUI changes to Figure 6. Users then interact with the "Add Quick" function in Figure 6. After the user enters the execution command in the "Shortcut Command" interface, the graphical user interface in Design 5 (Figure 6) changes to the graphical user interface in Design 5 (Figure 7). After the user enters the next execution command in the "Add Shortcut Command" section of the graphical user interface in Design 5 (Figure 7), the graphical user interface in Design 5 (Figure 8) changes to the graphical user interface in Design 5 (Figure 8). After the user enters the required execution command in the "Add Shortcut Command" section of the graphical user interface in Design 5 (Figure 8), the graphical user interface in Design 5 (Figure 9) changes to the graphical user interface in Design 5 (Figure 9). The user then selects the icon in Design 5 (Figure 9) through interactive operations. When an executable command created in the graphical user interface (GUI) is deleted, the GUI in Design 5 (Figure 9) changes to the GUI in Design 5 (Figure 10). After the user completes the deletion of the selected executable command through interactive operation in the GUI in Design 5 (Figure 10), clicking the "OK" button in the GUI in Design 5 (Figure 10) changes the GUI in Design 5 (Figure 11). The user then clicks the "Save" button in the GUI in Design 5 (Figure 11), and the GUI in Design 5 (Figure 12) changes.Within this graphical user interface, created commands can be added as custom shortcuts. The graphical user interface (GUI) in Design 6's main view serves as the main page for remote control binding commands. When a user interacts by clicking any "X key binding" button in the GUI of Design 6's main view, the GUI changes to the GUI shown in Design 6's interface change state diagram 1 when the user first binds the remote control and commands. Clicking "OK" in the GUI of Design 6's interface change state diagram 1 then leads to the GUI of Design 6's interface change state diagram 2. Clicking "OK" in the GUI of Design 6's interface change state diagram 2 then leads to the GUI of Design 6's interface change state diagram 3. Interoperability: Clicking the custom combination command bar in the graphical user interface (GUI) of Design 6 (Figure 3) transitions to the GUI of Design 6 (Figure 4). The user enters a name in the command name field of the GUI of Design 6 (Figure 4). If no duplicate name is entered, the GUI of Design 6 (Figure 4) transitions to the GUI of Design 6 (Figure 5). After the user enters the execution command in the "Add Shortcut" field of the GUI of Design 6 (Figure 5), the GUI of Design 6 (Figure 5) transitions to the GUI of Design 6 (Figure 6) (Figure 6). After the user enters the next execution command in the "Add Shortcut" section of the graphical user interface in Design 6 (as shown in Figure 6), the graphical user interface changes to the one in Design 6 (Figure 7). After the user enters the desired execution command in the "Add Shortcut" section of the graphical user interface in Design 6 (Figure 7), the graphical user interface changes to the one in Design 6 (Figure 8). When the user selects and deletes a created execution command in the graphical user interface of Design 6 (Figure 8), the graphical user interface changes to the one in Design 6 (Figure 8). The graphical user interface (GUI) in Figure 9 (interface state change diagram) is designed as follows: After the user completes the deletion of the selected execution command through interactive operation in the GUI of Figure 9 (interface state change diagram), and clicks the "OK" button in the GUI of Figure 9 (interface state change diagram), the GUI of Figure 9 (interface state change diagram) changes to the GUI of Figure 10 (interface state change diagram). After the user clicks the "Save" button in the GUI of Figure 10 (interface state change diagram), the GUI of Figure 10 (interface state change diagram) changes to the GUI of Figure 11 (interface state change diagram). In this GUI, the created command can be added as a custom shortcut command.

Images