Electronic device with 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 Design 1'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 1's main view, if it's not the first time the user is binding the remote control and commands, the GUI of Design 1's main view changes to the GUI of Design 1's interface change state diagram 1. The user then clicks the custom combination command bar in the GUI of Design 1's interface change state diagram 1 to enter the GUI of Design 1's interface change state diagram 2. The user then enters a name in the command name field of the GUI of Design 1's interface change state diagram 2. If the entered name is duplicated, the GUI of Design 1's interface change state diagram 2 changes to the GUI of Design 1's interface change state diagram 3. The user then re-enters a name in the command name field of the GUI of Design 1's interface change state diagram 3. When the entered name is usable, the GUI of Design 1's interface change state diagram 3 changes to the GUI of Design 1's interface change state diagram 4. The user then executes the "Add Shortcut Command" input in the GUI of Design 1's interface change state diagram 4. After receiving the command, the graphical user interface (GUI) in Design 1, as shown in Figure 4, changes to the GUI in Design 1, as shown in Figure 5. After the user enters the next command in the "Add Shortcut" section of the GUI in Design 1, the GUI in Design 1, as shown in Figure 5, changes to the GUI in Design 1, as shown in Figure 6. After the user enters the required command in the "Add Shortcut" section of the GUI in Design 1, as shown in Figure 6, the GUI in Design 1, as shown in Figure 7, changes to the GUI in Design 1, as shown in Figure 7. The user then clicks the "OK" button in the GUI in Design 1, as shown in Figure 7, as shown in Figure 8, and finally clicks the "Save" button in the GUI in Design 1, as shown in Figure 8, as shown in Figure 9. In this GUI, the created command can be added as a custom shortcut. The graphical user interface (GUI) of the main view in Design 2 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 2, if it is not the first time the user is binding the remote control and commands, the GUI of the main view in Design 2 changes to the GUI of Design 2 interface change state diagram 1. The user clicks the custom combination command bar in the GUI of Design 2 interface change state diagram 1 to enter the GUI of Design 2 interface change state diagram 2. The user enters a name in the command name field in the GUI of Design 2 interface change state diagram 2. If the entered name is unique, the GUI of Design 2 interface change state diagram 2 changes to the GUI of Design 2 interface change state diagram 3. After the user enters the execution command in the "Add Shortcut Command" field in the GUI of Design 2 interface change state diagram 3, the GUI of Design 2 interface change state diagram 3 changes to the GUI of Design 2 interface change state diagram 4. After the user enters the next execution command in the "Add Shortcut" section of the graphical user interface in Design 2 (Figure 4), the graphical user interface changes to the graphical user interface in Design 2 (Figure 5). After the user enters the required execution command in the "Add Shortcut" section of the graphical user interface in Design 2 (Figure 5), the graphical user interface changes to the graphical user interface in Design 2 (Figure 6). After the user clicks the "OK" button in the graphical user interface in Design 2 (Figure 6), the graphical user interface changes to the graphical user interface in Design 2 (Figure 7). After the user clicks the "Save" button in the graphical user interface in Design 2 (Figure 7), the graphical user interface changes to the graphical user interface in Design 2 (Figure 8). In this graphical user interface, the created command can be added as a custom shortcut. The graphical user interface (GUI) in Design 3'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 3's main view, the GUI changes to the GUI shown in Design 3's interface state diagram 1 when the user first binds the remote control and commands. The user then interacts by clicking the custom combination command bar in Design 3's interface state diagram 1, entering the GUI in Design 3's interface state diagram 2. The user then interacts by entering a name in the command name field of the GUI in Design 3's interface state diagram 2. If the entered name is duplicated, the GUI will display a different name. The graphical user interface (GUI) in state 2 changes to the GUI in state 3 of design interface 3. The user re-enters a name in the command name field of the GUI in state 3 of design interface 3 through interactive operations. When the entered name is available, the GUI in state 3 of design interface 3 changes to the GUI in state 4 of design interface 3. After the user enters the execution command in the "Add Shortcut" field of the GUI in state 4 of design interface 3 through interactive operations, the GUI in state 4 of design interface 3 changes to the GUI in state 5 of design interface 3. The user then interacts with the GUI in state 3... After the user enters the next execution command in the "Add Shortcut" section of the graphical user interface in Design 3 (State 5), the graphical user interface changes to the graphical user interface in Design 3 (State 6). After the user enters the required execution command in the "Add Shortcut" section of the graphical user interface in Design 3 (State 6), the graphical user interface changes to the graphical user interface in Design 3 (State 7). When the user selects and sorts the created execution commands in the graphical user interface in Design 3 (State 7), the graphical user interface in Design 3 (State 7) changes to the Design 3 interface. The graphical user interface (GUI) in Figure 8 changes state. After the user completes the sorting of the selected execution instructions through interactive operations in the GUI of Figure 8, they click the "OK" button in the GUI of Figure 8, and the GUI of Figure 8 changes to the GUI of Figure 9. The user then clicks the "Save" button in the GUI of Figure 9, and the GUI of Figure 9 changes to the GUI of Figure 10. In this GUI, the created instructions 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 clicks 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 transition state diagram 1 when the user first binds the remote control and commands. Clicking the custom combination command bar in Design 4's interface transition state diagram 1 leads to the GUI shown in Design 4's interface transition state diagram 2. Entering a name in the command name field in Design 4's interface transition state diagram 2, and then changing to the GUI shown in Design 4's interface transition state diagram 3 when no duplicate names are entered, leads to the GUI shown in Design 4's interface transition state diagram 3. After entering the execution command in the "Add Shortcut Command" field in Design 4's interface transition state diagram 3, the GUI changes to the GUI shown in Design 4's interface transition state diagram 4. Finally, after entering the next execution command in the "Add Shortcut Command" field in Design 4's interface transition state diagram 4, the GUI changes to the GUI shown in Design 4's interface transition state diagram 4. The graphical user interface (GUI) changes to the GUI shown in Figure 5 of the interface change diagram. After the user interacts with the interface and enters the required execution command in the "Add Shortcut" section of the GUI in Figure 5, the GUI changes to the GUI in Figure 6. When the user selects and sorts the created execution commands in the GUI in Figure 6, the GUI changes to the GUI in Figure 7. After the user sorts the selected execution commands in the GUI in Figure 7, they click the "OK" button, and the GUI changes to the GUI in Figure 8. When the user clicks the "Save" button, the GUI changes to the GUI in Figure 9. In this GUI, the created command can be added as a custom shortcut. 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. The user then clicks the custom combination command bar in Design 5's interface change state diagram 1 to enter the GUI of Design 5's interface change state diagram 2. The user then enters a name in the command name field of the GUI of Design 5's interface change state diagram 2. If the entered name is duplicated, the Design 5 interface... The graphical user interface (GUI) in state change diagram 2 changes to the GUI in state change diagram 3 of design 5. The user re-enters a name in the command name field of the GUI in state change diagram 3 of design 5 through interactive operations. When the entered name is usable, the GUI in state change diagram 3 of design 5 changes to the GUI in state change diagram 4 of design 5. After the user enters the execution command in the "Add Shortcut" section of the GUI in state change diagram 4 of design 5, the GUI in state change diagram 4 of design 5 changes to the GUI in state change diagram 5 of design 5. The user then interacts with the GUI in state change diagram 5... After the user enters the next execution command in the "Add Shortcut" section of the graphical user interface in Design 5 (State 5), the graphical user interface changes to the graphical user interface in Design 5 (State 6). After the user enters the required execution command in the "Add Shortcut" section of the graphical user interface in Design 5 (State 6), the graphical user interface changes to the graphical user interface in Design 5 (State 7). When the user selects and deletes a created execution command in the graphical user interface in Design 5 (State 7), the graphical user interface in Design 5 (State 7) changes to the Design 5 interface... The graphical user interface (GUI) in Figure 8 changes state. After the user completes the deletion of the selected execution command through interactive operation in the GUI of Figure 8, they click the "OK" button in the GUI of Figure 8, and the GUI of Figure 8 changes to the GUI of Figure 9. The user then clicks the "Save" button in the GUI of Figure 9, and the GUI of Figure 9 changes to the GUI of Figure 10. In this GUI, the created command can be added as a custom shortcut command. 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 state diagram 1 when the user first binds the remote control and commands. Clicking the custom combination command bar in Design 6's interface state diagram 1 leads to the GUI shown in Design 6's interface state diagram 2. Entering a name in the command name field in Design 6's interface state diagram 2, and then changing to the GUI shown in Design 6's interface state diagram 3 when no duplicate names are entered, leads to the GUI shown in Design 6's interface state diagram 3. After entering the execution command in the "Add Shortcut Command" field in Design 6's interface state diagram 3, the GUI changes to the GUI shown in Design 6's interface state diagram 4. Finally, after entering the next execution command in the "Add Shortcut Command" field in Design 6's interface state diagram 4, the GUI changes to the GUI shown in Design 6's interface state diagram 4. The graphical user interface (GUI) changes to the GUI of Design 6 (Figure 5). After the user interacts with the GUI in Figure 5 and enters the desired command in the "Add Shortcut" section, the GUI changes to the GUI of Design 6 (Figure 6). When the user selects and deletes the created command in the GUI of Design 6 (Figure 6), the GUI changes to the GUI of Design 6 (Figure 7). After deleting the selected command in the GUI of Design 6 (Figure 7), the user clicks the "OK" button in the GUI of Design 6 (Figure 7), and the GUI changes to the GUI of Design 6 (Figure 8). When the user clicks the "Save" button in the GUI of Design 6 (Figure 8), the GUI changes to the GUI of Design 6 (Figure 9). In this GUI, the created command can be added as a custom shortcut.

Images