CN113110889B - Global message prompting method, global message prompting device, medium and electronic equipment - Google Patents

Global message prompting method, global message prompting device, medium and electronic equipment Download PDF

Info

Publication number
CN113110889B
CN113110889B CN202110413645.8A CN202110413645A CN113110889B CN 113110889 B CN113110889 B CN 113110889B CN 202110413645 A CN202110413645 A CN 202110413645A CN 113110889 B CN113110889 B CN 113110889B
Authority
CN
China
Prior art keywords
message
interface component
window container
target
application program
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110413645.8A
Other languages
Chinese (zh)
Other versions
CN113110889A (en
Inventor
张磊
顾云
陈泓屹
赵宇
***
李廷昌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Century Trading Co Ltd, Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN202110413645.8A priority Critical patent/CN113110889B/en
Publication of CN113110889A publication Critical patent/CN113110889A/en
Application granted granted Critical
Publication of CN113110889B publication Critical patent/CN113110889B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G06F9/4451—User profiles; Roaming

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The disclosure relates to the field of computers, in particular to a global message prompting method, a global message prompting device, a storage medium and electronic equipment, wherein the method comprises the following steps: monitoring the running state of an interface component corresponding to an application program, determining a first target interface component and acquiring a first target window container when the running state of the first interface component is in an active state, adding a message window container corresponding to a message to be prompted into the first target window container, determining a second target interface component when the running state of the second interface component is in an active state in the switching process of the application program, removing the message window container from the first target window container, acquiring a second target window container, and adding the message window container into the second target window container. Through the technical scheme of the embodiment of the disclosure, the problems that the existing message prompt is not visual enough and the interaction logic is poor can be solved.

Description

Global message prompting method, global message prompting device, medium and electronic equipment
Technical Field
The present disclosure relates to the field of computers, and in particular, to a global message prompting method, a global message prompting apparatus, a computer readable storage medium, and an electronic device.
Background
With the rapid development of the internet, more and more users start to use the intelligent terminal, so that the user has an increasing degree to terminal equipment, and the terminal equipment is realized through the intelligent terminal in many things such as study, life, work and the like.
When the user uses the intelligent terminal every day, various messages are received, and the messages can be notified to the user in a message popup window or a notification bar.
However, in the prior art, the scheme of adopting the message popup to prompt the user for the message can only be based on the application program display, and after the user switches the application program, the user cannot see the message popup; with the notification bar, the user cannot intuitively notice the received message, and the user easily clears the message in the notification bar directly, which may result in neglecting some important information. Therefore, the scheme of message prompting in the prior art is not intuitive enough and has poor interaction logic for users.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The disclosure aims to provide a global message prompting method, a global message prompting device, a computer-readable storage medium and electronic equipment, which can solve the problems that the existing message prompting is not intuitive enough and has poor interaction logic.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.
According to a first aspect of the present disclosure, there is provided a global message prompting method, including: monitoring the running states of interface components corresponding to one or more application programs, and determining a first target interface component according to the running states of the first interface component when the running states of the first interface component corresponding to a first application program are monitored to be in an active state; acquiring a first target window container corresponding to the first target interface component, and adding a message window container corresponding to a message to be prompted into the first target window container so as to display the message on a first application view; when the running state of a second interface component corresponding to a second application program is monitored to be in an active state in the switching process of the application program, determining a second target interface component according to the active state of the second interface component, and moving the message window container out of the first target window container; and acquiring a second target window container corresponding to the second interface component, and adding the message window container into the second target window container so as to display the message on a second application view.
In an exemplary embodiment of the disclosure, based on the foregoing solution, before the monitoring the running states of the interface components corresponding to the one or more applications, the method further includes: acquiring configuration files loaded by the application programs; acquiring a plurality of candidate components of each application program in the configuration file; and determining the interface component operated by each application program according to the candidate components of each application program.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, the monitoring an operation state of an interface component corresponding to one or more application programs includes: acquiring monitoring interfaces of interface components of the application programs; monitoring the running state of the interface component according to the monitoring interface of the interface component corresponding to each application program
In an exemplary embodiment of the disclosure, based on the foregoing solution, the determining a first target interface component according to an activity state of the first interface component includes obtaining a callback parameter corresponding to the activity state of the first interface component; and determining a first target interface component according to the callback parameters.
In an exemplary embodiment of the disclosure, based on the foregoing solution, the determining the first target interface component according to the activity state of the first interface component includes: acquiring stacks of the plurality of interface components; and determining the first interface component as a first target interface component when the first interface component is positioned at the stack top.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, the adding a message window container corresponding to a message to be prompted to the first target window container includes: acquiring a window layout file corresponding to the first target window container; and adding a message window container corresponding to the message to be prompted into the first target window container according to the window layout file.
In an exemplary embodiment of the disclosure, based on the foregoing scheme, the window layout file has preset layout parameters.
In one exemplary embodiment of the present disclosure, based on the foregoing scheme, the presence status of the message is monitored; the message window container is removed from the target window container upon monitoring that the message is processed.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the method further includes: acquiring a notification manager of a terminal device where the application program is located; wherein the notification manager is configured to display a message in a drop-down notification bar; and acquiring message parameters corresponding to the message, and inputting the message parameters into the notification manager so that the message is displayed in a drop-down notification bar.
According to a second aspect of the present disclosure, there is provided a global message alert apparatus, the apparatus comprising: the interface component determining module is used for monitoring the running states of the interface components corresponding to one or more application programs, and determining a first target interface component according to the running states of the first interface component when the running states of the first interface component corresponding to the first application program are monitored to be in the active states; the first application view display module is used for acquiring a first target window container corresponding to the first target interface component, and adding a message window container corresponding to a message to be prompted into the first target window container so as to display the message on a first application view; the application program switching module is used for determining a second target interface component according to the active state of the second interface component when the running state of the second interface component corresponding to the second application program is monitored to be in the active state in the switching process of the application program, and removing the message window container from the first target window container; and the second application view display module is used for acquiring a second target window container corresponding to the second interface component and adding the message window container into the second target window container so as to display the message on a second application view.
According to a third aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the global message prompting method as described in the first aspect of the embodiments above.
According to a fourth aspect of the present disclosure, there is provided an electronic device comprising:
a processor; and
and a memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the global message hint method according to the first aspect of the embodiments described above.
The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:
in the global message prompting method provided by an embodiment of the present disclosure, an operation state of an interface component corresponding to one or more application programs may be monitored, when the operation state of a first interface component corresponding to a first application program is monitored to be in an active state, a first target interface component is determined according to the active state of the first interface component, a first target window container corresponding to the first target interface component is obtained, a message window container corresponding to a message to be prompted is added to the first target window container, so that the message is displayed on a first application view, and when the operation state of a second interface component corresponding to a second application program is monitored to be in an active state in a switching process of the application program, a second target interface component is determined according to the active state of the second interface component, the message container is removed from the first target window container, a second target window container corresponding to the second interface component is obtained, and the message window container is added to the second target window container, so that the message is displayed on a second application view.
Embodiments of the present disclosure. On the one hand, when the user switches application programs, the message can be globally displayed in different application programs, so that the problem that the message cannot be acquired and processed in time due to application switching is avoided, and the message display method is visual for the user; on the other hand, the message does not need to be stored in the notification bar, and the user can directly process the message, so that the problem that the user clears the message in the notification bar in batches is avoided; in still another aspect, the message corresponding to other application programs can be processed in the current application program, the interaction logic is good, the user operation can be facilitated, and the user experience is further improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort. In the drawings:
FIG. 1 schematically illustrates a flow chart of a global message hint method in an exemplary embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow diagram of determining interface components for each application to run based on a plurality of candidate components for each application in an exemplary embodiment of the present disclosure;
FIG. 3 schematically illustrates a flowchart of a monitoring interface of an interface component corresponding to each application program in an exemplary embodiment of the disclosure monitoring an operation state of the interface component;
FIG. 4 schematically illustrates a flowchart of determining a first interface component as a first target interface component when the first interface component is at the top of the stack in an exemplary embodiment of the present disclosure;
FIG. 5 schematically illustrates a flow chart of adding a message window container corresponding to a message to be prompted to a first target window container according to a window layout file in an exemplary embodiment of the present disclosure;
FIG. 6 schematically illustrates a flowchart of removing a message window container from a target window container upon monitoring that a message is processed in an exemplary embodiment of the present disclosure;
FIG. 7 schematically illustrates a flow chart of entering message parameters into a notification manager to cause a message to be displayed in a drop-down notification bar in an exemplary embodiment of the present disclosure;
FIG. 8 schematically illustrates a flow chart of a global message hint method in an exemplary embodiment of the present disclosure;
FIG. 9 schematically illustrates a composition diagram of a global message alert device in an exemplary embodiment of the present disclosure;
fig. 10 schematically illustrates a structural schematic diagram of a computer system suitable for use in implementing the electronic device of the exemplary embodiments of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed aspects may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known structures, methods, devices, implementations, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, or in one or more software-hardened modules, or in different networks and/or processor devices and/or microcontroller devices.
With the rapid development of the internet, more and more people begin to use intelligent terminals, and in some intelligent terminal devices, when reminding a message, a scheme of message popup window can be adopted for reminding. For example, in an android system, a Dialog may be used to prompt a message, where the Dialog scheme is based on displaying a message by an activity component corresponding to an application, and the visibility of the message depends on the visibility of the activity component; when reminding the message, the message reminding can be carried out in a notification bar mode. For example, the Notification scheme may be used to prompt a message, where the Notification scheme is to uniformly display the message in a Notification bar (e.g., a drop-down Notification bar, etc.) of the mobile phone, which is independent of the application.
However, the message prompting scheme using dialogs cannot be displayed across different applications. For example, when a user switches to the B application, the Dialog cannot display the message based on the B application, and the user cannot acquire the message in time, so that if the important program of the message to be prompted is high, the user may be adversely affected.
And a Notification message prompting scheme is adopted. On the one hand, the received message is stored in the notification bar, the message display is not visual enough, and the user easily ignores the message in the notification bar; on the other hand, the user can close the message notification authority in the system setting, and the application program has no authority to notify the message to the user; on the other hand, when the user uses the intelligent terminal, a plurality of messages may exist in the notification bar, some of the messages may be meaningless to the user, and the user has difficulty in determining useful messages for the user among the plurality of messages in the notification bar, so the user may perform batch clearing on the messages in the notification bar, thereby causing the user to ignore important information, and further causing poor user experience.
According to the global message prompting method provided in this exemplary embodiment, the running state of one or more interface components corresponding to an application program may be monitored, when the running state of a first interface component corresponding to a first application program is monitored to be in an active state, a first target interface component may be determined according to the first interface component, then a first target window container corresponding to the target interface component is obtained, a message window container corresponding to a message to be prompted is added to the first target window container, so that the message is displayed on a first application view, and when the running state of a second interface component corresponding to a second application program is monitored to be in an active state in a switching process of the application program, a second target interface component is determined according to the second interface component, and the message window container is removed from the first target window container, and then a second target window container corresponding to the second interface component is obtained, and is added to the second target window container, so that the message is displayed on a second application view. As shown in fig. 1, the global message prompting method may include the steps of:
Step S110, monitoring the running states of interface components corresponding to one or more application programs, and determining a first target interface component according to the running states of a first interface component when the running states of the first interface component corresponding to a first application program are monitored to be in an active state;
step S120, a first target window container corresponding to the first target interface component is obtained, and a message window container corresponding to a message to be prompted is added into the first target window container, so that the message is displayed on a first application view;
step S130, when the running state of a second interface component corresponding to a second application program is monitored to be in an active state in the switching process of the application program, determining a second target interface component according to the active state of the second interface component, and removing the message window container from the first target window container;
and step S140, obtaining a second target window container corresponding to the second interface component, and adding the message window container into the second target window container so as to display the message on a second application view.
In the global message prompting method provided in this example embodiment, the running state of one or more interface components corresponding to an application program may be monitored, when the running state of a first interface component corresponding to a first application program is monitored to be in an active state, a first target interface component may be determined according to the active state of the first interface component, then a first target window container corresponding to the first target interface component is obtained, a message window container corresponding to a message to be prompted is added to the first target window container, so that the message is displayed on a first application view, and when the running state of a second interface component corresponding to a second application program is monitored to be in an active state in a switching process of the application program, a second target interface component is determined according to the active state of the second interface component, the message container is removed from the first target window container, and a second target window container corresponding to the second interface component is obtained.
Embodiments of the present disclosure. On the one hand, when the user switches application programs, the message can be globally displayed in different application programs, so that the problem that the message cannot be acquired and processed in time due to application switching is avoided, and the message display method is visual for the user; on the other hand, the message does not need to be stored in the notification bar, and the user can directly process the message, so that the problem that the user clears the message in the notification bar in batches is avoided; in still another aspect, the message corresponding to other application programs can be processed in the current application program, the interaction logic is good, the user operation can be facilitated, and the user experience is further improved.
Next, steps S110 to S140 of the global message hint in the present exemplary embodiment will be described in more detail with reference to the drawings and embodiments.
Step S110, monitoring the running states of interface components corresponding to one or more application programs, and determining a first target interface component according to a first interface component when the running states of the first interface component corresponding to a first application program are monitored to be in an active state;
in one example embodiment of the present disclosure, the application is an application based on the use of the intelligent terminal, various programming languages that the user may use, and programming the application with the various programming languages. The host application may include software installed on the smart phone to run based on a corresponding system, such as ios system, android system, windows mobile system, symbian system, blackBerry OS system, etc. Applications may include office applications, internet applications, multimedia applications, data analysis applications, work collaboration applications, business applications. It should be noted that the present disclosure does not limit the type of application program in particular.
In an example embodiment of the present disclosure, an application program corresponds to an interface component, which may be used to compose a host application program, and in general, the application program may include multiple components, the interface component may be used to display a screen, and a user may interact with content in the interface component to accomplish a task while using the terminal device.
In an example embodiment of the present disclosure, the interface component may include an activity component in Android, one activity component may provide a screen, and may interact with a user through the activity component, where different activity components communicate through an agent. Activity represents a screen that a user can see, and is mainly used for processing the overall work of an application program, such as monitoring system events, displaying a specified View for the user, starting other activities, and the like. All the activities of the applications are inherited in an Android. App. Activity class, which is a basic class provided by Android, and after other activities inherit the parent class, various functions are realized by the method of the parent class.
In one example embodiment of the present disclosure, the interface component generally has a plurality of operational states. For example, for android (android) systems, the interface component is an Activity component, the running states of which include an Active/ringing state, when a new Activity starts to push a stack, it is at the forefront end of the screen, and is at the foretop of the stack, and at this time, it is in an Active state that is visible and can interact with the user; also included is a Paused state, a state when an Activity is covered by another transparent or Dialog style Activity. At this point it remains connected to the window manager, the system continues to maintain its internal state, so it is still visible, but it has lost focus and is not available to interact with the user; the device also comprises a Stoped state, and the Stoped state is when the Activity is covered by another Activity, the focus is lost and is invisible; the system also includes a Killed state that is in when Activity is reclaimed by the system or not activated. When an Activity instance is created, destroyed, or another Activity is launched, it transitions between these four states, the transition taking place in dependence on the actions of the user program. Further, the life cycle executed by the Active/ringing state includes onResume (), which is an Active state at this time, and can interact with the user; the lifecycle performed by the Paused state includes onPause (), a state (including partially visible) in which the current activity has lost focus but is still visible; the lifecycle performed by the stop state includes onstate (); the lifecycle performed by the Killed state includes onDestroy ().
In one example embodiment of the present disclosure, the operating state of the interface component corresponding to one or more applications may be monitored. Specifically, the interface component of each application program can be obtained and the running state of the interface component can be monitored, or the interface component positioned at the stack top can be obtained and the running state of the interface component can be monitored. For example, for android (android) systems, activitylifecyclecalllbs may be used to monitor the running states of multiple interface components, where activitylifecyclecalllbs is an interface in Application, and monitor the lifecycle of an Application.
When the running state of the first interface component corresponding to the first application program is monitored to be in an active state, the first target interface component can be determined according to the active state of the first interface component. For example, when the running state of the first interface component is changed from other states to an active state, the active state may be recalled into activityLifeCycloeClallbs, and the current activityLifeCycloeClallbs only obtains the active state, and at this time, the first target interface component corresponding to the active state needs to be obtained according to the active state. The first target interface component is a first interface component.
In one example embodiment of the present disclosure, a configuration file loaded by each application may be obtained, a plurality of candidate components for each application may be obtained in the configuration file, and an interface component for each application to run may be determined according to the plurality of candidate components for each application. Referring to fig. 2, determining an interface component for each application to run according to a plurality of candidate components for each application may include the following steps S210 to S230:
step S210, acquiring configuration files loaded by each application program;
in one example embodiment of the present disclosure, when an interface component of an application needs to be obtained, a configuration file that the application needs to load may be obtained first. Specifically, the configuration file related to each application program may be searched in the memory of the terminal device according to the index of the application program.
Step S220, obtaining a plurality of candidate components of each application program in the configuration file.
Step S230, determining interface components operated by each application program according to the candidate components of each application program.
In one example embodiment of the present disclosure, after a configuration file of an application is obtained, a plurality of candidate components in the configuration file may be obtained, and then an interface component to be run is determined among the plurality of candidate components. For example, for android (android) system, the android system comprises an activity component, which is a visual interface operated by a user, and provides a window for completing operation instructions for the user and provides an interactive entrance for the user; a Service component, typically used as logic that is time consuming in the background process; broadcast Receive (broadcast receiver) component, a type of component that filters the broadcast that is sent out for reception and response, can be used to let the application respond to an external time; a Content Provider component provides other application-specific datasets. At this time, the candidate components are an activity component, a Service component, a Broadcast Receive component, and a Content Provider component, respectively, and the activity component (interface component) can be acquired from these candidate components.
Through the steps S210 to S230, a configuration file loaded by each application program may be obtained, a plurality of candidate components of each application program may be obtained in the configuration file, and an interface component operated by each application program may be determined according to the plurality of candidate components of each application program.
In an example embodiment of the present disclosure, a monitoring interface of an interface component of each application may be obtained, and then an operation state of the interface component may be monitored according to the monitoring interface of the interface component corresponding to each application. Referring to fig. 3, the monitoring interface of the interface component corresponding to each application program monitors the running state of the interface component, and may include the following steps S310 to S320:
step S310: acquiring monitoring interfaces of interface components of all application programs;
in an example embodiment of the present disclosure, a listening interface is provided in an interface component of an application program, and a running condition of the interface component of the application program may be listened through the listening interface. For an android system, the lifecycle of the activity component may be monitored.
Step S320, monitoring the running state of the interface component according to the monitoring interface of the interface component corresponding to each application program.
In an example embodiment of the present disclosure, the running state of the interface component may be monitored according to a monitoring interface of the interface component corresponding to each application. Specifically, the running state of the interface component can be monitored through the monitoring interface by an external tool. For example, software Development Kit (SDK, software development kit) may be used to monitor the running state of the interface components, tools such as debugging may be included in the SDK, and the SDK often also includes example code, supporting technical notes, or other supporting documents that clarify erasures for the underlying reference material.
Through the steps S310 to S320, the monitoring interface of the interface component of each application program can be obtained, and then the running state of the interface component is monitored according to the monitoring interface of the interface component corresponding to each application program.
In an example embodiment of the present disclosure, a callback parameter corresponding to an active state of a first interface component may be obtained. Specifically, the callback function may be a function of the parameter transfer. The callback functions are implemented differently in different programming languages. In the C language, callback functions can only be implemented using function pointers, and in more modern programming languages such as c++, python, ECMAScript, etc., either pseudo-functions or anonymous functions can be used. The callback function corresponds to a callback parameter, i.e., the callback parameter is an object of the callback function. For an android system, when the onResume () state of the activity component is monitored through activityLifcycloallbacks, an onActiityResumed function can be called back at this time, and a callback parameter is included in the onActiityResumed.
In one example embodiment of the present disclosure, the first target interface component may be determined from the callback parameter. The callback parameter may be used to indicate an interface component corresponding to the current callback parameter, specifically, the callback parameter corresponds to a callback function, a current callback object, that is, the current interface component, may be determined through the callback function, and the interface component may be determined as the first target interface component.
In one example embodiment of the present disclosure, a stack of multiple interface components may be obtained, with a first interface component being determined to be a first target interface component when the first interface component is at the top of the stack. Referring to fig. 4, when the first interface component is located at the stack top, determining the first interface component as the first target interface component may include the following steps S410 to S420:
step S410, obtaining stacks of a plurality of interface components;
in one example embodiment of the present disclosure, a stack of multiple interface components may be obtained. Specifically, the stack is a data structure, which is a linear table capable of performing an insert or delete operation at the end of the table, data is stored according to a last-in first-out principle, the first-in data is pressed into the bottom of the stack, and the last data is popped from the top of the stack when the data needs to be read. Stacks are special linear tables that can only be inserted and deleted at one end. The incoming presses are stacked down and then up one by one. When taken away, the utility model can only be taken from the upper part. Both reading and taking are performed on top, and the bottom is typically stationary. The stack is a data structure similar to a barrel for stacking articles, one end for deleting and inserting is called the stack top, and the other end is called the stack bottom. Insertion is generally referred to as pushing and deletion is referred to as popping.
In step S420, when the first interface component is located at the stack top, the first interface component is determined to be the first target interface component.
In an example embodiment of the present disclosure, the stack of the plurality of interface components is obtained through the steps described above, and when the first interface component is located at the top of the stack, the first interface component may be determined to be the first target interface component. Specifically, the current first interface component is at the stack top, and the first interface component is in an active state at this time, so the first interface component can be determined to be the first target interface component.
Through the steps S410 to S420, a stack of a plurality of interface components may be obtained, and when the first interface component is located at the stack top, the first interface component is determined to be the first target interface component.
Step S120, a first target window container corresponding to the first target interface component is obtained, and a message window container corresponding to a message to be prompted is added into the first target window container, so that the message is displayed on a first application view;
in one example embodiment of the present disclosure, a first target window container may be used to display content corresponding to a first target interface component. Specifically, for an android system, when the lifecycle of an application is in the OnResume (active state), the content in the interface component is indicated to enter the foreground, is visible to the user, and is the focus of the user's current operation.
In one example embodiment of the present disclosure, a message may be prompted. In particular, the messages may include software messages, warning messages, system messages, dialogue messages, and the like; alternatively, the message may also include a single option message, a multiple option message, a notification message, and the like. The message window container may be used to display a message to be prompted. In particular, the message window container may have a predetermined window layout that may be used to adjust the display form of the message window container. Further, upon receipt of a message, the message window container may be determined based on the type of message. The form and content of the message and the message window container are not particularly limited in this disclosure.
In one example embodiment of the present disclosure, a first target window container corresponding to a first target interface component may be obtained, and a message window container corresponding to a message to be prompted may be added to the first target window container, so that the message is displayed on a first application view. For example, for an android system, the first target window container is a root view container, such as DecoreView, which is a sub-class of FrameLayout, and the activity component corresponds to DecoreView. A message window container may be added to the first target window container, at which point the contents of the message window container may be displayed on the first application view. The first application view is view data specifically presented by the first target interface component.
In an example embodiment of the present disclosure, a window layout file corresponding to a first target window container may be obtained, and a message window container corresponding to a message to be prompted is added to the first target window container according to the window layout file. Referring to fig. 5, adding a message window container corresponding to a message to be prompted to a first target window container according to a window layout file may include the following steps S510 to S520:
step S510, a window layout file corresponding to a first target window container is obtained;
in an example embodiment of the present disclosure, the content in the first target window container may be presented according to a rule of a window layout file, and a window layout file corresponding to the first target window container may be set, and the window layout file has preset layout parameters. For example, in the window layout file, contents such as a display position, a size direction, a display timing, and the like of various contents in the first target window container may be set. It should be noted that, the specific content of the window layout file corresponding to the first target window container is not limited in this disclosure.
Step S520, adding the message window container corresponding to the message to be prompted into the first target window container according to the window layout file.
In an example embodiment of the present disclosure, after the window layout file corresponding to the first target window container is acquired, a message window container corresponding to the message to be prompted may be added to the first target window container according to the window layout file. Specifically, the message window container corresponds to the content of the first target window container, and thus, the message window container may be disposed within the first target window container in accordance with the window layout file.
Through the steps S510 to S520, a window layout file corresponding to the first target window container may be obtained, and a message window container corresponding to the message to be prompted is added to the first target window container according to the window layout file.
Step S130, when the running state of the second interface component corresponding to the second application program is monitored to be in an active state in the switching process of the application program, determining a second target interface component according to the active state of the second interface component, and moving the message window container out of the first target window container;
in an example embodiment of the present disclosure, after the message is displayed on the first application view through the above steps, the user performs application switching, and the running state of the first interface component corresponding to the first application program enters the inactive state from the active state, and at this time, it is monitored that the running state of the second interface component corresponding to the second application program is in the active state, that is, the second interface component is in an active state that is visible and can interact with the user. The message window container may be removed from the first target window container without destroying the message window container. For example, for an android system, the message window container view may be removed from the first target window container decorview.
In one example embodiment of the present disclosure, the second target interface component may be determined based on an activity state of the second interface component. For example, a callback parameter corresponding to the activity state of the second interface component may be obtained, where the callback parameter corresponds to the interface component, and therefore, the second target interface component may be determined according to the callback parameter corresponding to the activity state of the second interface component.
Step S140, a second target window container corresponding to the second interface component is obtained, and the message window container is added into the second target window container, so that the message is displayed on the second application view.
In one example embodiment of the present disclosure, after the message window container is removed from the first target window container, a second target window container corresponding to the second interface component may be acquired and the message window container may be added to the second target window container to cause the message to be displayed on the second application view.
In particular, the second target window container may be used to display content corresponding to the second target interface component. A second target window container corresponding to the second target interface component may be obtained and the message window container removed from the first target view container may be added to the second target window container to cause the message to be displayed on the second application view. At this point, the content in the message window container may be displayed on the second application view. The second application view is view data specifically presented by the second target interface component. Based on this, when an application is switched, a message can be presented in another application.
In one example embodiment of the present disclosure, the presence status of a message may be monitored, and upon detecting that the message is processed, the message window container is removed from the target window container. Referring to fig. 6, when it is monitored that a message is processed, the message window container is removed from the target window container, the following steps S610 to S620 may be referred to:
step S610, monitoring the existence state of the message;
in one example embodiment of the present disclosure, upon receipt of a message, the presence status of the message may be recorded. Specifically, when a message window container is added to the first or second target window container, the current message may be recorded by an external tool through a specific variable. If the user does not process the message, the message exists; if the user processes the message, the message does not exist.
In step S620, the message window container is removed from the target window container upon monitoring that the message is processed.
In one example embodiment of the present disclosure, when a message is monitored to be processed, indicating that the message has been communicated to the user and the user has responded to the message, the message window container to which the message corresponds needs to be removed from the target window container. When a message exists, the message window container is in the first target window container or the second window container, and when the message is processed, the message window container is removed from the first target window container or the second window container. The target window container includes a first target window container or a second target window container. For example, for an android system, a recording tool may be provided in the SDK to record the presence of a message, and after the message is processed, the message window container view may be removed from the target window container decorvview.
Through the above steps S610 to S620, the existence state of the message can be monitored, and the message window container is removed from the target window container when it is monitored that the message is processed.
In one example embodiment of the present disclosure, a notification manager of a terminal device in which an application is located may be obtained; the notification manager is used for displaying the message in the drop-down notification bar, acquiring the message parameter corresponding to the message, and inputting the message parameter into the notification manager so that the message is displayed in the drop-down notification bar. Referring to fig. 7, inputting a message parameter into the notification manager to cause a message to be displayed in a drop-down notification bar may include the following steps S710 to S720:
step S710, acquiring a notification manager of a terminal device where an application program is located; wherein the notification manager is configured to display a message in a drop-down notification bar;
in one example embodiment of the present disclosure, a notification manager may be preset in advance in the system, through which some important messages may be told to the user. Wherein the notification manager can display the message by pulling down the notification bar.
Step S720, obtaining the message parameters corresponding to the message, and inputting the message parameters into the notification manager to display the message in the drop-down notification bar.
In one example embodiment of the present disclosure, after a message is acquired, a message parameter corresponding to the message may be acquired. In particular, the message parameters may include content of the message, display form, display icon, display action, and the like. The message parameters may be entered into a notification manager that displays the message in a drop down notification bar based on the message parameters. For example, for an android system, a notifianger (notification manager) may be acquired first, then a Builder structure class of a notification bar is created, then relevant message parameters are input to the Builder, a build () method of the Builder is called to assign a value to a notification, and the notification is displayed by the notifianger's notify () method. Note that, the content of the message parameters is not particularly limited in this disclosure.
Through the steps S710 to S720, the notification manager of the terminal device where the application program is located may be obtained, the message parameter corresponding to the message may be obtained, and the message parameter may be input into the notification manager, so that the message may be displayed in the drop-down notification bar, the message may be displayed in the drop-down notification bar while the message is displayed in the application program, and when the user is not in the application program, the message may also be checked, so as to avoid the user from missing important information.
In an example embodiment of the present disclosure, an application may initialize an application, the application may initialize an SDK, register actigylifecyclics in an interface component of the application through the SDK after initializing the SDK, call back the active state to the SDK when the running state of a first interface component corresponding to the first application is in the active state, the SDK may remove a message window container view from a target window container decorview, and when a message is acquired, may send a message prompt signal to the application, at this time, the application may call a global message prompt method in the SDK, and add the removed message window container view to the current target window container decorview according to the global message prompt method, at this time, may display the message in the current application. Referring to fig. 8, the global message alert method may include the steps of:
step 810, initializing an application program; step S820, initializing the SDK; step S830, register ActivityLifeCycleCallbacks in the interface component through SDK; step S840, when the running state of the first interface component corresponding to the first application program is monitored to be in an active state, the active state is called back to the SDK; step S850, the SDK removes the message window container view from the target window container decorview; step S860, when the message is acquired, sending a message prompt signal to the application program; step S870, the application program invokes the global message prompting method in the SDK; step S880, adding the removed message window container view to the current target window container decorview according to the global message prompt method; step S890, the message is displayed on the current application.
In an example embodiment of the present disclosure, the running state of an interface component corresponding to one or more application programs may be monitored, when the running state of a first interface component corresponding to a first application program is monitored to be in an active state, a first target interface component is determined according to the active state of the first interface component, a first target window container corresponding to the first target interface component is obtained, a message window container corresponding to a message to be prompted is added to the first target window container, so that the message is displayed on a first application view, and when the running state of a second interface component corresponding to a second application program is monitored to be in an active state in a switching process of the application program, a second target interface component is determined according to the active state of the second interface component, and the message window container is removed from the first target window container, a second target window container corresponding to the second interface component is obtained, and the message window container is added to the second target window container, so that the message is displayed on a second application view.
Embodiments of the present disclosure. On the one hand, when the user switches application programs, the message can be globally displayed in different application programs, so that the problem that the message cannot be acquired and processed in time due to application switching is avoided, and the message display method is visual for the user; on the other hand, the message does not need to be stored in the notification bar, and the user can directly process the message, so that the problem that the user clears the message in the notification bar in batches is avoided; in still another aspect, the message corresponding to other application programs can be processed in the current application program, the interaction logic is good, the user operation can be facilitated, and the user experience is further improved.
It is noted that the above-described figures are merely schematic illustrations of processes involved in a method according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
In addition, in the exemplary embodiment of the disclosure, a global message prompting apparatus is also provided. Referring to fig. 9, a global message alert device 900 includes: an interface component determination module 910, a first application view display module 920, an application switching module 930, and a second application view display module 940.
The interface component determining module is used for monitoring the running states of the interface components corresponding to one or more application programs, and determining a first target interface component according to the running states of the first interface component when the running states of the first interface component corresponding to the first application program are monitored to be in the active states; the first application view display module is used for acquiring a first target window container corresponding to the first target interface component, and adding a message window container corresponding to a message to be prompted into the first target window container so as to display the message on the first application view; the application program switching module is used for determining a second target interface component according to the active state of the second interface component when the running state of the second interface component corresponding to the second application program is monitored to be in the active state in the switching process of the application program, and removing the message window container from the first target window container; and the second application view display module is used for acquiring a second target window container corresponding to the second interface component and adding the message window container into the second target window container so as to display the message on the second application view.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, before monitoring the running states of the interface components corresponding to the one or more applications, the method further includes: acquiring configuration files loaded by each application program; acquiring a plurality of candidate components of each application program in a configuration file; the interface component that each application operates is determined based on the plurality of candidate components for each application.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, monitoring an operation state of an interface component corresponding to one or more applications includes: acquiring monitoring interfaces of interface components of all application programs; and monitoring the running state of the interface component according to the monitoring interface of the interface component corresponding to each application program.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, determining a first target interface component according to an activity state of the first interface component includes obtaining a callback parameter corresponding to the activity state of the first interface component; and determining a first target interface component according to the callback parameters.
In one exemplary embodiment of the present disclosure, based on the foregoing, determining the first target interface component according to the activity state of the first interface component includes: acquiring stacks of a plurality of interface components; and determining the first interface component as a first target interface component when the first interface component is positioned at the stack top.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, adding a message window container corresponding to a message to be prompted to a first target window container includes: acquiring a window layout file corresponding to a first target window container; and adding the message window container corresponding to the message to be prompted into the first target window container according to the window layout file.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the window layout file has preset layout parameters.
In one exemplary embodiment of the present disclosure, based on the foregoing scheme, the presence status of a message is monitored; upon monitoring that the message is processed, the message window container is removed from the target window container.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, a notification manager of a terminal device in which an application is located is acquired; wherein the notification manager is configured to display a message in a drop-down notification bar; and acquiring message parameters corresponding to the message, and inputting the message parameters into the notification manager so that the message is displayed in a drop-down notification bar.
Since each functional module of the global message prompting apparatus of the exemplary embodiment of the present disclosure corresponds to a step of the foregoing exemplary embodiment of the global message prompting method, for details not disclosed in the embodiment of the apparatus of the present disclosure, please refer to the foregoing embodiment of the global message prompting method of the present disclosure.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
In addition, in the exemplary embodiment of the disclosure, an electronic device capable of implementing the global message prompting method is also provided.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 1000 according to such an embodiment of the present disclosure is described below with reference to fig. 10. The electronic device 1000 shown in fig. 10 is merely an example and should not be construed as limiting the functionality and scope of use of the disclosed embodiments.
As shown in fig. 10, the electronic device 1000 is embodied in the form of a general purpose computing device. Components of electronic device 1000 may include, but are not limited to: the at least one processing unit 1010, the at least one memory unit 1020, a bus 1030 connecting the various system components (including the memory unit 1020 and the processing unit 1010), and a display unit 1040.
Wherein the storage unit stores program code that is executable by the processing unit 1010 such that the processing unit 1010 performs steps according to various exemplary embodiments of the present disclosure described in the above section of the present specification. For example, the processing unit 1010 may execute step S110 shown in fig. 1, monitor the running states of the interface components corresponding to one or more applications, and determine the first target interface component according to the active state of the first interface component when it is monitored that the running state of the first interface component corresponding to the first application is in the active state; step S120, a first target window container corresponding to the first target interface component is obtained, and a message window container corresponding to a message to be prompted is added into the first target window container, so that the message is displayed on a first application view; step S130, when the running state of the second interface component corresponding to the second application program is monitored to be in an active state in the switching process of the application program, determining a second target interface component according to the active state of the second interface component, and moving the message window container out of the first target window container; step S140, a second target window container corresponding to the second interface component is obtained, and the message window container is added into the second target window container, so that the message is displayed on the second application view.
As another example, the electronic device may implement the various steps shown in fig. 1.
The memory unit 1020 may include readable media in the form of volatile memory units such as Random Access Memory (RAM) 1021 and/or cache memory unit 1022, and may further include Read Only Memory (ROM) 1023.
Storage unit 1020 may also include a program/utility 1024 having a set (at least one) of program modules 1025, such program modules 1025 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 1030 may be representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 1000 can also communicate with one or more external devices 1070 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 1000, and/or with any device (e.g., router, modem, etc.) that enables the electronic device 1000 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1050. Also, electronic device 1000 can communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 1060. As shown, the network adapter 1060 communicates with other modules of the electronic device 1000 over the bus 1030. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with the electronic device 1000, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the present disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the "exemplary methods" section of this specification, when the program product is run on the terminal device.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims (12)

1. A global message prompting method, comprising:
monitoring the running states of interface components corresponding to one or more application programs, and determining a first target interface component according to the running states of the first interface component when the running states of the first interface component corresponding to a first application program are monitored to be in an active state;
Acquiring a first target window container corresponding to the first target interface component, and adding a message window container corresponding to a message to be prompted into the first target window container so as to display the message on a first application view;
when the running state of a second interface component corresponding to a second application program is monitored to be in an active state in the switching process of the application program, determining a second target interface component according to the active state of the second interface component, and moving the message window container out of the first target window container;
and acquiring a second target window container corresponding to the second interface component, and adding the message window container into the second target window container so as to display the message on a second application view.
2. The method of claim 1, wherein prior to said listening for the operational status of the interface component corresponding to the one or more applications, the method further comprises:
acquiring configuration files loaded by the application programs;
acquiring a plurality of candidate components of each application program in the configuration file;
and determining the interface component operated by each application program according to the candidate components of each application program.
3. The method of claim 1, wherein monitoring the operating state of the interface component corresponding to the one or more applications comprises:
acquiring monitoring interfaces of interface components of the application programs;
and monitoring the running state of the interface component according to the monitoring interface of the interface component corresponding to each application program.
4. The method of claim 1, wherein the determining a first target interface component based on the activity status of the first interface component comprises
Obtaining callback parameters corresponding to the active state of the first interface component;
and determining a first target interface component according to the callback parameters.
5. The method of claim 1, wherein the determining a first target interface component based on the activity status of the first interface component comprises:
acquiring stacks of the plurality of interface components;
and determining the first interface component as a first target interface component when the first interface component is positioned at the stack top.
6. The method of claim 1, wherein adding a message window container corresponding to the message to be prompted to the first target window container comprises:
Acquiring a window layout file corresponding to the first target window container;
and adding a message window container corresponding to the message to be prompted into the first target window container according to the window layout file.
7. The method of claim 6, wherein the window layout file has predetermined layout parameters.
8. The method according to claim 1, wherein the method further comprises:
monitoring the presence status of the message;
the message window container is removed from the target window container upon monitoring that the message is processed.
9. The method according to claim 1, wherein the method further comprises:
acquiring a notification manager of a terminal device where the application program is located; wherein the notification manager is configured to display a message in a drop-down notification bar;
and acquiring message parameters corresponding to the message, and inputting the message parameters into the notification manager so that the message is displayed in a drop-down notification bar.
10. A global message alert device, the device comprising:
the interface component determining module is used for monitoring the running states of the interface components corresponding to one or more application programs, and determining a first target interface component according to the running states of the first interface component when the running states of the first interface component corresponding to the first application program are monitored to be in the active states;
The first application view display module is used for acquiring a first target window container corresponding to the first target interface component, and adding a message window container corresponding to a message to be prompted into the first target window container so as to display the message on a first application view;
the application program switching module is used for determining a second target interface component according to the active state of the second interface component when the running state of the second interface component corresponding to the second application program is monitored to be in the active state in the switching process of the application program, and removing the message window container from the first target window container;
and the second application view display module is used for acquiring a second target window container corresponding to the second interface component and adding the message window container into the second target window container so as to display the message on a second application view.
11. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 1-9.
12. An electronic device, comprising:
A processor; and
a memory for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-9.
CN202110413645.8A 2021-04-16 2021-04-16 Global message prompting method, global message prompting device, medium and electronic equipment Active CN113110889B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110413645.8A CN113110889B (en) 2021-04-16 2021-04-16 Global message prompting method, global message prompting device, medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110413645.8A CN113110889B (en) 2021-04-16 2021-04-16 Global message prompting method, global message prompting device, medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN113110889A CN113110889A (en) 2021-07-13
CN113110889B true CN113110889B (en) 2023-12-05

Family

ID=76718099

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110413645.8A Active CN113110889B (en) 2021-04-16 2021-04-16 Global message prompting method, global message prompting device, medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN113110889B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114296855B (en) * 2021-12-29 2024-04-30 北京字节跳动网络技术有限公司 State management method and device of user interface, electronic equipment and storage medium

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015176673A1 (en) * 2014-05-22 2015-11-26 北京奇虎科技有限公司 Method and device for storing status bar notification, and management handover method and device
WO2016078624A1 (en) * 2014-11-21 2016-05-26 北京奇虎科技有限公司 Method and device for controlling popping up of window by identifying full screen mode
WO2018120905A1 (en) * 2016-12-29 2018-07-05 华为技术有限公司 Message reminding method for terminal, and terminal
CN108762843A (en) * 2018-05-29 2018-11-06 Oppo广东移动通信有限公司 Preloading method, apparatus, storage medium and the intelligent terminal of application program
CN109725950A (en) * 2018-12-29 2019-05-07 武汉斗鱼网络科技有限公司 A kind of method, apparatus and storage medium for realizing the operation of client list example
CN110162371A (en) * 2019-05-24 2019-08-23 网易（杭州）网络有限公司 Display control method and device, electronic equipment and storage medium
CN110879677A (en) * 2018-09-06 2020-03-13 武汉斗鱼网络科技有限公司 Window interface message management method and related equipment
CN112527172A (en) * 2020-12-30 2021-03-19 网易（杭州）网络有限公司 Interface display method and device, computer readable storage medium and electronic equipment

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040034860A1 (en) * 2002-08-15 2004-02-19 Microsoft Corporation Dynamically extensible application program framework including message and notification routing

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015176673A1 (en) * 2014-05-22 2015-11-26 北京奇虎科技有限公司 Method and device for storing status bar notification, and management handover method and device
WO2016078624A1 (en) * 2014-11-21 2016-05-26 北京奇虎科技有限公司 Method and device for controlling popping up of window by identifying full screen mode
WO2018120905A1 (en) * 2016-12-29 2018-07-05 华为技术有限公司 Message reminding method for terminal, and terminal
CN108762843A (en) * 2018-05-29 2018-11-06 Oppo广东移动通信有限公司 Preloading method, apparatus, storage medium and the intelligent terminal of application program
CN110879677A (en) * 2018-09-06 2020-03-13 武汉斗鱼网络科技有限公司 Window interface message management method and related equipment
CN109725950A (en) * 2018-12-29 2019-05-07 武汉斗鱼网络科技有限公司 A kind of method, apparatus and storage medium for realizing the operation of client list example
CN110162371A (en) * 2019-05-24 2019-08-23 网易（杭州）网络有限公司 Display control method and device, electronic equipment and storage medium
WO2020238815A1 (en) * 2019-05-24 2020-12-03 网易（杭州）网络有限公司 Display control method and device, electronic device and storage medium
CN112527172A (en) * 2020-12-30 2021-03-19 网易（杭州）网络有限公司 Interface display method and device, computer readable storage medium and electronic equipment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Android应用中一种Activity窗口管理***;夏德冰;陈庆奎;;计算机***应用(06);全文 *

Also Published As

Publication number Publication date
CN113110889A (en) 2021-07-13

Similar Documents

Publication Publication Date Title
CN102197362B (en) Surfacing and management of window-specific controls
US9542949B2 (en) Satisfying specified intent(s) based on multimodal request(s)
EP3816997A2 (en) Automatic performance of user interaction operations on a computing device
CN110309005B (en) Function calling method and device, terminal equipment and storage medium
US11244288B2 (en) Task reminder generator
CN112947813B (en) Resident display method, resident display device, resident display medium and electronic equipment for controlling floating window
CN109947408B (en) Message pushing method and device, storage medium and electronic equipment
CN111324252B (en) Display control method and device in live broadcast platform, storage medium and electronic equipment
CN108595520B (en) Method and device for generating multimedia file
CN110399576B (en) Page switching method and device, readable medium and electronic equipment
CN111263175A (en) Interaction control method and device for live broadcast platform, storage medium and electronic equipment
CN110851045A (en) Information display method and device, electronic equipment and computer readable storage medium
CN110377341B (en) Method, device, medium and electronic equipment for monitoring no-response exception
WO2016095386A1 (en) Short message processing method and short message processing terminal
US20240211116A1 (en) Screen recording interaction method and apparatus, and electronic device and computer-readable storage medium
CN113110889B (en) Global message prompting method, global message prompting device, medium and electronic equipment
CN110290058B (en) Method and equipment for presenting session message in application
CN111918102A (en) Bullet screen management method, bullet screen management device, bullet screen management equipment and storage medium
CN109885781B (en) Mixed page unified browsing method, device, equipment and storage medium
CN109634702B (en) Information prompting method and device, electronic equipment and readable medium
CN111291090B (en) Method, device, electronic equipment and medium for acquiring time period based on time control
CN108520063A (en) Processing method, device and the terminal device of event log
CN112764862A (en) Application program control method and device and electronic equipment
CN113411627B (en) Data pushing method and device, readable storage medium and electronic equipment
CN107515720B (en) Message processing method, medium, device and computing equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant