A task status prompting method and system

Abstract

This invention discloses a task status prompting method and system, relating to the field of computer technology. The method includes: monitoring the execution status of a background task in a first application view that initiated the background task, and determining whether the first application view is currently the user's focus; when the first application view is not currently the user's focus, determining corresponding visual prompt parameters based on the execution status of the background task, and synchronizing the visual prompt parameters to a second application view that is currently the user's focus. This achieves cross-application view background task status prompts, allowing users to perceive the background task's execution progress in real time within the view where their current focus is located even after switching to another application view. This solves the problem that users cannot perceive the background task status or grasp the real-time progress of tasks in views other than the one initiating the task, improving multi-task management efficiency and user experience.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a task status prompting method and system. Background Technology

[0002] In existing application scenarios, the progress display and status prompts for asynchronous background tasks such as data export and batch processing typically rely on built-in visual controls such as progress bars, pop-ups, and overlays within the task initiation interface. These status prompt methods all depend on the application view to which the task belongs, requiring the user to remain within the application view that initiated the background task to obtain updated information about the task's execution status.

[0003] The above method binds task status monitoring and prompts to the task initiation view, failing to achieve status awareness across application views. When the user switches the focus to another application view, or when the original task view is not displayed in the foreground, the user cannot effectively perceive the status updates within the application view that initiated the background task. Consequently, it is difficult to grasp the real-time execution progress of the background task, making it easy to miss task completion milestones. This also reduces the efficiency of multi-task parallel management and affects the user experience. Summary of the Invention

[0004] The main objective of this invention is to provide a method and system for displaying task status. It enables background task status display across application views, allowing users to perceive the real-time progress of background tasks in the currently active view even after switching focus to other application views. This solves the problem of users being unable to perceive the status of background tasks or grasp their real-time progress in non-task-initiating views, thus improving multi-task management efficiency and user experience.

[0005] To achieve the above objectives, the embodiments of this application provide the following technical solutions: According to a first aspect of the embodiments of this application, a task status prompting method is provided, the method comprising: In the first application view that initiates the background task, monitor the execution status of the background task and determine whether the first application view is currently the focus of the user's operation. If the first application view is not currently in the user's focus, the corresponding visual cue parameters are determined based on the execution status of the background task; The visual cue parameters are synchronized from the first application view to the second application view that is currently in the user's focus, so that in the second application view, the visual appearance of a specific non-content area of ​​the second application view is changed according to the visual cue parameters to indicate the execution status of the background task to the user.

[0006] Optionally, synchronizing the visual cue parameters from the first application view to the second application view that is currently the focus of the user's operation includes: The determined visual cue parameters are encrypted to generate encrypted target synchronization parameters; The target synchronization parameters are stored in a shared storage area between the first application view and the second application view, and a storage identifier associated with the unique identifier of the background task is configured for the target synchronization parameters. Register a parameter change listener for the shared storage area in the second application view, and monitor the parameter changes corresponding to the storage identifier in real time through the parameter change listener. When a parameter change is detected, the target synchronization parameter is decrypted to restore the visual cue parameter, thus completing the synchronization of the visual cue parameter.

[0007] Optionally, in the second application view, changing the visual appearance of a specific non-content area of ​​the second application view according to the visual cue parameters includes: The received visual cue parameters are parsed to extract control information characterizing the visual change pattern of the specific non-content area; The visual appearance control function is invoked to adjust the display state of the specific non-content area, thereby achieving dynamic visual cues for the specific non-content area.

[0008] Optionally, the method further includes: Real-time detection of whether the background task has been completed; If the background task is completed, the instruction parameter to stop visual changes will be passed to the visual appearance control function to terminate the operation of the visual appearance control function and restore the display state of the specific non-content area to the initial display state.

[0009] Optionally, the method further includes: When the first application view returns to the user's current focus, the determination of the visual cue parameters and the synchronization of the visual cue parameters are stopped. A visual state recovery instruction is sent to the second application view so that the second application view restores the display state of the specific non-content area to its initial display state according to the visual state recovery instruction.

[0010] Optionally, the corresponding visual cue parameters are determined based on the execution status of the background task, including: Based on the preset mapping rules between background task execution status and visual cue parameters, the execution status of the background task is matched to the corresponding associated item in the mapping rules, and the visual cue parameters in the associated item are retrieved.

[0011] Optionally, the mapping rule between the background task execution status and the visual cue parameters is determined as follows: The execution status of the background task is divided into several consecutive execution status intervals, and each execution status interval covers the entire execution process of the background task from start to completion; Configure corresponding visual cue parameters for each execution state interval; The execution completion status is divided into execution completion intervals, and instruction parameters to stop visual changes are configured for the execution completion intervals; The mapping rule is formed by integrating the correspondence between each execution state interval, the completed execution interval and the corresponding visual cue parameters; the visual cue parameters are parameters that control the visual change pattern of specific non-content areas, and the visual cue parameters include time interval parameters or frequency parameters of visual changes.

[0012] Optionally, determining whether the first application view is currently in the user's focus includes: Call the view state detection interface to obtain the real-time state parameters of the first application view; Based on the real-time status parameters, identify whether the first application view is currently the user's focus. Generate a determination result to identify whether the first application view is in focus or not.

[0013] Optionally, monitoring the execution status of the background task includes: Real-time collection of execution process data for the background tasks; The execution process data is calculated and processed according to preset state transition rules to obtain execution state parameters that characterize the degree of completion of the background task; The execution status parameter is used as the execution status of the background task.

[0014] According to a second aspect of the embodiments of this application, a task status prompting system is provided, the system comprising: The task status monitoring module is used to monitor the execution status of the background task in the first application view that initiates the background task, and to determine whether the first application view is currently the focus of the user's operation. The parameter determination module is used to determine the corresponding visual prompt parameters based on the execution status of the background task if the first application view is not in the user's current focus. A visual cue module is used to synchronize the visual cue parameters from the first application view to the second application view that is currently in the user's focus, so that in the second application view, the visual appearance of a specific non-content area of ​​the second application view is changed according to the visual cue parameters to prompt the user about the execution status of the background task.

[0015] According to a third aspect of the present application, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in the first aspect above.

[0016] According to a fourth aspect of the embodiments of this application, a computer-readable storage medium is provided having computer-readable instructions stored thereon, the computer-readable instructions being executable by a processor to implement the method described in the first aspect above.

[0017] In summary, this application provides a method and system for indicating task status. By monitoring the execution status of a background task in a first application view that initiates the task, and determining whether the first application view is currently the user's focus, when the first application view is not currently the user's focus, corresponding visual cue parameters are determined based on the background task's execution status. These visual cue parameters are then synchronized to a second application view that is currently the user's focus. This causes the second application view to change the visual appearance of specific non-content areas according to the visual cue parameters, thus indicating the background task's execution status to the user. This achieves cross-application view background task status indication, allowing users to perceive the background task's progress in real-time within the view where their current focus is located even after switching to another application view. This solves the problem of users being unable to perceive the background task status or grasp the real-time progress of tasks in non-task-initiating views, improving multi-task management efficiency and user experience. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0019] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0020] Figure 1 A flowchart of a task status prompting method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the overall process of the task status prompting method provided in the embodiments of this application; Figure 3 This is a schematic diagram illustrating the actual display effect in the title area of ​​a browser tab, provided in an embodiment of this application. Figure 4 This is a schematic diagram of a task status prompting system provided in an embodiment of this application; Figure 5 This paper shows a structural diagram of an electronic device provided in an embodiment of this application; Figure 6 A diagram of a computer-readable storage medium provided in an embodiment of this application is shown.

[0021] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0023] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0024] Furthermore, in this invention, descriptions involving "first," "second," etc., are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0025] In this invention, unless otherwise explicitly specified and limited, the terms "connection," "fixed," etc., should be interpreted broadly. For example, "fixed" can mean a fixed connection, a detachable connection, or an integral part; it can mean a mechanical connection or an electrical connection; it can mean a direct connection or an indirect connection through an intermediate medium; it can mean the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0026] Furthermore, the technical solutions of the various embodiments of the present invention can be combined with each other, but only if they are feasible for those skilled in the art. If the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such combination of technical solutions does not exist and is not within the scope of protection claimed by the present invention.

[0027] Figure 1 This application illustrates a task status prompting method provided by an embodiment of the present application. The method includes: Step 101: In the first application view that initiates the background task, monitor the execution status of the background task and determine whether the first application view is currently the focus of the user's operation. Step 102: If the first application view is not currently in the user's focus, determine the corresponding visual cue parameters based on the execution status of the background task; Step 103: Synchronize the visual cue parameters from the first application view to the second application view that is currently in the user's focus, so that in the second application view, the visual appearance of a specific non-content area of ​​the second application view is changed according to the visual cue parameters to prompt the user about the execution status of the background task.

[0028] The task status prompting method provided in this application addresses the problem of users being unable to ascertain the execution status of background tasks after switching application views, thereby improving information perception efficiency and operational experience in multi-tasking scenarios. This method monitors the execution status of the background task in real time within the first application view that initiated the task, and simultaneously determines whether this view is the user's current focus to decide whether to send task status prompts. When the first application view is not the user's current focus, the corresponding visual prompt parameters are determined according to the actual execution status of the background task, ensuring that the prompt accurately reflects the current execution stage of the task.

[0029] The visual cues are then synchronized to the second application view, which is the focus of the user's interaction. This second application view then changes the visual appearance of specific non-content areas to indicate the execution status of the background task to the user. This cross-view notification method allows users to intuitively view the progress of background tasks without remaining in the task initiation view, ensuring uninterrupted use while providing timely updates on task execution and improving multitasking efficiency.

[0030] In one possible implementation, step 101, monitoring the execution status of the background task, includes: collecting execution process data of the background task in real time; calculating and processing the execution process data according to a preset state transition rule to obtain an execution status parameter characterizing the degree of completion of the background task; and using the execution status parameter as the execution status of the background task.

[0031] In one possible implementation, in step 101, determining whether the first application view is currently in the user's focus includes: calling a view state detection interface to obtain real-time state parameters of the first application view; identifying whether the first application view is currently in the user's focus based on the real-time state parameters; and generating a determination result to identify whether the first application view is in focus or not.

[0032] This application embodiment also provides a specific implementation method for monitoring the execution status of background tasks in step 101. During actual execution, execution process data of the background tasks is collected in real time, reflecting the real-time progress of the tasks. Then, according to preset state transition rules, the collected execution process data is processed to obtain execution status parameters that characterize the degree of completion of the background tasks. Finally, these execution status parameters are used as the execution status of the background tasks, achieving accurate monitoring of the background task execution status.

[0033] Meanwhile, in step 101, determining whether the first application view is currently in the user's focus involves calling a view state detection interface. This interface retrieves real-time state parameters of the first application view, reflecting its current display state and user interaction. Based on these parameters, the system further identifies whether the first application view is currently in the user's focus and generates a corresponding result. This result clearly indicates whether the first application view is currently in focus or not, providing an accurate basis for determining whether to trigger a cross-view prompt.

[0034] In one possible implementation, in step 102, determining the corresponding visual cue parameters based on the execution status of the background task includes: matching the execution status of the background task to the corresponding associated item in the mapping rule based on a preset mapping rule between the execution status of the background task and the visual cue parameters, and retrieving the visual cue parameters in the associated item.

[0035] In one possible implementation, the mapping rule between the background task execution state and the visual cue parameters is determined as follows: the execution state of the background task is divided into several consecutive execution state intervals, each execution state interval covering the entire execution process of the background task from start to completion; a corresponding visual cue parameter is configured for each execution state interval; the execution completion state is divided into a completion execution interval, and an instruction parameter to stop visual changes is configured for the completion execution interval; the correspondence between each execution state interval, the completion execution interval, and the corresponding visual cue parameter is integrated to form the mapping rule; the visual cue parameter is a parameter that controls the visual change pattern of a specific non-content area, and the visual cue parameter includes a time interval parameter or a frequency parameter for visual changes.

[0036] In one possible implementation, the specific implementation method of determining the corresponding visual cue parameters based on the execution status of the background task in step 102 is based on a preset mapping rule between the execution status of the background task and the visual cue parameters. Specifically, the execution status of the background task is first divided into several consecutive execution status intervals. These intervals cover the entire process of the background task from start to completion, ensuring that each execution stage corresponds to the corresponding visual cue parameters.

[0037] For each defined execution state interval, corresponding visual cue parameters are configured. These parameters are primarily used to control the visual change patterns of specific non-content areas, including the time interval and frequency parameters for visual changes. These parameters allow for precise control over the presentation effect of the visual cue. Simultaneously, the execution completion state is divided into a separate completion execution interval, for which a command parameter is configured to stop visual changes. This ensures that visual cueing stops promptly after the background task is completed, avoiding unnecessary resource consumption.

[0038] Finally, the correspondence between all execution status intervals, completion execution intervals, and corresponding visual cue parameters is integrated to form a complete mapping rule between background task execution status and visual cue parameters. Subsequently, the execution status of the background task can be matched with this mapping rule to quickly retrieve the corresponding visual cue parameters, ensuring that the visual cue can accurately reflect the actual execution status of the background task.

[0039] In one possible implementation, step 103, synchronizing the visual cue parameters from the first application view to the second application view currently in the user's focus, includes: encrypting the determined visual cue parameters to generate encrypted target synchronization parameters; storing the target synchronization parameters in a shared storage area between the first and second application views, and configuring a storage identifier associated with the unique identifier of the background task for the target synchronization parameters; registering a parameter change monitoring program for the shared storage area in the second application view, and monitoring parameter changes corresponding to the storage identifier in real time through the parameter change monitoring program; when a parameter change is detected, decrypting the target synchronization parameters to restore the visual cue parameters, thus completing the synchronization of the visual cue parameters.

[0040] In one possible implementation, step 103, which synchronizes the visual cue parameters from the first application view to the second application view, is achieved through data encryption, shared storage, and a monitoring mechanism. The system first encrypts the determined visual cue parameters to generate encrypted target synchronization parameters, then stores these parameters in a shared storage area between the first and second application views, and configures a storage identifier associated with a unique background task identifier for accurate identification and retrieval later.

[0041] The second application view registers a parameter change listener in the shared storage area, which continuously monitors parameter changes under the corresponding storage identifier. When an update is detected for the parameter corresponding to the storage identifier, the second application view decrypts the encrypted target synchronization parameter to restore the original visual cue parameter, thus completing the full synchronization of the visual cue parameter from the first application view to the second application view.

[0042] In one possible implementation, in step 103, changing the visual appearance of a specific non-content area in the second application view according to the visual cue parameters includes: parsing the received visual cue parameters and extracting control information characterizing the visual change pattern of the specific non-content area; calling a visual appearance control function to adjust the display state of the specific non-content area and realize dynamic visual cueing for the specific non-content area.

[0043] In one possible implementation, the specific process of the second application view changing the visual appearance of a specific non-content area according to the visual cue parameters in step 103 is as follows: First, the received visual cue parameters are parsed to extract the control information representing the visual change pattern of the specific non-content area, clarifying the specific rules and requirements of the visual change. Then, the visual appearance control function is called to adjust the display state of the specific non-content area according to the parsed control information, achieving a dynamic visual cue effect. The entire process does not require any additional operation steps; it only uses existing parameters and control functions to complete the visual adjustment of the specific non-content area, ensuring that the visual cue is clear and distinguishable, while not affecting the normal use of the second application view itself. This not only fits the overall technical solution but also accurately conveys the execution status of the background task, meeting the needs of cross-view status prompts and avoiding redundant operations and interference from invalid information.

[0044] In one possible implementation, after step 103, the method further includes: detecting in real time whether the background task has been completed; if the background task has been completed, passing the instruction parameter to stop visual changes to the visual appearance control function to terminate the operation of the visual appearance control function, and restoring the display state of the specific non-content area to the initial display state.

[0045] In one possible implementation, after the visual cues are completed in step 103, the method continuously monitors the execution progress of the background task. When the background task is detected to be completed, the system passes the instruction parameter to stop visual changes to the visual appearance control function, terminates the operation of the visual appearance control function, and restores the display state of a specific non-content area in the second application view to its initial display state, so that the interface returns to the display effect before the task execution.

[0046] In one possible implementation, after step 103, the method further includes: when the first application view returns to the user's current focus, stopping the determination operation of the visual cue parameter and the synchronization operation of the visual cue parameter; sending a visual state recovery instruction to the second application view, so that the second application view restores the display state of the specific non-content area to the initial display state according to the visual state recovery instruction.

[0047] In one possible implementation, after step 103, the method further monitors the focus state of the first application view. When the first application view regains the user's current focus, the system stops the determination of visual cue parameters and the synchronization of parameters between views, and sends a visual state restoration command to the second application view. Upon receiving the command, the second application view restores the display state of a specific non-content area to its initial display state, completing the final processing of the cue process.

[0048] The task status prompting method provided in the embodiments of this application will be further explained below with reference to the accompanying drawings.

[0049] The task status prompting method provided in this application addresses the problem of users being unable to ascertain the background task execution status after switching application views, thereby improving information perception efficiency and operational experience in multi-tasking scenarios. This method dynamically adjusts the visual change rhythm of specific non-content areas within the application view to provide intuitive prompts for multi-task progress status. This overcomes the shortcomings of existing visual prompts, which only provide simple notifications and cannot be linked to task progress. It achieves dynamic binding between progress status and visual change rhythm, improving progress perception efficiency in cross-view scenarios. This method establishes a mapping rule between task progress and visual prompt parameters, combining view visibility detection and cross-view communication mechanisms to allow users to perceive the multi-task execution status in real time through visual changes in the current operating view, without relying on in-page controls.

[0050] The method in this application mainly includes four core modules: task monitoring, visual rule mapping, cross-view synchronization, and dynamic rhythm adjustment. Figure 2 The overall flowchart of the task status prompting method provided in the embodiments of this application is shown, which mainly includes four stages: multi-task progress parameter acquisition, flashing rhythm mapping model construction, cross-tab progress synchronization, and dynamic adjustment and stopping of flashing rhythm.

[0051] During the multi-task progress parameter acquisition phase, the progress values ​​of each background task are acquired in real time through the task monitoring module. The range can be set from 0 to 100, and it is detected whether the first application view is currently the focus of the user's operation. In the blinking rhythm mapping model construction phase, multi-dimensional mapping rules are preset to convert task progress parameters into visual cue parameters, including the time interval and frequency parameters of visual changes, and parameters are configured to stop visual changes when the task is completed. In the cross-tab progress synchronization phase, the visual cue parameters are encrypted and stored in a shared storage area based on the same environment. The second application view acquires and decrypts these parameters in real time through an event listening mechanism, completing the cross-view synchronization of parameters. In the blinking rhythm dynamic adjustment and stopping phase, the second application view dynamically adjusts the display state of specific non-content areas based on the synchronized visual cue parameters, and stops visual changes and restores the initial interface state when the task is completed or the focus is switched back.

[0052] In the first application view that initiates a background task, the execution status of the background task is monitored in real time. Simultaneously, it's determined whether the view is currently the user's focus, thus deciding whether to send task status notifications. Specifically, when monitoring the background task's execution status, execution process data is collected in real time, reflecting the task's real-time progress. Then, according to preset state transition rules, the collected execution process data is processed to obtain execution status parameters characterizing the background task's completion level. These execution status parameters are then used as the background task's execution status, achieving precise monitoring of its execution. When determining whether the first application view is currently the user's focus, a view status detection interface is called to obtain real-time status parameters reflecting the view's current display state and user interaction. Based on these parameters, the user further identifies whether the first application view is currently the user's focus and generates a corresponding judgment result. This result clearly identifies whether the first application view is currently in focus or not, providing an accurate basis for whether to trigger cross-view notifications.

[0053] When the primary application view is not currently in the user's focus, the corresponding visual cue parameters are determined according to the actual execution status of the background task, ensuring that the cue information accurately reflects the current execution stage of the task. This is achieved based on a preset mapping rule between the background task execution status and the visual cue parameters.

[0054] Next, a flashing rhythm mapping model is constructed, with preset multi-dimensional mapping rules to transform the progress parameters of background tasks into visual cue parameters. The task progress can be divided into several continuous intervals, with different progress intervals corresponding to different visual change interval parameters. For example, progress from 0% to 30% corresponds to a flashing interval of 500 milliseconds, 31% to 70% to 300 milliseconds, and 71% to 99% to 150 milliseconds. At 100% progress, a command parameter to stop visual changes is configured, thus achieving precise matching between progress status and visual cue effects. For each defined execution state interval, corresponding visual cue parameters are configured. These parameters are mainly used to control the visual change patterns of specific non-content areas, including the time interval and frequency parameters of visual changes. These parameters precisely control the presentation effect of the visual cue. Simultaneously, the execution completion state is divided into a separate completion execution interval, with a command parameter to stop visual changes configured for this interval, ensuring that the visual cue stops promptly after the background task is completed, avoiding unnecessary resource consumption. Finally, the correspondence between all execution status intervals, completion execution intervals, and corresponding visual cue parameters is integrated to form a complete mapping rule between background task execution status and visual cue parameters. Subsequently, the execution status of the background task can be matched with this mapping rule to quickly retrieve the corresponding visual cue parameters, ensuring that the visual cue can accurately reflect the actual execution status of the background task.

[0055] Subsequently, cross-tab progress synchronization is performed, enabling multi-view communication based on a shared storage area within the same environment. The first application view initiating the task encrypts the determined visual cue parameters, generating encrypted target synchronization parameters, which are then stored in the shared storage area between the first and second application views, and configured with a storage identifier associated with the unique identifier of the background task. The second application view, which is currently the focus of the user's operation, registers a parameter change listener in the shared storage area to detect parameter changes under the corresponding storage identifier in real time. Upon detecting an update, it decrypts the encrypted parameters, restoring the original visual cue parameters, thus completing cross-view parameter synchronization.

[0056] The second application view changes the visual appearance of specific non-content areas based on the received visual cue parameters. First, the received visual cue parameters are parsed to extract control information representing the visual change pattern of the specific non-content area, clarifying the specific rules and requirements for visual changes. Then, the visual appearance control function is called to adjust the display state of the specific non-content area based on the parsed control information, achieving a dynamic visual cue effect.

[0057] Figure 3This example illustrates the actual display effect of the browser tab title area according to an embodiment of this application. The figure shows two tab title display styles with different progress states. In the upper example, a progress indicator is attached next to the tab title, showing approximately 10% progress, corresponding to a slower flashing rhythm. In the lower example, the progress is shown at approximately 68%, corresponding to a faster flashing rhythm, allowing users to quickly distinguish the task progress stage. This implementation demonstrates that the solution of this application can provide intuitive task status prompts in specific non-content areas of the application view, without relying on in-page controls, improving user perception efficiency in cross-view scenarios. The entire process requires no additional operation steps; it only uses existing parameters and control functions to complete the visual adjustment of specific non-content areas, ensuring clear and identifiable visual prompts without affecting the normal use of the second application view itself.

[0058] After completing the visual cues, the method continuously monitors the progress of background tasks. When the background task is detected as complete, the system sends a command parameter to stop visual changes to the visual appearance control function, terminates the function's execution, and restores the display state of specific non-content areas in the second application view to its initial state, returning the interface to its pre-task display state. Simultaneously, the system monitors the focus state of the first application view. When the first application view becomes the user's current focus, the system stops determining the visual cues parameters and synchronizing them between views, and sends a visual state restoration command to the second application view. Upon receiving this command, the second application view restores the display state of specific non-content areas to its initial state, completing the final processing of the cues.

[0059] It should be noted that the task status prompting method provided in this application embodiment is not only applicable to the interaction scenario between the first and second application views, but can also be extended to situations where a third, fourth, and more application views exist simultaneously. Visual prompt parameters are globally published through a shared storage area, and all application views can register listeners to detect parameter changes. The system only displays visual prompts on the single application view currently under the user's focus, avoiding interface interference caused by simultaneous prompts from multiple views and ensuring the clarity and effectiveness of the prompt information. When the task execution ends or the user switches back to the task initiation view, all application views can be synchronously reset according to a unified status recovery command, maintaining consistency in the interface display.

[0060] Regarding the number of background tasks, it supports status prompts for single background tasks and multiple parallel background tasks. For multi-tasking scenarios, by assigning a unique identifier to each background task, a relationship can be established between different tasks and their corresponding stored identifiers and visual prompt parameters. This allows the progress status of multiple tasks to be displayed differently in the same application view through different visual representations, enabling users to quickly identify the execution stage of the corresponding task based on the visual changes.

[0061] In terms of visual cues, in addition to dynamically changing visual effects, more expressive forms can be expanded according to actual needs. Different visual cue parameters can be configured for background tasks of different types and urgency levels to achieve matching between visual effects and task attributes. Visual cue parameters can include not only time interval and frequency parameters, but can also be further expanded to include color change parameters, brightness change parameters, display order parameters, etc.

[0062] Regarding data synchronization security, in addition to encrypting visual cue parameters, a data verification mechanism can be added during shared storage to ensure that parameters received by the second application view or other application views are complete and untampered with. Simultaneously, a parameter validity period can be set to prevent residual data from interfering with subsequent task prompts under abnormal circumstances, thereby improving system stability.

[0063] Regarding triggering conditions, this method can expand upon existing focus judgments with more triggering strategies. For example, it can dynamically adjust whether to activate cross-view prompts by combining application running status, current device usage mode, and user preset habits. In specific scenarios, it can also support manually enabling or disabling visual prompts, making the overall solution more flexible and applicable.

[0064] This application embodiment utilizes the aforementioned cross-view state synchronization and visual cues mechanism, allowing users to intuitively obtain background task progress in the currently operating view without remaining in the task initiation view. This ensures normal use while providing timely updates on task execution, improving the efficiency of multitasking. This method is compatible with mainstream operating environments and can be applied to scenarios such as asynchronous task processing and batch data operations, effectively enhancing multitasking management efficiency and user experience.

[0065] In summary, this application provides a task status prompting method. It monitors the execution status of a background task in a first application view that initiates the task and determines whether the first application view is currently the user's focus. When the first application view is not currently the user's focus, it determines corresponding visual prompt parameters based on the background task's execution status and synchronizes these parameters to a second application view that is currently the user's focus. This causes the second application view to change the visual appearance of specific non-content areas according to the visual prompt parameters, thus prompting the user about the background task's execution status. This achieves cross-application view background task status prompts, allowing users to perceive the background task's progress in real-time within the view where their current focus is located even after switching to another application view. This solves the problem of users being unable to perceive the background task status or grasp the real-time progress of tasks in non-task-initiating views, improving multi-task management efficiency and user experience.

[0066] Based on the same technical concept, embodiments of this application also provide a task status prompting system, such as... Figure 4 As shown, the system includes: The task status monitoring module 401 is used to monitor the execution status of the background task in the first application view that initiates the background task, and to determine whether the first application view is currently the focus of the user's operation. The parameter determination module 402 is used to determine the corresponding visual prompt parameters based on the execution status of the background task if the first application view is not in the user's current operation focus. The visual prompt module 403 is used to synchronize the visual prompt parameters from the first application view to the second application view that is currently in the user's focus, so that in the second application view, the visual appearance of a specific non-content area of ​​the second application view is changed according to the visual prompt parameters, so as to prompt the user about the execution status of the background task.

[0067] This application also provides an electronic device corresponding to the method provided in the foregoing embodiments. Please refer to... Figure 5 The diagram illustrates an electronic device provided by some embodiments of this application. The electronic device 20 may include: a processor 200, a memory 201, a bus 202, and a communication interface 203, wherein the processor 200, the communication interface 203, and the memory 201 are connected via the bus 202; the memory 201 stores a computer program that can run on the processor 200, and when the processor 200 runs the computer program, it executes the method provided by any of the foregoing embodiments of this application.

[0068] The memory 201 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one physical port (which can be wired or wireless), such as the Internet, wide area network, local area network, or metropolitan area network.

[0069] Bus 202 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 201 is used to store programs. After receiving an execution instruction, the processor 200 executes the program. The method disclosed in any of the foregoing embodiments of this application can be applied to the processor 200, or implemented by the processor 200.

[0070] The processor 200 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 200 or by instructions in software form. The processor 200 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 201. The processor 200 reads the information in memory 201 and, in conjunction with its hardware, completes the steps of the above method.

[0071] The electronic devices and methods provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods they employ, operate, or implement.

[0072] This application also provides a computer-readable storage medium corresponding to the method provided in the foregoing embodiments. Please refer to... Figure 6The computer-readable storage medium shown is an optical disc 30, on which a computer program (i.e., a program product) is stored, which, when run by a processor, executes the methods provided in any of the foregoing embodiments.

[0073] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0074] The computer-readable storage medium provided in the above embodiments of this application and the method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0075] It should be noted that the above embodiments are illustrative of this application and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

[0076] The above description is merely a preferred embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0077] The above description is only a preferred embodiment of the present invention and does not limit the patent scope of the present invention. All equivalent structural transformations made under the concept of the present invention using the contents of the present invention specification and drawings, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.

Claims

1. A method for indicating task status, characterized in that, The method includes: In the first application view that initiates the background task, monitor the execution status of the background task and determine whether the first application view is currently the focus of the user's operation. If the first application view is not currently in the user's focus, the corresponding visual cue parameters are determined based on the execution status of the background task; The visual cue parameters are synchronized from the first application view to the second application view that is currently in the user's focus, so that in the second application view, the visual appearance of a specific non-content area of ​​the second application view is changed according to the visual cue parameters to indicate the execution status of the background task to the user.

2. The method as described in claim 1, characterized in that, Synchronizing the visual cue parameters from the first application view to the second application view that is currently the focus of the user's operation includes: The determined visual cue parameters are encrypted to generate encrypted target synchronization parameters; The target synchronization parameters are stored in a shared storage area between the first application view and the second application view, and a storage identifier associated with the unique identifier of the background task is configured for the target synchronization parameters. Register a parameter change listener for the shared storage area in the second application view, and monitor the parameter changes corresponding to the storage identifier in real time through the parameter change listener. When a parameter change is detected, the target synchronization parameter is decrypted to restore the visual cue parameter, thus completing the synchronization of the visual cue parameter.

3. The method as described in claim 1, characterized in that, In the second application view, changing the visual appearance of specific non-content areas of the second application view according to the visual cue parameters includes: The received visual cue parameters are parsed to extract control information characterizing the visual change pattern of the specific non-content area; The visual appearance control function is invoked to adjust the display state of the specific non-content area, thereby achieving dynamic visual cues for the specific non-content area.

4. The method as described in claim 3, characterized in that, The method further includes: Real-time detection of whether the background task has been completed; If the background task is completed, the instruction parameter to stop visual changes will be passed to the visual appearance control function to terminate the operation of the visual appearance control function and restore the display state of the specific non-content area to the initial display state.

5. The method as described in claim 1, characterized in that, The method further includes: When the first application view returns to the user's current focus, the determination of the visual cue parameters and the synchronization of the visual cue parameters are stopped. A visual state recovery instruction is sent to the second application view so that the second application view restores the display state of the specific non-content area to its initial display state according to the visual state recovery instruction.

6. The method as described in claim 1, characterized in that, The corresponding visual cue parameters are determined based on the execution status of the background task, including: Based on the preset mapping rules between background task execution status and visual cue parameters, the execution status of the background task is matched to the corresponding associated item in the mapping rules, and the visual cue parameters in the associated item are retrieved.

7. The method as described in claim 6, characterized in that, The mapping rule between the background task execution status and the visual cue parameters is determined as follows: The execution status of the background task is divided into several consecutive execution status intervals, and each execution status interval covers the entire execution process of the background task from start to completion; Configure corresponding visual cue parameters for each execution state interval; The execution completion status is divided into execution completion intervals, and instruction parameters to stop visual changes are configured for the execution completion intervals; The mapping rule is formed by integrating the correspondence between each execution state interval, the completed execution interval and the corresponding visual cue parameters; the visual cue parameters are parameters that control the visual change pattern of specific non-content areas, and the visual cue parameters include time interval parameters or frequency parameters of visual changes.

8. The method as described in claim 1, characterized in that, Determining whether the first application view is currently in the user's focus includes: Call the view state detection interface to obtain the real-time state parameters of the first application view; Based on the real-time status parameters, identify whether the first application view is currently the user's focus. Generate a determination result to identify whether the first application view is in focus or not.

9. The method as described in claim 1, characterized in that, Monitoring the execution status of the background tasks includes: Real-time collection of execution process data for the background tasks; The execution process data is calculated and processed according to preset state transition rules to obtain execution state parameters that characterize the degree of completion of the background task; The execution status parameter is used as the execution status of the background task.

10. A task status prompting system, characterized in that, The system includes: The task status monitoring module is used to monitor the execution status of the background task in the first application view that initiates the background task, and to determine whether the first application view is currently the focus of the user's operation. The parameter determination module is used to determine the corresponding visual prompt parameters based on the execution status of the background task if the first application view is not in the user's current focus. A visual cue module is used to synchronize the visual cue parameters from the first application view to the second application view that is currently in the user's focus, so that in the second application view, the visual appearance of a specific non-content area of ​​the second application view is changed according to the visual cue parameters to prompt the user about the execution status of the background task.

Images