Terminal control method and engine architecture based on graphical user interface system

Abstract

The present application relates to a terminal control method, engine architecture, computer equipment and storage medium based on a graphical user interface system. The method comprises: in response to a request instruction of at least one sending terminal, loading and running a driver corresponding to the sending terminal that sends the request instruction, wherein the driver defines screen parameters corresponding to the sending terminal; when the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, traversing the message loop path, instructing the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameter, and obtain the execution result corresponding to the request instruction; based on the execution result, updating the interface of the sending terminal. The use of this method enables the control device to update the interfaces of multiple sending terminals based on the graphical user interface system.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a terminal control method, engine architecture, computer equipment and storage medium based on a graphical user interface system. Background Art

[0002] With the development of computer technology, graphical user interface technology has emerged. Graphical user interface technology uses graphics to display the computer operation user interface. Whether it is a Windows system or a Linux system, whether it is a multi-process system or a single-process or even a single-threaded system, it can have its own graphical user interface system. Applications with graphical interfaces run on the graphical user interface. Therefore, graphical user interface technology is widely used in electronic devices with graphical display interfaces.

[0003] However, the current graphical user interface system architecture only supports a single display touch screen, and cannot meet the problem of two or more display touch screens displaying different interface contents and implementing different touch operations. Summary of the invention

[0004] Based on this, it is necessary to provide a terminal control method, engine architecture, computer device and storage medium based on a graphical user interface system that can support multiple display touch screens in order to solve the above technical problems.

[0005] A terminal control method based on a graphical user interface system, the method comprising:

[0006] In response to a request instruction from at least one sending terminal, loading and running a driver corresponding to the sending terminal that sends the request instruction, wherein the driver defines screen parameters corresponding to the sending terminal;

[0007] When the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, traverse the message loop path, instruct the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameters, and obtain the execution result corresponding to the request instruction;

[0008] Based on the execution result, the interface of the sending terminal is updated.

[0009] In one embodiment, updating the interface of the sending terminal based on the execution result includes:

[0010] When there is a co-screen display identifier corresponding to the sending terminal, storing the execution result in a frame buffer of each sending terminal associated with the co-screen display identifier, and updating the interface of each sending terminal associated with the co-screen display identifier based on the frame buffer storing the execution result;

[0011] In one embodiment, updating the interface of the sending terminal based on the execution result includes:

[0012] The execution result is stored in a frame buffer of a sending terminal corresponding to the request instruction, and an interface of the sending terminal is updated based on the frame buffer storing the execution result.

[0013] In one embodiment, it also includes:

[0014] When the screen parameters enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, the message loop path is traversed, and based on the preset priorities of the screen parameters, request instructions corresponding to screen parameters with high priorities are preferentially executed.

[0015] In one embodiment, after responding to the request instruction of at least one sending terminal and before loading and running the driver corresponding to the sending terminal that sends the request instruction, the method includes:

[0016] The sending terminal is authenticated, and when the authentication is passed, a driver corresponding to the sending terminal that sends the request instruction is loaded and run.

[0017] In one embodiment, after loading and running a driver corresponding to a sending terminal that sends a request instruction, before the screen parameters of the sending terminal enter the message loop path of the graphical user interface via the engine layer of the graphical user interface system, the process includes:

[0018] Based on the loaded and executed driver program, the screen parameters are transferred to the engine layer of the graphical user interface system.

[0019] In one embodiment, traversing the message loop path to instruct the management layer of the graphical user interface system to execute a request instruction corresponding to the screen parameter includes:

[0020] Based on the screen parameters, access the management layer of the graphical user interface system, wherein the management layer includes an application management layer and a window management layer;

[0021] Instruct the application management layer and the window management layer to execute a request instruction corresponding to the screen parameter.

[0022] An engine architecture of a graphical user interface system, the engine architecture of the graphical user interface system comprising a device driver layer, an engine layer and a management layer; the output end of the device driver layer is connected to the input end of the engine layer, and the output end of the engine layer is connected to the management layer;

[0023] The device driver layer includes at least two driver programs with screen parameters defined therein, and is used to load and run a driver program corresponding to the sending terminal that sends the request instruction in response to a request instruction from at least one sending terminal;

[0024] The engine layer is used to transfer the screen parameters in the driver to the message loop path of the graphical user interface system;

[0025] The management layer is used to execute the request instruction corresponding to the screen parameter and obtain the execution result corresponding to the request instruction.

[0026] In one of the embodiments, the management layer is used to traverse the message loop path of the graphical user interface system when the screen parameters enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, and based on the preset priority of the screen parameters, preferentially execute request instructions corresponding to screen parameters with high priority.

[0027] In one of the embodiments, the device driver layer is used to transfer the screen parameters to the engine layer of the graphical user interface system based on the loaded and running driver program.

[0028] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0029] A computer-readable storage medium stores a computer program, which implements the steps of the above method when executed by a processor.

[0030] The terminal control method, engine architecture, computer device and storage medium based on the graphical user interface system described above, in response to a request instruction of at least one sending terminal, loads and runs a driver corresponding to the sending terminal that sends the request instruction, wherein the driver defines the screen parameters corresponding to the sending terminal; when the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, the message loop path is traversed to instruct the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameter, and obtain the execution result corresponding to the request instruction; based on the execution result, the interface of the sending terminal is updated. Among them, by loading the driver with the screen parameters corresponding to the sending terminal defined, when the screen parameters pass through the message loop path of the engine layer of the graphical user interface system, the message loop path is traversed to instruct the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameter, so that the control device can update the interface of two or more sending terminals based on the graphical user interface system through the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A diagram of an application environment of a graphical user interface system method in one embodiment;

[0032] Figure 2 A schematic diagram of a flow chart of a graphical user interface system method in one embodiment;

[0033] Figure 3 A structural block diagram of an engine architecture of a graphical user interface system in one embodiment;

[0034] Figure 4 A structural block diagram of an engine architecture of a graphical user interface system in another embodiment;

[0035] Figure 5 is an internal structure diagram of a computer device in another embodiment;

[0036] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0038] The terminal control method of the graphical user interface system provided in this application can be applied to Figure 1In the application environment shown, the control device 102 responds to a request instruction from at least one sending terminal, such as the sending terminal 104, the sending terminal 106, and the sending terminal 108; the control device 102 loads and runs a driver corresponding to the sending terminal that sends the request instruction, and the driver defines screen parameters corresponding to the sending terminal; when the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, the message loop path is traversed to instruct the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameter, and obtain the execution result corresponding to the request instruction; based on the execution result, the interface of the sending terminal is updated. The control device 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices.

[0039] In one embodiment, Figure 2 As shown, a terminal control method based on a graphical user interface system is provided, and the method is applied to Figure 1 Taking the control device 102 in the example as an example, the method includes the following steps:

[0040] Step 202: In response to a request instruction from at least one sending terminal, load and run a driver corresponding to the sending terminal that sends the request instruction, wherein the driver defines screen parameters corresponding to the sending terminal.

[0041] Among them, the sending terminal can be an electronic device that supports display and touch functions, or an electronic device that only supports display functions but not touch functions, or an electronic device that supports dual-touch and single-display functions. Among them, the dual-touch and single-display electronic device refers to an electronic device in which one screen module supports display and touch functions, and the other screen module supports touch functions but does not support display functions. The display screen of the electronic device can support the results generated after the touch functions from the two screen modules are triggered.

[0042] When the sending terminal is triggered by an external event such as a mouse, keyboard, button or touch, a request instruction is generated, and the control device responds to the request instruction of the sending terminal and loads and runs the driver corresponding to the sending terminal that sends the request instruction. The driver refers to a program that enables the control device to establish a communication connection with the sending terminal. Different sending terminals have corresponding drivers. The screen parameter refers to a parameter identifier corresponding to the sending terminal. For example, the screen parameter can be defined in the driver when developing the driver.

[0043] In one embodiment, the screen parameters can have a variety of different settings, for example, the screen parameters can be marked with letters, specifically, the screen parameter of the first sending terminal can be set to A, and correspondingly, the screen parameter of the second sending terminal can be set to B. Optionally, the electric stove head can also be marked with numbers, for example, the screen parameter of the first sending terminal can be set to 1, and correspondingly, the screen parameter of the second sending terminal can be set to 2.

[0044] Step 204, when the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, traverse the message loop path, instruct the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameters, and obtain the execution result corresponding to the request instruction.

[0045] Among them, the graphical user interface refers to a computer operation user interface that can be displayed in a graphical manner and is developed based on an object-oriented class library. For example, the object-oriented class library can be developed based on the Android Framework (Android application framework), iOS (mobile operating system developed by Apple) graphics library, QT (application development framework), etc. The graphical user interface system can run on a variety of operating systems such as Windows (windows) operating system, Linux operating system, single-threaded system, and multi-process system. Among them, the engine layer of the graphical user interface system includes a graphics engine layer and an event engine layer. By creating a virtual interface, the lower side of the graphics engine corresponds to the display screen connected to the sending terminal, and the lower side of the event engine corresponds to the input and output ports connected to the sending terminal.

[0046] When the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, the control device traverses the message loop path, instructs the management layer of the graphical user interface system, executes the request instruction corresponding to the screen parameters, and obtains the execution result corresponding to the request instruction. The message loop path refers to the process of the control device cyclically accessing the hierarchical structures of the graphical user interface system, and the hierarchical structure includes the engine layer, the management layer, etc. During the access process, the control device instructs the management layer of the graphical user interface system based on the screen parameters to execute the request instruction corresponding to the screen parameters. During the execution of the request instruction, the execution result corresponding to the request instruction can be obtained by calling the class function in the class library, creating an object, and calling a sequence of functions.

[0047] Step 206: Update the interface of the sending terminal based on the execution result.

[0048] The control device updates the interface of the sending terminal based on the obtained execution result corresponding to the request instruction. In one embodiment, if a calculator icon is displayed on the interface of one of the sending terminals, when the sending terminal is triggered by a mouse click or touch, etc., a request instruction is sent to the control device. After the control device processes the request instruction, the interface at the corresponding sending terminal is updated to an interface that can implement conventional calculation functions, and the user can implement the corresponding function based on the updated interface of the sending terminal.

[0049] In the terminal control method based on the graphical user interface system, by responding to the request instruction of at least one sending terminal, the driver corresponding to the sending terminal that sends the request instruction is loaded and run, and the screen parameters corresponding to the sending terminal are defined in the driver; when the screen parameters of the sending terminal enter the message loop path of the graphical user interface system through the engine layer of the graphical user interface system, the message loop path is traversed to instruct the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameter, and obtain the execution result corresponding to the request instruction; based on the execution result, the interface of the sending terminal is updated. Therefore, through the above method, the control device can update the interface of two or more sending terminals based on the graphical user interface system.

[0050] In one embodiment, updating the interface of the sending terminal based on the execution result includes:

[0051] When there is a co-screen display identifier corresponding to the sending terminal, the execution result is stored in the frame buffer of each sending terminal associated with the co-screen display identifier, and based on the frame buffer storing the execution result, the interface of each sending terminal associated with the co-screen display identifier is updated.

[0052] In one embodiment, updating the interface of the sending terminal based on the execution result includes:

[0053] The execution result is stored in a frame buffer of a sending terminal corresponding to the request instruction, and an interface of the sending terminal is updated based on the frame buffer storing the execution result.

[0054] Wherein, after the execution result is obtained, when there is a co-screen display identifier corresponding to the sending terminal, the execution result can be stored in the frame buffer of each sending terminal associated with the co-screen display identifier. Wherein, the co-screen display identifier can have a variety of different settings, for example, the co-screen display identifier can be marked with letters, the co-screen display identifier of sending terminal 1 is set to letter A, and the co-screen display identifier of sending terminal 2 is set to letter B. Optionally, the co-screen display identifier can also be marked with numbers. Specifically, the co-screen display identifier of sending terminal 1 is set to number 1, and the co-screen display identifier of sending terminal 2 is set to number 2. Based on the set co-screen display identifier, the co-display function of each sending terminal can be realized by setting the association relationship between each sending terminal and the co-screen display identifier. For example, taking the co-screen display identifier of sending terminal 1 as letter A as an example, the identifiers of other sending terminals that need to realize co-display with sending terminal 1 are set to a, thereby realizing the association relationship between the sending terminal and other sending terminals.

[0055] In one embodiment, if the sending terminal 3 and the sending terminal 4 need to realize the same display as the sending terminal 1 whose display identifier is letter A, the letter a is used to identify the sending terminal 3 and the sending terminal 4. After the execution result corresponding to the sending terminal 1 is obtained, it is detected that the sending terminal 1 has the shared screen display identifier A, and the sending terminal 3 and the sending terminal 4 have the identifier a associated with the shared screen display identifier A, then the execution result of the sending terminal 1 is stored in the frame buffer of the sending terminal 1, the sending terminal 3, and the sending terminal 4, and the interface of the sending terminal 1, the sending terminal 3, and the sending terminal 4 is updated based on the frame buffer storing the execution result. Thus, the interface of each sending terminal is displayed at the same time through the above method.

[0056] Among them, after obtaining the execution result, the execution result can also be stored in the frame buffer of the sending terminal corresponding to the request instruction, and the interface of the sending terminal can be updated based on the execution result of the frame buffer storing the execution result, so as to realize the different display of the interface of each sending terminal through the above method.

[0057] In one embodiment, the method further comprises:

[0058] When the screen parameters enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, the message loop path is traversed, and based on the preset priorities of the screen parameters, request instructions corresponding to screen parameters with high priorities are preferentially executed.

[0059] Among them, the priority of the screen parameters can be set so that when multiple screen parameters enter the message loop path of the graphical user interface system through the engine layer of the graphical user interface system, the message loop path can be traversed and the request instructions corresponding to the screen parameters with high priority can be executed based on the preset priority.

[0060] In one embodiment, after responding to the request instruction of at least one sending terminal and before loading and running the driver corresponding to the sending terminal that sends the request instruction, the method includes:

[0061] The sending terminal is authenticated, and when the authentication is passed, a driver corresponding to the sending terminal that sends the request instruction is loaded and run.

[0062] Among them, before establishing communication between the control device and the sending terminal, the identity of the sending terminal can also be authenticated. Only when the identity authentication is passed, can the driver corresponding to the sending terminal that sends the request instruction be loaded and run. For example, the method for identity authentication can be that after the control device responds to the request instruction of the sending terminal, the device identification pre-stored in the database is called, and the device identification stored in the database is matched with the device identification of the sending terminal. If the device identification pre-stored in the database contains a device identification that matches the device identification of the sending terminal, it means that the sending terminal that sends the request instruction at this time is safe and legal, and the next step of loading the driver program can be performed. Therefore, the legitimacy of the sending terminal can be verified by the above method.

[0063] In one embodiment, after loading and running a driver corresponding to a sending terminal that sends a request instruction, before the screen parameters of the sending terminal enter the message loop path of the graphical user interface via the engine layer of the graphical user interface system, the process includes:

[0064] Based on the loaded and executed driver program, the screen parameters are transferred to the engine layer of the graphical user interface system.

[0065] When the driver program is loaded and run, the screen parameters defined in the driver program can be written into the data structure of the driver program, thereby transferring the screen parameters to the engine layer of the graphical user interface system.

[0066] In one embodiment, traversing the message loop path to instruct the management layer of the graphical user interface system to execute a request instruction corresponding to the screen parameter includes:

[0067] Based on the screen parameters, access the management layer of the graphical user interface system, wherein the management layer includes an application management layer and a window management layer;

[0068] Instruct the application management layer and the window management layer to execute a request instruction corresponding to the screen parameter.

[0069] Among them, the management layer of the graphical user interface system includes the application management layer and the window management layer. The application management layer is responsible for the scheduling and operation of applications, and the window management layer is responsible for the sequence management of windows, focus switching, etc. Under the cooperation of the application management layer and the graphics management layer, the request instructions corresponding to the screen parameters are executed.

[0070] In one embodiment, if Figure 3 As shown, an engine architecture of a graphical user interface system is provided, and the engine architecture of the graphical user interface system includes a device driver layer 302, an engine layer 304 and a management layer 306; the output end of the device driver layer is connected to the input end of the engine layer, and the output end of the engine layer is connected to the management layer.

[0071] The device driver layer 302 includes at least two driver programs with screen parameters defined therein, and is used to load and run a driver program corresponding to the sending terminal that sends the request instruction in response to a request instruction from at least one sending terminal.

[0072] The engine layer 304 is used to transfer the screen parameters in the driver to the message loop path of the graphical user interface system.

[0073] The management layer 306 is used to execute the request instruction corresponding to the screen parameter and obtain the execution result corresponding to the request instruction.

[0074] The engine architecture of the graphical user interface system includes a device driver layer 302, an engine layer 304, and a management layer 306. The device driver layer 302 includes at least two driver programs with screen parameters defined, wherein the screen parameters refer to parameter identifiers corresponding to the sending terminal, and the driver program refers to a special program that enables the sending terminal and the graphical user interface system to establish a communication connection. The device driver layer is used to respond to a request instruction from at least one sending terminal and load and run a driver program corresponding to the sending terminal that sends the request instruction.

[0075] The engine layer 304 is used to transfer the screen parameters in the driver to the message loop path of the graphical user interface system. The message loop path refers to the process of controlling the device to cyclically access the hierarchical structures of the graphical user interface system, which include the engine layer, the management layer, etc.

[0076] The management layer 306 is used to execute the request instruction corresponding to the screen parameter and obtain the execution result corresponding to the request instruction. During the process of executing the request instruction, the control device can obtain the execution result corresponding to the request instruction by calling the class function in the class library, creating objects and calling a sequence of functions.

[0077] In one of the embodiments, the management layer is used to traverse the message loop path of the graphical user interface system when the screen parameters enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, and based on the preset priority of the screen parameters, preferentially execute request instructions corresponding to screen parameters with high priority.

[0078] In one of the embodiments, the device driver layer is used to transfer the screen parameters to the engine layer of the graphical user interface system based on the loaded and running driver program.

[0079] In one embodiment, if Figure 4 , which is a structural diagram of a terminal control method implemented based on an engine architecture of a graphical user interface system in a specific embodiment.

[0080] Among them, the device driver layer is defined with at least two driver programs that define screen parameters. The screen parameters refer to parameter identifiers corresponding to the sending terminal. The driver program refers to a program that can establish a communication connection between the control device and the sending terminal. Different sending terminals correspond to corresponding driver programs. When the device driver layer responds to a request instruction from at least one sending terminal and loads and runs the driver program in the device driver layer, the screen parameters enter the graphical user interface engine layer through the device driver layer.

[0081] The engine layer of the graphical user interface system includes a graphics engine layer and an event engine layer. By creating a virtual interface, the graphics engine corresponds to the display function of the connected sending terminal, and the event engine corresponds to the input and output function of the connected sending terminal.

[0082] When the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, the control device traverses the message loop path, instructs the application management layer and the window management layer of the graphical user interface system, executes the request instruction corresponding to the screen parameters, and obtains the execution result corresponding to the request instruction. The message loop path refers to the process of the control device cyclically accessing the hierarchical structures of the graphical user interface system, and the hierarchical structure includes the engine layer, the application management layer, the window management layer, etc. During the access process, the control device instructs the application management layer and the window management layer of the graphical user interface system based on the screen parameters to execute the request instruction corresponding to the screen parameters. During the execution of the request instruction, the execution result corresponding to the request instruction can be obtained by calling the application program in the class library, creating an object, and calling a sequence of functions.

[0083] It should be understood that although Figure 2The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0084] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store a class library of a graphical user interface system. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a terminal control method of the above-mentioned graphical user interface system is implemented.

[0085] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a terminal control method of a graphical user interface system is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0086] Those skilled in the art will understand that Figure 5 , Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0087] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the terminal control method of the graphical user interface system when executing the computer program.

[0088] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the terminal control method of the graphical user interface system is implemented.

[0089] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0090] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0091] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A terminal control method based on a graphical user interface system, characterized in that: The method comprises: In response to a request instruction from at least one sending terminal, loading and running a driver corresponding to the sending terminal that sends the request instruction, wherein the driver defines screen parameters corresponding to the sending terminal; When the screen parameters of the sending terminal enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, traverse the message loop path, instruct the management layer of the graphical user interface system to execute the request instruction corresponding to the screen parameters, and obtain the execution result corresponding to the request instruction; Based on the execution result, updating the interface of the sending terminal; The executing the request instruction corresponding to the screen parameter to obtain the execution result corresponding to the request instruction includes: The execution result corresponding to the request instruction is obtained by calling the class function in the class library, creating an object and calling the sequence of functions.

2. The method according to claim 1, characterized in that The updating the interface of the sending terminal based on the execution result includes: When there is a co-screen display identifier corresponding to the sending terminal, storing the execution result in a frame buffer of each sending terminal associated with the co-screen display identifier, and updating the interface of each sending terminal associated with the co-screen display identifier based on the frame buffer storing the execution result; or, The execution result is stored in a frame buffer of a sending terminal corresponding to the request instruction, and an interface of the sending terminal is updated based on the frame buffer storing the execution result.

3. The method according to claim 1, characterized in that: Also includes: When the screen parameters enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, the message loop path is traversed, and based on the preset priorities of the screen parameters, request instructions corresponding to screen parameters with high priorities are preferentially executed.

4. The method according to claim 1, characterized in that: After responding to the request instruction of at least one sending terminal and before loading and running the driver corresponding to the sending terminal sending the request instruction, the method includes: The sending terminal is authenticated, and when the authentication is passed, a driver corresponding to the sending terminal that sends the request instruction is loaded and run.

5. The method according to claim 1, characterized in that After loading and running a driver corresponding to a sending terminal that sends a request instruction, before the screen parameters of the sending terminal enter the message loop path of the graphical user interface via the engine layer of the graphical user interface system, the process includes: Based on the loaded and executed driver program, the screen parameters are transferred to the engine layer of the graphical user interface system.

6. The method according to claim 1, characterized in that The traversing the message loop path and instructing the management layer of the graphical user interface system to execute a request instruction corresponding to the screen parameter includes: Based on the screen parameters, access the management layer of the graphical user interface system, wherein the management layer includes an application management layer and a window management layer; Instruct the application management layer and the window management layer to execute a request instruction corresponding to the screen parameter.

7. An engine architecture of a graphical user interface system, characterized in that: The engine architecture of the graphical user interface system includes a device driver layer, an engine layer and a management layer; the output end of the device driver layer is connected to the input end of the engine layer, and the output end of the engine layer is connected to the management layer; The device driver layer includes at least two driver programs with screen parameters defined therein, and is used to load and run a driver program corresponding to the sending terminal that sends the request instruction in response to a request instruction from at least one sending terminal; The engine layer is used to transfer the screen parameters in the driver to the message loop path of the graphical user interface system; The management layer is used to execute the request instruction corresponding to the screen parameter and obtain the execution result corresponding to the request instruction; The executing the request instruction corresponding to the screen parameter to obtain the execution result corresponding to the request instruction includes: The execution result corresponding to the request instruction is obtained by calling the class function in the class library, creating an object and calling the sequence of functions.

8. The engine architecture of the graphical user interface system according to claim 7, characterized in that: The management layer is used to traverse the message loop path when the screen parameters enter the message loop path of the graphical user interface system via the engine layer of the graphical user interface system, and based on the preset priorities of the screen parameters, preferentially execute request instructions corresponding to screen parameters with high priorities.

9. The engine architecture of the graphical user interface system according to claim 7, characterized in that: The device driver layer is used to transfer the screen parameters to the engine layer of the graphical user interface system based on the loaded and running driver program.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

Images