UI-based small-screen equipment control method and system
By separating the UI from application logic on small-screen devices, the UI process focuses on interaction, and the application sub-process focuses on data processing, which solves the problem of slow response speed and improves response efficiency and system stability.
Patent Information
- Application Number
- CN202510813954.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-18
- Publication Date
- 2025-09-30
AI Technical Summary
When developing UIs and applications for small-screen devices on the Linux operating system, conventional solutions result in high software complexity and low CPU utilization, leading to slow responses and unable to meet the real-time requirements of the medical and industrial control fields.
By separating the UI from the application logic, the UI process focuses on user interaction, and the application sub-process focuses on data processing and device control. The fork() function is used to create independent application sub-processes, and they interact through pipe communication to ensure the correct release of resources and system stability.
It reduces software complexity, improves the response efficiency of UI processes and application sub-processes, solves the problem of slow UI response speed, and improves system stability and resource utilization.
Smart Images
Figure CN120723328A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of small-screen device control, and in particular, to a UI-based small-screen device control method and system. Background Art
[0002] With the widespread adoption of embedded devices and mobile terminals, demand for small-screen devices is growing in healthcare, industrial control, smart home, and other fields. Efficient software operation and convenient interaction are crucial for these devices. When developing UIs and applications based on the Flythings interactive operating system on a Linux operating system, the typical approach is to integrate the UI with applications and data, allowing for direct data manipulation or application logic execution through UI interaction. This conventional approach suffers from excessive engineering software complexity and inadequate CPU utilization in the product software.
[0003] For example, in healthcare scenarios, medical staff need to quickly and accurately operate medical software on small-screen devices to create and execute training programs. However, conventional solutions underutilize CPU resources, resulting in slow response times when handling multiple tasks and hindering medical efficiency. In the industrial control field, operators need to monitor and control production processes in real time using small-screen devices. Complex software architectures result in slow system responses and fail to meet the stringent real-time requirements of industrial production. These issues urgently require new technical solutions. Summary of the Invention
[0004] The embodiments of the present invention provide a UI-based small-screen device control method and system to at least solve the problem of slow UI task response speed in the related art.
[0005] According to one embodiment of the present invention, a UI-based small-screen device control method is provided, comprising: Obtaining a UI process start instruction, wherein the UI process start instruction is obtained based on an interactive operation; Based on the UI process startup instruction, calling a first function to create an application sub-process, wherein the application sub-process is independent of the UI process; The application sub-process executes a target action according to the action signal sent by the UI process.
[0006] In an exemplary embodiment, after calling the first function to create the application sub-process based on the UI process startup instruction, the method further includes: Get a shutdown message from the UI process; The application sub-process performs a cleanup operation according to the close message and calls a second function to end the application sub-process.
[0007] In an exemplary embodiment, the application sub-process performs a cleanup operation according to the close message, and calls a second function to end the application sub-process, including: If the application sub-process does not end within a predetermined time, the UI process performs action waiting; When the action waiting time is greater than the first time and the application sub-process has not yet ended, the UI process forcibly ends the application sub-process.
[0008] In an exemplary embodiment, the application sub-process executing the target action according to the action signal sent by the UI process includes: If the application sub-process fails to successfully execute the target action, sending feedback information to the UI process; The UI process performs a UI prompt for the feedback information.
[0009] In an exemplary embodiment, before the application sub-process performs the target action according to the action signal sent by the UI process, the method further includes: Acquiring device information and design information, wherein the device information includes device screen information, and the design information includes font information and image resolution; Determining a font dynamic value and an image dynamic value according to the device screen information, font information, and image resolution; The UI process sends an action instruction to the application sub-process based on the font dynamic value and the image dynamic value.
[0010] According to another embodiment of the present invention, a UI-based small-screen device control system is provided, including: A startup instruction module is used to obtain a UI process startup instruction, wherein the UI process startup instruction is obtained based on an interactive operation; a sub-process creation module, configured to call a first function to create an application sub-process based on the UI process startup instruction, wherein the application sub-process is independent of the UI process; An action execution module is used for the application sub-process to execute a target action according to the action signal sent by the UI process.
[0011] In an exemplary embodiment, it further includes: A closing message obtaining module, configured to obtain a closing message from the UI process after the first function is called to create an application sub-process based on the UI process starting instruction; The application sub-process performs a cleanup operation according to the close message and calls a second function to end the application sub-process.
[0012] In an exemplary embodiment, the application sub-process performs a cleanup operation according to the close message, and calls a second function to end the application sub-process, including: If the application sub-process does not end within a predetermined time, the UI process performs action waiting; When the action waiting time is greater than the first time and the application sub-process has not yet ended, the UI process forcibly ends the application sub-process.
[0013] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.
[0014] According to another embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.
[0015] Through the present invention, by separating the UI from the application logic, the UI process focuses on user interaction, and the application sub-process focuses on data processing and device control, thereby reducing the complexity of the software and improving the response efficiency of the UI process and application sub-process. Therefore, the problem of slow UI response speed can be solved, thereby achieving the effect of improving the UI response speed. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 is a flowchart of a small-screen device control method based on UI according to an embodiment of the present invention; Figure 2 It is a flow chart of a specific embodiment of the present invention; Figure 3 This is a structural block diagram of a small-screen device control system based on UI according to an embodiment of the present invention. DETAILED DESCRIPTION
[0017] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments.
[0018] Hereinafter, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature identified with "first," "second," etc., may explicitly or implicitly include one or more of the features. In the description of this application, unless otherwise specified, "plurality" means two or more.
[0019] In addition, in this application, directional terms such as "up", "down", "left", and "right" may be defined including but not limited to the orientation relative to the schematic placement of the components in the drawings. It should be understood that these directional terms may be relative concepts. They are used for relative descriptions and clarifications, and they may change accordingly according to changes in the orientation of the components in the drawings.
[0020] In this application, unless otherwise specified or limited, the term "connection" should be understood broadly. For example, "connection" can mean fixed connection, detachable connection, or integration; it can mean direct connection or indirect connection through an intermediate medium. In addition, the term "coupling" can refer to the manner in which electrical connection is achieved for signal transmission.
[0021] As used herein, "about," "substantially," or "approximately" includes the stated value and an average value that is within an acceptable range of deviation from the particular value as determined by one of ordinary skill in the art taking into account the measurements in question and the errors associated with the measurement of the particular quantity (i.e., the limitations of the measurement system).
[0022] In the field of small-screen devices, UI and applications are usually developed based on the flythings interactive operating system. This type of product has poor response speed and high memory usage, so a new interactive control method needs to be developed to improve response efficiency.
[0023] In this embodiment, a small screen device control method based on UI is provided. Figure 1 is a flowchart of a small-screen device control method based on UI according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps: Step S11, obtaining a UI process start instruction, wherein the UI process start instruction is obtained based on an interactive operation; In this embodiment, when the user interacts, the user first inputs the interaction instructions through the operation buttons of the UI interface on the screen, such as clicking a button, entering parameters, etc. At this time, the processing module in the system captures and analyzes the interaction instructions through the UI process, thereby obtaining UI process instructions for performing related operations, where the UI process instructions can be instructions for indicating the device operations that need to be performed, and the device operations that need to be performed can be data reading and writing, device driver control, UI interface changes, etc.
[0024] Taking the process from creating a training project to executing a training project for a medical product as an example, the UI software interacts with the product user, and the user's interactive operation (i.e., the aforementioned interactive operation) selects training parameters for the training project. The selected training parameters are one of the UI process startup instructions.
[0025] Step S12: Based on the UI process startup instruction, calling a first function to create an application sub-process, wherein the application sub-process is independent of the UI process; In this embodiment, after the UI process is started, the UI process first notifies the application software that actually performs the corresponding operation to establish a corresponding sub-process, so as to perform the corresponding operation through the sub-process; wherein the first function may be a fork() function.
[0026] For example, the UI process calls the fork() function provided by the system to create a child process. The fork() function will create a child process (the aforementioned application child process) that is almost identical to the parent process (the aforementioned UI process). After the fork() function is called, the parent process and the child process have their own independent memory space, but share some resources. It should be noted that the UI process and the application child process are independent of each other, so that the error of one process will not directly affect the other process. For example, when the application child process fails to start, the UI process can still run normally and prompt the user with an error message, which greatly increases the stability of the system.
[0027] Step S13: the application sub-process executes a target action according to the action signal sent by the UI process.
[0028] In this embodiment, after establishing a child process, the application executes corresponding operation actions according to the operation instructions contained in the instructions of the UI process. This process reduces the logic that the UI needs to process, that is, the UI only needs to generate and send relevant instructions, without the need for additional identification, analysis and processing of action logic. The application only needs to execute corresponding operations according to the control words in the instructions, and there is no need to analyze the action logic, which greatly reduces the computing power requirements and improves the UI response efficiency.
[0029] Specifically, the parent process (i.e., the aforementioned UI process) notifies the child process to initialize relevant resources (i.e., the aforementioned target action) by sending a specific startup message to the child process (e.g., sending a startup signal through pipe communication, i.e., the aforementioned action signal), such as loading a database configuration file, initializing a device driver, etc.
[0030] For example, the UI process generates an action signal based on the user's operation and sends it to the application sub-process via UDP communication or other inter-process communication mechanisms. For example, if the user sets training parameters on the UI interface and starts training, the UI process sends these parameters and the start command as an action signal to the application sub-process. After receiving the action signal, the application sub-process parses it to determine the specific target action to be performed. For example, it parses the training parameters set by the user and the command to start training. The application sub-process then executes the corresponding logic based on the parsed instructions, such as reading or writing data based on the training parameters, controlling the device driver, etc., to complete the operation requested by the user.
[0031] It should be noted that separating the UI from the application logic makes the software development architecture clearer, that is, the UI process focuses on user interaction, and the application sub-process focuses on data processing and device control, thereby reducing the complexity of the software and improving development efficiency; and for products with similar functional divisions or UI displays, this method can reduce product development time, improve program maintainability, and improve the reusability of functional module programs; and the multi-process parallel execution method can fully utilize the advantages of multi-core processors and greatly improve software operation efficiency.
[0032] Through the above steps, by separating the UI from the application logic, the UI process focuses on user interaction, and the application sub-process focuses on data processing and device control, thereby reducing the complexity of the software, improving the response efficiency of the UI process and application sub-process, solving the problem of slow UI response speed, and improving the UI response speed.
[0033] The following is an explanation using specific examples.
[0034] like Figure 2 As shown, this application uses the flythings interactive operating system to develop interactive UI and database operation interfaces, and uniformly packages them into static libraries, and develops the application software separately as process firmware, starts / ends the application software process when the interactive UI software process starts and ends, and communicates between processes through UDP.
[0035] Taking the process from creating a training project to executing a training project for a medical product as an example, the UI software interacts with the product user, and the training parameters are selected for training through the user's interactive operations. The UI process notifies the application software to perform data operations, and the application software executes the corresponding logic (data reading and writing, device driver control) through the corresponding control words to reduce the logic that the UI needs to process.
[0036] Specifically, when the interactive UI software process is started, a child process is created by calling the system's fork() function, and the child process is the application software process.
[0037] After the fork() function is called, the parent process (ie the aforementioned interactive UI software process) and the child process (ie the aforementioned application software process) have their own independent memory space, but share some resources.
[0038] Afterwards, the parent process notifies the child process to initialize related resources, such as loading database configuration files and initializing device drivers, by sending a specific startup message to the child process (such as sending a startup signal through pipe communication).
[0039] In an optional embodiment, after calling the first function to create the application sub-process based on the UI process startup instruction, the method further includes: Step S121, obtaining a close message from the UI process; Step S122: the application sub-process performs a cleanup operation according to the close message, and calls a second function to terminate the application sub-process.
[0040] In this embodiment, in the UI-based small-screen startup method, the closing process of the application sub-process is an important link, which ensures the correct release of resources and the stable operation of the system; and closing the application sub-process at the same time as closing the UI process can maximize the release of resources, so that other processes can effectively call related resources, thereby improving the resource reuse rate.
[0041] The second function can be the exit() function (or other similar system call). When the UI process needs to shut down the application subprocess, it sends a shutdown message to the application subprocess via a predefined communication mechanism (such as a pipe, UDP, or TCP). This shutdown message typically contains a specific instruction or flag indicating the need to shut down the subprocess. The application subprocess receives the message from the UI process by listening on the communication channel. Once the shutdown message is received, the application child process will enter the cleanup phase; if the application child process opens a database connection during operation, these connections need to be released before closing to avoid data loss or database table locks; if the application child process controls hardware devices (such as sensors, drives, etc.), these device resources need to be released correctly to ensure that the devices can be safely used by other processes or systems; if the application child process generates important status information or temporary data during operation, this information needs to be saved to persistent storage so that it can be restored or processed later; after the cleanup operation or resource release operation is completed, the application child process calls the exit() function (or other similar system calls) to end its own process. The exit() function notifies the operating system to release the resources occupied by the process, including memory, file descriptors, etc.; at this time, the UI process (parent process) usually calls the wait() or waitpid() function to wait for the application child process (child process) to end to ensure that the child process has completely exited and released all resources.
[0042] Specifically, when the interactive UI software process ends, it first sends a close message to the application software process. After receiving the message, the application software process performs cleanup operations, such as closing database connections, releasing device resources, etc., and then calls the exit() function to end its own process.
[0043] It should be noted that by calling the exit() function and letting the parent process correctly wait for the child process to end, the child process can be prevented from becoming a zombie process, thereby improving the overall stability of the system.
[0044] In an optional embodiment, the application sub-process performs a cleanup operation according to the close message, and calls a second function to end the application sub-process, including: Step S1221: If the application sub-process does not end within a predetermined time, the UI process performs an action wait; Step S1222: When the action waiting time is greater than the first time and the application sub-process has not yet ended, the UI process forcibly ends the application sub-process.
[0045] In this embodiment, if the application sub-process cannot be closed smoothly, the UI process will wait first, and if it is still not closed, it will be forcibly closed, thereby ensuring that the application sub-process can be completely terminated and the normal operation of the system is guaranteed.
[0046] Specifically, if the application software process is not closed in time (i.e., it is not ended within the scheduled time), the interactive UI software process will wait for a certain period of time (i.e., the first time mentioned above, such as 5 seconds). If it is not closed successfully after the timeout (i.e., the time mentioned above is greater than the first time), the application software process will be forcibly terminated to ensure the normal operation of the system.
[0047] It should be noted that before closing the child process, state information and temporary data need to be saved to prevent data loss and ensure that the system can be correctly restored or continue processing in subsequent operations.
[0048] In an optional embodiment, the application sub-process executing the target action according to the action signal sent by the UI process includes: Step S131, sending feedback information to the UI process when the application sub-process fails to successfully execute the target action; Step S132: The UI process performs a UI prompt for the feedback information.
[0049] In this embodiment, if the application sub-process is not closed normally, a UI prompt is given, so that the user can perform subsequent processing in time.
[0050] Among them, the UI prompt can be a text prompt or a voice prompt on the UI interface; the target action can be a process start, a process close, etc., which is not limited here.
[0051] For example, during the entire process, if the application software sub-process fails to start (such as initialization failure due to insufficient resources), the interactive UI software process will receive corresponding error feedback and prompt the user on the UI interface: "Application software startup failed, please check the device status."
[0052] In an optional embodiment, before the application sub-process performs the target action according to the action signal sent by the UI process, the method further includes: Step S1301, obtaining device information and design information, wherein the device information includes device screen information, and the design information includes font information and image resolution; Step S1302, determining a font dynamic value and an image dynamic value according to the device screen information, font information, and image resolution; Step S1303: The UI process sends an action instruction to the application sub-process based on the font dynamic value and the image dynamic value.
[0053] In this embodiment, for small-screen devices, when displaying images or fonts, the UI interface needs to ensure the adaptability of the font screen to the screen size to ensure that the font screen can be effectively viewed by users after the interface changes. In order to reduce the difficulty of development, it is necessary to enable devices of different sizes to automatically adjust the font screen.
[0054] Assume that the screen width is W (in logical pixels, such as dp / dip / pt), the image width is D (in dp, such as 375 dp), and the font size in the image is (unit is sp, such as 16 sp), the image resolution is The image resolution scaling exponent is α (recommended 0.7-0.9), which is used to control the relationship between resolution and screen width. The image resolution scaling exponent α is set because the screen area grows to W. 2 , but the human eye only needs W to perceive the resolution 1.5 Therefore, by setting the image resolution scaling exponent α, we can balance screen clarity while avoiding resource waste; the font scaling exponent is β (recommended 0.3-0.6), which is used to control the rate at which the font grows with the screen width. This is to avoid the font growing too fast and make the presented font consistent with human eye perception. Therefore: (Formula 1) (Formula 2) Where F is the dynamic size of the font in the image, R is the dynamic resolution of the image, and c is the minimum font size compensation value (such as 2sp), which is used to prevent the font size from being too small on extremely small screens. It is the ratio of the screen width to the design width, used to convert the size of the design to the actual screen size. If you want the visual density of text and image details to be consistent, you need to meet the following requirements: (Formula 3) In particular, the following Table 1 can be used for parameter selection: Table 1 Through the description of the above embodiments, those skilled in the art will clearly understand that the methods according to the above embodiments can be implemented using software plus the necessary general-purpose hardware platform. Of course, hardware can also be used, but in many cases the former is a more preferred embodiment. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, or optical disk) and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present invention.
[0055] In this embodiment, a small-screen device control system based on UI is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the details that have been described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation by hardware, or a combination of software and hardware, is also possible and conceivable.
[0056] Figure 3 is a structural block diagram of a small-screen device control system based on UI according to an embodiment of the present invention, such as Figure 3 As shown, the system includes: A startup instruction module 21 is configured to obtain a UI process startup instruction, wherein the UI process startup instruction is obtained based on an interactive operation; A sub-process establishing module 22 is configured to call a first function to create an application sub-process based on the UI process starting instruction, wherein the application sub-process is independent of the UI process; The action execution module 23 is configured to cause the application sub-process to execute a target action according to an action signal sent by the UI process.
[0057] In an optional embodiment, the method further includes: A closing message obtaining module, configured to obtain a closing message from the UI process after the first function is called to create an application sub-process based on the UI process starting instruction; The application sub-process performs a cleanup operation according to the close message and calls a second function to end the application sub-process.
[0058] In an optional embodiment, the application sub-process performs a cleanup operation according to the close message, and calls a second function to end the application sub-process, including: If the application sub-process does not end within a predetermined time, the UI process performs action waiting; When the action waiting time is greater than the first time and the application sub-process has not yet ended, the UI process forcibly ends the application sub-process.
[0059] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.
[0060] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.
[0061] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
[0062] An embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
[0063] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.
[0064] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0065] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0066] Units described as separate components may or may not be physically separate, and components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0067] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0068] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program code.
[0069] The above content is only a specific embodiment of this application, but the scope of protection of this application is not limited to this. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A small screen device control method based on UI, characterized in that: include: Obtaining a UI process start instruction, wherein the UI process start instruction is obtained based on an interactive operation; Based on the UI process startup instruction, calling a first function to create an application sub-process, wherein the application sub-process is independent of the UI process; The application sub-process executes a target action according to the action signal sent by the UI process.
2. The method according to claim 1, characterized in that After calling the first function to create the application sub-process based on the UI process startup instruction, the method further includes: Get a shutdown message from the UI process; The application sub-process performs a cleanup operation according to the close message and calls a second function to end the application sub-process.
3. The method according to claim 2, characterized in that The application sub-process performs a cleanup operation according to the close message, and calls a second function to end the application sub-process, including: If the application sub-process does not end within a predetermined time, the UI process performs an action wait; When the action waiting time is greater than the first time and the application sub-process has not yet ended, the UI process forcibly ends the application sub-process.
4. The method according to claim 1, wherein The application sub-process executing the target action according to the action signal sent by the UI process includes: If the application sub-process fails to successfully execute the target action, sending feedback information to the UI process; The UI process performs a UI prompt for the feedback information.
5. The method according to claim 1, characterized in that Before the application sub-process performs the target action according to the action signal sent by the UI process, the method further includes: Acquiring device information and design information, wherein the device information includes device screen information, and the design information includes font information and image resolution; Determining a font dynamic value and an image dynamic value according to the device screen information, font information, and image resolution; The UI process sends an action instruction to the application sub-process based on the font dynamic value and the image dynamic value.
6. A small screen device control system based on UI, characterized in that: include: A startup instruction module is used to obtain a UI process startup instruction, wherein the UI process startup instruction is obtained based on an interactive operation; a sub-process creation module, configured to call a first function to create an application sub-process based on the UI process startup instruction, wherein the application sub-process is independent of the UI process; An action execution module is used for the application sub-process to execute a target action according to the action signal sent by the UI process.
7. The method according to claim 5, characterized in that Also includes: A closing message obtaining module, configured to obtain a closing message from the UI process after the first function is called to create an application sub-process based on the UI process starting instruction; The application sub-process performs a cleanup operation according to the close message and calls a second function to end the application sub-process.
8. The method according to claim 7, wherein: The application sub-process performs a cleanup operation according to the close message, and calls a second function to end the application sub-process, including: If the application sub-process does not end within a predetermined time, the UI process performs an action wait; When the action waiting time is greater than the first time and the application sub-process has not yet ended, the UI process forcibly ends the application sub-process.
9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 5 when executed.
10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 5.