CN111124210B

CN111124210B - List management method and electronic equipment

Info

Publication number: CN111124210B
Application number: CN202010145184.6A
Authority: CN
Inventors: 刘芳芳; 张斌
Original assignee: Individual
Current assignee: Individual
Priority date: 2019-03-19
Filing date: 2020-03-04
Publication date: 2021-09-07
Anticipated expiration: 2040-03-04
Also published as: CN109947322A; CN111124210A

Abstract

The embodiment of the application provides a list management method and electronic equipment, wherein the list management method comprises the following steps: displaying prompt information of the event list in the first floating window; judging whether the current time meets the reminding condition of each event to be handled in the event list; when the current time meets the reminding condition of a first event in the event list, displaying the content of the first event in a second floating window, wherein the first event is any event to be handled in the event list, and the stacking priority of the first floating window and the second floating window on the current interface is higher than that of other windows on the current interface. Therefore, the problems that prompt is inconvenient to carry out at any time and operation is complicated when a list is checked in the prior art can be solved.

Description

List management method and electronic equipment

Technical Field

The application relates to the field of windows, in particular to a list management method and electronic equipment.

Background

In the daily learning, working and living process, people always have various things to be processed, and in order to achieve the purpose of memorandum, the affairs needed to be processed in a period of time in the future are arranged in advance and effectively recorded so as to improve the processing efficiency. Compared with a non-electronic recording mode, the task event list is recorded by adopting the electronic terminals such as the computer, the mobile phone, the electronic watch and the like, so that the method is more convenient and more flexible, and resources can be saved.

However, the conventional list software is inconvenient for reminding a user at any time, and the user usually needs to select the list software as a current operation interface to check the information in the list, so that the operation is complicated.

Disclosure of Invention

In view of this, an object of the present invention is to provide a method for managing a list and an electronic device, so as to solve the problems that in the prior art, prompt is not convenient at any time, and the operation is complicated when the list is viewed.

In a first aspect, an embodiment of the present application provides a method for list management, where the method includes:

displaying prompt information of the event list in the first floating window;

judging whether the current time meets the reminding condition of each event to be handled in the event list;

when the current time meets the reminding condition of a first event in the event list, displaying the content of the first event in a second floating window, wherein the first event is any event to be handled in the event list, and the stacking priority of the first floating window and the second floating window on the current interface is higher than that of other windows on the current interface.

In the implementation process, because the stacking priority of the floating window on the current interface is higher than that of other common windows, the floating window is adopted to display the prompt message of the event list, so that the effect of reminding at any time can be achieved. For the user, on one hand, brief contents of the event list, namely prompt information of the event list, can be focused through the first floating window, and on the other hand, contents of one or more events to be handled can be focused through the second floating window. Because the operation required for viewing the prompt message of the event list is omitted, the user can pay attention to the prompt message of the event list without selecting list software as a current operation interface. Even if the user works in the windows of other software, the user does not need to additionally perform window switching operation to check the related information of the event list, and the working efficiency is favorably improved.

With reference to the first aspect, in one possible design, the method further includes: responding to the interface setting operation of the first floating window to obtain a setting parameter in the interface setting operation; and changing the display attribute of the first floating window according to the setting parameter.

In the implementation process, the display attribute of the first floating window may be changed, and the display attribute may include size, color, shape, and the like. Display attributes can be changed to display various display interfaces, and display conflicts or interferences between the first floating window and other windows in the current interface are avoided.

With reference to the first aspect, in one possible design, the method further includes: in response to the viewing operation of the first floating window and/or the second floating window, displaying the content of part or all of the events to be handled in the event list in a third window associated with the first floating window and/or the second floating window, wherein the size of the third window is larger than that of the first floating window and the second floating window.

In the implementation process, after the floating window is viewed, a third window can be displayed, the third window can display the contents of a plurality of events to be handled in the event list, and can display the specific contents of all events in the event list. Since the third window is larger in size than the first floating window and the second floating window, the third window may show more detailed manifest information than the first floating window and the second floating window.

With reference to the first aspect, in one possible design, the method further includes: acquiring the display time length of the third window; judging whether the display time length meets a preset monitoring time length or not; and when the display time length meets the preset monitoring time length, closing the third window and displaying the first floating window.

In the above implementation, the third window may be automatically closed. For example, when the display duration of the third window reaches a certain time length, the third window may be switched back to the first floating window, so as to avoid the user from being disturbed by the too long display duration of the third window.

With reference to the first aspect, in one possible design, the second floating window is further configured to display labeled buttons, where the labeled buttons include a completion button and a delay button, and the method further includes: marking the first event as a completed state in response to a first marking operation for the completion button; or responding to a second marking operation of the delay button, obtaining a delay reminding time in the second marking operation, and setting the next reminding time of the first event as the delay reminding time.

In the implementation process, a single event to be handled can be operated through the marking button on the second suspension window, and the operation mode is convenient and fast. The marking of the appointed event or the deferred reminding of the appointed event can be finished only by simple marking operation, so that the repeated reminding of the same event can be avoided.

With reference to the first aspect, in one possible design, the prompt information includes summary information of the to-do events in the event list, and the summary information includes the number of the to-do events in the event list.

In the implementation process, the first floating window can display the number of the events to be handled in the event list, and a user can pay attention to the number of the events to be handled at any time, so that the user can reasonably arrange time to complete the corresponding events to be handled.

With reference to the first aspect, in one possible design, the method further includes: and responding to a first switching operation of the first floating window, and switching the first floating window into a common window, wherein the common window is a non-floating window.

In the implementation process, a mode for changing the display state of the first floating window is provided. The floating window can be retained without changing the state of the first floating window, and after the first switching operation is performed, the first floating window can be temporarily switched to the ordinary window in the non-floating state.

With reference to the first aspect, in one possible design, the method further includes: and responding to an event increment triggering operation of the first floating window, and displaying a fourth window, wherein the fourth window is used for acquiring the input content of the newly added event.

Through the implementation process, the first floating window based on the floating state is beneficial to quickly adding new events.

With reference to the first aspect, in one possible design, the fourth window includes an input prompt box and an event setting item, and the method further includes: and responding to the setting triggering operation of the event setting item, and setting an event attribute for the input content of the newly added event after detecting the input content of the newly added event in the input prompt box.

Through the implementation process, the method is beneficial to quickly adding new event content and completing the attribute setting.

With reference to the first aspect, in one possible design, after setting an event attribute for the input content of the newly added event, the method further includes: and updating the display content in the first floating window based on the event attribute of the newly added event.

Through the implementation process, a mode of rapidly updating the display content of the first floating window is provided, the event attribute of the newly added event can be automatically updated after being set, and the phenomenon that a user delays the processing of the newly added event due to forgetting to update can be avoided to a certain extent.

With reference to the first aspect, in one possible design, the method further includes: responding to a preview operation of the first floating window, and displaying preview information of at least one event to be handled in the event list in a preview floating window associated with the first floating window, wherein the preview information is obtained according to a set data filtering strategy; and responding to an event attribute updating operation of the preview information in the preview floating window, and updating an event attribute for the event to be handled corresponding to the preview information, wherein the event attribute comprises at least one of the current completion state, the reminding time, the title and the event priority level of the event.

The implementation process provides an implementation mode which can preview an event list and quickly update the attributes of the event.

With reference to the first aspect, in one possible design, the window body of the first floating window is transparent.

In the implementation process, the transparent window body can be distinguished from other non-transparent components, and the interference to other windows can be reduced.

With reference to the first aspect, in one possible design, the displaying a prompt message of the event list in the first floating window includes: logging in a list management system through a user account to acquire list data of the user account; and obtaining prompt information of the event list according to the list data, and displaying the prompt information in the first floating window.

In the implementation process, the prompt information corresponding to the user account is obtained by acquiring the list data of the user account, and data synchronization can be achieved even if the user uses the list management software in different places. In addition, the problem of data confusion caused by using the same equipment by a plurality of users can be avoided.

In a second aspect, an embodiment of the present application further provides a list management apparatus, where the apparatus includes:

the display module is used for displaying prompt information of the event list in the first floating window;

the judging module is used for judging whether the current time meets the reminding condition of each event to be handled in the event list;

the display module is further configured to display content of a first event in a second floating window when a current time meets a reminding condition of the first event in the event list, where the first event is any event to be handled in the event list, and stacking priorities of the first floating window and the second floating window on a current interface are higher than those of other windows on the current interface.

In the implementation process, the list management device can execute the list management method according to the first aspect, and the list management device can play a role of reminding at any time, so that a user can pay attention to the prompt information of the event list without selecting list software as a current operation interface.

In a third aspect, an embodiment of the present application further provides an electronic device, where the electronic device includes: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the electronic device is operating, the machine-readable instructions when executed by the processor performing the steps of the method of the first aspect.

In a fourth aspect, the present invention further provides a readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, performs the steps in the method according to the first aspect.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Fig. 2 is a flowchart of a list management method according to an embodiment of the present application.

Fig. 3 is a schematic view of a first floating window in an example provided by an embodiment of the present application.

Fig. 4 is a schematic view of a second floating window in an example provided by an embodiment of the present application.

Fig. 5 is a schematic diagram of a third window in an example provided by the embodiment of the present application.

Fig. 6 is a schematic diagram illustrating an example of triggering a first floating window according to an embodiment of the present application.

Fig. 7 is a schematic diagram of a fourth window in an example provided by the embodiment of the present application.

Fig. 8 is a schematic diagram of a preview floating window in an example provided by an embodiment of the present application.

Fig. 9 is a functional structure block diagram of a list management apparatus according to an embodiment of the present application.

Detailed Description

The technical solution in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

The inventor finds that, for the traditional list software, when a user works in other software and windows of other webpages, the user cannot pay attention to the event to be handled, and the traditional list software cannot play a function of reminding the user at any time.

For example, when a user opens a plurality of applications, only the full screen interface corresponding to one of the applications is the current operation interface, but the other application interfaces including the application to which the conventional list software belongs are not the current operation interface, and at this time, if the user wants to view information related to the list, the user needs to select the interface of the list software as the current operation interface. Moreover, if a user wants to perform operations (such as adding and modifying the status) on the list, the user needs to switch to the list software window to complete the operations, and after the operations on the list software are completed, the user needs to switch back to another window to return to the interface of another software for work.

The defects of the method cause that the traditional inventory software is difficult to use and can influence the working efficiency of a user.

In the solution provided by the inventor, a floating window with a higher stack priority is used to display the prompt information of the event list, so that the effect of reminding the user at any time can be achieved, and the defect that the user can only check the content of the list after selecting the list software as the current operation interface is overcome.

Referring to fig. 1, fig. 1 is a schematic structural diagram of an electronic device 100 according to an embodiment of the present disclosure. The electronic device 100 may be a Personal Computer (PC), a tablet PC, a smart phone, a Personal Digital Assistant (PDA), or the like. Each user may have a user account, and the user may perform inventory management through the electronic device 100. For example, the electronic device 100 may log in a list management system to obtain list data of a corresponding user account, obtain prompt information of an event list associated with the user account, operate each event to be handled in the prompt information through the electronic terminal, and add or delete the event list through the electronic device 100. Where the event list may be managed using groups, there may be zero, one, or multiple groups, for example. The content of the event list may include various to-do events, media messages, internet links, etc.

The electronic device 100 includes: a memory 110, a processor 120, and a bus, the memory 110 storing machine-readable instructions executable by the processor 120, the processor 120 communicating with the memory 110 via the bus when the electronic device 100 is operating, the machine-readable instructions when executed by the processor 120 performing the steps of the inventory management method described below.

The Memory 110 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Read Only Memory (EPROM), an electrically Erasable Read Only Memory (EEPROM), and the like. The memory 110 may be used to store a program, for example, a software program corresponding to the inventory management device described below, and the processor 120 may execute the program stored in the memory 110 after receiving the execution instruction.

The Processor 120 has signal Processing capability, and may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The processor 120 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or the processor 120 may be any conventional processor or the like.

Optionally, the electronic device 100 further comprises a display unit 130, and the display unit 130 is connected to the processor 120 and also connected to the memory 110. The display unit 130 provides an interactive interface (e.g., a user operation interface) between the server (or the local terminal) and the user or serves to display information related to the event list to the user reference. In the present embodiment, the display unit 130 may be a liquid crystal display or a touch display. In the case of a touch display, the display can be a capacitive touch screen or a resistive touch screen, which supports single-point and multi-point touch operations. Supporting single-point and multi-point touch operations means that the touch display can sense touch operations from one or more locations on the touch display at the same time, and the sensed touch operations are sent to the processor 120 for calculation and processing.

In a specific implementation process, the electronic device 100 may include more or less structures than those shown in fig. 1, for example, the electronic device 100 may further include structures such as a mouse and a keyboard, and the like, which are not limited to the structures shown in fig. 1.

Referring to fig. 2, fig. 2 is a flowchart of a list management method according to an embodiment of the present application. The list management method may be applied to the electronic device 100 shown in fig. 1. If the electronic device 100 is a computer, the list management method may be applied to various operating systems of the computer, where the operating systems include Mac os, Windows, Linux, Android, and the like.

The specific process shown in fig. 2 will be described in detail below, and the steps include: S21-S23.

S21: and displaying prompt information of the event list in the first floating window.

The event list may include, but is not limited to: backlog, total event, partial event obtained after filtering, other media message and other notification message. These events or messages may be referred to as "to-do events" in the embodiments of the present application.

The prompt message of the event list can be the summary message of part or all of the events, such as the number, the keywords, the remark content, etc.

S22: and judging whether the current time meets the reminding condition of each event to be handled in the event list.

S23: and when the current time meets the reminding condition of the first event in the event list, displaying the content of the first event in the second floating window. The first event is any event to be handled in the event list, and the stacking priority of the first floating window and the second floating window on the current interface is higher than that of other windows on the current interface. The other windows on the current interface are common windows except the first floating window and the second floating window on the current interface, and the common windows are non-floating windows.

As one implementation, the to-do event may be an event in the event list that is not marked "complete". The first event may also represent a type of event, representing a type of event that requires a reminder at the current time. If the current time meets the reminding condition of one or more to-do events in the event list, the one or more to-do events may be collectively referred to as a first event, that is, the second floating window may display the content of a single event, or may display the content of multiple events.

The reminding condition comprises preset reminding time, a reminding time range, attributes of corresponding events to be handled and the like. It should be noted that, when one of the events to be handled X is marked as "no reminder", even if the current time reaches the set reminder time, the specific content of the event to be handled X may not be displayed in the second floating window.

Optionally, the window of the first floating window may be smaller than or equal to the window of the second floating window. When the size of the first floating window is the same as that of the second floating window, if a first event needs to be reminded, the second floating window can replace the first floating window to display; when the size of the first floating window is smaller than that of the second floating window, the contents in the first floating window and the second floating window may be simultaneously displayed.

Alternatively, the second floating window may display more content than the first floating window.

In one embodiment, the number of events respectively corresponding to the multiple types of event lists in each group can be displayed in a first floating window, and the content of one or more events can be displayed in a second floating window associated with the first floating window.

As another embodiment, the number of listings and the first notification information may be displayed in a first floating window and the number of listings and the second notification information may be displayed in a second floating window. The second notification information represents more detailed information than the first notification information.

In terms of the window floating angle, the first floating window and/or the second floating window may be floated on other full-screen or non-full-screen windows. In a multi-desktop operating system, after desktop switching is performed, the floating window can be suspended on an activated desktop, the floating window can be dragged to any position or a designated position on the desktop, and software functions are not affected in the dragging process. For example, some components in the window may be set to be draggable, other components may be set to be un-draggable, and when the draggable components are dragged, the entire window is dragged at the same time. The method comprises the steps of obtaining a window position of a user, and obtaining a window position of the user, wherein the window position of the user can be obtained when the user initializes the window position every time, so that the floating window is more suitable for the use habit of the user.

It should be noted that the stacking priority between the first floating window and the second floating window is not to be construed as a limitation to the present application, and if the first floating window and the second floating window are displayed simultaneously, the stacking priority of the first floating window and the second floating window may be the same, and if only the first floating window or the second floating window is displayed, the stacking priority of the first floating window and the second floating window may be different.

Through the implementation process, the stacking priority of the floating window on the current interface is higher than that of other common windows, and the effect of reminding at any time can be achieved by displaying the prompt message of the event list through the floating window. The user can not only pay attention to the brief content of the event list, namely the prompt information of the event list, through the first floating window, but also pay attention to the content of the first event through the second floating window. In the implementation process, the operation steps required for viewing the prompt information of the event list are omitted, and a user can pay attention to the prompt information of the event list even if the list software is not selected as the current operation interface. When the user works in the windows of other software in the current interface, the related information of the event list can be checked without additionally carrying out window switching operation, the operation cost is low, and the work efficiency is favorably improved. In addition, in the implementation process, even if other windows in the current interface are displayed in a full-screen mode, the prompt information of the event list can still be displayed in the current interface, and the prompt function can be played at any time.

Optionally, based on the first floating window or the second floating window, the inventory management method may further include step S24: and in response to the viewing operation of the first floating window and/or the second floating window, displaying the content of part or all of the events to be handled in the event list in a third window associated with the first floating window and/or the second floating window, wherein the size of the third window is larger than that of the first floating window and the second floating window.

In one embodiment, the viewing operation may be any one of a single click, a double click, a triple click, a mouse-over, and a keyboard shortcut initiated on a component in the first floating window displaying the prompt message or a component in the second floating window displaying the content of the first event. And after the first floating window or the second floating window is checked, the displayed third window can be used as the current operation window. The first floating window or the second floating window may be displayed after the third window is closed.

The third window may be a floating window or a normal window, and the normal window represents a window in a non-floating state. The third window may change the tier priority as the user focuses on, manipulating the window during the implementation. The third window may show grouping conditions of the event lists, and may also show event contents respectively corresponding to each group. And the detail content of the first event can be displayed at the top by a third window which jumps out after the second floating window is subjected to the viewing operation.

The third window displays more detail than the second floating window. As an embodiment, the third window may display a plurality of groups, and the event list content of the corresponding group may be displayed under each group, and the event list in each group may include the to-do event and the historical event. The events to be handled can be sorted and displayed according to the priority and the expiration time.

The user can delete the events displayed in the third window to avoid interference caused by failure events, and can also add, edit, group and other operations to the third window.

Through the implementation process, the third window can be displayed after the floating window is checked, the third window can display the contents of a plurality of events to be handled in the event list, and the specific contents of all events in the event list can be displayed. Since the third window is larger in size than the first floating window and the second floating window, the third window may show more detailed manifest information than the first floating window and the second floating window.

Optionally, the closing manner of the second floating window may be closing after receiving a closing operation initiated by a user, or may be automatically closing after displaying a fixed time period, where the fixed time period may be ten seconds, thirty seconds, one minute, ten minutes, and the like.

Optionally, based on the above S24, the third window displaying the detailed content may also switch back to the first floating window displaying the prompt message.

As one implementation, the implementation of switching back from the third window to the first floating window may include steps S251-S253.

S251: and acquiring the display time length of the third window.

S252: and judging whether the display time length meets the preset monitoring time length.

The length of the preset monitoring time period can be arbitrarily set by a person skilled in the art, and for example, the preset monitoring time period can be half an hour, one hour, or two hours.

S253: and when the display duration of the current time meets the preset monitoring duration, closing the third window and displaying the first floating window.

After the display duration of the third window reaches a certain time length, the third window can be switched back to the first floating window, so that the situation that the display duration of the third window is too long and the user is disturbed can be avoided. And if the third window is displayed through the viewing operation of the second floating window, switching the third window back to the second floating window.

As another implementation of switching back from the third window to the first floating window, the third window may be closed and the first floating window may be displayed when the third window loses focus (e.g., when a mouse click is made on another window, another application, or a desktop).

As another implementation manner of window switching, a trigger area may be set on the operation interface in advance, and when the trigger area is triggered (for example, a mouse moves into or clicks the trigger area), the third window is closed and the first floating window is displayed.

In the implementation described above, three windows are involved: the first suspension window, the second suspension window, the third window. The three windows may be switched in state, for example, the first floating window may be switched to the second floating window, or may be switched to the third window; the second floating window can be switched to a third window and can also be switched back to the first floating window; the third window may be switched back to the first floating window or to the second floating window.

For the switching operation between any two windows, the switching operation that can be adopted includes, but is not limited to, single click, double click, triple continuous click, mouse sliding, shortcut key triggering. In the process of transitioning from the first floating window to the second floating window, because the change of the content presented by the interface is likely to be large, in order to reduce abrupt change of the interface, an interface switching scheme which is beneficial to visual optimization, such as gradual transparency change, gradual content expansion, and addition of displacement animation, can be set.

Optionally, based on the first floating window, in order to quickly add a new event, the inventory management method may further include step S31: and responding to the event increment triggering operation of the first floating window, and displaying a fourth window which is used for acquiring the input content of the newly added event.

The fourth window may be a floating window. The fourth window may include an input prompt box, an event setting item. The input content in the input prompt box can be used as the input content of the newly added event, and the attribute setting of the newly added event can be realized through the setting of the event setting item.

As an implementation manner, when the mouse identifier falls into the operation area of the first floating window, the user may be prompted to add a new event by changing the display form of the first floating window, and when the addition identifier on the first floating window is triggered, the fourth window may be displayed so as to quickly add the new event. As another implementation, when the operational area of the first floating window is triggered by a long press, double-click, a fourth window may be displayed to facilitate the addition of a new event. As still another implementation, the fourth window may be displayed by way of shortcut key triggering to facilitate quick addition of a new event.

The implementation process is beneficial to quickly adding new events based on the first floating window of the floating state.

Optionally, in addition to the first floating window, the second floating window, the third window, and the fourth window, the list management method may further include displaying a preview of the event list in the first floating window through a preview floating window, and quickly editing the event list, where the implementation includes steps S41-S42.

S41: and responding to the preview operation of the first floating window, and displaying preview information of at least one event to be handled in the event list in the preview floating window associated with the first floating window, wherein the preview information is obtained according to a set data filtering strategy.

The data filtering policy may be determined according to the importance level and the urgency level of the event, and the importance level and the urgency level of the event may be determined by marking a priority, and the data filtering policy may also be related to the prompt information of the event list in the first floating window, for example, the same data filtering policy as the display content of the first floating window may be used.

S42: and responding to an event attribute updating operation of the preview information in the preview floating window, and updating an event attribute for the event to be handled corresponding to the preview information, wherein the event attribute comprises at least one of the current completion state, the reminding time, the title and the event priority level of the event.

The display content of the preview floating window can be more than that of the first floating window but less than that of the third window, and the preview floating window can be used as a transition window between the first floating window and the third window, so that the preview floating window can be conveniently used for quickly checking the list content and performing quick operation.

The manner of evoking the preview floating window may include mouse floating evoking, shortcut evoking, triggering button clicking evoking, etc., and the preview floating window may be evoked in a state that the first floating window or the second floating window is opened. The preview floating window can be presented simultaneously with the fourth window or separately.

The window display content of the preview floating window comprises preview information of at least one event to be handled in the event list, so that one or more filtered event tasks can be previewed, and event attribute updating operation can be performed on each event previewed based on the preview information.

In one example, the prompt message of the event list displayed in the first floating window is used to prompt that 8 to-do events need to be completed on the current day (for example, the number "8" is displayed), and the preview message displayed in the preview floating window may include keywords of the 8 to-do events. The preview information displayed in the preview floating window may also be information of a part of events determined after further filtering is performed on the 8 to-be-handled events, for example, the preview information displayed in the preview floating window may also be a keyword of 3 events with the greatest importance determined after the 8 to-be-handled events are filtered. Compared with the content displayed in the third window, the content displayed in the preview floating window is more compact, and the content displayed in the preview floating window can be used for the user to quickly edit the filtered event to be handled.

For the implementation of closing the preview floating window, reference may be made to the related contents of the third window or the second floating window described above.

The implementation mode provides an implementation mode which can preview the event list and quickly update the attributes of the event.

The display contents of the first floating window, the second floating window, the third window, the fourth window and the preview floating window are respectively described below.

Optionally, the display content for the first floating window may include: and displaying summary information and notification information of the events to be handled in the event list in the first floating window. The summary information includes the number of events to be handled in the event list. The notification information includes a brief notification description of the to-do event in the event list.

The summary information may be the number of listings, and/or the summary of the listings, filtered by various algorithms. Wherein the number may be one or more. In some examples, the first floating window may be divided into a plurality of groups, and the first floating window may be divided into a plurality of groups.

The notification information may be a single piece or a plurality of pieces, and includes one or more of a brief notification description, specific notification content, time, and operation item that need to be notified. In one example, the specific notification content may also be presented in a notification manner provided by the operating system.

In one example, as shown in fig. 3, the summary information includes only the number of events to be done, 6 events to be done on the current day are detected, the summary information is 6, and the number "6" is displayed on one component of the first floating window to remind the user of the number of events to be done on the current day. When the user marks that a to-do event is completed, the summary information is changed to 5, and the '6' is replaced by the '5' on the first floating window. Wherein "10" in fig. 3 denotes a first floating window.

The skilled person can set various data presentation strategies according to actual needs, for example, only the number of events to be handled that have expired in the last period of time, the number of events to be handled that have expired but are not marked to be completed, etc. are displayed on the first floating window.

Through the implementation process, the first floating window can display the number of the events to be handled in the event list. The user can pay attention to the number of the events to be handled at any time, and the user can conveniently arrange time to complete the corresponding events to be handled.

In another example, the summary information further includes brief contents of a list of events with the highest priority, and the keywords of the events to be handled with the highest priority can be displayed in the first floating window. The identification method of the priority includes but is not limited to: star level identification, color identification and character identification.

Since the event to be handled with the highest priority may or may not be the first event, the user may be prepared for the event with the highest priority in advance by displaying the related content of the event to be handled with the highest priority in the first floating window.

Optionally, for the display content of the second floating window, in addition to the content of the first event, as shown in fig. 4, the second floating window may also display the prompt information in the first floating window and mark buttons, where the mark buttons include a complete button, a delay button, an add button, an edit button, a group setting button, a software setting button, a close button, a click view details button, and the like.

In fig. 4, "20" indicates the second floating window, and "M" and "N" indicate the completion button and the delay button, respectively. Based on the labeled button in the second floating window, the list management method may further include:

in response to a first marking operation for the completion button, the first event is marked as a completion state. Or responding to the second marking operation of the delay button, obtaining the delay reminding time in the second marking operation, and setting the next reminding time of the first event as the delay reminding time.

When any delay time period in the delay time options is selected, the next reminding time of the first event is determined. For example, if the "three hours later" delay period is selected, the next reminding time of the first event is updated to the time corresponding to three hours later from the current time.

When the close button is triggered (e.g., clicked), the reminder content currently for the first event is closed (e.g., the second floating window is closed) to reduce and avoid causing too much annoyance to the user. However, this first event may not be flagged as a completed state when the close button is triggered.

When the click view details button is triggered, a third window or other presentation may be displayed showing detailed information related to the first event and the second floating window closed.

Optionally, a delete button may be further disposed on the second floating window, so that a user may directly delete the event that has been prompted, and repeated disturbance of the message is avoided.

Through the implementation process, the single event to be handled can be operated by utilizing the marking button on the second suspension window, and the operation mode is convenient and fast. The marking or postponing operation of the appointed event can be completed only by simple marking operation, and the user can be prevented from being disturbed by repeated reminding of the same event. When the first event displayed in the second floating window is marked, window switching operation is not needed, and one-key marking can be realized without obtaining the contents of other irrelevant events to be handled, so that the operation mode is simple.

Alternatively, for the display content of the third window, as shown in fig. 5, the third window may display groups of "task", "work", "home", "punch card", "travel", and the like, and under each group, an event sub-list of the corresponding group may be displayed. Wherein "30" in fig. 5 denotes a third window. The display interface of the third window may be part or all of the interface of the inventory management software.

In the implementation process, the first floating window displays less content than the second floating window, and the second floating window displays less content than the third window. The progressive effect is displayed on the content display among the three, and the progressive effect is displayed in a progressive mode on the window size, so that the condition that a large display area on the current interface is occupied due to the fact that a constant window is always adopted can be avoided, when only the first floating window is adopted for list management, the prompt at any time can be achieved, the disturbance on a user can be reduced, and the phenomenon that the work of the user on other windows is interfered by the overlarge window size can be avoided.

In one example, to quickly add a new event, the display modality of the first floating window may be changed when an event addition trigger operation for the first floating window is accepted. For example, the mode may be changed to the mode shown in fig. 6, in which the prompt information (number "6") of the original event list is retained in fig. 6, but the outline of the window is changed (it becomes an ellipse), an addition indicator (i.e., an addition button "+" in fig. 6) for triggering the display of the fourth window is also displayed, and when the addition indicator of the first floating window is triggered, the fourth window is displayed. The present application does not specifically limit the form of the added mark.

In one example, as shown in FIG. 7, a fourth window is indicated by "40" in FIG. 7. The fourth window includes an input prompt box and event settings. The event setting items may include a classification setting item Q, a cue time setting item T.

Based on the fourth window, the list management method may further include step S32.

S32: and responding to the setting triggering operation of the event setting item, and setting an event attribute for the input content of the newly added event after detecting the input content of the newly added event in the input prompt box.

And setting an event attribute for the input content of the newly added event after detecting the input content of the newly added event in the input prompt box.

For example, when the input content of the newly added event existing in the fourth window is "XX meeting" and the category setting item Q is triggered, a plurality of groups in the group setting interface may be displayed, and the groups may include, but are not limited to: tasks, work, travel, records, etc. When any one of the plurality of groups is selected, an event attribute is set for the input content of the newly added event based on the selected group (e.g., "job").

The reminding time for setting the newly added event can be input or selected through the prompt time setting item T.

It is to be understood that the event setting items may not be limited to only the category setting items, the cue time setting items, for example, the event setting items may also include priority setting items, and the like.

The implementation process is beneficial to quickly adding new event content and completing the attribute setting.

Optionally, after setting the event attribute for the input content of the new event, the inventory management method may further include step S33.

S33: and updating the display content in the first floating window based on the event attribute of the newly added event.

The number of events to be handled displayed in the first floating window can be updated based on the event attribute of the newly added event.

In one example, if the number "6" displayed in the first floating window indicates that there are 6 pending events that need to be processed on the current day, after the event attribute setting for 1 newly added event is completed, if the event attribute of the newly added event indicates that the newly added event is a processing event that needs to be completed on the current day, the number "6" displayed in the first floating window may be updated to the number "7".

In addition to displaying the events to be handled that need to be processed on the current day, a plurality of events to be handled with higher importance level within a period of time may also be displayed according to the processing priority of the events.

In addition to updating the display content of the first floating window, the display content of the second floating window and the third window can be updated based on the event attribute of the newly added event.

The method for rapidly updating the display content of the first floating window is provided through the implementation mode, automatic updating can be performed after the event attribute of the newly added event is set, and the phenomenon that a user delays processing of the newly added event due to forgetting updating can be avoided to a certain extent.

In one example, as shown in fig. 8, when the prompt information of the event list displayed in the first floating window is the number "3", when the mouse is hovered over the first floating window, the preview floating window may be presented (the "50" in fig. 8 represents the preview floating window). If the data filtering strategies of the first floating window and the preview floating window are the same, for example, the data filtering strategies of the first floating window and the preview floating window are both 'displaying events needing to be completed within two days', and then displaying preview information of 3 events in the preview floating window. If the preview information of an event is 'ticket booking 3 pm', and the event is actually completed, the user can mark the state of the event through the preview floating window, so as to complete the event attribute updating operation for the event. If the preview information of an event is 'writing document tomorrow' and the event is important, the user can set the priority level of the event by setting some function mark buttons on the preview floating window, thereby completing the event attribute updating operation for the event. The implementation manner of event attribute setting is various, and reference may be made to the related descriptions of the second floating window (corresponding to fig. 4), the third window (corresponding to fig. 5), and the fourth window (corresponding to fig. 7), which are not described herein again.

Since the interface shape of a window may be irregular or custom, making it difficult to create a polygonal or curved window that fits completely within the software interface to handle interaction events, a way to set up the components in each window that need to interact will be described below.

The rectangular window capable of wrapping part of the visible interface can be created for any window, a response designated triggering mode can be set for the area needing to present prompt information, event list items, event content and operation item content, and the other areas are set as trigger modes without response. The triggering manner includes, but is not limited to, a mouse triggering manner.

Taking the first floating window as an example, if the operating environment of the electronic device 100 supports the transparent area unresponsive mouse triggering manner, the largest peripheral component in the first floating window may be set to be transparent. In a specific implementation process, a title bar of a form can be set to be hidden, a background of the form can be set to be transparent, and a hierarchy of the form can be set to cover a main form. The transparent window body can be distinguished from other non-transparent window bodies, and interference with other window bodies can be reduced.

It should be noted that, although the frame of the first floating window is transparent, the area of the first floating window for displaying the prompt message may be non-transparent, semi-transparent or partially transparent, so that the first floating window can display the third window in response to the user-initiated viewing operation. The transparentization setting can be performed on part of the components of the second floating window according to the same principle.

For the area or the component needing to display information, events of mouse entering and mouse moving out can be monitored, and when the mouse entering event is triggered, the whole first floating window is set to respond to mouse interaction. When the mouse out event is triggered, the whole first floating window is set to be not responding to mouse interaction. If the actual operating environment of the method can provide the automatic transparent area penetration capability (for example, a transparent area penetration scheme carried by a desktop application development framework such as NW, Electron and the like is used), the method can be implemented by using the transparent area penetration scheme carried by the operating environment without additionally setting a response scheme of mouse interaction.

And according to the same principle, the components related to interaction in the second floating window, the third window and the fourth window can be set to realize the function that the designated component can respond to the user operation and other components or other areas do not respond to the user operation.

To implement the above process, internally, timed or polling tasks may be performed, including: synchronizing server data, detecting a marker status for each event, detecting a reminder time for each time, etc., by performing these tasks the presentation data for each window can be updated.

For example, in the process of displaying the second floating window, a polling task may be executed to circularly read all list entries to be notified, when it is detected that one of the list entries meets the reminding condition, for example, the set reminding time has elapsed, the content corresponding to the list entry is read and presented on the interface of the second floating window, and the interface of the floating window may include the operation item of the list entry. The user can be reminded by selecting the modes of playing reminding sound, window shaking, playing animation and the like. After the user finds the content in the second floating window, the event content in the second floating window may be operated to close the second floating window, and the operation may be marking completion, delaying notification time, deleting notification information of the event, deleting all contents of the event, skipping to display details of the event list, and the like. After the user operates the second floating window, the second floating window can be removed and returned to the first floating window, so that the disturbance to the user is reduced.

Optionally, based on the first floating window, the list management method further includes: responding to the interface setting operation of the first floating window to obtain a setting parameter in the interface setting operation; and changing the display attribute of the first floating window according to the setting parameters.

The display properties of the first floating window may be altered, which may include size, color, shape, and the like.

In one embodiment, one or more components for displaying information may be disposed in the first floating window. Taking the dimensional attribute as an example, the size of these components can be adjusted. For example, in response to a user's interface setting operation, continuous adjustment may be performed within a preset adjustment range or one size may be selected from several preset sizes as a new size of the corresponding component.

Similarly, the shape of the component can also be altered by responding to the interface setup operation. In one example, as shown in fig. 3, a component in the first floating window is circular, and the circular component can be modified to be square, polygonal, animal and plant part organ shape, and can support a user-defined shape.

Various display interfaces can be displayed by changing the display attributes, and display conflicts or interferences between the first floating window and other windows in the current interface are avoided.

Optionally, the display properties of the second floating window may also be modified using the principles described above.

Optionally, based on the first floating window, the list management method further includes: and responding to the first switching operation of the first floating window, and switching the first floating window into a common window, wherein the common window is a non-floating window.

Thereby providing a way to change the display state of the first floating window. The floating window can be retained without changing the state of the first floating window, and after the first switching operation is performed, the first floating window can be temporarily switched to the ordinary window in the non-floating state. When the first floating window is switched to the normal window, correspondingly, when the first event needs to be displayed, the content of the first event can be displayed by using the normal window with the same shape as the second floating window.

In one example, the position of the second hover window, the third window, the fourth window, or the preview hover window may be determined based on the position of the first hover window. Taking the second floating window as an example, the second floating window may be presented at a specified position around the first floating window, or directly replace the first floating window. The first suspension window has an automatic edge attaching and adsorbing function, when the display position of the first suspension window is changed, position detection is carried out on the first suspension window to obtain each distance between the first suspension window and multiple edges (top edge, bottom edge, left edge and right edge) of the current desktop, and when one distance is smaller than an adsorption critical edge distance, the position of the first suspension window is automatically adsorbed to a corresponding boundary. For example, if the distance between the first floating window and the left boundary of the desktop is less than 30px, the first floating window is attracted to the left, so that the distance between the first floating window and the left boundary is 0px or other values.

In one embodiment, if the second floating window is displayed directly in place of the first floating window, the position of the second floating window may be determined according to the size of the screen of the device and the size of the components in the visible portion of the window to determine the coordinates of the starting point. For example, if the first floating window is in the lower left corner of the current interface, the lower left corner is used as the starting point coordinate, and the second floating window can be tightly attached to the corner of the desktop according to the left boundary and the bottom boundary.

As another embodiment, if the second floating window is displayed around the first floating window, when the first floating window is at the lower left corner of the current interface, the displayed second floating window is located at the upper right corner of the first floating window, so as to reduce the change of the first floating window.

In another example, the display position of the second floating window or the third window may be fixed. For example, the display position of the window may be determined according to a notification manner provided by the operating system.

Optionally, for the above S21, the following may be specifically implemented: logging in a list management system through a user account to acquire list data of the user account; and obtaining prompt information of the event list according to the list data, and displaying the prompt information in the first floating window.

For the data storage of the software, a mode combining local storage and Remote storage can be selected, and the Remote storage can synchronously read and write the data of the Remote server through protocols such as HTTP (HyperText Transfer Protocol), RPC (Remote Procedure Call), and the like; when the network is not smooth, the data which is not synchronized to the server can be temporarily recorded in the local, and the temporary data can be deleted after the data synchronization of the server is realized.

And the personal information of the user account can be displayed in the third window or the second floating window. The personal information may include a user name, an avatar.

Therefore, the prompt information corresponding to the user account can be obtained by acquiring the list data of the user account, and data synchronization can be achieved even if the user uses the list management software in different places. In addition, the problem of data confusion caused by using the same equipment by a plurality of users can be avoided.

In a complete implementation process, in order to implement the method, a form may be created to carry page content, and a generation manner of the form may be implemented by using an object provided by a development language of a corresponding operating system, for example, for a Mac OS system, the form may be implemented by using NSWindow in Objective-C, or by using browser window in Electron.

The list management method can play a role in reminding a user at any time, the user can visually find the abstract and the notification information of the event list by adopting the presentation form of the floating window, the operation steps of the user on the list management software are reduced through the switching circulation of each window, the operation path of the user on the list management is shortened, and the reminding function can be realized even if other software windows are not switched to the list management software. The advantages are beneficial to improving the list management efficiency and having good auxiliary effect on the user. And the display attribute of the floating window can be changed, the display state of the floating window can be switched, data can be synchronized on different devices, and the floating window is more convenient for users to use.

Referring to fig. 9, fig. 9 is a functional block diagram of a list management apparatus 300 according to an embodiment of the present disclosure. The apparatus may be stored in the memory of the electronic device 100, and may be used to execute the above list management method. The device includes: a display module 310 and a judgment module 320.

And the display module 310 is configured to display the prompt information of the event list in the first floating window.

The determining module 320 is configured to determine whether the current time meets a reminding condition of each event to be handled in the event list.

The display module 310 is further configured to display the content of the first event in the second floating window when the current time meets a reminding condition of the first event in the event list, where the first event is any event to be handled in the event list, and the stacking priorities of the first floating window and the second floating window on the current interface are higher than those of other windows on the current interface.

The list management device 300 can execute each step in the list management method, the list management device 300 can play a role of reminding at any time, and a user can pay attention to the prompt information of the event list without selecting list software as a current operation interface.

Optionally, the apparatus may further include an obtaining module and a setting module. The acquisition module is used for acquiring setting parameters in the interface setting operation of the first floating window, and the setting module is used for changing the display attribute of the first floating window according to the setting parameters.

Optionally, the display module 310 is further configured to display the content of part or all of the to-do events in the event list in a third window associated with the first floating window and/or the second floating window, where the third window is larger in size than the first floating window and the second floating window.

Optionally, the obtaining module is further configured to obtain the current display duration of the third window, the determining module 320 is further configured to determine whether the current display duration meets the preset monitoring duration, and the displaying module 310 is further configured to close the third window and display the first floating window when the current display duration meets the preset monitoring duration.

Optionally, the display module 310 is further configured to display a mark button in the second floating window, where the mark button includes a finish button and a delay button, and the apparatus further includes a mark module configured to mark the first event as a finish state in response to a first mark operation on the finish button; or responding to the second marking operation of the delay button, obtaining the delay reminding time in the second marking operation, and setting the next reminding time of the first event as the delay reminding time.

Optionally, the apparatus further includes a switching module, configured to switch the first floating window to a normal window, where the normal window is a non-floating window.

Optionally, the display module 310 may further be configured to: and responding to the event increment triggering operation of the first floating window, and displaying a fourth window which is used for acquiring the input content of the newly added event.

Optionally, the setting module may be further configured to: and responding to the setting triggering operation of the event setting item, and setting an event attribute for the input content of the newly added event after detecting the input content of the newly added event in the input prompt box.

Optionally, the apparatus may further include an update module, the update module being configured to: and updating the display content in the first floating window based on the event attribute of the newly added event. The display module 310 may also be configured to display the updated first floating window.

Optionally, the display module 310 may further be configured to: responding to a preview operation of the first floating window, and displaying preview information of at least one event to be handled in the event list in a preview floating window associated with the first floating window, wherein the preview information is obtained according to a set data filtering strategy; the updating module may be further configured to respond to an event attribute updating operation on the preview information in the preview floating window, and update an event attribute for a to-do event corresponding to the preview information, where the event attribute includes at least one of a current completion status, a reminding time, a title, and an event priority level of the event.

Optionally, the obtaining module is further configured to obtain list data of the user account, and obtain prompt information of the event list according to the list data, and the display module 310 is configured to display the prompt information in the first floating window.

For other details of the list management apparatus 300 in the embodiment of the present application, reference is made to the related description in the list management method, and details are not repeated herein.

In addition to the above embodiments, the present application provides a readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, performs the steps of the above list management method.

In summary, by the method, the device and the electronic device, a prompt function can be played at any time, so that a user can pay attention to relevant information of an event list. When the user works with windows of other software, the user can pay attention to the prompt information of the events to be handled without switching the windows, and the user can pay attention to the content of the first event in the events to be handled. The three windows can be used for reminding, but the reminding strength is different, so that the use by a user is facilitated, and the improvement of the working efficiency of the user is facilitated.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part. The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media that can store program codes, such as a U disk, a removable hard disk, a memory, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims. It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

Claims

1. A method for inventory management, the method comprising:

displaying prompt information of an event list in a first floating window, wherein the prompt information comprises abstract information of events to be handled in the event list, and the abstract information comprises the number of the events to be handled in the event list;

when the current time meets the reminding condition of a first event in the event list, displaying the content of the first event in a second floating window, wherein the first event is any event to be handled in the event list, and the stacking priority of the first floating window and the second floating window on a current interface is higher than that of other windows on the current interface;

responding to a preview operation of the first floating window, and displaying preview information of at least one event to be handled in the event list in a preview floating window associated with the first floating window, wherein the preview information is obtained according to a set data filtering strategy;

and responding to an event attribute updating operation of the preview information in the preview floating window, and updating an event attribute for the event to be handled corresponding to the preview information, wherein the event attribute comprises at least one of the current completion state, the reminding time, the title and the event priority level of the event.

2. The method of claim 1, further comprising:

responding to the interface setting operation of the first floating window to obtain a setting parameter in the interface setting operation;

and changing the display attribute of the first floating window according to the setting parameter.

3. The method of claim 1, further comprising:

in response to the viewing operation of the first floating window and/or the second floating window, displaying the content of part or all of the events to be handled in the event list in a third window associated with the first floating window and/or the second floating window, wherein the size of the third window is larger than that of the first floating window and the second floating window.

4. The method of claim 3, further comprising:

acquiring the display time length of the third window;

judging whether the display time length meets a preset monitoring time length or not;

when the display time length meets the preset monitoring time length, closing the third window and displaying the first floating window;

or when the third window is detected to lose focus, closing the third window and displaying the first floating window;

or when the set trigger area is triggered, closing the third window and displaying the first floating window.

5. The method of claim 1, wherein the second floating window is further configured to display markup buttons, the markup buttons including a done button, a delay button, the method further comprising:

marking the first event as a completed state in response to a first marking operation for the completion button;

or responding to a second marking operation of the delay button, obtaining a delay reminding time in the second marking operation, and setting the next reminding time of the first event as the delay reminding time.

6. The method of claim 1, further comprising:

and responding to a first switching operation of the first floating window, and switching the first floating window into a common window, wherein the common window is a non-floating window.

7. The method of claim 1, further comprising:

and responding to an event increment triggering operation of the first floating window, and displaying a fourth window, wherein the fourth window is used for acquiring the input content of the newly added event.

8. The method of claim 7, wherein the fourth window comprises an input prompt box, an event setting item, and further comprising:

and responding to the setting triggering operation of the event setting item, and setting an event attribute for the input content of the newly added event after detecting the input content of the newly added event in the input prompt box.

9. The method according to claim 8, wherein after setting an event attribute for the input content of the newly added event, the method further comprises:

and updating the display content in the first floating window based on the event attribute of the newly added event.

10. A method according to any of claims 1-9, wherein the window of the first floating window is transparent.

11. The method according to any one of claims 1-9, wherein displaying a prompt for a list of events in the first floating window comprises:

logging in a list management system through a user account to acquire list data of the user account;

and obtaining prompt information of the event list according to the list data, and displaying the prompt information in the first floating window.

12. An electronic device, characterized in that the electronic device comprises: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when the electronic device is operating, the machine-readable instructions when executed by the processor performing the steps of the method of any of claims 1-11.