Historical recording method, device and equipment based on large-screen Kanban and storage medium
By introducing a history recording mechanism in the design of large-screen kanbans, recording and displaying the historical status of users' operations, the problem of inefficient adjustment caused by operational errors is solved, and more efficient and accurate design adjustments are achieved.
Patent Information
- Application Number
- CN202510161267.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-13
- Publication Date
- 2025-06-13
AI Technical Summary
In the process of designing large-screen kanbans, users are prone to low adjustment efficiency due to operational errors, and lack of an effective historical record mechanism, resulting in users relying on memory and traceability operation status.
A history recording method based on a large-screen kanban is provided. By receiving user operation instructions, the relevant information of the pending component is stored in a back stack list set or a forward back stack list set, and the list set is updated when forward or back commands are received to display the historical operation status.
This method allows the user to quickly locate any historical state by recording and displaying the user's operation history in detail, without relying on memory, significantly improving the efficiency of adjustment and reducing operational errors caused by memory blur or omission.
Smart Images
Figure CN120144028A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of user interface control, and particularly to a historical record method, device, equipment and storage medium based on a large-screen dashboard. Background Art
[0002] In the application scenario of visualizing a large-screen design dashboard, users usually need to complete the final design layout through a series of complex operations. These operations include, but are not limited to, adding, moving, deleting, copying, and pasting various visual components (such as charts, text boxes, pictures, etc.).
[0003] Since the design process often cannot be completed in one step but requires multiple adjustments and layouts, during the design process, users are prone to make operational mistakes.
[0004] When an operational mistake occurs and the user wants to know what functions were operated in the previous steps and whether they need to go back to the previous step, they can only rely on memory to readjust, which results in relatively low adjustment efficiency. Summary of the Invention
[0005] Embodiments of this application provide a historical record method, device, equipment and storage medium based on a large-screen dashboard, aiming to solve the problem of relatively low adjustment efficiency caused by users having to rely on memory to readjust.
[0006] In a first aspect, embodiments of this application provide a historical record method based on a large-screen dashboard. The method includes:
[0007] Receiving an operation instruction from a user for a component to be processed in the large-screen dashboard;
[0008] Based on the type of the operation instruction, storing relevant information of the component to be processed into a preset backward stack list set or forward stack list set;
[0009] When receiving a forward instruction or a backward instruction from the user, updating the preset backward stack list set and forward stack list set, and displaying based on the data in the updated backward stack list set.
[0010] A further technical solution thereof is that when receiving a forward instruction or a backward instruction from the user, updating the preset backward stack list set and / or forward stack list set includes:
[0011] When receiving a backward instruction from the user, determining whether there is data in the backward stack list set;
[0012] If there is data in the back stack list set, remove the target data at the last position in the back stack list set, and add the removed target data to the last position in the forward stack list set.
[0013] A further technical solution thereof is that when receiving a forward instruction or a backward instruction from the user, update the preset back stack list set and / or forward stack list set, including:
[0014] When receiving a forward instruction from the user, determine whether there is data in the forward stack list set;
[0015] If there is data in the forward stack list set, remove the target data at the last position in the forward stack list set, and add the removed target data to the last position in the forward stack list set.
[0016] A further technical solution thereof is that based on the type of the operation instruction, store the relevant information of the component to be processed in the preset back stack list set or forward stack list set, including:
[0017] When the type of the operation instruction is move, delete, copy, cut, top, bottom, up, or down, store the relevant information of the component to be processed in the back stack list set.
[0018] A further technical solution thereof is that based on the type of the operation instruction, store the relevant information of the component to be processed in the preset back stack list set or forward stack list set, including:
[0019] When the type of the operation instruction is recall or backward, store the relevant information of the component to be processed in the forward stack list set.
[0020] A further technical solution thereof is that the relevant information of the component to be processed includes a component identifier, a component type, an operation type, and current configuration information of the component.
[0021] A further technical solution thereof is that the determination of whether there is data in the back stack list set further includes:
[0022] If there is no data in the back stack list set, end the operation instruction.
[0023] In a second aspect, an embodiment of the present application further provides a historical record device based on a large screen dashboard, which includes a unit for executing the above method.
[0024] In a third aspect, an embodiment of the present application further provides a computer device, which includes a memory and a processor. A computer program is stored on the memory, and when the processor executes the computer program, the above method is implemented.
[0025] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium. The storage medium stores a computer program, and when the computer program is executed by a processor, the above method can be implemented.
[0026] An embodiment of the present application provides a historical record method, device, computer device, and storage medium based on a large-screen dashboard. Among them, the method includes: receiving an operation instruction of a component to be processed in the large-screen dashboard; based on the type of the operation instruction, storing relevant information of the component to be processed into a preset back-stack list set or forward-stack list set; when a forward instruction or a backward instruction is received, the preset back-stack list set and forward-stack list set are updated, and display is performed based on the data in the updated back-stack list set. Since the relevant information of the component to be processed is stored in the preset back-stack list set or forward-stack list set in the embodiment of the present application, that is, all operations are detailedly recorded and displayed. Therefore, when the user needs to go forward or backward, the user can directly operate the back-stack list set or forward-stack list set to quickly locate any historical state, without relying on memory to track and restore the previous operation state. This reduces the time for the user to recall, and thus can improve the adjustment efficiency. Description of the Drawings
[0027] The drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.
[0028] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.
[0029] One or more embodiments are exemplarily illustrated by the pictures in the corresponding drawings. These exemplary illustrations do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements, unless otherwise stated, and the drawings in the drawings do not constitute a proportional limitation.
[0030] Figure 1 It is a schematic flowchart of the first embodiment of a historical record method based on a large-screen dashboard provided by the present application;
[0031] Figure 2Another embodiment flowchart of a historical record method based on a large-screen dashboard provided by this application;
[0032] Figure 3 A schematic structural diagram of an embodiment of a computer device provided by this application. Detailed implementation manners
[0033] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are some but not all of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without creative efforts shall fall within the scope of protection of this application.
[0034] The following disclosure provides many different embodiments or examples for implementing different structures of this application. To simplify the disclosure of this application, components and settings of specific examples are described below. Of course, they are only examples and are not intended to limit this application. In addition, this application may repeat reference numerals and / or letters in different examples. This repetition is for the purpose of simplification and clarity and does not in itself indicate the relationship between the various embodiments and / or settings discussed.
[0035] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprise" indicate the presence of the described features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.
[0036] It should also be understood that the terms used in this specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application. As used in this specification of this application and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms.
[0037] It should be further understood that the term " / and / " as used in this specification of this application and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0038] As used in this specification and the appended claims, the term "if" may be construed, depending on the context, as "when", "once", "in response to determining", or "in response to detecting". Similarly, the phrase "if determined" or "if [the described condition or event] is detected" may be construed, depending on the context, to mean "once determined", "in response to determining", "once [the described condition or event] is detected", or "in response to detecting [the described condition or event]".
[0039] In the application scenario of a visual large-screen design dashboard, users usually need to complete the final design layout through a series of complex operations. These operations include, but are not limited to, adding, moving, deleting, copying, and pasting various visual components (such as charts, text boxes, pictures, etc.).
[0040] Since the design process often cannot be completed in one step but requires multiple adjustments and layouts, during the design process, users are prone to making operational mistakes.
[0041] When an operational mistake occurs and the user wants to know what functions were operated in the previous steps and whether they need to go back to the previous step, they can only rely on memory to readjust, which results in relatively low adjustment efficiency.
[0042] To solve the problem in the prior art that the adjustment efficiency is relatively low because users can only rely on memory to readjust, this application provides a historical record method based on a large-screen dashboard, which can record the user's operation instructions. When the user needs to go forward or backward, they can directly operate on the back stack list set or the forward stack list set to quickly locate any historical state, without relying on memory to track and restore the previous operation state, reducing the time for users to recall, and thus improving the adjustment efficiency.
[0043] Refer to Figure 1 , Figure 1 which is a schematic flowchart of the first embodiment of a historical record method based on a large-screen dashboard provided by this application, and specifically may include the following steps:
[0044] Step 110: Receive the operation instructions of the user on the component to be processed in the large-screen dashboard.
[0045] Step 120: Based on the type of the operation instructions, store the relevant information of the component to be processed into a preset back stack list set or forward stack list set.
[0046] Step 130: When receiving the forward instruction or backward instruction of the user, update the preset back stack list set and forward stack list set, and display based on the data in the updated back stack list set.
[0047] In this embodiment, since the relevant information of the component to be processed is stored in a preset back stack list set or forward stack list set, that is, all operations are detailedly recorded and displayed. Therefore, when the user needs to go forward or backward, they can directly operate on the back stack list set or forward stack list set to quickly locate any historical state without relying on memory to track and restore the previous operation state. This reduces the time for the user to recall and thus can improve the adjustment efficiency.
[0048] In addition, it can also reduce operation errors caused by memory blur or omission and improve the accuracy of adjustment.
[0049] Referring to the second embodiment of a historical record method based on a large screen dashboard provided in this application, it may specifically include the following steps:
[0050] Step 210: Receive an operation instruction from the user for the component to be processed in the large screen dashboard.
[0051] Among them, the operation instruction can be drag, move, delete, copy, cut, top, bottom, up, down, etc.
[0052] Specifically, it can be that the user operates on the component to be processed through the operation panel or directly on the canvas, and the system obtains these operations and generates corresponding operation instructions.
[0053] Step 220: Based on the type of the operation instruction, store the relevant information of the component to be processed in a preset back stack list set or forward stack list set.
[0054] In some embodiments, the relevant information of the component to be processed includes a component identifier, a component type, an operation type, and the current configuration information of the component.
[0055] Among them, the component identifier is the unique identifier of each component in the system, used to distinguish different components. When recording the operation history, the component identifier can be directly recorded for subsequent reference in operations.
[0056] In some embodiments, the component type may include but is not limited to chart components, text components, picture components, table components, video components, button components, and custom components, etc.
[0057] In some embodiments, the operation type refers to the specific operation types performed by the user on the component. Common operation types include add, move, delete, copy, cut, top, bottom, up, down, etc.
[0058] In some embodiments, the current configuration information of a component may refer to all configuration parameters of the component at a certain moment. Such information may include position, size, style, data source, etc., which are used to record the state of the component and provide detailed component attributes for users to view and adjust, so that the state can be restored during the backward or forward operation. For example, the configuration information of a chart component may be the data source, coordinate axes, colors, etc., while the configuration information of a text component may be the font, font size, alignment method, etc.
[0059] Among them, the types of the backward stack list set and the forward stack list set can both be arrays. The backward stack list set is mainly used to store data of steps that can be backward, and the forward stack list set is mainly used to store data of steps that can be forward.
[0060] In some embodiments, step 220 may include the following two cases:
[0061] 1) When the type of the operation instruction is move, delete, copy, cut, bring to front, send to back, move up, or move down, the relevant information of the component to be processed is stored in the backward stack list set.
[0062] 2) When the type of the operation instruction is recall or backward, the relevant information of the component to be processed is stored in the forward stack list set.
[0063] In addition, when the user drags a chart component onto the canvas, the relevant information of the component to be processed can also be stored in the backward stack list set.
[0064] In this way, by recording and storing the user's operation steps in the backward stack list set and the forward stack list set, each operation step of the user can be recorded and stored in the history for the user to view.
[0065] Step 230: When receiving a forward instruction or a backward instruction from the user, update the preset backward stack list set and the forward stack list set, and perform display based on the data in the updated backward stack list set.
[0066] Among them, step 230 may include the following two cases:
[0067] The first case: When receiving a backward instruction from the user, determine whether there is data in the backward stack list set;
[0068] If there is data in the backward stack list set, remove the target data at the last position in the backward stack list set, and add the removed target data to the last position in the forward stack list set for subsequent forward operations.
[0069] If there is no data in the back stack list set, end the operation instruction.
[0070] The second case: When a forward instruction from the user is received, it is determined whether there is data in the forward stack list set;
[0071] If there is data in the forward stack list set, remove the target data at the last position in the forward stack list set, and add the removed target data to the last position in the back stack list set for subsequent backward operations.
[0072] If there is no data in the forward stack list set, end the operation instruction.
[0073] Based on the above embodiments, combined with Figure 2 , another embodiment of the historical record method based on the large screen dashboard provided by the present application may specifically include the following processes:
[0074] 1) The user drags chart components 1, 2, 3, and 5 in the component list to the canvas, and stores the data of chart components 1, 2, 3, and 5 in the canvas in the back stack list set.
[0075] 2) Receive the execution action of the user on chart component 3 in the canvas.
[0076] When the execution action of the user on chart component 3 (i.e., the component to be processed) in the canvas is delete, move, top, bottom, etc., directly add the operation instruction to the last position in the back stack list set. For example Figure 2 When clicking to delete chart component 3 in , add "Component 3 data [Delete]" to the last position in the back stack list set.
[0077] Among them, the relevant information of the component to be processed can also be stored in the preset back stack list set, such as the component identifier (i.e., Figure 2 the component ID in )), component type, operation type, and the current configuration information of the component.
[0078] When receiving the backward instruction of the user on chart component 3 in the canvas, that is, when the user clicks the backward button, it is determined whether there is data in the back stack list set; if there is data in the back stack list set, remove the target data at the last position in the back stack list set (i.e., delete the data of component 3 in the back stack list set), and add the removed target data, that is, "Component 3 data [Delete]", to the last position in the forward stack list set.
[0079] When receiving a forward instruction from the user for the chart component 3 in the canvas, that is, when the user clicks the forward button, it is determined whether there is data in the forward stack list set; if there is data in the forward stack list set, the target data at the last position in the forward stack list set is removed (that is, the data of component 3 in the forward stack list set is deleted), and the removed target data, that is, "Component 3 data [deleted]", is added to the last position in the backward stack list set.
[0080] When it is determined that there is no data in the backward stack list set, or when it is determined that there is no data in the forward stack list set, the operation instruction ends.
[0081] Among them, the rendering logic of the canvas is displayed according to the data in the backward stack list set.
[0082] In this way, each step of the user's operation can be recorded and stored in the historical record, that is, the backward stack list set, and the operation history record is displayed for the user to view, so that the user knows each operation record, can roll back or forward the historical operation record, and avoid incorrect operations relying on memory, thereby improving the efficiency of the dashboard design and the user experience.
[0083] Corresponding to the above historical record method based on the large-screen dashboard, the present application also provides a historical record device based on the large-screen dashboard. The historical record device based on the large-screen dashboard includes a unit for executing the above historical record method based on the large-screen dashboard, and the historical record device based on the large-screen dashboard can be configured in terminals such as desktop computers, tablet computers, and laptops.
[0084] As Figure 3 shown, an embodiment of the present application provides a computer device, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114. Among them, the processor 111, the communication interface 112, and the memory 113 complete mutual communication through the communication bus 114.
[0085] The memory 113 is used to store a computer program.
[0086] In an embodiment of the present application, when the processor 111 executes the program stored in the memory 113, it implements the historical record method based on the large-screen dashboard provided by any one of the foregoing method embodiments, including:
[0087] Receiving an operation instruction from the user for the component to be processed in the large-screen dashboard;
[0088] Based on the type of the operation instruction, storing the relevant information of the component to be processed in a preset backward stack list set or a forward stack list set.
[0089] When a forward instruction or a backward instruction from the user is received, the preset backward stack list set and the forward stack list set are updated, and display is performed based on the data in the updated backward stack list set.
[0090] Those of ordinary skill in the art can understand that all or part of the processes in the methods of implementing the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a storage medium, and the storage medium is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.
[0091] Therefore, the embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of the method for historical records based on a large-screen dashboard provided in any of the foregoing method embodiments, including:
[0092] Receiving an operation instruction of the user for a component to be processed in the large-screen dashboard;
[0093] Based on the type of the operation instruction, storing relevant information of the component to be processed into a preset backward stack list set or a forward stack list set;
[0094] When a forward instruction or a backward instruction from the user is received, the preset backward stack list set and the forward stack list set are updated, and display is performed based on the data in the updated backward stack list set.
[0095] The storage medium is a physical, non-transitory storage medium, such as a USB flash drive, a portable hard disk, a read-only memory (ROM), a magnetic disk, or an optical disc, etc., which are all physical storage media that can store program codes. The computer-readable storage medium can be non-volatile or volatile.
[0096] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of the examples have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present application.
[0097] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of each unit is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
[0098] The steps in the method embodiments of the present application can be adjusted, combined, and deleted according to actual needs. The units in the device embodiments of the present application can be combined, divided, and deleted according to actual needs. In addition, in each embodiment of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.
[0099] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the essence of the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
[0100] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0101] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these changes and modifications.
[0102] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or substitutions within the technical scope disclosed in the present application, and these modifications or substitutions should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A history recording method based on a large screen billboard, characterized in that: The method comprises: Receive user operation instructions for components to be processed in the large screen dashboard; Based on the type of the operation instruction, the relevant information of the component to be processed is stored in a preset back stack list set or a front stack list set; When a forward instruction or a backward instruction from the user is received, the preset back stack list set and the front back stack list set are updated, and displayed based on the data in the updated back stack list set.
2. The method according to claim 1, characterized in that When receiving a forward instruction or a backward instruction from the user, the preset back stack list set and / or the front stack list set are updated, including: When receiving a back instruction from the user, determining whether there is data in the back stack list set; If there is data in the back stack list set, the target data at the last position in the back stack list set is removed, and the removed target data is added to the last position in the front stack list set.
3. The method according to claim 1, characterized in that When receiving a forward instruction or a backward instruction from the user, the preset back stack list set and / or the front stack list set are updated, including: When receiving a forward instruction from the user, determining whether there is data in the forward stack list set; If there is data in the forward stack list set, the target data at the last position in the forward stack list set is removed, and the removed target data is added to the last position in the forward popped stack list set.
4. The method according to claim 1, characterized in that Based on the type of the operation instruction, storing the relevant information of the to-be-processed component into a preset back stack list set or a front stack list set includes: When the type of the operation instruction is move, delete, copy, cut, top, bottom, move up, or move down, the relevant information of the component to be processed is stored in the back stack list set.
5. The method according to claim 1, characterized in that Based on the type of the operation instruction, storing the relevant information of the to-be-processed component into a preset back stack list set or a front stack list set includes: When the type of the operation instruction is withdraw or back, the relevant information of the to-be-processed component is stored in the forward stack list set.
6. The method according to claim 1, characterized in that The relevant information of the component to be processed includes a component identifier, a component type, an operation type and current configuration information of the component.
7. The method according to claim 2, characterized in that: The step of determining whether there is data in the back stack list set further includes: If no data exists in the back stack list set, the operation instruction is terminated.
8. A history recording device based on a large screen billboard, characterized in that: The history recording device comprises means for executing the method according to any one of claims 1-7.
9. A computer device, characterized in that: The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 can be implemented.