CN112379808B

CN112379808B - Window control method, device, equipment and medium

Info

Publication number: CN112379808B
Application number: CN202011388106.5A
Authority: CN
Inventors: 余怀亮; 傅坤龙; 范甜甜
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-12-01
Filing date: 2020-12-01
Publication date: 2023-08-22
Anticipated expiration: 2040-12-01
Also published as: CN112379808A

Abstract

The application provides a window control method, a device, equipment and a medium, relates to the technical field of computers, and is used for reducing system resources occupied by a window control process. The method comprises the following steps: deleting the object data of the first account number displayed by the first object window in response to ending processing operation triggered by the first account number in the window control interface to obtain a free window; in response to a start processing operation triggered by the second account in the window control interface, adding object data of the second account in the idle window to obtain a second object window; displaying a second object window in the window control interface; the second object window is displayed in the window control interface, and the method reduces the times of creating and destroying the window by multiplexing the window, thereby reducing the system resources occupied in the window control process.

Description

Window control method, device, equipment and medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a medium for controlling a window.

Background

In online customer service, an agent often needs to provide service for multiple users, and a service device corresponding to the agent creates an independent user window for each user, so that the agent can perform service processing in the corresponding user window, which involves how the service device controls the multiple user windows.

Currently, the manner in which the user window is controlled is roughly: after the service equipment determines that a new user equipment access agent exists, a user window is created for the user; the service equipment determines that the agent finishes processing the related matters of the user, and destroys a user window corresponding to the user, and so on. Because the number of users that the agent needs to serve every day is large, in the current manner of controlling the user window, the service device frequently creates and destroys the user window, and more system resources in the service device can be occupied.

Disclosure of Invention

The embodiment of the application provides a window control method, device, equipment and medium, which are used for reducing system resources occupied by a window control process.

In one aspect, a window control method is provided, including:

deleting object data of a first account displayed by a first object window in response to ending processing operation triggered by the first account in a window control interface to obtain a free window;

in response to a start processing operation triggered by a second account in the window control interface, adding object data of the second account in the idle window to obtain a second object window;

and displaying the second object window in the window control interface.

The embodiment of the application provides a window control device, which comprises:

the system comprises a free window acquisition module, a first object window acquisition module and a second object window acquisition module, wherein the free window acquisition module is used for deleting object data of a first account, which is displayed by the first object window, in response to ending processing operation triggered by the first account in a window control interface, so as to acquire a free window;

the object window obtaining module is used for responding to a start processing operation triggered by a second account in the window control interface and adding object data of the second account in the idle window so as to obtain a second object window;

and the display module is used for displaying the second object window in the window control interface.

In a possible embodiment, the idle window obtaining module is further configured to:

deleting the object data of the first account displayed by the first object window, and determining that the number of the saved idle windows in an idle window list does not reach a preset threshold before the idle windows are obtained, wherein the idle window list is used for saving the idle windows;

and deleting the object data of the first account displayed by the first object window, and storing the idle window into the idle window list after obtaining the idle window.

In a possible embodiment, the window control display interface further includes an account list area for displaying account identifiers; the display module is further configured to:

and hiding the first object window when responding to the ending processing operation triggered by the first account in the window control interface, and deleting the account identification of the first account in the account list area.

In one possible embodiment, the display module is further configured to:

before adding object data of a second account in the idle window in response to a start processing operation triggered by the second account in the window control interface to obtain a second object window, if any accessed account does not exist currently, displaying a default window in the window control interface; no object data is added in the default window; or alternatively, the process may be performed,

and if any accessed account exists currently, displaying an object window corresponding to any account in the window control interface.

determining the idle window as the idle window with the longest saved time in the idle window list; or alternatively, the process may be performed,

And determining the idle window as the idle window with the shortest saved duration in the idle window list.

In a possible embodiment, the object window obtaining module is specifically configured to:

when an access request for a second account is received, displaying an account identifier of the second account in an account list area in the window control interface;

according to the access request, displaying the account identification of the second account in an account list area in the window control interface;

and responding to the triggering operation of the account identification of the second account, and adding the object data of the second account in the idle window to obtain a second object window.

after the second object window is displayed in the window control interface, if the number of the saved idle windows in the idle window list does not reach a preset threshold value, creating a new idle window;

and storing the new idle window into the idle window list.

In a possible embodiment, the idle window obtaining module is specifically configured to:

creating a preset number of new idle windows according to the current system resource occupancy rate; the system resource occupancy rate is inversely related to the preset number; the preset number is less than or equal to the preset threshold value.

In one possible embodiment, the display module is further configured to:

after the second object window is displayed in the window control interface, responding to triggering operation of account identification of other accounts in the account list area, and switching the second object window to other object windows corresponding to the other accounts in the window control interface, wherein the other accounts refer to accounts except the second account in the account list area.

An embodiment of the present application provides a computer apparatus including:

at least one processor, and

a memory communicatively coupled to the at least one processor;

wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing the window control method of any one of the aspects by executing the memory stored instructions.

An embodiment of the present application provides a storage medium storing computer instructions that, when executed on a computer, cause the computer to perform a window control method as in any one of the aspects.

Due to the adoption of the technical scheme, the embodiment of the application has at least the following technical effects:

In the embodiment of the application, after the object window corresponding to a certain account is used, the object window is not directly destroyed, but the object data displayed by the object window is deleted, the object window is marked as the idle window, and the object data corresponding to other accounts can be loaded by directly using the idle window subsequently, so that the object window corresponding to other accounts is displayed, the window multiplexing is realized, and because each window can be multiplexed for a plurality of accounts, the times of creating the window and the times of destroying the window are relatively reduced, thereby reducing the occupied system resources. Moreover, the problem of blocking caused by frequently creating and destroying windows is avoided, the operation smoothness is facilitated, and the user experience is improved.

Drawings

Fig. 1 is an application scenario diagram of a window control method provided by an embodiment of the present application;

FIG. 2 is a flowchart of a window control method according to an embodiment of the present application;

FIG. 3 is an exemplary change diagram of an interface in a window control process according to an embodiment of the present application;

fig. 4 is a flowchart of account access provided in an embodiment of the present application;

FIG. 5 is a flowchart of an embodiment of the present application for marking idle windows;

FIG. 6 is a schematic diagram of interaction between the devices in FIG. 1 according to an embodiment of the present application;

FIG. 7 is a diagram illustrating an exemplary process of displaying a first object window according to an embodiment of the present application;

FIG. 8 is a diagram illustrating an exemplary process of displaying a second object window according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a window control device according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

In order to better understand the technical solutions provided by the embodiments of the present application, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.

In order to facilitate a better understanding of the technical solutions of the present application, the following description of the terms related to the present application will be presented to those skilled in the art.

1. Artificial intelligence (Artificial Intelligence, AI): the system is a theory, a method, a technology and an application system which simulate, extend and extend human intelligence by using a digital computer or a machine controlled by the digital computer, sense environment, acquire knowledge and acquire an optimal result by using the knowledge. In other words, artificial intelligence is an integrated technology of computer science that attempts to understand the essence of intelligence and to produce a new intelligent machine that can react in a similar way to human intelligence. Artificial intelligence, i.e. research on design principles and implementation methods of various intelligent machines, enables the machines to have functions of sensing, reasoning and decision. The artificial intelligence technology is a comprehensive subject, and relates to the technology with wide fields, namely the technology with a hardware level and the technology with a software level. Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions. In the embodiment of the application, the robot can be used as an agent, and the robot is realized mainly by using an AI technology, for example, a question-answering robot in a customer service scene, and can provide corresponding answers for a user by using keywords in the identified user message.

2. Online customer service: refers to customer service providing instant messaging.

3. Seat: the system is used for customer service wiring of an online customer service system and for consultation solution and problem acceptance of daily online services. The seat in the embodiment of the application can be a person or a robot.

4. Archiving: the method means that after the operation of the seat, the online customer service background can store the communication record and the problem of the online service when the online customer service is finished each time.

5. Stack window technology: it means that the interface may include a plurality of switchable windows, each window having a window Identification (ID), and the respective windows are displayed in an array. For the human eye, only one window is in a visible state at a time. The user can switch the windows by clicking on the window IDs. In the embodiment of the application, the window ID can be represented by an account number identifier.

6. Object window: the method is used for displaying the object data and the window control, and supporting the operations related to interaction with the object, recording of the object problem and the like. Each object has its own independent object window. An object is, for example, a user, and when the object is a user, the object window may also be referred to as a user window.

7. Object data: the data related to the object corresponding to the window is displayed in the window, and the object data may include one or more of basic data of the object, current service data sent by the object at this time, and historical service data related to the object. The basic data of the object includes basic information of the object, for example, when the object is a user, the basic data of the object may be an account number identification used by the user of the user, a user avatar, and the like. The present business data refers to business data related to the present time, such as a consultation work order submitted by the user in the present customer service. The historical business data related to the object refers to business processing related to the object in the past, such as a maintenance work order submitted by a user last time.

8. Idle window: the window with the window control is loaded, and the idle window is the same as the window control included in the object window, but the idle window does not add any object data.

9. Default window: refers to a window displayed when no object window is displayed, and no object data is added to the default window. To maintain visual consistency, the default window may be displayed with the same window control as the object window.

10. Window multiplexing: the same window is reused by loading object data of different objects. When multiplexing, only the object data corresponding to the window is needed to be changed, and the window control is not re-created.

11. Window control interface: the window control interface can also comprise an account list area which is used for displaying account identifiers of all accounts which are accessed currently.

12. List of account numbers: refers to a list formed by account numbers of the accessed accounts. The account number is opposite to the user, and one user wants to access the seat, which is usually realized by an account number on a certain software.

13. List of free windows: the method may also be called an idle window queue, and is used for storing idle windows, where each idle window in the idle window list may be arranged according to a preset sequence, for example, according to a sequence from front to back of a time stored in each idle window, or according to a sequence from back to front of a time stored in each idle window.

14. Dynamic loading: the list includes number and names which are not fixed, and operations such as adding or deleting the list can be performed at any time. The free window list and the account list involved in the embodiment of the application can be dynamically loaded.

15. Destroying: and the method can also be called as destructing, which means that when a certain window is not needed, the window can be destroyed, for example, a window control loaded in the destroyed window, or object data in the window, and the like are destroyed. In destroying the window, for example, a destructor for destroying the window may be run.

16. System resource occupancy rate: refers to the ratio of occupied system resources in a device to the maximum system resources that the device can provide, such as, in particular, memory resources of the device or central processing unit (Central Processing Unit, CPU) resources of the device.

The following describes the related art:

most online customer service systems employ stack window technology to achieve the goal of switching user windows. The stack window technology involves the creation, switching and destruction of multiple user windows, specifically: a user accesses the seat, and a user window needs to be created for the user; after the user data processing of a certain user by the agent is completed, the user window needs to be destroyed. In the online customer service system, the number of users served by one agent is large, and the manner of controlling the user window in the related technology can lead to frequent creation and destruction operations, thereby leading to high resource occupancy rate of the equipment.

In view of this, the embodiment of the present application provides a window control scheme, and the following describes the design concept of the scheme.

After the processing of a certain account is determined to be finished, the scheme does not directly destroy the object window corresponding to the account, but deletes the object data displayed by the object window to obtain a free window. And then other accounts are accessed, and object data of the other accounts can be loaded into the idle window, so that services are provided for the other accounts, and the window multiplexing process is realized. Because the scheme can multiplex the windows, the times of destroying and creating the windows can be relatively reduced, so that the resource occupancy rate in the control process of the object window is reduced. And when the window control that the window includes is more, all need consume certain time in creating the window and destroying the window in-process, cause the card problem easily, and this scheme has reduced the creation of window and destroyed the number of times, has reduced card and has blocked the condition to a certain extent, has promoted the operation smoothness nature, is favorable to promoting the use experience.

Based on the above design concept, the application scenario of the window control method according to the embodiment of the present application is described below.

The window control method related to the embodiment of the application can be suitable for any scene needing multi-window control, including but not limited to a customer service scene, an instant messaging social scene and the like.

The following describes an example of an application scenario of the window control method according to the embodiment of the present application with reference to an application scenario of the window control method according to the embodiment of the present application shown in fig. 1.

As shown in fig. 1, the application scenario includes a plurality of terminals and a server 120. A terminal, such as a personal computer or a cell phone, a server 120, such as an entity server or a cloud server, and the server 120 may be implemented as a single server or a cluster of servers.

For convenience of description, in the embodiment of the present application, a terminal corresponding to a user that needs to access is referred to as an access terminal, and a terminal corresponding to an accessed agent is referred to as an accessed terminal. An access terminal and an accessed terminal are relative concepts in that a terminal may belong to the access terminal at a certain time and to the accessed terminal at a certain time.

Specifically, the access terminal accesses the accessed terminal through the server 120, and the communication manner between the server 120 and each terminal may be arbitrary, and the present application is not particularly limited. Each access terminal may have an access client installed therein and each accessed terminal may have an accessed client installed therein. The access terminal accesses the accessed terminal through the server 120 may specifically be: the access client accesses the accessed client through the server 120. The access client may designate an accessed client when accessing, or the server 120 accesses an appropriate accessed client according to actual situations. The access client and the accessed client can be web page clients, preinstalled clients or clients embedded in third-party applications, and the application is not limited to the specific type of the access client or the accessed client. An example description of the relationship between an access client and an accessed client is provided below.

(1) The access client and the accessed client may be for the same application. There is no substantial distinction between the access client and the accessed client at this time. For example, the application is an instant messaging application, the access client may be the end that sends the instant messaging message, and the accessed client may be the end that receives the instant messaging message.

(2) The access client and the accessed client may be for different applications, but the two different applications may share one background server, or the two different applications correspond to different background servers, but the two corresponding background servers may communicate with each other. In this case, the display interfaces of the access client and the accessed client may not be identical. For example, the application is a customer service application, the access client corresponds to a general user, and the accessed client corresponds to an agent.

It should be noted that, in fig. 1, communication between the access client and the accessed client through the server is taken as an example, in practical application, direct communication between the access client and the accessed client may also be possible, for example, when the access client needs to access the accessed client, an access request may be directly initiated to the accessed client.

It should be noted that, in fig. 1, an example is taken in which an access client and an accessed client correspond to a background server. In fig. 1, the access terminals are exemplified by a first access terminal 110-1 and a second access terminal 110-2, respectively, wherein an access client in the first access terminal 110-1 is referred to as a first access client 111-1, and an access client in the second access terminal 110-2 is referred to as a second access client 111-2. For ease of description, the first access terminal 110-1 corresponds to user a, the second access terminal 110-2 corresponds to user B, and so on. Two access terminals are illustrated in fig. 1, and the number of access terminals is not limited in practice.

The accessed terminals take the first accessed terminal 130-1, the second accessed terminal 130-2 and the third accessed terminal 130-3 as examples, respectively, the accessed client in the first accessed terminal 130-1 is called a first accessed client 131-1, the accessed client in the second accessed terminal 130-2 is called a second accessed client 131-2, and the accessed client in the third accessed terminal 130-3 is called a third accessed client 131-3. For ease of description, the first accessed terminal 130-1 corresponds to user a, the second accessed terminal 130-2 corresponds to user b, and so on. In fig. 1, two accessed terminals are taken as an example, and the number of accessed terminals is not limited in practice.

After the interrelationship between the devices is described, the following examples briefly describe the functions of the devices:

user a may register the first account with the first access client 111-1 or may create a temporary first account for user a while using the first access client 111-1. User a may then send an access request to server 120 via the first account, where the access request may be used to request access to a corresponding accessed client for corresponding service processing. The access request may also carry object data corresponding to the first access client 111-1, and the access request may also carry a specified accessed client. After obtaining the access request, the server 120 may send the access request to the first accessed client 131-1.

After receiving the access request, the first accessed client 131-1 performs a corresponding window control procedure. The window control process will be described hereinafter.

The first accessed client 131-1 determines that after the corresponding processing for the first account is finished, the user a may also send the service processing result to the server 120, and after the server 120 receives the service processing result, the service processing result is fed back to the first accessed client 111-1, and may also store the service processing result, thereby completing the service processing process.

It should be noted that fig. 1 is an exemplary description of an application scenario related to an embodiment of the present application, but the scheme of the embodiment of the present application may be adapted to multiple scenarios, and is not limited thereto.

Taking the first accessed client 131-1 in fig. 1 as an example to execute the object window control method, the window control method in the embodiment of the present application is described below:

referring to fig. 2, a flowchart of a window control method is shown, where the flowchart includes:

s201, the first accessed client 131-1 responds to the ending processing operation triggered by the window control interface for the first account, and deletes the object data of the first account displayed by the first object window to obtain a free window.

After the first accessed client 131-1 is turned on, the first accessed client 131-1 may display a window control interface, which may refer to the content discussed above, and will not be described herein. When no access terminal is accessed, a window area in the window control interface can display a default window. The default window may refer to what has been discussed above, and will not be described in detail herein. If there is another account accessing the first accessed client 131-1 at this time, the accessing client may display an object window corresponding to the other account.

In order to facilitate the subsequent account access, after the first accessed client 131-1 is started, it may be determined whether the number of idle windows in the idle window list reaches a preset threshold, and if the number of idle windows reaches the preset threshold, no idle windows are created. If the preset threshold is not reached, a preset number of idle windows are created.

When creating the idle windows, the more the idle windows are created, the more convenient the subsequent multiple object windows are quickly created and displayed, but the creating of the idle windows needs to consume a certain resource, so in the embodiment of the present application, the first accessed client 131-1 can determine the preset number of creating the idle windows according to the occupancy rate of the system resource. The preset number and the system resource occupancy rate may be in an inverse relationship, specifically: when the system resource occupancy rate of the first accessed client 131-1 is small, it indicates that the idle resources of the first accessed client 131-1 are more, so that the preset number of idle windows that can be created by the first accessed client 131-1 can be more; when the system resource occupancy of the first accessed client 131-1 is large, it means that the idle resources of the first accessed client 131-1 are relatively small, and thus the preset number of idle windows created by the first accessed client 131-1 can be smaller.

Further, the first accessed client 131-1 may also add the created free window to the free window list.

The first accessed client 131-1 may further hide the created idle window, and specifically, for example, the first accessed client 131-1 may stack the first idle window under the default window.

In the embodiment of the present application, the first accessed client 131-1 may determine the number of created idle windows according to the system resource occupancy rate, so as to avoid creating too many idle windows and consuming too many system resources.

Further, the first accessed client 131-1 may consider, in addition to the system resource occupancy, the reference number of access requests processed by the first accessed client 131-1 in a preset time period to create a preset number of idle windows. The preset time period may be during a current time period, and the reference number may be determined with reference to the number of access requests historically processed by the first accessed client 131.

Specifically, the first accessed client 131-1 may determine, according to the occupancy rate of the system resources, the maximum number of idle windows that may be created by the idle resources, and then determine, according to the reference number of access requests processed by the first accessed client 131-1 in the historical time period, the preset number of created idle windows. If the maximum number is greater than or equal to the reference number, the preset number may be valued with reference to the reference number, for example, the preset number may be valued as the reference number. If the maximum number is less than or equal to the reference number, the preset number may be valued with reference to the maximum number, e.g., the preset number may be valued as the maximum number.

For example, referring to fig. 3, an exemplary process diagram of a control window is shown, an example of a window area currently displayed by the first accessed client 131-1 is shown in fig. 3 (1), a window indicated by a pointer 310 in fig. 3 (1) represents a window currently displayed, the window area 320 displays a default window, and a first idle window shown as "idle 1" is stacked under the default window. The first free window is included in the free window list 330. It should be noted that the illustration of the free window list 330 in fig. 3 (1) is for convenience of description of the technical solution, but the free window list 330 may not be visible to the user.

Before the first object window is processed, the first object window needs to be generated, and the following description is given of the process of accessing the first account to the first accessed client 131-1 with reference to the access flowchart shown in fig. 4:

s401, the first accessed client 131-1 receives an access request of the first account.

The first access client 111-1 generates an access request in response to the access operation, and the access request may refer to the foregoing discussion, which is not described herein. In addition, the access request may also carry the accessed client to which the first access client 111-1 designates access. The first access client 111-1 sends an access request to the server 120 through the first account,

After the server 120 receives the access request, if the accessed client is designated as the first accessed client 131-1 in the access request, the server 120 forwards the access request to the first accessed client 131-1. If the accessed client is not specified in the access request, the server 120 may determine that the first accessed client 131-1 satisfies the first accessed client 131-1 of the preset access condition. The preset access condition is, for example, that the number of access clients currently accessed in the accessed clients is less than the second threshold, or any accessed client on line, or the client closest to the first access client 111-1.

After the first accessed client 131-1 receives the access request, it is equivalent to determining the first account access. At this time, the first accessed client 131-1 may obtain the object data corresponding to the first account according to the access request, or the first accessed client 131-1 may request the object data of the first account from the server 120 according to the account identifier of the first account, so as to obtain the object data of the first account.

Further, the first accessed client 131-1 loads the object data of the first account in the idle window.

If the first accessed client 131-1 did not previously create a free window, a free window may be created and object data for the first account may be loaded to obtain a first object window.

Alternatively, if the first accessed client 131-1 created the first idle window before, the first accessed client 131-1 may load the object data of the first account into the first idle window, thereby obtaining the first object window, and display the first object window.

Specifically, if the first accessed client 131-1 is originally displayed as empty in the window area, then the first object window is directly displayed at this time, and if the first accessed client 131-1 is originally displayed as a default window in the window area, then the first object window may be displayed at this time and the default window may be stacked under the first object window to hide the default window. In addition, the first accessed client 131-1 may further display an account identifier of the first account in the account list area.

S402, the first accessed client 131-1 determines whether the number of the idle windows in the idle window list reaches a preset threshold.

If the number of the idle windows in the idle window list reaches the preset threshold value, ending, and not creating the idle windows any more.

If it is determined that the number of idle windows in the idle window list does not reach the preset threshold, S403 is executed, that is, the first accessed client 131-1 creates a preset number of idle windows, and adds the created idle windows to the idle window list. Further, after the preset number of free windows are created, the created free windows may be added to the free window list.

The determining manner of the preset number may refer to the foregoing discussion, and will not be repeated herein. It should be noted that, the system resource occupancy of the first accessed client 131-1 is different at different times, so the preset number of values determined by the first accessed client 131-1 may be the same or different.

For example, continuing with the example of fig. 3, the first accessed client 131-1 may load object data of the first account number according to the first currently existing idle window to generate a first object window, and at the same time, may create a third idle window, and may further display a window area shown in fig. 3 (2), where the first object window shown by "user a window" is displayed, and a third idle window shown by "idle 2" is stacked in sequence under the first object window.

After the first object window is displayed, the first accessed client 131-1 may process the service corresponding to the first account in response to the service processing operation performed in the first object window. After the corresponding service processing in the first object window is completed, the user A can perform an ending processing operation in the window control interface, for example, an ending control is displayed in the window area, and the user A clicks the ending control, which is equivalent to performing the ending processing operation, or the user A can click the account identifier of the first account in the account list area, which is equivalent to performing the ending processing operation, or the like, and the user A can perform a voice input instruction ending, which is equivalent to performing the ending processing operation. In response to the ending processing operation, the first accessed client 131-1 determines that the related processing of the first account has ended, and may delete the object data displayed in the first object window. The account identifier of the first account in the account list area may be further deleted.

Meanwhile, the first accessed client 131-1 may conceal the first object window according to the ending processing operation, switch and display the object window corresponding to the other accounts, and the first accessed client 131-1 may skip and display the object window corresponding to any one accessed account, or the first accessed client 131-1 may skip and display the object window corresponding to the account with the longest access time in the other accounts. If there is currently no account number that has accessed the first accessed client 131-1, the first accessed client 131-1 may display a default window.

Further, after the first accessed client 131-1 determines that the related processing of the first account has ended, if the corresponding service processing result needs to be fed back to the server 120, the first accessed client 131-1 may feed back the corresponding service processing result of the first account to the server 120, so that the server 120 feeds back the service processing result to the first access client 121-1, and stores the corresponding service processing result.

For example, continuing with the example shown in fig. 3, by such pushing, the first accessed client 131-1 may sequentially generate corresponding object windows for each of the users a to N, and specifically, referring to the example diagram shown in fig. 3 (3), the areas where the users a to N shown in fig. 3 (3) are located may be equivalent to the account list area in the window control interface. At this time, the idle window list further includes an idle window shown by "idle n+1", and at this time, the first accessed client 131-1 determines that the related processing of the first account is finished, and then the first accessed client 131-1 may skip to display the object window corresponding to the user B.

The first accessed client 131-1 may mark the object data shown in the first object window as a free window after deleting the object data, which is referred to as a first free window in the embodiment of the present application for convenience of distinction. Further, the first accessed client 131-1 may also save the first idle window into the idle window list.

As an embodiment, the first accessed client 131-1 may selectively tag the first object window. The process of selectively marking an idle window in the present embodiment is illustrated by referring to the flowchart of marking an idle window shown in fig. 5:

s501, the first accessed client 131-1 determines whether the number of idle windows in the idle window list reaches a preset threshold.

If the preset threshold value is not reached, that is, the number of the saved idle windows in the idle window list is not large, S502 is executed, the first object window after deleting the object data is marked as a first idle window, and the first idle window is saved in the idle window list. Further, the first idle window may be saved to the tail of the idle window list, and the corresponding idle window may be subsequently called according to the arrangement sequence of the idle windows in the idle window list.

If it is determined that the number of the idle windows in the idle window list has reached the preset threshold, which indicates that the number of the idle windows in the idle window list is greater, S503 is executed, that is, the first object window after deleting the object data is destroyed, so as to avoid that too many idle windows occupy too many resources.

In the embodiment of the present application, according to the number of idle windows stored in the idle window list, it is flexibly determined whether the first object window after deleting the object data needs to be marked as the first idle window, so as to avoid the situation that the idle windows stored in the idle window list are too many and consume too many resources of the first accessed client 131-1.

For example, continuing with the example of fig. 3, after processing the first object window, the first accessed client 131-1 may jump to display the object window corresponding to the user B as shown in (4) of fig. 3, and save the first idle window shown as "idle 1" to the idle window list.

For example, continuing to use the example shown in fig. 3, after determining that the corresponding processing of the account corresponding to the user B has ended, the first accessed client 131 may delete the object data in the object window corresponding to the user B, so as to obtain a window area shown in (5) in fig. 3, display the object window shown in the user 3 in the window area, and add a free window shown as "free 2" in (5) in fig. 3 in the free window list.

S202, in response to a start processing operation triggered by a second account in the window control interface, adding object data of the second account in a first idle window to obtain a second object window.

The server 120 may also continuously receive access requests of other users and allocate part or all of the access requests to the first accessed client 131-1, where after the first accessed client 131 receives the access request of the second account, the account identifier of the second account may be displayed in the account list area. For example, after the user clicks the account identifier of the second account, the starting processing operation of the second account is equivalent to that the first accessed client 131-1 determines, in response to the starting processing operation, that a corresponding object window needs to be generated for the second account currently. The first accessed client 131 may acquire the object data of the second account, and the manner of acquiring the object data of the second account may refer to the foregoing process of acquiring the object data of the first account, which is not described herein.

In addition, the first accessed client 131-1 needs to determine a free window meeting a certain condition from the free window list, and generate a corresponding object window for the second account. If the list of free windows includes only the first free window, then the first accessed client 131-1 invokes the first free window. If the idle window list includes a plurality of idle windows, the first accessed client 131-1 may screen the idle windows that satisfy the preset screening condition. The preset screening condition may be, for example, an idle window with the longest saved duration or the shortest saved duration in the idle window list, and the present application does not limit the preset condition. When the first idle window is an idle window satisfying the preset condition, the first accessed client 131-1 may call the first idle window.

After determining to invoke the first idle window, the first accessed client 131 may add object data of the second account in the first idle window, thereby obtaining a second object window.

S203, the first accessed client 131 displays the second object window in the window control interface.

If the first accessed client 131 displays a default window when obtaining the second object window, the first accessed client 131 may directly display the second object window after obtaining the second object window. If the first accessed client 131 displays the object window corresponding to the other account when obtaining the second object window, the first accessed client 131 may display the second object window in response to the confirmation display operation of the second object window. And confirming a display operation such as a clicking operation for an account identification of the second account.

For example, continuing with the example of fig. 3, user P accesses, and first accessed client 131 reads the first free window queue, i.e., the free window indicated by "free P" loads data and displays the interface as shown in fig. 3 (6), at which point no further creation is required since there are free windows. I.e. the list of empty windows remains with at least one empty window throughout the process.

If the user Q accesses later, the first accessed client 131 reads the first idle window queue, i.e. the idle window load data shown by "idle 1", and displays the interface shown in (7) in fig. 3, at this time, no re-creation is required because there is an idle window.

Subsequently, if there is a user W accessing, the first accessed client 131 reads the first idle window of the idle window list, loads data for the idle window shown by "idle 2" and displays the interface shown in (8) in fig. 3, at this time, there is no idle window, creates an idle window shown by "idle n+2" and adds the idle window to the idle window list.

In a possible embodiment, the user a may perform a triggering operation on the account identifiers of the other accounts, where the other accounts refer to accounts except the second account in the account list area, for example, the first accessed client 131-1 currently displays the object window of the user W, and the user a clicks the account identifier corresponding to the user Q, which is equivalent to performing a triggering operation on the account identifiers of the other accounts, so that the first accessed client 131-1 may switch the window control interface corresponding to the currently displayed account to the window control interface corresponding to the other accounts. In the embodiment of the application, the user A can switch the displayed window control interface at will, thereby being convenient for the user A to switch the business of different users.

After the second object window is displayed, the first accessed client 131-1 determines that the number of the saved idle windows in the idle window list does not reach the preset threshold value, and creates a new idle window, and the specific manner of creating the new idle window may refer to the content discussed above, which is not repeated herein. If the first accessed client 131-1 determines that the number of the saved idle windows in the idle window list reaches the preset threshold value, it is not necessary to create the idle windows. In the embodiment of the application, the second object window can be displayed first, and then whether the idle window needs to be created is judged, because the time consumption for loading the object data is small, but the time consumption of the creating process is long, and the creating of the idle window is not perceived by the user A, so that the user A can be refreshed to view the second object window as soon as possible by displaying the second object window first, and the user experience is improved.

In one possible embodiment, the first accessed client 131-1 deletes the object data of the second account displayed in the second object window in response to the ending processing operation triggered for the second account. When the object data of the second account displayed in the second object window is deleted, the account identifier of the second account displayed in the account list area can be deleted. The deleting the object data content displayed in the second object window may refer to the content discussed above, which is not described herein.

If the first accessed client 131-1 determines that the number of the idle windows in the idle window list reaches the preset threshold value, the second object window for deleting the object data is destroyed. The first accessed client 131-1 determines that the number of idle windows in the idle window list does not reach the preset threshold, and may mark the second object window for deleting the object data as an idle window for use by other accounts. The contents of the marking idle window, destroying window, etc. may refer to the contents discussed above, and will not be described herein.

It should be noted that, in fig. 2, the first object window for controlling the first account and the second object window for controlling the second account are taken as examples, and the window control method is actually executed by the object window for accessing each account, which is not described herein again.

It should be noted that, in fig. 2, the window control method according to the embodiment of the present application is described by taking the first accessed client 131-1 as an accessed client as an example, but any accessed client may actually execute the above scheme, which is not repeated here.

In the embodiment shown in fig. 2, an idle window can be created in advance, an object window and a window control can be multiplexed, the times of creating and destroying the window can be reduced, the running load of a machine is effectively reduced, and the program loading and clamping condition is avoided. In addition, when a new user accesses, only the user data pulled from the server is loaded into the existing idle window and displayed, time-consuming window creation operation is not needed, interface response speed is improved, interaction experience is improved, and the work efficiency of the user is facilitated.

In order to further explain the window control method according to the embodiment of the present application, the window control method according to the embodiment of the present application is described below with reference to an interaction diagram between devices in fig. 1 shown in fig. 6, and referring to fig. 6, the interaction procedure includes:

s601, the first access client 111-1 generates a first access request in response to the access operation.

Taking the first access client 111-1 as an example, when the user a needs to be served by a user corresponding to the access client, the user a may perform a corresponding access operation on the first access client 111-1, and the first access client responds to the access operation to generate a first access request. The first access request includes an account identifier of the first account of the first access client 111-1, and in addition, the first access request may further include object data of the first account, where the object data may refer to the content discussed above and will not be described herein.

For example, the accessed client and the access client are the same application, e.g., after the user a opens the first access client 111-1, the first access client 111-1 may display the access control, and the user a clicks the access control, which is equivalent to performing the access operation.

Or for example, the accessed client and the accessed client are applied differently, the accessed client responds to the attention operation of the user A for the corresponding public communication account, the accessed client can be accessed through the public communication account, and when the user A sends the communication message through the public communication account, the access operation is equivalent.

S602, the first access client 111-1 sends the first access request to the server 120.

S603, the server 120 sends the first access request to the first accessed client 131-1.

As previously discussed, there are a plurality of accessed clients, and the server 120 may screen the first accessed client 131-1 from the plurality of accessed clients and send the first access request to the first accessed client 131 in the manner previously discussed. Alternatively, the first access request designates the accessed client having a need for access as the first accessed client 131-1, and then the server 120 directly transmits the first access request to the first accessed client 131-1 after receiving the first access request.

It should be noted that, in fig. 6, the server 120 sends the first access request to the first accessed client 131-1 is taken as an example, but the device that sends the access request to the first accessed client 131-1 is not limited in practice, and for example, the first access client 111-1 may send the first access request directly to the first accessed client 131-1.

S604, the first accessed client 131-1 generates a query request.

After the first accessed client 131-1 receives the first access request, the first access request may be parsed to obtain an account identifier of the first account. In the embodiment of the present application, if the first access request does not carry the object data corresponding to the first account, the first accessed client 131-1 may generate a query request according to the account identifier of the first account, where the query request is used to request to query the object data of the first account.

S605, the first accessed client 131-1 sends a query request to the server 120.

S606, the server 120 sends the object data of the first account to the server 120.

After receiving the query request, the server 120 may query the object data corresponding to the first account according to the account identifier of the first account, and send the object data of the first account to the server 120.

As an example, S604 to S606 are optional parts.

S607, the first accessed client 131-1 displays the account identifier of the first account in the account list area.

S608, the first accessed client 131-1 displays the first object window in the window area in response to the clicking operation of the account identifier for the first account.

The manner in which the first object window is generated may refer to the foregoing discussion, and will not be described herein.

If the first accessed client 131-1 has already displayed other object windows corresponding to other accounts, the first accessed client 131-1 may not immediately skip to display the first object window after determining that the first account is accessed, for example, may display the first object window in the window area after the user a clicks on the account identifier of the first account. The manner of generating the first object window may refer to the content discussed in fig. 2, which is not described herein.

If the first accessed client 131-1 determines that the current display is the default window, the first accessed client 131-1 may directly display the first object window after determining that the first account is accessed.

After the first accessed client 131-1 displays the first object window, the user a may perform a corresponding operation on the first object window, perform service processing, and generate corresponding service processing data.

For example, referring to fig. 7, an exemplary diagram of a process for displaying a first object window is shown, when the first accessed client 131-1 does not have an accessed account, the first accessed client 131-1 displays a window control interface as shown in fig. 7 (1), a window area 710 in the window control interface displays a default window as shown in fig. 7 (1), and an account list area 720 in the window control interface is shown as empty.

After the first accessed client 131-1 determines that the first account is accessed, a first window control interface 700 corresponding to the user a as shown in (2) in fig. 7 may be displayed, where a first object window is displayed in a window area 710 in the first window control interface 700, and an account identifier of "user a" as shown in (2) in fig. 7 is displayed in an account list area 720. As can be seen from comparison between (1) in fig. 7 and (2) in fig. 7, the first object window shows the corresponding data of the user a, in particular, for example, the chat record of the user a with the customer service a, the personal information of the user a, and the like shown in (2) in fig. 7, compared with the default window.

In addition, the second window control interface 730 including the default window and the third window control interface 740 including the idle window are hidden under the first window control interface 700 of fig. 7 (2).

S609, the first accessed client 131-1 responds to the ending processing operation triggered by the first account, and deletes the object data of the first account displayed in the first object window.

An end control may be displayed in the first object window, where clicking the end control by the user a is equivalent to performing an end processing operation, or performing a closing triggering operation by the user a on the account identifier of the first account, which is equivalent to performing an end processing operation, and if the first accessed client 131-1 determines that the user a has already processed the service corresponding to the user a in response to the end processing operation, the object data of the first account displayed in the first object window may be deleted. At the same time, the first object window may also be hidden.

For example, referring to the window control interface shown in fig. 7 (2), when the user a clicks the "archive" button 701 shown in fig. 7 (2), it is equivalent to performing an end processing operation.

S610, if the first accessed client 131-1 determines that the number of the idle windows in the idle window list does not reach the preset threshold, the first object window after deleting the object data is marked as a first idle window.

After deleting the object data of the first account displayed by the first object window, the first accessed client 131-1 may determine the number of the saved idle windows in the idle window list, and if the number does not reach the preset threshold value, mark the first object window after deleting the object data as the first idle window. If the number reaches a preset threshold value, destroying the first object window after deleting the object data.

S610 is an optional step, for example, the first accessed client 131-1 may directly mark the first object window after deleting the object data as the first idle window without determining the number of idle windows in the idle window list.

S611, the first accessed client 131-1 may save the first idle window to the idle window list.

S611 is an optional step, for example, the first accessed client 131-1 may directly save the first idle window, without separately maintaining the idle window list.

S612, the second access client 111-2 generates a second access request in response to the access operation.

The content of the second access request may be referred to in the foregoing discussion, and will not be described in detail herein.

S613, the second access client 111-2 sends the second access request to the server 120.

S614, the server 120 sends the second access request to the first accessed client 131-1.

S615, the first accessed client 131-1 generates a second query request.

S616, the first accessed client 131-1 sends the second query request to the server 120.

S617, the server 120 transmits the object data of the second account to the first accessed client 131-1.

S618, the first accessed client 131-1 displays the account identifier of the second account in the account list area.

S619, the first accessed client 131-1 calls the first idle window in response to the clicking operation for the account identifier of the second account.

S620, the first accessed client 131-1 loads object data of the second account in the first idle window to obtain a second object window.

S621, the first accessed client 131-1 displays the second object window.

Similarly, after the second object window is displayed, the first accessed client 131-1 may switch the second object window to another object window corresponding to another account in the window control interface in response to a triggering operation for the account identifier of the other account in the account list area.

S622, if the first accessed client 131-1 determines that the number of idle windows in the idle window list does not reach the preset threshold value, a new idle window with the preset number is created, and the created new idle window is saved in the idle window list.

S623, the first accessed client 131-1 deletes the object data of the second account displayed in the second object window in response to the ending processing operation triggered for the second account.

When the object data of the second account displayed in the second object window is deleted, the account identifier of the second account displayed in the account list area can be deleted.

S624, if the first accessed client 131-1 determines that the number of the idle windows in the idle window list reaches the preset threshold value, the second object window of the deleted object data is destroyed.

It should be noted that S624 is an optional step, and if the first accessed client 131-1 determines that the number of free windows in the free window list does not reach the preset threshold, the second object window for deleting the object data may be marked as a free window for later use by other accounts.

For example, continuing with the example of fig. 7, after the account corresponding to the user C accesses the first accessed client 131-1, the first accessed client 131-1 may display a fourth window control interface 810 corresponding to the user C as shown in (1) in fig. 8, and hide the second window control interface 730, the third window control interface 740, and the first window control interface 700 under the fourth window control interface 810. Displayed on the fourth window control interface 810 is object data corresponding to the user C.

When the first accessed client 131-1 determines that the corresponding service processing of the first account is completed, the first accessed client 131-1 may mark the first object window as a first idle window, where the first idle window corresponds to the fifth window control interface 850, and at this time, the first accessed client 131-1 may display a fourth window control interface 810 as shown in (2) in fig. 8, and the second window control interface 730, the third window control interface 740, and the fifth window control interface 850 are hidden under the fourth window control interface 810.

After the second account corresponding to the user B accesses the first accessed client 131-1, the first accessed client 131-1 may display a sixth window control interface 810 corresponding to the user B as shown in (3) in fig. 8, and the second window control interface 730, the third window control interface 740, and the fourth window control interface 810 are hidden under the fourth window control interface 810.

It should be noted that, in fig. 6, the first object window for controlling the first account and the second object window for controlling the second account are taken as examples, and the window control method is actually executed by the object window for accessing each account, which is not described herein again.

In the embodiment shown in fig. 6, the first accessed client 131-1 may create a redundant idle window after a certain account is accessed, and after other accounts are accessed later, the object data of other accounts may be loaded and displayed in the idle window, which is beneficial to increasing the efficiency of displaying the object window. And because different accounts can multiplex the idle windows, the times of creating and destroying the windows can be relatively reduced, the processing capacity of the equipment can be reduced, and the system resource occupancy rate of the equipment can also be reduced.

Based on the same inventive concept, the implementation of the present application provides a window control device, which can be used to implement the functions of the accessed client as discussed above. Referring to fig. 9, the window control device includes:

the idle window obtaining module 901 is configured to delete object data of a first account displayed in a first object window in response to an ending processing operation triggered for the first account in a window control interface, so as to obtain an idle window;

An object window obtaining module 902, configured to add object data of a second account in the idle window in response to a start processing operation triggered for the second account in the window control interface, so as to obtain a second object window;

the display module 903 is configured to display the second object window in the window control interface.

In one possible embodiment, the idle window acquisition module 901 is further configured to:

deleting object data of a first account displayed by a first object window, and determining that the number of the saved idle windows in an idle window list does not reach a preset threshold before the idle windows are obtained, wherein the idle window list is used for saving the idle windows;

and deleting the object data of the first account number displayed by the first object window, and storing the idle window into an idle window list after obtaining the idle window.

In a possible embodiment, the window control display interface further includes an account list area for displaying account identifiers; the display module 903 is also configured to:

and hiding the first object window when ending processing operation triggered by the first account in the window control interface is responded, and deleting the account identification of the first account in the account list area.

In one possible embodiment, the presentation module 903 is further configured to:

in response to a start processing operation triggered by a second account in the window control interface, adding object data of the second account in the idle window to obtain a second object window, and displaying a default window in the window control interface if any accessed account does not exist currently; no object data is added in the default window; or alternatively, the process may be performed,

determining that the idle window is the idle window with the longest saved time in the idle window list; or alternatively, the process may be performed,

In one possible embodiment, the object window obtaining module 902 is specifically configured to:

when an access request for a second account is received, displaying an account identifier of the second account in an account list area in a window control interface;

and saving the new free window into the free window list.

In one possible embodiment, the idle window obtaining module 901 is specifically configured to:

creating a preset number of new idle windows according to the current system resource occupancy rate; the occupancy rate of system resources is inversely related to the preset quantity; the preset number is less than or equal to a preset threshold value.

after the second object window is displayed in the window control interface, responding to triggering operation of account identification of other accounts in the account list area, and switching the second object window to other object windows corresponding to other accounts in the window control interface, wherein the other accounts refer to accounts except the second account in the account list area.

The apparatus shown in fig. 9 may be used to implement any of the window control methods discussed above, and will not be described in detail herein.

Based on the same inventive concept, an embodiment of the present application provides a computer device, please refer to fig. 10, which includes a processor 1001 and a memory 1002.

The processor 1001 may be a central processing unit (central processing unit, CPU), or a digital processing unit or the like. The specific connection medium between the memory 1002 and the processor 1001 is not limited in the embodiments of the present application. In the embodiment of the present application, the memory 1002 and the processor 1001 are connected by the bus 1003 in fig. 10, the bus 1003 is shown by a thick line in fig. 10, and the connection manner between other components is only schematically illustrated, but not limited to. The bus 1003 may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, only one thick line is shown in fig. 10, but not only one bus or one type of bus.

The memory 1002 may be a volatile memory (RAM) such as a random-access memory (RAM); the memory 1002 may also be a non-volatile memory (non-volatile memory), such as a read-only memory, a flash memory (flash memory), a Hard Disk Drive (HDD) or a Solid State Drive (SSD), or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory 1002 may be a combination of the above.

The processor 1001, when configured to execute the window control method discussed above when invoking the computer program stored in the memory 1002, may also be configured to implement the functionality of the apparatus of fig. 9, and may also be configured to implement the corresponding functionality of the accessed client as discussed above.

Based on the same inventive concept, embodiments of the present application provide a storage medium storing computer instructions that, when run on a computer, cause the computer to perform any of the window control methods discussed above. The storage medium may be a computer storage medium.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Based on the same inventive concept, embodiments of the present application provide a computer program product comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the window control method described above.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, or the like, which can store program codes.

Alternatively, the above-described integrated units of the present application may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in essence or a part contributing to the prior art in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A window control method, comprising:

deleting object data of a first account displayed by a first object window in response to ending processing operation triggered by the first account in a window control interface to obtain a free window, wherein the object data of the first account comprises basic data of an object corresponding to the first account;

in response to a start processing operation triggered by a second account in the window control interface, adding object data of the second account in the idle window to obtain a second object window, wherein the object data of the second account comprises basic data of an object corresponding to the second account;

and displaying the second object window in the window control interface.

2. The method according to claim 1, wherein deleting the object data of the first account displayed in the first object window, before obtaining the idle window, includes:

Determining that the number of the saved idle windows in an idle window list does not reach a preset threshold value, wherein the idle window list is used for saving the idle windows;

the method further comprises the steps of after deleting the object data of the first account displayed in the first object window to obtain the idle window:

and storing the idle window into the idle window list.

3. The method of claim 1 or 2, wherein the window control display interface further comprises an account list area for displaying account identifications;

the method further comprises, in response to an end processing operation triggered in the window control interface for the first account, the steps of:

hiding the first object window, and deleting the account identification of the first account in the account list area.

4. The method of claim 3, wherein the method further comprises, before adding object data of a second account in the idle window to obtain a second object window in response to a start processing operation triggered for the second account in the window control interface:

if any accessed account number does not exist currently, displaying a default window in the window control interface; no object data is added in the default window; or alternatively, the process may be performed,

5. The method of claim 2, wherein the adding object data of the second account in the idle window in response to a start processing operation triggered in the window control interface for the second account to obtain a second object window comprises:

6. The method of claim 2, wherein the adding object data of the second account in the idle window in response to a start processing operation triggered in the window control interface for the second account to obtain a second object window comprises:

7. The method of claim 6, wherein after the second object window is presented in the window control interface, the method further comprises:

if the number of the saved idle windows in the idle window list does not reach a preset threshold value, creating a new idle window;

and storing the new idle window into the idle window list.

8. The method of claim 7, wherein creating a new idle window comprises:

9. The method of any of claims 6-8, wherein after the second object window is presented in the window control interface, the method further comprises:

and responding to triggering operation of account identification of other accounts in the account list area, and switching a second object window to other object windows corresponding to the other accounts in the window control interface, wherein the other accounts refer to accounts except the second account in the account list area.

10. A window control device, comprising:

the system comprises a free window acquisition module, a first account number acquisition module and a second account number acquisition module, wherein the free window acquisition module is used for deleting object data of the first account number displayed by a first object window in response to ending processing operation triggered by the first account number in a window control interface to obtain a free window, and the object data of the first account number comprises basic data of an object corresponding to the first account number;

the object window obtaining module is used for responding to a start processing operation triggered by a second account in the window control interface, and adding object data of the second account in the idle window to obtain a second object window, wherein the object data of the second account comprises basic data of an object corresponding to the second account;

11. The apparatus of claim 10, wherein the idle window acquisition module is further to:

12. A computer device, comprising:

at least one processor, and

a memory communicatively coupled to the at least one processor;

wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing the method of any one of claims 1-9 by executing the memory stored instructions.

13. A storage medium storing computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-9.