CN112947813B - Resident display method, resident display device, resident display medium and electronic equipment for controlling floating window - Google Patents
Resident display method, resident display device, resident display medium and electronic equipment for controlling floating window Download PDFInfo
- Publication number
- CN112947813B CN112947813B CN202110240533.7A CN202110240533A CN112947813B CN 112947813 B CN112947813 B CN 112947813B CN 202110240533 A CN202110240533 A CN 202110240533A CN 112947813 B CN112947813 B CN 112947813B
- Authority
- CN
- China
- Prior art keywords
- floating window
- layout file
- component
- interface
- management component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The present disclosure relates to the field of computers, and in particular, to a method and an apparatus for controlling a resident display of a floating window, a computer-readable storage medium, and an electronic device, where the method includes: creating a floating window management component; the method comprises the steps that a component monitors the running state of an interface assembly corresponding to each application program, and when the component monitors that a first interface assembly is in an active state, a window layout file is added into a first layout file by the component, so that window view data are displayed on first application view data; when the first interface component enters an inactive state, the window layout file is moved out of the first layout file; when the second interface component is in the active state, the window layout file is added to the second layout file with the component such that the window view data is displayed on the second application view data. Through the technical scheme of the embodiment of the disclosure, the problems that a user is inconvenient to operate and poor in experience when the user uses the floating window to display the application can be solved.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to a method and an apparatus for controlling a floating window to reside on a display, a computer readable storage medium, and an electronic device.
Background
With the rapid development of the internet, more and more users begin to use the intelligent terminals, and the degree of the users getting to the terminal devices is higher and higher, so that the intelligent terminals are needed to be used in many things such as study, life and work.
When a user uses the intelligent terminal daily, if one application program is used, another application program needs to be used, and information of the application program can be displayed in a floating window mode.
However, in this way, the user is required to agree to grant the system display permission, and the system display permission requirements are different for different operating systems, so that the implementation method of the floating window in the prior art is inconvenient for the user to operate, and further causes the problem of poor user experience.
It is to be noted that the information disclosed in the above background section is only for enhancement of 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 present disclosure is directed to a method for controlling a floating window to reside in a display, a device for controlling a floating window to reside in a display, a computer readable storage medium, and an electronic device, which can solve the problems of inconvenient operation and poor experience when a user uses a floating window to display an application.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to a first aspect of the present disclosure, there is provided a method for controlling a floating window resident display, including: creating a floating window management component, wherein the floating window management component is used for monitoring the running state of an interface assembly corresponding to each application program and outputting a floating window layout file, and the floating window layout file corresponds to floating window view data; the floating window management component monitors the running state of the interface assembly corresponding to each application program, and when the floating window management component monitors that a first interface assembly corresponding to a first application program is in an active state, the floating window management component is used for adding the floating window layout file to a first layout file corresponding to the first interface assembly so as to display the floating window view data on the first application view data; the first layout file corresponds to first application view data; in the switching process of an application program, when the floating window management component monitors that a first interface component enters an inactive state, removing the floating window layout file from the first layout file; when the floating window management component monitors that a second interface component corresponding to a second application program is in an active state, the floating window management component is utilized to add the floating window layout file to a second layout file corresponding to the second interface component, so that the floating window view data is displayed on the second application view data, wherein the second layout file corresponds to the second application view data.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, the create floating window management component includes: receiving a floating window opening instruction; and responding to the floating window opening instruction, and creating a floating window management component.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, the create floating window management component includes: obtaining a cache space of a terminal device where the application program is located; creating the floating window management component in the cache space.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, before the floating window management component monitors the running status of the interface component of each application program, the method further includes: acquiring a configuration file loaded by each application program; obtaining 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 scheme, the monitoring, by the floating window management component, the running state of the interface component corresponding to each application program includes: the floating window management part acquires a monitoring interface of an interface component of each application program; and monitoring the running state of the first 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, the adding, by the floating window management component, the floating window layout file to the first layout file corresponding to the first interface component includes: the floating window management part acquires a storage path of the first layout file; and adding the floating window layout file into the first layout file corresponding to the first interface component according to the storage path of the first layout file.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, the moving out the floating window layout file in the first layout file includes: the floating window management component calls a component pause method to pause the first interface component; and removing the layout file of the floating window from the first layout file corresponding to the first component interface.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the floating window layout file has preset layout parameters.
According to a second aspect of the present disclosure, there is provided a control-suspended window resident display device, the device comprising: the management component creating module is used for creating a floating window management component, the floating window management component is used for monitoring the running state of an interface component corresponding to each application program and outputting a floating window layout file, and the floating window layout file corresponds to floating window view data; an interface component monitoring module, configured to monitor an operating state of an interface component of each application program by the floating window management component, and when the floating window management component monitors that a first interface component corresponding to a first application program is in an active state, add the floating window layout file to a first layout file corresponding to the first interface component by using the floating window management component, so that the floating window view data is displayed on the first application view data; wherein the first layout file corresponds to first application view data; a window layout shifting-out module, configured to, in a switching process of an application program, shift out a floating window layout file in a first layout file when the floating window management component monitors that a first interface component enters an inactive state; and the window layout switching module is used for adding the floating window layout file to a second layout file corresponding to a second interface component by using the floating window management component when the floating window management component monitors that the second interface component corresponding to a second application program is in an active state, so that the floating window view data is displayed on the second application view data, wherein the second layout file corresponds to the second application view data.
According to a third aspect of the present disclosure, there is provided a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the method of controlling a floating window resident display 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
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 method of controlling a floating window resident display of the first aspect of the embodiments as described above.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
in the method for controlling a floating window to reside in a display device according to an embodiment of the present disclosure, after a floating window management component is created, an operation state of an interface assembly corresponding to each application program may be monitored by the floating window management component, and when the floating window management component monitors that a first interface assembly corresponding to a first application program is in an active state, the floating window management component is used to add a floating window layout file to a first layout file corresponding to the first interface assembly, so that floating window view data is displayed on the first application view data.
Embodiments of the present disclosure. On one hand, when the user uses the floating window to display the application program, the system display permission does not need to be granted to the terminal equipment, so that the operation of the user is reduced, the time of the user is saved, the utilization efficiency of the user on the terminal equipment is higher, and the user experience is further improved; on the other hand, the floating window display method does not need to be developed according to the requirements of system display authorities of different operating systems, can adaptively display the floating window according to different operating systems, reduces the development time and the development difficulty of developers, and greatly reduces the development cost; on the other hand, when facing different operating systems, the user does not need to learn the specific operation of the system, so that the use cost of the user is reduced, 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 present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty. In the drawings:
FIG. 1 schematically illustrates a flow chart of a method of controlling a floating window resident display in an exemplary embodiment of the disclosure;
FIG. 2 schematically illustrates a flow diagram of a floating window management component responsive to a floating window open instruction and created in an exemplary embodiment of the disclosure;
FIG. 3 schematically illustrates a flow diagram of creating a floating window management component in a cache space in an exemplary embodiment of the disclosure;
FIG. 4 is a flow diagram that schematically illustrates determining an interface component for each application run among a plurality of candidate components in an exemplary embodiment of the present disclosure;
fig. 5 schematically illustrates a flowchart of monitoring an operating state of a first interface component according to a monitoring interface of an interface component corresponding to each application in the exemplary embodiment of the present disclosure;
FIG. 6 is a flowchart illustrating adding a floating window layout file to a first layout file corresponding to a first interface component according to a storage path of the first layout file in an exemplary embodiment of the present disclosure;
FIG. 7 is a flow diagram that schematically illustrates invoking a component pause method to pause a first interface component and remove a floating window layout file in a first layout file in an exemplary embodiment of the present disclosure;
FIG. 8 schematically illustrates a component diagram of a resident display device controlling a floating window in an exemplary embodiment of the disclosure;
fig. 9 schematically shows a schematic structural diagram of a computer system of an electronic device suitable for implementing an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different 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 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 subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. 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 shown in the figures are functional entities only 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, in some intelligent terminal devices, one application needs to be used while another application needs to be displayed in a resident mode, and at the moment, the application can be displayed by using a floating window. For example, the floating window may include an information notification window, a navigation window, a game window, a chat window, a video playback window, etc., and the floating window needs to be displayed on the top layer of the application no matter which application the user uses.
In a general operating system, the system level application view and the application level application view are divided, and the permission level of the system level application view is higher than that of the application level application view. In the prior art, the application view can be added by using a system-level manager of the terminal device, and the application view of the floating window is added to the top layer of the system, so that the floating window is displayed.
When the floating window is displayed by the scheme, a user is required to agree to grant system display permission, and the requirements of the system display permission are different for different operating systems, so that the implementation method of the floating window in the prior art is inconvenient for the user to operate, and further causes the problem of poor user experience.
According to the resident display method for controlling the floating window provided in the exemplary embodiment, when a floating window management component is created, the floating window management component is configured to monitor an operation state of an interface component corresponding to each application program and output a floating window layout file, the floating window layout file corresponds to floating window view data, the floating window management component monitors the operation state of the interface component corresponding to each application program, and when the floating window management component monitors that a first interface component corresponding to a first application program is in an active state, the floating window management component is utilized to add the floating window layout file to a first layout file corresponding to the first interface component, so that the floating window view data is displayed on the first application view data; the first layout file corresponds to first application view data, in the switching process of the application programs, when the floating window management component monitors that the first interface component enters an inactive state, the floating window layout file is moved out of the first layout file, and when the floating window management component monitors that the second interface component corresponding to the second application program is in an active state, the floating window management component is used for adding the floating window layout file into the second layout file corresponding to the second interface component, so that the floating window view data are displayed on the second application view data, wherein the second layout file corresponds to the second application view data. As shown in fig. 1, the method for controlling the floating window resident display may include the following steps:
step S110, a floating window management component is created, wherein the floating window management component is used for monitoring the running state of an interface assembly corresponding to each application program and outputting a floating window layout file, and the floating window layout file corresponds to floating window view data;
step S120, the floating window management part monitors the running state of the interface assembly corresponding to each application program, and when the floating window management part monitors that the first interface assembly corresponding to the first application program is in an active state, the floating window management part is used for adding the floating window layout file to the first layout file corresponding to the first interface assembly so as to display the floating window view data on the first application view data; the first layout file corresponds to first application view data;
step S130, in the switching process of the application program, when the floating window management part monitors that the first interface component enters the inactive state, the floating window layout file is moved out of the first layout file;
step S140, when the floating window management component monitors that the second interface component corresponding to the second application program is in an active state, the floating window management component adds the floating window layout file to the second layout file corresponding to the second interface component, so that the floating window view data is displayed on the second application view data, where the second layout file corresponds to the second application view data.
In the method for controlling a floating window to reside in a display device provided in this example embodiment, a floating window management component may be created, where the floating window management component is configured to monitor an operating state of an interface assembly corresponding to each application program and output a floating window layout file, the floating window layout file corresponds to floating window view data, the floating window management component monitors an operating state of an interface assembly corresponding to each application program, when the floating window management component monitors that a first interface assembly corresponding to a first application program is in an active state, the floating window management component adds the floating window layout file to a first layout file corresponding to the first interface assembly, so that the floating window view data is displayed on the first application view data, in a switching process of the application programs, when the floating window management component monitors that the first interface assembly enters an inactive state, the floating window layout file is removed from the first layout file, and when the floating window management component monitors that a second interface assembly corresponding to a second application program is in an active state, the floating window management component adds the floating window layout file to a second layout file corresponding to the second application program, so that the floating window layout file is displayed on the second application view data.
Embodiments of the present disclosure. On one hand, when the user uses the floating window to display the application program, the system display permission does not need to be granted to the terminal equipment, so that the operation of the user is reduced, the time of the user is saved, the utilization efficiency of the user on the terminal equipment is higher, and the user experience is further improved; on the other hand, the method does not need to be developed according to the requirements of system display authorities of different operating systems, and can adaptively display the floating window according to different operating systems. .
Next, the steps S110 to S140 of controlling the always-on display of the floating window in the present exemplary embodiment will be described in more detail with reference to the drawings and the embodiments.
Step S110, a floating window management component is created, wherein the floating window management component is used for monitoring the running state of an interface assembly corresponding to each application program and outputting a floating window layout file, and the floating window layout file corresponds to floating window view data;
in an example embodiment of the present disclosure, the application is based on an application used by the smart terminal, various programming languages that can be used by the user, and application software programmed in various programming languages. The host application may include software installed on the smart phone and run based on a corresponding system, such as an ios system, an Android system, a windows mobile system, a Symbian system, a BlackBerry OS system, and the like. 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 specifically limit the type of the application program.
In an example embodiment of the present disclosure, an application may include an interface component, and the interface component may be used to compose a host application, and generally speaking, the application may include multiple components, and the interface component is used to display a screen, and a user may interact with content in the interface component to complete a task when using a terminal device.
In an example embodiment of the present disclosure, the interface component may include activity components in Android, one activity component may provide one screen, and may interact with a user through the activity component, and different activity components communicate through an intent.
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. Activity classes are inherited by all the applications, the classes are base-layer classes provided by Android, and after other activities inherit the parent classes, various functions are realized through a parent class method.
In an example embodiment of the present disclosure, a floating window is a system tool of a computer or smartphone that floats one or more movable windows on the surface of other applications in order to open different applications. The floating window can float the operation window of the software above the software interface or on the desktop. In many application scenarios, when one application is used, the operation of another application needs to be paid attention to at any time. In this case, another application may be displayed using the floating window, and the floating window may be provided on an upper layer of the application, so that the operation of the other application may be focused on at any time while one application is used. Further, the layout file of the floating window may have preset layout parameters, and the size and the position of the floating window may be controlled by adjusting the preset layout parameters.
In an example embodiment of the present disclosure, the floating window management component may listen to the operating state of an interface component of an application, which typically has multiple operating states. For example, for an android system, the interface component is an Activity component, and the running state of the interface component includes an Active/running state, when a new Activity is started to be stacked, the new Activity is at the forefront of the screen and at the topmost end of the stack, and is in an Active state which is visible and can interact with a user; also included is the Paused state, the state when Activity is overridden 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 therefore not available to interact with the user; the method also comprises a stop state, wherein the stop state is in the state when the Activity is covered by another Activity, the focus is lost and the Activity is not visible; also included is a kill state, which is when Activity is reclaimed by the system or not enabled. When an Activity instance is created, destroyed, or another Activity is initiated, it transitions between the four states, which occurs depending on the actions of the user program.
Further, the lifecycle executed in the Active/tuning state is onCreate (), onStart (), onResume (), which is in the Active state, and the current activity component is at the top layer of the task stack and can interact with the user; the lifecycle performed by the Paused state is onPause (), the current activity has lost focus but is still a visible state (including partially visible); the lifecycle of stop state execution is onStop ();
the lifecycle performed by the Killed state is ontstroy ().
In an example embodiment of the present disclosure, a floating window management component may be used to output a window layout file. Specifically, logic for the floating window service function may be included in the floating window management component, such as a game assistant application, a video playing application, a social chat application, a music playing application, and so on. In other words, an application program may be started in the floating window management component, where the floating window management component may obtain an interface component of the application program started by the floating window management component, where the interface component corresponds to the floating window layout file. At this time, the floating window layout file may be acquired and output. The floating window layout file is a control part of the floating window view, and therefore the floating window layout file also corresponds to floating window view data, and the floating window view data is equivalent to a display part of the floating window view. The interface component is a display container, and the floating window view data can be displayed in the interface component.
For example, for an android system, activity components of a floating window output by a floating window management component may be acquired, and a layout file of the activity components of the floating window may be acquired, where the floating window layout file corresponds to a view of the floating window, and the view of the floating window may be displayed in the activity of the floating window.
In an example embodiment of the present disclosure, a floating window open instruction may be received, and a floating window management component may be created in response to the floating window open instruction. Referring to fig. 2, in response to the floating window opening instruction and creating the floating window management component, the following steps S210 to S220 may be included:
step S210, receiving a floating window opening instruction;
in an example embodiment of the present disclosure, a floating window open instruction may be received. Specifically, the user may input a floating window opening instruction into the terminal device, where the floating window opening instruction may include an application program to be specifically pointed to be opened, and a starting mode of the floating window management component. Therefore, the floating window management component with specific business logic can be created according to the starting mode of the floating window management component.
Step S220, creating a floating window management component in response to the floating window opening instruction.
In an example embodiment of the present disclosure, after receiving a floating window open instruction, a window management component may be created from the floating window open instruction. Specifically, the floating window opening instruction may include a storage address of an application file of the floating window management component, obtain the storage address of the application file of the floating window management component, search for the application file, and create the floating window management component according to the application file of the floating window management component.
Through the above steps S210 to S220, the floating window opening instruction may be received, and the floating window management component may be created in response to the floating window opening instruction.
In an example embodiment of the present disclosure, a cache space of a terminal device where an application is located may be obtained, and then a floating window management component may be created in the cache space. Referring to fig. 3, creating a floating window management unit in a cache space may include the following steps S310 to S320:
step S310, obtaining a cache space of the terminal equipment where the application program is located;
in an example embodiment of the present disclosure, a cache space of a terminal device where an application program is located may be acquired. In particular, the cache may include a high speed data exchange memory that exchanges data with the processor prior to memory, and thus at a faster rate. Such as RAM, in which the stored information disappears after power is lost. The RAM can be classified into dynamic RAM and static RAM. The cache may be used for pre-read, write, temporary storage, etc. The space occupied by the cache is the cache space.
Step S320, creating a floating window management component in the buffer space.
In an example embodiment of the present disclosure, after the cache space of the terminal device is obtained, a floating window management tool may be created in the cache space. Specifically, after the terminal device is opened, the cache space of the terminal device may be obtained according to an operation instruction of a user, and the floating window management component may be created in the cache space.
In an example embodiment of the present disclosure, a cache space of a terminal device where an application is located may be obtained, and then a floating window management component may be created in the cache space.
Step S120, the floating window management part monitors the running state of the interface assembly corresponding to each application program, and when the floating window management part monitors that the first interface assembly corresponding to the first application program is in an active state, the floating window management part is used for adding the floating window layout file to the first layout file corresponding to the first interface assembly so as to display the floating window view data on the first application view data; the first layout file corresponds to first application view data;
in an example embodiment of the present disclosure, a first interface component may be included in the first application, and the first interface component may correspond to a first layout file corresponding to the first application view data. For example, for an android system, a first application may include an activity component that corresponds to a first layout file that corresponds to a view (first application view data).
In an example embodiment of the present disclosure, a terminal device may simultaneously start a plurality of applications, and interface components corresponding to the applications may be in different states, such as an active state, an inactive state, and the like. For the android system, the state of the interface component corresponding to the application program comprises each life cycle stage of the activity component, and the active state can comprise.
In an example embodiment of the present disclosure, after the floating window management component is created, the floating window management component may be used to monitor an operation state of an interface component corresponding to a plurality of applications that are operated by the terminal device, and when the floating window management component monitors that a first interface component corresponding to a first application in the plurality of applications is in an active state, the floating window management component is used to add the floating window layout file obtained in the above step to a first layout file corresponding to the first interface component. The floating window view data is data specifically displayed by an application program of the floating window, and the first application view data is data specifically displayed by the first application program. At this time, the floating window layout file is in the first layout file, that is, the floating window is also displayed when the first application program is displayed, and at this time, the floating window view data is displayed on the first application view data, so that the effect of floating display is achieved.
In an example embodiment of the present disclosure, before the floating window management component monitors the running state of the interface component of each application, a configuration file loaded by each application may be obtained, then a plurality of candidate components of each application are obtained in the configuration file, and then the interface component in which each application runs is determined according to the plurality of candidate components of each application. Referring to fig. 4, determining an interface component for each application to run among the candidate components may include the following steps S410 to S430:
step S410, acquiring configuration files loaded by each application program;
in an 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 associated with each application may be searched in the memory of the terminal device according to the index of the application.
Step S420, acquiring a plurality of candidate components of each application program in a configuration file;
step S430, determining the interface component operated by each application according to the multiple candidate components of each application.
In an example embodiment of the present disclosure, after the configuration file of the application program is obtained, a plurality of candidate components in the configuration file may be obtained, and then the interface component to be executed is determined among the plurality of candidate components. For example, for an android system, the android system includes an activity component, which is a visual interface operated by a user, and provides a window for the user to complete an operation instruction, and provides an interactive access for the user; a Service component, typically used as logic that is time consuming to process in the background; a Broadcast receiver component, which is a type of component that filters, accepts and responds to outgoing broadcasts, and may be used to respond to an external time by an application; a Content Provider component that provides other applications with a specified data set. 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 obtained from these candidate components.
Through the steps S410 to S430, the configuration file loaded by each application program may be obtained, then a plurality of candidate components of each application program are obtained in the configuration file, and the interface component operated by each application program is determined according to the plurality of candidate components of each application program.
In an example embodiment of the present disclosure, the floating window management component obtains the monitoring interface of the interface component of each application program, and may monitor the running state of the first interface component according to the monitoring interface of the interface component corresponding to each application program. Referring to fig. 5, monitoring the operating state of the first interface component according to the monitoring interface of the interface component corresponding to each application program may include the following steps S510 to S520:
step S510, the floating window management part acquires a monitoring interface of an interface component of each application program;
in an example embodiment of the present disclosure, in an operating system of a terminal device, a listening interface may be reserved in an interface component of an application, and the listening interface may be used to listen to an operating condition of the interface component of the application. For the android system, the lifecycle of the activity component may be monitored, that is, whether the activity component is in an Active/running state, a used state, a stored state, or a kill state may be monitored.
And step S520, monitoring the running state of the first 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 operation state of the interface component of the application program may be monitored according to the monitoring interface obtained in the above step. For an android system, a callback method of the life cycle of an interface component of a current application program can be compared with a callback method input through a monitoring interface, and when the two methods are the same, the running state of the interface component of the current application program can be monitored. For example, if the callback method input through the listening interface is onResume (), and the callback method of the lifecycle of the interface component of the current application is also onResume (), it is monitored that the interface component of the current application is in an active state.
Through the steps S510 to S520, the floating window management component may obtain the monitoring interface of the interface component of each application program, and monitor the running state of the first 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 floating window management component may obtain a storage path of the first layout file, and add the floating window layout file to the first layout file corresponding to the first interface component according to the storage path of the first layout file. Referring to fig. 6, adding the floating window layout file to the first layout file corresponding to the first interface component according to the storage path of the first layout file may include the following steps S610 to S620:
step S610, the floating window management part acquires a storage path of the first layout file;
in an example embodiment of the present disclosure, the floating window management component may obtain a configuration file index of the first application program, where the configuration file index of the first application program includes a storage path of the first layout file, and may search the storage path of the first layout file according to the configuration file index of the first application program.
Step S620, adding the floating window layout file to the first layout file corresponding to the first interface component according to the storage path of the first layout file.
In an example embodiment of the present disclosure, after the storage path of the first layout file is obtained, the floating window layout file may be added to the first layout file corresponding to the first interface component according to the storage path of the first layout file. For example, when the storage path of the first layout file is a1-a2-a3, it means that the first layout file is stored in the folder a3 in the subfolder a2 in the folder a 1; alternatively, the first layout file may be a file with a file name a3 in the subfolder a2 stored in the folder a 1. It should be noted that, in the present disclosure, the form of the storage path is not particularly limited as long as the first layout file can be searched according to the storage path.
Through the above steps S610 to S620, the floating window management component may obtain the storage path of the first layout file, and add the floating window layout file to the first layout file corresponding to the first interface component according to the storage path of the first layout file.
Step S130, in the switching process of the application program, when the floating window management part monitors that the first interface component enters the inactive state, the floating window layout file is moved out of the first layout file;
in an example embodiment of the present disclosure, the floating window layout file may be removed from the first layout file when the floating window management component hears that the first interface component enters an inactive state. For an android system, the floating window management component may be configured to monitor a life cycle of an activity component, and when the floating window management component monitors that the life cycle of the activity component is in a used state, a stored state, or a Killed state, it indicates that the activity component is in an inactive state, and the floating window layout file may be removed from a first layout file corresponding to the current activity component.
In an example embodiment of the present disclosure, the floating window management component calls a component pause method to pause the first interface component and remove the floating window layout file from the first layout file corresponding to the first component interface. Referring to fig. 7, invoking the component pausing method to pause the first interface component and remove the floating window layout file in the first layout file may include the following steps S710 to S720:
step S710, the floating window management part calls a component pause method to pause the first interface component;
in an example embodiment of the present disclosure, the floating window management component may monitor an operating state of an interface component corresponding to each application program, and when the floating window management component monitors that the interface component corresponding to the first application program is in an inactive state, may call a component suspension method to suspend the first interface component first. For the android system, when the activity component of the first application program is in a hidden state, an OnPause () method can be called, and at the moment, the activity component corresponding to the first application program can be paused.
Step S720, removing the floating window layout file from the first layout file corresponding to the first component interface.
Through the steps S710 to S720, the floating window management component calls the component suspension method to suspend the first interface component, and removes the floating window layout file from the first layout file corresponding to the first component interface.
Step S140, when the floating window management component monitors that the second interface assembly corresponding to the second application program is in an active state, the floating window management component adds the floating window layout file to the second layout file corresponding to the second interface assembly, so that the floating window view data is displayed on the second application view data, where the second layout file corresponds to the second application view data.
In an example embodiment of the present disclosure, the floating window management component may monitor an operating state of an interface component corresponding to each application, and when the floating window management component monitors that a second interface component corresponding to a second application is in an active state, the floating window layout file removed from the first layout file in the above steps may be added to a second layout file corresponding to the second interface component. At this time, the floating window layout file is in the second layout file, that is, the floating window is also displayed when the second application program is displayed, and the second application view data is data specifically displayed by the second application program. At this time, the floating window view data is displayed on the second application view data, and the effect of floating display is achieved.
In an example embodiment of the disclosure, on one hand, when a user uses a floating window to display an application program, the user does not need to grant a system display permission to a terminal device, so that the user operation is reduced, the user time is saved, the user has higher utilization efficiency for the terminal device, and the user experience is further improved; on the other hand, the method does not need to be developed according to the requirements of system display authorities of different operating systems, can display the floating window in a self-adaptive manner according to different operating systems, reduces the development time and development difficulty of developers, greatly reduces the development cost, does not need to start service, and reduces the application overhead; on the other hand, when the user faces different operating systems, the user does not need to learn the specific operation of the system, so that the use cost of the user is reduced, and the user experience is further improved.
It is noted that the above-mentioned figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Further, in an exemplary embodiment of the present disclosure, a control floating window resident display device is also provided. Referring to fig. 8, a resident display device 800 for controlling a floating window includes: the management component comprises a management component creating module 810, an interface component monitoring module 820, a window layout removing module 830 and a window layout switching module 840.
The management component creating module is used for creating a floating window management component, the floating window management component is used for monitoring the running state of an interface component corresponding to each application program and outputting a floating window layout file, and the floating window layout file corresponds to floating window view data; the interface component monitoring module is used for monitoring the running state of the interface component of each application program by the floating window management component, and when the floating window management component monitors that the first interface component corresponding to the first application program is in an active state, the floating window management component is used for adding the floating window layout file to the first layout file corresponding to the first interface component so as to display the floating window view data on the first application view data; the first layout file corresponds to first application view data; the window layout shifting-out module is used for shifting out the floating window layout file from the first layout file when the floating window management component monitors that the first interface component enters the inactive state in the switching process of the application program; and the window layout switching module is used for adding the floating window layout file to a second layout file corresponding to the second interface component by using the floating window management component when the floating window management component monitors that the second interface component corresponding to the second application program is in an active state, so that the floating window view data is displayed on the second application view data, wherein the second layout file corresponds to the second application view data.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, the creating of the floating window management component includes: receiving a floating window opening instruction; in response to the floating window open instruction, a floating window management component is created.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, a floating window management component is created, including: obtaining a cache space of a terminal device where an application program is located; a floating window management component is created in the cache space.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, before the floating window management component monitors the running state of the interface component of each application, the method further includes: acquiring a configuration file loaded by each application program; and 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 plurality of candidate components of each application program.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the monitoring, by the floating window management component, the running state of the interface component corresponding to each application program includes: the floating window management part acquires a monitoring interface of an interface component of each application program; and monitoring the running state of the first 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, adding, by using the floating window management component, the floating window layout file to the first layout file corresponding to the first interface component includes: the floating window management part acquires a storage path of the first layout file; and adding the floating window layout file into a first layout file corresponding to the first interface component according to the storage path of the first layout file.
In an exemplary embodiment of the present disclosure, based on the foregoing solution, removing the floating window layout file from the first layout file includes: the floating window management part calls a component pause method to pause the first interface component; and removing the floating window layout file from the first layout file corresponding to the first component interface.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the floating window layout file has preset layout parameters.
Since each functional module of the floating window resident display control apparatus in the exemplary embodiment of the present disclosure corresponds to the steps of the exemplary embodiment of the floating window resident display control method, please refer to the above-mentioned floating window resident display control method embodiment of the present disclosure for details that are not disclosed in the exemplary embodiment of the present disclosure.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above-described control floating window resident display method is also provided.
As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or program product. Accordingly, various aspects of the present disclosure may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 900 according to such an embodiment of the disclosure is described below with reference to fig. 9. The electronic device 900 shown in fig. 9 is only an example and should not bring any limitations to the functionality or scope of use of the embodiments of the present disclosure.
As shown in fig. 9, the electronic device 900 is embodied in the form of a general purpose computing device. Components of electronic device 900 may include, but are not limited to: the at least one processing unit 910, the at least one storage unit 920, a bus 930 connecting different system components (including the storage unit 920 and the processing unit 910), and a display unit 940.
Where the storage unit stores program code, the program code may be executed by the processing unit 910 to cause the processing unit 910 to perform the steps according to various exemplary embodiments of the present disclosure described in the above-mentioned "exemplary methods" section of this specification. For example, the processing unit 910 may execute step S110 shown in fig. 1, and create a floating window management component, where the floating window management component is configured to monitor an operating state of an interface component corresponding to each application and output a floating window layout file, where the floating window layout file corresponds to floating window view data; step S120, the floating window management part monitors the running state of the interface assembly corresponding to each application program, and when the floating window management part monitors that the first interface assembly corresponding to the first application program is in an active state, the floating window management part is used for adding the floating window layout file to the first layout file corresponding to the first interface assembly so as to display the floating window view data on the first application view data; the first layout file corresponds to first application view data; step S130, in the switching process of the application program, when the floating window management component monitors that the first interface component enters the inactive state, moving out the floating window layout file from the first layout file; step S140, when the floating window management component monitors that the second interface component corresponding to the second application program is in an active state, the floating window management component adds the floating window layout file to the second layout file corresponding to the second interface component, so that the floating window view data is displayed on the second application view data, where the second layout file corresponds to the second application view data.
As another example, an electronic device may implement the various steps shown in FIG. 1.
The storage unit 920 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM) 921 and/or a cache memory unit 922, and may further include a read only memory unit (ROM) 923.
The electronic device 900 may also communicate with one or more external devices 970 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 900, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 900 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interface 950. Also, the electronic device 900 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet) via the network adapter 960. As shown, the network adapter 960 communicates with the other modules of the electronic device 900 via the bus 930. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, 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 (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, various aspects of the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the disclosure as described in the above-mentioned "exemplary methods" section of this specification, when the program product is run on the terminal device.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. 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 for 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 and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, 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., through the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes included in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, 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 (11)
1. A resident display method for controlling a floating window is characterized by comprising the following steps:
creating a floating window management component, wherein the floating window management component is used for monitoring the running state of an interface assembly corresponding to each application program and outputting a floating window layout file, and the floating window layout file corresponds to floating window view data;
the floating window management component monitors the running state of an interface assembly corresponding to each application program, and when the floating window management component monitors that a first interface assembly corresponding to a first application program is in an active state, the floating window management component is used for adding a floating window layout file to a first layout file corresponding to the first interface assembly so as to display the floating window view data on the first application view data; wherein the first layout file corresponds to first application view data;
in the switching process of an application program, when the floating window management component monitors that a first interface component enters an inactive state, removing the floating window layout file from the first layout file;
when the floating window management component monitors that a second interface assembly corresponding to a second application program is in an active state, the floating window management component is utilized to add the floating window layout file to a second layout file corresponding to the second interface assembly, so that the floating window view data is displayed on the second application view data, wherein the second layout file corresponds to the second application view data.
2. The method of claim 1, wherein the creating a floating window management component comprises:
receiving a floating window opening instruction;
and creating a floating window management component in response to the floating window opening instruction.
3. The method of claim 1, wherein the creating a floating window management component comprises:
obtaining a cache space of the terminal equipment where the application program is located;
creating the floating window management component in the cache space.
4. The method of claim 1, wherein before the floating window management component listens to the running state of the interface component of each application, the method further comprises:
acquiring a configuration file loaded by each application program;
obtaining 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.
5. The method according to claim 1, wherein the monitoring, by the floating window management component, the running state of the interface component corresponding to each application program comprises:
the floating window management part acquires a monitoring interface of the interface component of each application program;
and monitoring the running state of the first interface component according to the monitoring interface of the interface component corresponding to each application program.
6. The method of claim 1, wherein the adding, with the floating window management component, the floating window layout file to the first layout file corresponding to the first interface component comprises:
the floating window management part acquires a storage path of the first layout file;
and adding the floating window layout file into the first layout file corresponding to the first interface component according to the storage path of the first layout file.
7. The method of claim 1, the removing the floating window layout file in the first layout file, comprising:
the floating window management component calls a component pause method to pause the first interface component;
and removing the floating window layout file from the first layout file corresponding to the first interface component.
8. The method of claim 1, wherein the floating window layout file has preset layout parameters.
9. A device for controlling a floating window resident display, the device comprising:
the management component creating module is used for creating a floating window management component, the floating window management component is used for monitoring the running state of an interface component corresponding to each application program and outputting a floating window layout file, and the floating window layout file corresponds to floating window view data;
an interface component monitoring module, configured to monitor an operating state of an interface component of each application program by the floating window management component, and when the floating window management component monitors that a first interface component corresponding to a first application program is in an active state, add the floating window layout file to a first layout file corresponding to the first interface component by using the floating window management component, so that the floating window view data is displayed on the first application view data; wherein the first layout file corresponds to first application view data;
a window layout moving-out module, configured to, in a switching process of an application program, move out a floating window layout file in a first layout file when the floating window management component monitors that a first interface component enters an inactive state;
and the window layout switching module is used for adding the floating window layout file to a second layout file corresponding to a second interface component by using the floating window management component when the floating window management component monitors that the second interface component corresponding to a second application program is in an active state, so that the floating window view data is displayed on the second application view data, wherein the second layout file corresponds to the second application view data.
10. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 8.
11. An electronic device, comprising:
a processor; and
memory for storing one or more programs which, when executed by one or more processors, cause the one or more processors to implement the method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110240533.7A CN112947813B (en) | 2021-03-04 | 2021-03-04 | Resident display method, resident display device, resident display medium and electronic equipment for controlling floating window |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110240533.7A CN112947813B (en) | 2021-03-04 | 2021-03-04 | Resident display method, resident display device, resident display medium and electronic equipment for controlling floating window |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112947813A CN112947813A (en) | 2021-06-11 |
| CN112947813B true CN112947813B (en) | 2022-12-06 |
Family
ID=76247629
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110240533.7A Active CN112947813B (en) | 2021-03-04 | 2021-03-04 | Resident display method, resident display device, resident display medium and electronic equipment for controlling floating window |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112947813B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254140A (en) * | 2021-06-21 | 2021-08-13 | 杭州涂鸦信息技术有限公司 | Floating window control method and device, computer equipment and readable storage medium |
| CN113672325B (en) * | 2021-08-09 | 2024-08-06 | 广州虎牙科技有限公司 | Suspension window display method and device, electronic equipment and storage medium |
| CN115225950A (en) * | 2022-07-18 | 2022-10-21 | 上海哔哩哔哩科技有限公司 | Video playing control method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462284A (en) * | 2014-11-27 | 2015-03-25 | 百度在线网络技术（北京）有限公司 | Method and system for judging webpage quality |
| CN109348070A (en) * | 2018-12-21 | 2019-02-15 | 北京金山安全软件有限公司 | Caller identification method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130080969A1 (en) * | 2011-09-27 | 2013-03-28 | Z124 | Unified desktop docking flow |
| US20070128899A1 (en) * | 2003-01-12 | 2007-06-07 | Yaron Mayer | System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows |
| US8191008B2 (en) * | 2005-10-03 | 2012-05-29 | Citrix Systems, Inc. | Simulating multi-monitor functionality in a single monitor environment |
-
2021
- 2021-03-04 CN CN202110240533.7A patent/CN112947813B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462284A (en) * | 2014-11-27 | 2015-03-25 | 百度在线网络技术（北京）有限公司 | Method and system for judging webpage quality |
| CN109348070A (en) * | 2018-12-21 | 2019-02-15 | 北京金山安全软件有限公司 | Caller identification method and device |
Non-Patent Citations (1)
| Title |
|---|
| 基于Android平台的大学生生活费手机管理系统设计与实现;刘奇付 等;《软件导刊》;20150930;第14卷(第9期);第141-143页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112947813A (en) | 2021-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112947813B (en) | Resident display method, resident display device, resident display medium and electronic equipment for controlling floating window | |
| CN107172454B (en) | Video recommendation method, medium, device and computing equipment | |
| US9934782B2 (en) | Automatic performance of user interaction operations on a computing device | |
| RU2689203C2 (en) | Flexible circuit for adjusting language model | |
| KR20180006966A (en) | Digital assistant scalability to third party applications | |
| CN108932087B (en) | Desktop split screen system for mobile equipment and implementation method thereof | |
| CN109885781B (en) | Mixed page unified browsing method, device, equipment and storage medium | |
| US11334374B2 (en) | Modifying readable and focusable elements on a page during execution of automated scripts | |
| CN109359118B (en) | Data writing method and device | |
| CN110290058B (en) | Method and equipment for presenting session message in application | |
| CN110399576B (en) | Page switching method and device, readable medium and electronic equipment | |
| US20170161098A1 (en) | Method, device, and terminal for switching operating systems | |
| JP2017529624A (en) | Component-specific application presentation history | |
| US10810019B2 (en) | Method for interface refresh synchronization, terminal device, and non-transitory computer-readable storage medium | |
| CN111817945B (en) | Method and equipment for replying communication information in instant communication application | |
| CN110780955A (en) | Method and equipment for processing emoticon message | |
| CN110727473A (en) | Resource control method, device, system, storage medium and electronic equipment | |
| CN113110889B (en) | Global message prompting method, global message prompting device, medium and electronic equipment | |
| CN114691273A (en) | User interface returning method and device, electronic equipment and storage medium | |
| CN112256372B (en) | Information processing method and device and electronic equipment | |
| CN113821205A (en) | Method and device for controlling small program page parameters, medium and electronic equipment | |
| CN113377585B (en) | Online education network fault processing method and device | |
| CN112199262B (en) | Storage space use condition calculation method and device, storage medium and electronic equipment | |
| CN113835817B (en) | Method, device, medium and program product for jumping pages | |
| US20240321270A1 (en) | Virtual assistant notification amelioration and awareness systems and methods |
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 |