CN112000262B - Method and system for repeating user operation - Google Patents
Method and system for repeating user operation Download PDFInfo
- Publication number
- CN112000262B CN112000262B CN202010767883.4A CN202010767883A CN112000262B CN 112000262 B CN112000262 B CN 112000262B CN 202010767883 A CN202010767883 A CN 202010767883A CN 112000262 B CN112000262 B CN 112000262B
- Authority
- CN
- China
- Prior art keywords
- shortcut
- user
- event
- operations
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
A method and system for repeating user operations is provided. The method comprises the following steps: monitoring events triggered by user operation, wherein the events comprise a starting event for identifying and starting recording the user operation and a termination event for terminating recording the user operation; when an initial event is monitored, judging whether shortcut operation corresponding to the initial event exists or not; and when the shortcut operation does not exist, stopping monitoring a termination event, and collecting user operation information between the starting event and the termination event as the shortcut operation.
Description
Technical Field
The present disclosure relates to the field of intelligent devices, and in particular, to a method and system for repeating user operations.
Background
Currently, monitoring of gestures or keys by platforms such as Android, iOS and the like is very mature, and the monitoring comprises a multi-point touch technology, multi-point signal acquisition and signal identification; at present, the interprocess communication technology is also very mature, and comprises a plurality of modes such as pipeline pipe, message queue, shared memory, socket and the like.
With the popularization of intelligent devices and the development of network technologies, users need to face a large amount of network information. The user needs to perform many complicated operations to process a large amount of information, and many operations are repeated. Too many repetitive, cumbersome operations can degrade user experience.
Disclosure of Invention
The invention aims to provide a method and a system for repeating user operation. More specifically, the user operation is automatically saved as the shortcut operation, so that the user can complete the complex operation only through simple operation, the user operation can be repeated more conveniently, the inconvenience brought to the user by the repeated complex operation is solved, the efficiency of the user is improved, the operation complexity is reduced, and the user experience is improved.
An example embodiment of the present disclosure provides a method of repeating a user operation, the method including: monitoring events triggered by user operation, wherein the events comprise a starting event for identifying and starting recording the user operation and a termination event for terminating recording the user operation; when an initial event is monitored, judging whether a shortcut operation corresponding to the initial event exists or not; and when the shortcut operation does not exist, monitoring a termination event, and collecting user operation information between the start event and the termination event as the shortcut operation.
In a method according to an example embodiment of the present disclosure, when a start event is monitored and a shortcut operation exists, the shortcut operation is executed.
In a method according to an example embodiment of the present disclosure, the start event may be an event having a start tag, and the end event may be an event having an end tag.
In a method according to an example embodiment of the present disclosure, the start event may be triggered by a custom user operation.
In the method according to the example embodiment of the present disclosure, when a start event is monitored and a shortcut operation does not exist, if there are other shortcut operations that do not correspond to the start event, the other shortcut operations are deleted.
In a method according to an example embodiment of the present disclosure, the user operation information may include: the type of user operation and the data resulting from the user operation.
In the method according to an example embodiment of the present disclosure, the step of saving the user operation information between the start event and the end event as a shortcut operation may include: gradually saving user operation information of each step of operation between a starting event and a terminating event, wherein the operation of each step in the shortcut operation is executed according to the following mode: collecting user operation information; processing the corresponding user operation information according to the type of the user operation information; and saving the processed user operation information.
In the method according to an example embodiment of the present disclosure, the step of processing the corresponding user operation information may include: judging whether the user operation information is related to a destination pointed by the termination event or not according to the termination event; discarding user operation information irrelevant to the destination; and processing user operation information related to the destination.
In a method according to an example embodiment of the present disclosure, when a shortcut operation exists, the performing of the shortcut operation may include: gradually executing each step of shortcut operation, wherein for each step of shortcut operation, executing the following steps: acquiring operation information of current operation; preprocessing the operation information of the current operation according to the type of the current operation; calling an interface corresponding to the current operation; and executing the current operation using the preprocessed operation information and the interface.
In a method according to an example embodiment of the present disclosure, a shortcut operation includes an operation to be interacted with and a no-interaction operation.
In a method according to an example embodiment of the present disclosure, when a shortcut operation exists, the step of performing the shortcut operation includes: gradually executing each step of shortcut operation, wherein for each step of shortcut operation, executing the following steps: acquiring operation information of current operation; preprocessing the operation information of the current operation according to the type of the current operation; calling an interface corresponding to the current operation; when the current operation is the operation to be interacted, generating interaction data through interaction with a user; and executing the current operation by using the preprocessed operation information, the interactive data and the interface.
In the method according to an example embodiment of the present disclosure, when the shortcut operation exists, the performing the shortcut operation includes: acquiring operation information of all operations in the shortcut operations; preprocessing corresponding operation information according to the type of each step of operation in the shortcut operation; calling an interface corresponding to each step of operation in the shortcut operation; aiming at all operations to be interacted in the shortcut operations, generating corresponding interaction data through interaction with a user; and executing shortcut operation by utilizing the preprocessed operation information, the interaction data and the interface.
An example embodiment of the present disclosure provides a system repeating a user operation, the system including: the monitoring module monitors an event triggered by user operation; the judging module is used for judging whether the shortcut operation corresponding to the initial event exists or not when the initial event is monitored; and the information collection module is used for intercepting the monitoring module to monitor the termination event when the judgment module judges that the shortcut operation does not exist, and collecting the user operation information between the starting event and the termination event as the shortcut operation.
In the system according to the example embodiment of the present disclosure, the system may further include a shortcut operation module, and when the monitoring module monitors the start event and the determining module determines that the shortcut operation exists, the shortcut operation module executes the shortcut operation.
In a system according to an example embodiment of the present disclosure, the start event may be an event with a start tag, and the end event may be an event with an end tag.
In a system according to an example embodiment of the present disclosure, the initiation event may be triggered by a custom user operation.
In the system according to the example embodiment of the present disclosure, when the monitoring module monitors the start event and the determining module determines that the shortcut operation does not exist, if there is another shortcut operation that does not correspond to the start event, the information collecting module deletes the another shortcut operation.
In a system according to an example embodiment of the present disclosure, the user operation information may include: the type of user operation and the data resulting from the user operation.
In the system according to the example embodiment of the present disclosure, when the determining module determines that the shortcut operation does not exist, the information collecting module may gradually store the user operation information between the start event and the end event until the monitoring module monitors the end event, where the information collecting module may perform the following steps for each step of the shortcut operation: collecting user operation information; processing the corresponding user operation information according to the type of the user operation information; and saving the processed user operation information.
In a system according to an example embodiment of the present disclosure, the information collection module may perform the following steps in processing the corresponding user operation information: judging whether the user operation information is related to a destination pointed by the termination event or not according to the termination event; discarding user operation information irrelevant to the destination; and processing user operation information related to the destination.
In the system according to the example embodiment of the present disclosure, the shortcut operation module performs each step of the shortcut operations step by step when the shortcut operations exist, wherein the shortcut operation module may perform the following for each step of the shortcut operations: acquiring operation information of current operation; preprocessing the operation information of the current operation according to the type of the current operation; calling an interface corresponding to the current operation; and executing the current operation using the preprocessed operation information and the interface.
In a system according to an example embodiment of the present disclosure, the shortcut operations may include an operation to be interacted with and a no-interaction operation.
In the system according to the example embodiment of the present disclosure, the shortcut operation module performs each step of the shortcut operations step by step when the shortcut operations exist, wherein the shortcut operation module may perform the following for each step of the shortcut operations: acquiring operation information of current operation; preprocessing the operation information of the current operation according to the type of the current operation; calling an interface corresponding to the current operation; when the current operation is the operation to be interacted, generating interaction data through interaction with a user; and executing the current operation by using the preprocessed operation information, the interaction data and the interface.
In a system according to an example embodiment of the present disclosure, a shortcut operation module performs a shortcut operation in the presence of the shortcut operation according to the following steps: acquiring operation information of all operations in the shortcut operations; preprocessing corresponding operation information according to the type of each step of operation in the shortcut operation; calling an interface corresponding to each step of operation in the shortcut operation; aiming at all operations to be interacted in the shortcut operations, generating corresponding interaction data through interaction with a user; and executing shortcut operation by utilizing the preprocessed operation information, the interactive data and the interface.
Example embodiments of the present disclosure provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements a method of repeating user operations as described above.
An example embodiment of the present disclosure provides an electronic terminal, wherein the electronic terminal includes: a processor; a memory storing a computer program which, when executed by the processor, implements the method of repeating user operations as described above.
In accordance with one or more aspects of the present disclosure, a method and system for repeating user operations is provided. The method monitors an event triggered by user operation, and automatically judges whether a shortcut operation corresponding to the event exists after the user operation triggers an initial event. Since the recording/executing step of the shortcut operation can be automatically performed without an additional operation by the user, the user's operation is simplified and the user experience is improved.
Drawings
These and/or other aspects and advantages of the present disclosure will become more apparent and more readily appreciated from the following detailed description of the embodiments of the present disclosure, taken in conjunction with the accompanying drawings of which:
fig. 1 is a flowchart illustrating a method of repeating a user operation according to an exemplary embodiment of the present disclosure;
FIGS. 2 and 3 are flowcharts illustrating steps in FIG. 1 to perform a save shortcut operation in accordance with an embodiment;
FIGS. 4-6 are flow diagrams illustrating steps in FIG. 1 to perform a shortcut operation, according to an embodiment;
FIG. 7 is a block diagram illustrating a system of repeating user operations according to an exemplary embodiment of the present disclosure;
FIG. 8 is a flow diagram of performing screenshot sharing according to a comparative example;
FIG. 9 is a flow diagram to perform screenshot sharing according to an embodiment;
FIG. 10 is a flowchart of performing gallery management according to a comparative example; and
FIG. 11 is a flow diagram to perform gallery management according to an embodiment.
Detailed Description
Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. Examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below in order to explain the present disclosure by referring to the figures.
In this case, the expression "at least one of the items" in the present disclosure means a case where three types of parallel expressions "any one of the items", "a combination of any plural ones of the items", and "the entirety of the items" are included. For example, "include at least one of a and B" includes the following three cases in parallel: (1) comprises A; (2) comprises B; (3) including a and B. For another example, "at least one of the first step and the second step is performed", which means that the following three cases are juxtaposed: (1) executing the step one; (2) executing the step two; (3) and executing the step one and the step two.
Fig. 1 is a flowchart illustrating a method of repeating a user operation according to an exemplary embodiment of the present disclosure.
Referring to fig. 1, in step S10, an event triggered by a user operation is listened to.
In an embodiment, the user operation and the event triggered by the user operation may include an interaction (input/output) between the user and the smart device/system. For example, the user operations may include making a phone call, network connection on/off, flight mode on/off, bluetooth on/off, selecting a bluetooth device, screen capture, adjusting screen brightness, flashlight on/off, restarting a device, turning off, starting a home screen, font settings, run mode settings, sharing (file/photo, location, etc.), taking a picture, adjusting volume, and so forth. The above examples of user operations are for example only and should not be construed as limiting the present disclosure. The events include an initial event identifying a start of recording a user operation and a termination event terminating recording of the user operation.
In step S20, an event triggered by a user operation is determined. For example, when a start event is monitored, whether a shortcut operation corresponding to the start event exists is determined.
In an embodiment, the start event is an event with a start tag, which may be an attribute of the event. For example, unlike events in the prior art, events according to embodiments of the present disclosure have an additional start tag. In an example embodiment, the addition or deletion of a start tag to an event may be set by the system or a user as desired. In another embodiment, whether an event has the attribute of the start tag may be preset, and the start tag is set to be enabled or disabled as needed, and the enabling or disabling of the start tag may be set by the system or the user. In this case, the event that the start tag is set to enabled may be referred to as a start departure event. However, the above examples are shown only for convenience of explanation and understanding. The start event may be a predetermined specific event.
In another embodiment, the initiation event may be triggered by a custom user action. For example, the custom user operation may be a custom button, a custom combination button, a custom hover button, a custom multi-touch, and the like. For example, a long press of the volume down key, volume down key + power on/off key, a float button, a two-finger double click, or a custom gesture (e.g., long press, drag, zoom, and/or rotate, etc.). In some embodiments, the custom user operation corresponds to only one of a custom button, a custom combination button, a custom hover button, a custom multi-touch, and the like. In this case, the memory burden of the user can be reduced, and the user experience can be improved.
When it is judged in step S20 that the shortcut operation corresponding to the start event does not exist, step S30 is performed. In step S30, when the termination event is intercepted, the user operation information between the start event and the termination event is collected as a shortcut operation.
The shortcut operation may be saved to a storage device. The memory devices may include non-volatile memory devices (such as erasable programmable read-only memory (EPROM) devices, electrically erasable programmable read-only memory (EEPROM) devices, flash memory devices, phase change random access memory (PRAM) devices, Resistive Random Access Memory (RRAM) devices, Nano Floating Gate Memory (NFGM) devices, polymer random access memory (ponam) devices, Magnetic Random Access Memory (MRAM) devices, Ferroelectric Random Access Memory (FRAM) devices, and the like) and/or volatile memory devices (such as Dynamic Random Access Memory (DRAM) devices, static random access memory (SDRAM) devices, mobile dynamic random access memory (mobile DRAM), and the like).
The termination event may be an event with a termination tag, which may be an attribute of the event. The termination tag is similar to the start tag described above, and thus repeated description may be omitted. In an embodiment, the shortcut operation may include user operation information between a start event to a termination event. In an embodiment, the shortcut operations may include user operations that trigger a start event and a stop event, and may include triggering a start event and a stop event. In an embodiment, the user operation information may include a type of the user operation and data generated by the user operation. For example, the types of user operations may include: screen capture, sliding, clicking, sharing of files, editing and/or copying, and data corresponding to user operations include but are not limited to: data stored in shared memory (e.g., photos, screenshots, etc.), record clicks, drags, swipes, multi-touch, coordinates of gesture events, name of APP, interface, file/text information, data called through an interface of an application (candidate list), etc.
When it is judged in step S20 that the shortcut operation corresponding to the start event exists, in step S40, the shortcut operation is executed.
Fig. 2 and 3 are flowcharts illustrating step S30 of performing a save shortcut operation in fig. 1 according to an embodiment, and a detailed flow of step S30 will be described below with reference to fig. 2 and 3.
In an embodiment, the step 30 of performing a save shortcut operation may include: and gradually saving user operation information of each operation from the starting event to the ending event.
As shown in fig. 2, the following is performed for each operation in the shortcut operation:
in step S310, user operation information is collected. In some embodiments, if there are other shortcut operations that do not correspond to the start event, the other shortcut operations are deleted. For example, a storage device used to save shortcut operations may be emptied such that the storage device only saves a set of shortcut operations. In this case, the memory burden of the user can be reduced, and the user experience can be improved.
In step S320, the corresponding user operation information is processed according to the type of the user operation information. For example, data of the user operation information is formatted according to the type of the user operation information, for example, the data is processed to meet a specific requirement or format. In addition, the context of the user operation information can be recorded according to the type of the user operation information.
In step S330, the processed user operation information is saved.
In another embodiment, step S320 may further include a step of determining whether the user operation information is related to a destination pointed to by the termination event according to the termination event (step S321, see fig. 3). If the user operation information is not related to the destination, discarding the user operation information; and if the user operation information is related to the destination, processing the user operation information.
According to the embodiments described above with reference to fig. 2 and 3, the method of repeating a user operation may automatically record subsequent user operation information according to the trigger of the start event when the shortcut operation does not exist, and may automatically end recording according to the trigger of the end event without a user presetting when to start recording or when to end recording. In addition, the method can also exclude irrelevant user operations according to whether the user operations between the starting event and the ending event are related to the destination pointed by the ending event, thereby improving the efficiency of repeated user operations and avoiding unnecessary operations.
Fig. 4 to 6 are flowcharts illustrating the step S40 of performing a shortcut operation in fig. 1 according to an embodiment.
The step S40 of executing the shortcut operation includes: and executing each step of the shortcut operation step by step.
As shown in fig. 4, for each step of the shortcut operation, the following is performed:
in step S410, operation information of the current operation is acquired.
In step S420, the operation information of the current operation is preprocessed according to the type of the current operation. Since the information of each operation is different, the acquired data is preprocessed according to the operation type. For example, the data is preprocessed to meet specific requirements or formats.
In step S430, an interface corresponding to the current operation is called according to different operation types.
In step S440, the current operation is performed using the preprocessed operation information and the interface.
Referring to FIG. 5, in another example embodiment, shortcut operations may include to-be-interacted-with operations and no-interaction operations. In this case, except for step S435, step S40 of performing the shortcut operation may be substantially the same as step S40 described with reference to fig. 4, and thus, the same steps as those described with reference to fig. 4 may be omitted.
Referring to fig. 5, for each operation of the shortcut operations, step S410, step S420, step S430 are performed in the same manner as the steps described in fig. 4, and in step S435, when the current operation is an operation to be interacted with, interaction data is generated by interacting with a user. Then, step S440 is performed in the same manner as the step described in fig. 4.
In another embodiment, in step S435, when the current operation is the operation to be interacted with, if the user selects cancel without generating the interaction data, the execution of the shortcut operation may be suspended, or the execution of the shortcut operation may be suspended and the shortcut operation is deleted, and then return is made to step S30. For example, the storage for saving shortcut operations may be emptied so that another set of shortcut operations different from the current shortcut operation may be recorded again.
Referring to fig. 6, in another embodiment, the step S40 of performing a shortcut operation includes:
in step 410', operation information of all operations in the shortcut operation is acquired.
In step 420', the corresponding operation information is preprocessed according to the type of each operation in the shortcut operation.
In step S430', an interface corresponding to each of the shortcut operations is called.
In step S435', for all to-be-interacted operations in the shortcut operation, generating corresponding interaction data by interacting with a user. For example, when the shortcut operation includes 2 or more operations to be interacted with, interaction data is obtained by interacting with a user. In such embodiments, the interaction may be through an interactive interface built into the system, or a unified interactive interface (or the same interactive interface) may be used. For example, interaction data with the user may be obtained by means of a multi-box, hierarchical tab, or the like. The above examples are merely illustrative of example embodiments and should not be construed as limiting the present disclosure. The manner in which interaction with a user and obtaining real-time interaction information can be achieved is to be understood to be included within the scope of the inventive concept. This step will be further described later with reference to fig. 9.
In another embodiment, in step S435', if the user selects cancellation without generating interactive data, the execution of the shortcut operation may be suspended, or the execution of the shortcut operation may be suspended and the shortcut operation is deleted, and then the process returns to step S30. For example, the storage for saving shortcut operations may be emptied so that another set of shortcut operations for the user different from the current shortcut operation may be recorded again.
It should be noted that the above examples are only for ease of understanding and should not be construed as limiting the concepts of the present disclosure. In another embodiment, step S435' may be omitted when the event to be interacted with is not included in the shortcut operation or no interaction with the user is required. In this case, the shortcut operation without the event to be interacted may be triggered only by the user-defined user operation, thereby avoiding the user misoperation.
In step S440', the shortcut operation is performed using the preprocessed operation information, the interaction data, and the interface. Step S440 'may be performed in the order of each operation in the shortcut operation, and for the operation to be interacted, is performed using the interaction data obtained at step S435'.
According to the above embodiments with reference to fig. 4 to 6, the method of repeating a user operation may perform a shortcut operation when the shortcut operation exists. The method may perform each of the shortcut operations step by step. In some embodiments, the method may perform interaction with the user collectively using a uniform interactive interface, thereby reducing steps that the user needs to participate in or reducing the waiting time of the user, in which case, the efficiency of repeating user operations may be further improved, and the user experience may be improved.
Fig. 7 is a block diagram illustrating a system of repeating user operations according to an exemplary embodiment of the present disclosure.
In fig. 7, the system for repeating the user operation includes a listening module 10, a judging module 20, an original operation module 25, an information collecting module 30, and a storage device M.
The listening module 10 listens for events triggered by user actions. The listening module may be configured to perform step S10 described with reference to fig. 1, and thus redundant description is omitted herein.
The determining module 20 determines whether a start event triggered by a user operation exists, and further determines whether a shortcut operation corresponding to the start event exists in the storage device M. The determination module 20 may be configured to perform step S20 described with reference to fig. 1, and thus redundant description is omitted herein.
The original operation module 25 performs an original user operation. When the original operation ends (execution end event), the original operation module notifies the information collection module of the end of the operation.
The information collection module 30 collects the user operation information generated by the original operation module 25 and saves the user operation information in the storage device M. The information collection module 30 may be configured to perform step S30 described with reference to fig. 1, 2, and 3, and thus redundant description is omitted herein.
The shortcut operation module 40 performs a shortcut operation. The shortcut operation module 40 may obtain operation information from the storage device M and call an operation interface. The shortcut operation module 40 may be configured to perform step S40 described with reference to fig. 1 and 4 to 6, and thus redundant description is omitted herein.
In another embodiment, when the shortcut operation module 40 performs the shortcut operation, when the current operation is the to-be-interacted operation, if the user selects to cancel without generating the interaction data, the performance of the shortcut operation may be suspended, or the performance of the shortcut operation may be suspended and deleted, and then returned to the original operation module 25. For example, the storage for saving the shortcut operations may be cleared, so that the original user operation may be performed through the original operation module 25, and another set of shortcut operations different from the current shortcut operation may be recorded again.
Fig. 8 is a flowchart of performing screenshot sharing according to a comparative example, and fig. 9 is a flowchart of performing screenshot sharing according to an embodiment.
Assume a scenario where a user wishes to share a browsed screenshot of an item with a friend seeking advice and wishes to compare multiple items. At this time, the user needs to send multiple product screenshots to the friend. In fig. 8 and 9, the operation identified by Δ represents a user operation, and the remaining unidentified operations are performed by the system.
Referring to fig. 8, one screenshot share goes through the five steps shown in fig. 8: screen capture, screenshot, share clicking, APP selection and contact person selection. If such operations are performed frequently, the user experience is deteriorated.
Referring to fig. 9, in the same scenario, a user operation triggers a screen capture event. In an embodiment according to the present disclosure, the screen capture event is a start event with a start tag. The screen capture event triggered by the user operation can be judged, and when the shortcut operation corresponding to the screen capture event does not exist, the user executes the original operation, namely, the operations of screen capture, screenshot clicking, sharing, APP selecting and contact person selecting are sequentially executed. The sharing event triggered by the sharing operation is performed by the system, and the sharing event may be a termination event with a termination tag. The operations of selecting the APP and selecting the contact person can be to-be-interacted operations, and the screen capture, the screen click-on capture and the screen click-on sharing are non-interacted operations. The user operation information of the operation screen capture, the click sharing, the selection of the APP and the selection of the contact between the starting event and the ending event can be saved as the shortcut operation. The user operation information may further include data related to the user operation.
When the user operates to trigger the screen capture event again, the system judges the screen capture event triggered by the user operation, knows that the shortcut operation corresponding to the screen capture event exists, and executes the shortcut operation. When each step of operation in the shortcut operation is executed, because the operations of selecting the APP and selecting the contact person are events to be interacted, when the operations of selecting the APP and selecting the contact person are executed, a user is waited for interaction, and the user selects the APP and the contact person to be used. Under the condition, the user only needs to perform two operations of screen capture triggering and item selection, and the screen capture sharing operation can be realized. The present disclosure reduces user operations compared to the screenshot sharing operation illustrated with reference to fig. 8. Compared with the method that the screenshots are firstly captured for multiple times and then sent in batches by one key, the screenshot and the sharing action are combined into one action, the content can be shared at any time when being browsed, and the method is more real-time. The user experience is better.
In another embodiment, when the user triggers the screen capture event again, if the user selects cancellation in the interaction step without generating the interaction data, the execution of the shortcut operation may be suspended, or the execution of the shortcut operation may be suspended, and the storage device for storing the shortcut operation is cleared, and then the action of clicking on the screen capture is returned and the execution is continued according to the original operation module.
In another embodiment, a multi-box may be added, thereby enabling one-touch sharing to multiple contacts of multiple APPs. For example, a list of select APPs and select contacts may be provided at the same user interface. Because the operations of selecting the APP and selecting the contact are combined at the same user interface, the efficiency of the user operation is further improved.
Fig. 10 is a flowchart of performing gallery management according to a comparative example, and fig. 10 is a flowchart of performing gallery management according to an embodiment.
In fig. 10 and 11, the operations identified by Δ represent user operations, and the remaining unidentified operations are performed by the system.
Assuming a scenario in which a user wants to put an album in his/her style in the original image browsing mode, the user needs to perform many copying or moving operations.
Referring to FIG. 10, the user needs to click on add to, select album, select operation (copy and/or move). That is, one move or copy operation goes through the four steps of the above figure, and the workload becomes large for the entire process of collating the album. The user experience is not good.
Referring to fig. 11, the user only needs to go through one step of event triggering (for example, clicking an add or user-defined gesture, such as a two-finger double click, a three-finger drag, etc.), so as to implement the operation of copying or moving the picture, thereby greatly improving the efficiency. In this embodiment, the selected album is not set to be interactively operated. However, this is merely an example. Whether the event is to be interacted with can be set by the system or the user according to the situation. For example, the operation of selecting an album may be set to be an interactive operation. And is performed with reference to the steps described in fig. 4 to 6.
In another embodiment, the shortcut operation can be triggered only through a user-defined gesture under the condition that the selected photo album is not set to be interactively operated, so that misoperation of a user under the unknown condition is avoided.
The method and system for repeating user operations, which can automatically record subsequent user operation information according to the trigger of a start event when a shortcut operation does not exist and can automatically end recording according to the trigger of an end event without a user's preset time for starting recording or ending recording, are described above with reference to the accompanying drawings. The method and the system can execute the shortcut operation when the shortcut operation exists. According to the method and the system for repeating the user operation, steps required to be participated by the user or waiting time required by the user can be reduced, in this case, the efficiency of repeating the user operation can be further improved, and the user experience is improved.
A method and system of repeating user operations according to an exemplary embodiment of the present disclosure have been described above with reference to fig. 1 to 11.
The various elements of the system shown in fig. 7 that repeat user operations may be configured as software, hardware, firmware, or any combination thereof that perform particular functions. For example, each unit may correspond to an application-specific integrated circuit, to pure software code, or to a module combining software and hardware. Furthermore, one or more functions implemented by the respective units may also be uniformly executed by components in a physical entity device (e.g., a processor, a client, a server, or the like).
Further, the method of repeating user operations described with reference to fig. 1 may be implemented by a program (or instructions) recorded on a computer-readable storage medium. For example, according to an exemplary embodiment of the present disclosure, a computer-readable storage medium storing instructions may be provided, wherein the instructions, when executed by at least one computing device, cause the at least one computing device to perform a method of repeating user operations according to the present disclosure.
The computer program in the computer-readable storage medium may be executed in an environment deployed in a computer device such as a client, a host, a proxy device, a server, and the like, and it should be noted that the computer program may also be used to perform additional steps other than the above steps or perform more specific processing when the above steps are performed, and the content of the additional steps and the further processing are already mentioned in the description of the related method with reference to fig. 1, and therefore will not be described again here to avoid repetition.
It should be noted that each unit in the system of repeating user operations according to the exemplary embodiment of the present disclosure may completely depend on the execution of the computer program to realize the corresponding function, that is, each unit corresponds to each step in the functional architecture of the computer program, so that the entire system is called by a special software package (e.g., lib library) to realize the corresponding function.
Alternatively, the various elements shown in fig. 7 may be implemented by hardware, software, firmware, middleware, microcode, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the corresponding operations may be stored in a computer-readable medium such as a storage medium, so that a processor may perform the corresponding operations by reading and executing the corresponding program code or code segments.
For example, exemplary embodiments of the present disclosure may also be implemented as a computing device including a storage component having stored therein a set of computer-executable instructions that, when executed by a processor, perform a method of repeating user operations according to exemplary embodiments of the present disclosure.
In particular, computing devices may be deployed in servers or clients, as well as on node devices in a distributed network environment. Further, the computing device may be a PC computer, tablet device, personal digital assistant, smart phone, web application, or other device capable of executing the set of instructions.
The computing device need not be a single computing device, but can be any device or collection of circuits capable of executing the instructions (or sets of instructions) described above, individually or in combination. The computing device may also be part of an integrated control system or system manager, or may be configured as a portable electronic device that interfaces with local or remote (e.g., via wireless transmission).
In a computing device, a processor may include a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller, or a microprocessor. By way of example, and not limitation, processors may also include analog processors, digital processors, microprocessors, multi-core processors, processor arrays, network processors, and the like.
Some of the operations described in the method of repeating user operations according to the exemplary embodiments of the present disclosure may be implemented by software, some of the operations may be implemented by hardware, and further, the operations may be implemented by a combination of hardware and software.
The processor may execute instructions or code stored in one of the storage components, which may also store data. The instructions and data may also be transmitted or received over a network via a network interface device, which may employ any known transmission protocol.
The memory component may be integral to the processor, e.g., having RAM or flash memory disposed within an integrated circuit microprocessor or the like. Further, the storage component may comprise a stand-alone device, such as an external disk drive, storage array, or any other storage device usable by a database system. The storage component and the processor may be operatively coupled or may communicate with each other, such as through an I/O port, a network connection, etc., so that the processor can read files stored in the storage component.
In addition, the computing device may also include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, mouse, touch input device, etc.). All components of the computing device may be connected to each other via a bus and/or a network.
The method of repeating user operations according to an exemplary embodiment of the present disclosure may be described as various interconnected or coupled functional blocks or functional diagrams. However, these functional blocks or functional diagrams may be equally integrated into a single logic device or operated on with non-exact boundaries.
Thus, the method of repeating user operations described with reference to FIG. 1 may be implemented by a system comprising at least one computing device and at least one storage device storing instructions.
According to an exemplary embodiment of the present disclosure, the at least one computing device is a computing device for performing a method of repeating user operations according to an exemplary embodiment of the present disclosure, the storage device having stored therein a set of computer-executable instructions that, when executed by the at least one computing device, perform the method of repeating user operations described with reference to fig. 1.
While various exemplary embodiments of the present disclosure have been described above, it should be understood that the above description is exemplary only, and not exhaustive, and that the present disclosure is not limited to the disclosed exemplary embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. Therefore, the protection scope of the present disclosure should be subject to the scope of the claims.
Claims (26)
1. A method of repeating user operations, the method comprising:
monitoring events triggered by user operation, wherein the events comprise a starting event for identifying and starting recording the user operation and a termination event for terminating recording the user operation;
when an initial event is monitored, judging whether shortcut operation corresponding to the initial event exists or not; and
when the shortcut operation does not exist, stopping monitoring a termination event, collecting user operation information between the starting event and the termination event as the shortcut operation,
the shortcut operation comprises a user operation for triggering the starting event and a user operation for triggering the ending event.
2. The method of claim 1, wherein the shortcut operation is executed when a start event is monitored and the shortcut operation exists.
3. The method of claim 1, wherein the start event is an event with a start tag and the end event is an event with an end tag.
4. The method of claim 1, wherein the initiation event is triggered by a custom user action.
5. The method according to claim 1, wherein when a start event is monitored and the shortcut operation does not exist, if other shortcut operations which do not correspond to the start event exist, the other shortcut operations are deleted.
6. The method of claim 2, wherein the user operation information comprises: the type of user operation and the data resulting from the user operation.
7. The method according to claim 6, wherein the step of saving the user operation information from the start event to the end event as the shortcut operation comprises: gradually saving user operation information for each operation between the start event and the end event,
wherein, for each step of operation in the shortcut operation, the following steps are executed:
collecting user operation information;
processing the corresponding user operation information according to the type of the user operation information; and
and saving the processed user operation information.
8. The method of claim 7, wherein the step of processing the corresponding user operation information comprises:
judging whether the user operation information is related to a destination pointed by the termination event or not according to the termination event;
discarding user operation information irrelevant to the destination; and
and processing the user operation information related to the destination.
9. The method according to claim 7 or 8, wherein the step of executing the shortcut operation when the shortcut operation exists comprises: each of the shortcut operations is executed step by step,
Wherein, aiming at each step of operation in the shortcut operation, the following steps are executed:
acquiring operation information of current operation;
preprocessing the operation information of the current operation according to the type of the current operation;
calling an interface corresponding to the current operation; and
and executing the current operation by utilizing the preprocessed operation information and the interface.
10. The method according to claim 7 or 8, wherein the shortcut operations comprise to-be-interacted operations and no-interaction operations.
11. The method of claim 10, wherein when the shortcut operation exists, the step of executing the shortcut operation comprises: each of the shortcut operations is executed step by step,
wherein, aiming at each step of operation in the shortcut operation, the following steps are executed:
acquiring operation information of current operation;
preprocessing the operation information of the current operation according to the type of the current operation;
calling an interface corresponding to the current operation;
when the current operation is the operation to be interacted, generating interaction data through interaction with a user; and
performing a current operation using the preprocessed operation information, the interaction data, and the interface.
12. The method of claim 10, wherein when the shortcut operation exists, the step of executing the shortcut operation comprises:
acquiring operation information of all the operations in the shortcut operations;
preprocessing corresponding operation information according to the type of each step of operation in the shortcut operation;
calling an interface corresponding to each step of operation in the shortcut operation;
generating corresponding interactive data by interacting with a user aiming at all operations to be interacted in the shortcut operations;
and executing the shortcut operation by utilizing the preprocessed operation information, the interaction data and the interface.
13. A system for repeating user operations, the system comprising:
the monitoring module monitors an event triggered by user operation;
the judging module is used for judging whether shortcut operation corresponding to the initial event exists or not when the initial event is monitored;
an information collection module, when the judgment module judges that the shortcut operation does not exist, the monitoring module is stopped to monitor a termination event, and the user operation information between the start event and the termination event is collected as the shortcut operation,
the shortcut operation comprises a user operation for triggering the starting event and a user operation for triggering the ending event.
14. The system of claim 13, further comprising a shortcut module, wherein when the monitoring module monitors a start event and the determining module determines that the shortcut exists, the shortcut module executes the shortcut.
15. The system of claim 13, wherein the start event is an event with a start tag and the stop event is an event with a stop tag.
16. The system of claim 13, wherein the initiation event is triggered by a custom user action.
17. The system according to claim 13, wherein when the monitoring module monitors a start event and the determining module determines that the shortcut operation does not exist, if there is another shortcut operation that does not correspond to the start event, the information collecting module deletes the another shortcut operation.
18. The system of claim 14, wherein the user operation information comprises: the type of user operation and the data resulting from the user operation.
19. The system according to claim 18, wherein when the determining module determines that the shortcut operation does not exist, the information collecting module gradually saves the user operation information between the start event and the end event until the monitoring module monitors the end event,
Wherein the information collection module performs for each operation in the shortcut operations in the following manner:
collecting user operation information;
processing the corresponding user operation information according to the type of the user operation information; and
and saving the processed user operation information.
20. The system of claim 19, wherein the information collection module performs the following steps in processing the corresponding user operation information:
judging whether the user operation information is related to a destination pointed by the termination event or not according to the termination event;
discarding user operation information irrelevant to the destination; and
and processing the user operation information related to the destination.
21. The system of claim 19 or 20, wherein the shortcut module performs each of the shortcut operations step by step while the shortcut operation exists,
the shortcut operation module executes each step of operation in the shortcut operations according to the following modes:
acquiring operation information of current operation;
preprocessing the operation information of the current operation according to the type of the current operation;
Calling an interface corresponding to the current operation; and
performing a current operation using the preprocessed operation information and the interface.
22. The system according to claim 19 or 20, wherein the shortcut operations include to-be-interacted-operations and no-interaction-operations.
23. The system of claim 22, wherein the shortcut module performs each of the shortcut operations step by step while the shortcut operations exist,
the shortcut operation module executes each step of operation in the shortcut operations according to the following modes:
acquiring operation information of current operation;
preprocessing the operation information of the current operation according to the type of the current operation;
calling an interface corresponding to the current operation;
when the current operation is the operation to be interacted, generating interaction data through interaction with a user; and
performing a current operation using the preprocessed operation information, the interaction data, and the interface.
24. The system of claim 22, wherein the shortcut module executes the shortcut operation when the shortcut operation exists according to the following steps:
acquiring operation information of all the operations in the shortcut operations;
Preprocessing corresponding operation information according to the type of each step of operation in the shortcut operation;
calling an interface corresponding to each step of operation in the shortcut operation;
generating corresponding interactive data by interacting with a user aiming at all operations to be interacted in the shortcut operations; and
and executing the shortcut operation by utilizing the preprocessed operation information, the interaction data and the interface.
25. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out a method of repeating user operations according to any one of claims 1 to 12.
26. An electronic terminal, wherein the electronic terminal comprises:
a processor;
memory storing a computer program which, when executed by a processor, implements a method of repeating user operations as claimed in any one of claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010767883.4A CN112000262B (en) | 2020-08-03 | 2020-08-03 | Method and system for repeating user operation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010767883.4A CN112000262B (en) | 2020-08-03 | 2020-08-03 | Method and system for repeating user operation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112000262A CN112000262A (en) | 2020-11-27 |
| CN112000262B true CN112000262B (en) | 2022-05-24 |
Family
ID=73463605
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010767883.4A Active CN112000262B (en) | 2020-08-03 | 2020-08-03 | Method and system for repeating user operation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112000262B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102098380A (en) * | 2010-12-22 | 2011-06-15 | 中兴通讯股份有限公司 | Method and device for customizing shortcut in mobile terminal |
| CN107728874A (en) * | 2017-09-06 | 2018-02-23 | 阿里巴巴集团控股有限公司 | The method, apparatus and equipment of user prompt operation are provided |
| CN107918509A (en) * | 2017-06-26 | 2018-04-17 | 平安普惠企业管理有限公司 | Software shortcut prompting method to set up, device and readable storage medium storing program for executing |
| CN110515533A (en) * | 2019-08-20 | 2019-11-29 | Oppo（重庆）智能科技有限公司 | Electronic equipment shortcut operation method, device, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190066533A1 (en) * | 2017-08-31 | 2019-02-28 | Tatiana Ufimtceva | Methods for facilitating shortcut and hot key learning via computer application gamification and devices thereof |
-
2020
- 2020-08-03 CN CN202010767883.4A patent/CN112000262B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102098380A (en) * | 2010-12-22 | 2011-06-15 | 中兴通讯股份有限公司 | Method and device for customizing shortcut in mobile terminal |
| CN107918509A (en) * | 2017-06-26 | 2018-04-17 | 平安普惠企业管理有限公司 | Software shortcut prompting method to set up, device and readable storage medium storing program for executing |
| CN107728874A (en) * | 2017-09-06 | 2018-02-23 | 阿里巴巴集团控股有限公司 | The method, apparatus and equipment of user prompt operation are provided |
| CN110515533A (en) * | 2019-08-20 | 2019-11-29 | Oppo（重庆）智能科技有限公司 | Electronic equipment shortcut operation method, device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112000262A (en) | 2020-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210279203A1 (en) | System and method for provisioning databases in a hyperconverged infrastructure system | |
| WO2020057091A1 (en) | Ios-based data acquisition and analysis method and apparatus | |
| US20220107712A1 (en) | Systems and methods for providing tab previews via an operating system user interface | |
| CN107066188B (en) | A kind of method and terminal sending screenshot picture | |
| CN108132735B (en) | Terminal and application control method | |
| WO2019184490A1 (en) | Method for use in displaying icons of hosted applications, and device and storage medium | |
| WO2023010903A1 (en) | Desktop management method for terminal device, and terminal device | |
| CN110058763B (en) | Interactive information processing method, system, device, storage medium and notebook computer | |
| US10970049B2 (en) | Code execution and data processing pipeline | |
| US11036362B2 (en) | Graphic flow having unlimited number of connections between shapes | |
| WO2023046130A1 (en) | Application icon display method and apparatus, and electronic device and storage medium | |
| WO2018054251A1 (en) | Operation object processing method and apparatus | |
| WO2018086454A1 (en) | Page data processing method and device | |
| CN111782427A (en) | Content operation method and device and computer readable storage medium | |
| US20220244845A1 (en) | Method, device, electronic device, and storage medium for sending and receiving message | |
| WO2022135476A1 (en) | Screenshot method and apparatus, and electronic device | |
| WO2022041609A1 (en) | Icon arrangement method and apparatus, storage medium, and electronic device | |
| CN112000262B (en) | Method and system for repeating user operation | |
| US20230359343A1 (en) | Interface processing method and apparatus, electronic device, and computer-readable storage medium | |
| CN109597537B (en) | File synchronization method, device and equipment | |
| CN114510308B (en) | Method, device, equipment and medium for storing application page by mobile terminal | |
| WO2022242641A1 (en) | Task implementation method and apparatus, and electronic device | |
| WO2021088865A1 (en) | Gesture operation method and device | |
| JP2017102847A (en) | Information processing system, relay device, method, and program | |
| CN114270298A (en) | Touch event processing method and device, mobile terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |