Interface display control method, and electronic device, vehicle, mediums and product

Abstract

An interface display control method, and an electronic device, a vehicle, mediums and a product. The method comprises: in response to a trigger operation acting on a first application interface and used for pulling up a second application interface, acquiring a first process of the first application interface, wherein the process of the first application interface and the process of the second application interface are different processes; in response to the first process not being a target main process, intercepting an operation of creating a container by means of the first process to control the displaying of the second application interface; and creating a display container by means of the target main process, so as to control the displaying of the second application interface.

Description

Interface display control method, electronic device, vehicle, medium and product

[0001] The present application claims priority to the application with the application number 202411402963.4, the patent name: interface display control method, electronic device, vehicle, medium and product, which was filed on September 30, 2024, at the China Patent Office, the entire content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the technical field of electronic device control, in particular to an interface display control method, device, electronic device, vehicle, computer readable storage medium and computer instruction product. BACKGROUND

[0003] In the Android software ecosystem, most applications are developed for small-screen display devices such as mobile phones. These applications are difficult to display normally on large-screen devices (such as Pad) without special adaptation.

[0004] For example, as shown in FIG. 1-1, when only one interface in the application is opened, the interface is displayed in the center. However, when a new interface is started based on the interface, as shown in FIG. 1-2, multiple interface display confusion occurs. TECHNICAL SOLUTION

[0005] The present application provides an interface display control method, device, electronic device, vehicle, computer readable storage medium and computer instruction product, which realizes normal display of multiple interfaces.

[0006] In order to achieve the above purpose, according to the first aspect of the present application, an interface display control method is provided, the method comprising:

[0007] In response to a trigger operation for pulling up a second application interface acting on a first application interface, a first process of the first application interface is obtained; wherein the process of the first application interface and the process of the second application interface are different processes;

[0008] In response to the first process not being a target main process, an operation of the first process creating a container for controlling the display of the second application interface is intercepted;

[0009] A display container is created through the target main process to control the display of the second application interface.

[0010] According to the second aspect of the present application, an electronic device is provided, which comprises a processor and a memory, wherein the memory stores computer instructions, when the computer instructions are executed by the processor, the processor performs the steps of the above interface display control method.

[0011] According to a third aspect of the present application, a vehicle is provided, comprising a processor and a memory, wherein the memory stores computer instructions which, when executed by the processor, cause the processor to perform the steps of the interface display control method.

[0012] According to a fourth aspect of the present application, a computer readable storage medium is provided, comprising a processor and a memory, wherein the memory stores a plurality of instructions; the processor loads the instructions from the memory to perform the steps of the interface display control method.

[0013] According to a fifth aspect of the present application, a computer readable storage medium is provided, comprising computer instructions stored in the computer readable storage medium; when a processor of an electronic device reads the computer instructions from the computer readable storage medium, the processor executes the computer instructions, so that the electronic device performs the steps of the interface display control method.

[0014] According to a sixth aspect of the present application, a computer instruction product is provided, comprising computer instructions stored in the computer readable storage medium; when a processor of an electronic device reads the computer instructions from the computer readable storage medium, the processor executes the computer instructions, so that the electronic device performs the steps of the interface display control method.

[0015] In the interface display control method, apparatus, electronic device, vehicle, computer readable storage medium and computer instruction product of the embodiments of the present application, the triggering operation for pulling up the second application interface is responded to, which is applied to the first application interface, and the first process to which the first application interface belongs is obtained. When the first process is not the target main process, the operation of the first process to create a container is directly intercepted, so that the first process cannot control the display of the second application interface as a non-main process, and a display container is created by the target main process to control the display of the second application interface through the display container. Therefore, compared with the problem of display disorder of multiple interfaces caused by process isolation in the prior art, the present application can intercept the interface control operation of the non-main process, and the main process can uniformly manage the display of multiple application interfaces through the display container, effectively solving the problem of display disorder of multiple process interfaces, and realizing the normal display of interfaces in the multiple application interface scenario.

[0016] Other features and advantages of the present application will be described in detail in the following specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative effort based on these drawings.

[0018] For a more complete understanding of the present application and its advantages, the following description needs to be taken in conjunction with the drawings, in which the same reference numerals represent the same parts in the following description.

[0019] FIG. 1-1 is a first schematic diagram of an interface display according to an example embodiment of the present application;

[0020] FIG. 1-2 is a second schematic diagram of an interface display according to an example embodiment of the present application;

[0021] FIG. 2 is a third schematic diagram of an interface display according to an example embodiment of the present application;

[0022] FIG. 3 is a schematic diagram of an existing interface display architecture according to an example embodiment of the present application;

[0023] FIG. 4 is a schematic diagram of an interface display architecture according to an example embodiment of the present application;

[0024] FIG. 5 is a first schematic diagram of an interface display flow according to an example embodiment of the present application;

[0025] FIG. 6 is a second schematic diagram of an interface display flow according to an example embodiment of the present application;

[0026] FIG. 7 is a third schematic diagram of an interface display flow according to an example embodiment of the present application;

[0027] FIG. 8 is a schematic diagram of a structure of an interface display control device according to an example embodiment of the present application.

[0028] FIG. 9 is a schematic diagram of a structure of an electronic device according to an example embodiment of the present application.

[0029] Embodiments of the present application

[0030] With reference to the drawings and the embodiments of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of the present application. In addition, it should be understood that the specific implementation described herein is only used to illustrate and explain the present application, and is not used to limit the present application. In the present application, the orientation words such as “up” and “down” generally refer to the up and down in the actual use or working state of the device, and specifically refer to the direction of the drawing surface in the drawings; and “inner” and “outer” refer to the contour of the device.

[0031] Currently in the Android software ecosystem, most applications are developed for small-screen display devices such as mobile phones. If these applications are not specially adapted, it is difficult for them to have good display effects on large-screen devices (such as Pad). In order to provide users with a perfect software ecosystem experience, large-screen device manufacturers often adopt two methods to be compatible with applications originally supporting only mobile phones: cooperating with software developers to develop large-screen adapted versions; developing and customizing the system to adapt to the application. The latter method is often more preferred due to cost considerations.

[0032] A mainstream development and customization strategy at present is to display the interface (Activity) of the application flatly, that is, the so-called parallel view. As shown in FIG. 1-1, when the application only opens an Activity 1, the Activity 1 is displayed in the center. When the application starts a new interface (Secondary Activity) from the primary interface (Primary Activity), the two interfaces of the application are displayed on the two sides of the screen respectively.

[0033] For example, Google provides a set of AE (Activity Embedding) framework from Android 12. Application developers can formulate the display rules of Activity, and the AE framework can achieve the display effect of FIG. 2.

[0034] However, the implementation of the horizontal screen vertical display based on the AE will face the problem of interface disorder in multiple processes, as shown in FIG. 1-1 and FIG. 1-2, the left primary Activity is in process 1, and the secondary Activity is in process 2, which is started from the left. In this case, the left Activity will still be on the left, but the right Activity will be in the center, causing interface disorder. The reason for the interface disorder is that the primary Activity pulls up a new process Activity. According to the above description, when a process has only one Activity, the Activity will be required to be displayed in the center. The center is triggered in the Activity lifecycle callback. After the primary Activity moves to the left, it waits for the secondary Activity pulled up by it. However, since the secondary Activity completes the lifecycle callback in another process, the primary Activity and the secondary Activity cannot see each other due to process isolation, which causes the secondary Activity to be displayed in the center and the primary Activity to be displayed on the left of the screen. It can be seen that the parallel window solution based on the AE will encounter the problem of interface disorder in multiple processes.

[0035] In general, the root cause of the above interface disorder problem is that each process of the application has a controller to parse the display rule and regulate the interface display. The controller of the process where the primary Activity is located requires the secondary Activity to be displayed on the right of the screen, so as to move itself to the left of the screen. The controller of the process where the secondary Activity is located requires the controller to be displayed in the center. The controllers of the processes of different applications are isolated from each other, causing interface disorder.

[0036] For example, as shown in FIG. 3, the existing AE processes a single application with multiple process interfaces: when the user cold starts the application, the system creates an application main process, and creates a controller instance Controller 1, the controller instance discovers that there is only one interface in the main process, creates a container taskFragmentContainer1 in the application process, and requests the system to create a taskFragment1 in the center of the boundary, and loads ActivityRecord1 to realize the landscape portrait display. Further, the user interacts with the main process interface, and pulls up Activity2 of another process, Controller 1 in the main process moves taskFragmentContainer1 to the left of the screen, and prepares an empty container for Activity2, and after the system creates the process of Activity2, Controller2 is created, Controller2 discovers that there is only Activity2 in the process, creates taskFragmentContainer2, and requests the system to create taskFragment2 in the center of the boundary, and loads ActivityRecord2. The above operations cause the Activities of each process to be managed by the controllers of each process, and Activity1 is displayed on the left while Activity2 is displayed in the center.

[0037] Therefore, in order to solve the above-mentioned problem of display confusion of multiple interfaces, the present application provides an interface display control method and device, electronic equipment and computer readable storage medium, which can solve the problem that the AE-based framework supports landscape portrait display and encounters interface confusion of multiple processes, and according to the scene requirements of the user, the present application can at least support the following scenes:

[0038] (1) When the user starts the first interface (in the main process), the interface is displayed in landscape portrait display, and when the user interacts with the first interface to pull up the second interface, even if the second interface is in another process, it can be displayed in parallel window.

[0039] (2) Based on the above-mentioned scene, the present application can cope with the complex business requirements that the second interface pulls up the interface of the main process or other process interfaces, and will not cause interface confusion;

[0040] (3) In the parallel window scenario as shown in FIG. 2, the present application can process the business requirement that the interface is in a non-main process and requests full screen;

[0041] (4) On the basis of the above-mentioned scenario (3), the present application can process the business requirement that the non-main process interface requests to exit full screen after full screen, at which time the interface returns to the position and size before full screen.

[0042] Specifically, the interface display control method in the present application can be applied to the interface display control architecture as shown in FIG. 4, which can effectively handle the scenario of multiple process interfaces of a single application. When the user cold starts the application, the system creates taskFragmentContainer1 and taskFragment1 for Activity1 in the existing manner as shown in FIG. 4, the user interacts with Activity1 to pull up Activity2 of another process, the system side loads ActivityRecord2 by taskFragment2 of the main process, the size and position of the interface of Activity2 are managed by Controller1 of the main process, and only when Activity2 requests full screen / exit full screen, the event is transmitted to the system through Controller2, and finally the password of Controller1 needs to be obtained to modify the size and position of taskfragment2 corresponding to Controller1, Activity2 will change the size and position along with taskfragment2 to complete the enter / exit full screen request. Through the above scheme, the present application can host the activity of other processes to the main process, and the interface display is uniformly managed by Controller1 of the main process.

[0043] On this basis, the interface display control method in the embodiment of the present application can be applied to the interface display control system (hereinafter can be referred to as system) as shown in FIG. 4, and the method is as shown in FIG. 5, which can specifically include the following steps:

[0044] S10, in response to a trigger operation for pulling up a second application interface acting on a first application interface, obtaining a first process of the first application interface; wherein the process of the first application interface and the process of the second application interface are different processes;

[0045] It should be noted that in the present embodiment, the first application interface can be an application interface of a main process or an application interface of a sub-process, in order to avoid interface isolation caused by process isolation, in the present embodiment, the display of each interface is controlled by the main process.

[0046] In the present embodiment, the system can respond to the trigger operation for pulling up the second application interface acting on the first application interface, and obtain the first process to which the first application interface belongs, the process of the first application interface and the process of the second application interface are different processes.

[0047] Specifically, for example, the first application interface Activity1 can start the second application interface Activity2 through the intent (message passing object) mode.

[0048] S20, in response to the first process not being the target main process, intercepting an operation of the first process creating a container for controlling display of the second application interface;

[0049] In this embodiment, after obtaining the first process of the first application interface, the system can further determine whether the first process is a main process (i.e., the target main process in this embodiment).

[0050] If it is determined that the first process is not the target main process, the operation of the first process creating a container can be directly intercepted, so that the first process as a non-main process does not have the permission to control the display of the second application interface.

[0051] Specifically, for example, as shown in FIG. 6, the system can obtain the process name pA of the first process in which the first application interface Activity1 is located and the process name pB of the second process in which the second application interface Activity2 is located, where pA already exists, pA is obtained through ActivityThread (the main thread of the Android application, responsible for processing the life cycle and message loop of the application, etc.), and pB has not been created, and is obtained through package management to parse the configuration file. Further, the first process can be determined to be the target main process through the process name pA, and the second process can be determined to be the target main process through the process name pB.

[0052] S30, creating a display container through the target main process to control the display of the second application interface.

[0053] It should be noted that in this embodiment, the display container can include a system layer container taskFragment and an application layer container taskFragmentContainer.

[0054] In this embodiment, when the first process is not the target main process, the system can create a system layer container using the target main process, and control the display of the second application interface through the system layer container.

[0055] As shown in FIG. 4, the system can create a corresponding system layer container taskFragment2 for the second application interface in the target main process, in addition to creating an application container taskFragmentContainer1, a system layer container taskFragment1 for the first application interface, an application container taskFragmentContainer2 for the second application interface. The above taskFragmentContainer1, taskFragment1, taskFragmentContainer2 and taskFragment2 are all in the main process and are managed by the main process, so that the interfaces of non-main processes are hosted to the main process for management, so that when the application starts multiple interfaces, the multiple interfaces can be tiled and displayed, and the multiple interfaces will not exist overlapping and shielding and other display confusion.

[0056] Specifically, for example, the topmost taskFragment is found from the Task stack of the application. Since the first interface is the interface of the main process, and the taskFragment of other processes cannot be created in this embodiment, the topmost taskFragment of the Task stack must be the main process, and the taskFragment can be used as the system layer container created by the target main process.

[0057] In an embodiment, the interface display control method in the embodiment can further include:

[0058] In response to the first process being the target main process, a display container of the second application interface is created through the first process to control the display of the second application interface.

[0059] In this embodiment, if it is judged according to the process name that the first process is the target main process, the display container of the second application interface can be directly created through the first process to control the display of the second application interface at this time, that is, only the main process has the display container creation operation and the application interface display control operation in this embodiment.

[0060] It can be seen that in the embodiment of the present application, the system can respond to the trigger operation for pulling up the second application interface acting on the first application interface, and obtain the first process to which the first application interface belongs. When the first process is not the target main process, the operation of the first process to create a container can be directly intercepted, so that the first process cannot control the display of the second application interface as a non-main process, and a system layer container is created by the target main process to control the display of the second application interface through the system layer container. Therefore, compared with the problem of display disorder of multiple interfaces caused by process isolation in the prior art, the present application can intercept the interface control operation of the non-main process, and the main process uniformly manages the display of multiple application interfaces, effectively solving the problem of display disorder of multiple processes, and realizing the normal display of interfaces in the multiple application interface scenario.

[0061] In an embodiment, the display container at least includes a system layer container, and on this basis, the above S30, "creating a display container by the target main process to control the display of the second application interface", can include:

[0062] S301, creating a system layer container of the second application interface by the target main process;

[0063] S302, adding the interface control attribute parameter of the second application interface to the child node of the system layer container to control the display of the second application interface.

[0064] In the embodiment, the system can control the target main process to create a system layer container taskFragment2 corresponding to the second application interface, and then can add the interface control attribute parameter ActivityRecord2 of the second application interface to the system layer container taskFragment2, and add the interface control attribute parameter ActivityRecord2 as the child node Children of the system layer container taskFragment2, so that the target main process can control the display of the second application interface through the system layer container taskFragment2.

[0065] It should be noted that in the embodiment, in the Android operating system, WMS (Window Manager Service) is a system service responsible for managing all windows, which controls the creation, display, position and size of windows, and cooperates closely with the Activity Manager Service (AMS) to manage the life cycle and state of application programs. And WMS is a tree structure, and the Children of a certain node (such as the system layer container TaskFragment in the embodiment) are called child nodes.

[0066] It is worth noting that in the embodiment, the second application interface Activity2 can intercept the operation of the controller of its process to create a container when its process execution life cycle callback, in this way, the controller of the non-main process can be blocked to control Activity2, so that all interfaces are controlled by the main process.

[0067] Further, the display container further comprises an application layer container, and on this basis, the "controlling the display of the second application interface" in S30 can comprise:

[0068] S303, delivering the target instruction associated with the interface control attribute parameter in the control instruction to the application layer container corresponding to the second application interface, to control the second application interface to adjust the display parameter according to the target instruction.

[0069] It should be noted that in the embodiment, after the system takes the interface control attribute parameter ActivityRecord2 of the second application interface as a child node of the system layer container, the system can respond to the control instruction of the system layer container taskFragment2, wherein the control instruction can be triggered by the main process according to the display position and display size of the first application interface, to ensure that the first application interface and the second application interface can be displayed in a tiled manner, avoiding the situation of multiple interface display confusion.

[0070] Further, the system can deliver the target instruction associated with the interface control attribute parameter in the control instruction to the second process corresponding to the second application interface, to control the second application interface to adjust the display parameter according to the target instruction, in this way, the target main process can intervene the size and position of the non-main process Activity2 by modifying the boundary of the system layer container taskFragment2, so that the first application interface and the second application interface can be displayed in a tiled manner, for example, as shown in FIG. 2, the first application interface and the second application interface are displayed on the left and right sides respectively, realizing the function of multiple interface display in horizontal screen.

[0071] Further, before the "creating a display container by the target main process" in S30, it can further comprise:

[0072] S40, creating a second process corresponding to the second application interface;

[0073] S50, in response to the second process not being the target main process, executing the step of "creating a display container by the target main process".

[0074] In the embodiment, before creating the system layer container by the target main process, the system also needs to create the second process corresponding to the second application interface Activity2, and then can judge whether the second process is the target main process according to the process name of the second process.

[0075] If it is determined that the second process is not the target main process, the step of creating a system layer container through the target main process can be performed.

[0076] If it is determined that the second process is the target main process, other native starting processes of the system can be completed, and the task can be ended.

[0077] Further, before the S10, the method can further include:

[0078] S60, in response to a trigger operation acting on a system interaction interface, obtaining at least one application interface started;

[0079] S70, setting a process corresponding to a first started application interface in the application interface as a target main process.

[0080] It should be noted that in the embodiment, the system interaction interface can be an interface displayed on the display screen, and the user can operate the system interaction interface to operate a target application displayed on the system interaction interface to generate a corresponding trigger operation.

[0081] The system can obtain at least one application interface currently started in response to a trigger operation acting on the system interaction interface, and then set a process corresponding to a first started application interface in the application interface as a target main process.

[0082] In a specific embodiment, as shown in FIG. 6, the control flow of the second application interface being pulled up by the first application interface can include:

[0083] (1) the first application interface Activity1 pulls up the first application interface Activity2, where the pulling up manner is that Activity1 starts Activity1 through intent;

[0084] (2) obtaining a process name pA where Activity1 is located and a process name pB where Activity2 is located, where pA can be obtained through ActivityThread, and pB can be obtained through package management to parse a configuration file;

[0085] (3) checking whether pA is a main process name, if yes, go to (5), otherwise go to (4);

[0086] (4) pA is not a main process, intercepting pA to parse control rules and creating a container operation;

[0087] (5) checking whether pB is a main process name, if yes, go to (9), otherwise go to (6);

[0088] (6) Find the topmost taskFragment in the application's Task stack as the taskFragment of the main process;

[0089] (7) Add the ActivityRecord2 of pB to the Children of taskFragment2, so that the boundary changes of taskFragment2 can be passed to the ActivityRecord2 of Activity2, and the main process can intervene in the size and position of Activity2 of the non-main process by modifying the boundary of taskFragment2;

[0090] (8) Activity2 intercepts the operation of the controller of pB process to create a container when executing the life cycle callback of its own process, which blocks the control of the controller of the non-main process to the Activity.

[0091] (9) Complete the other native startup process of the system, and end.

[0092] Therefore, in the embodiment, the Activity not in the main process is managed by the TaskFragment of the main process on the system side, the size and position of which are controlled by the main process of the application, and the request of the Activity not in the main process for the controller of the process to control the operation is intercepted when the life cycle callback is executed, so that the application side will not be controlled by the controller other than the main process. When the user performs interface operation, the activities of other processes are controlled by the controller of the main process, and the size and position of the interface are switched, and under the control of a single controller, interface confusion will not occur.

[0093] In an embodiment, after the above S30, "creating a system layer container through the target main process to control the display of the second application interface", the method further comprises:

[0094] S80, obtaining an operation event for the displayed second application interface;

[0095] S90, according to the operation event, controlling the display state of the second application interface through the target main process.

[0096] It should be noted that in the embodiment, according to the above description, the request of the Activity not in the main process for the controller of the process to control the operation is intercepted when the life cycle callback is executed, and the application side will not be controlled by the controller other than the main process, resulting in the following problems:

[0097] If Activity2 is not in the main process, but requests full screen or exits full screen, because full screen and exit full screen involve changes in Activity size and boundary, the controller needs to perform operations, but according to the above description, all operations of the controller of the non-main process are intercepted, so that the request of Activity2 of the non-main process to full screen or exit full screen is invalid.

[0098] In order to solve the problem that the request of the non-main process to full screen or exit full screen cannot be responded, the embodiment can obtain an operation event for the displayed second application interface.

[0099] Wherein, the process in which the second application interface Activity2 is located is a non-main process (such as a second process), Activity2 is in a display state, and the interface control attribute parameter on the system side is managed by the taskFragment2 of the main process. At this time, the user can interact with Activity2 to request full screen operation, such as requesting full screen display or exiting full screen display of the second application interface.

[0100] At this time, the system can encapsulate the operation event of Activity2 requesting full screen, wherein the operation event contains an event flag and an Activity password. The event flag is used to represent different event types (full screen display or exit full screen display). The Activity password actually refers to the Binder object in the event. The Binder object is associated with the application container TaskFragmentContainer and the system layer container TaskFragment. When the application process generates an operation event, it will put a Binder object into the operation event based on the operation of the application side container (TaskFragmentContainer). When the system side analyzes the event, it will find the system layer container TaskFragment based on the Binder object.

[0101] On this basis, the system can control the display state of the second application interface through the main process according to the above operation event, so that the second application interface is full screen displayed or non-full screen displayed.

[0102] Further, in the above S90, "controlling the display state of the second application interface through the target main process according to the operation event" can include:

[0103] S901, analyzing the operation event to obtain the event type and initial display password corresponding to the operation event;

[0104] S902, generating a target display password according to the event type and initial display password;

[0105] S903, display state of the second application interface is controlled by the target main process according to the target display password.

[0106] It should be noted that in this embodiment, Activity2 can pass the event to the controller Controller2 of the process in which Activity2 is located, and Controller2 forwards the event to the system.

[0107] The system can analyze the operation event to obtain the event type and the initial display password in the operation event.

[0108] The initial display password can be understood as a password sent to the controller Controller2 in the non-main process. However, all operations of the controller in the non-main process will be intercepted, so the system generates a target display password for controlling the controller Controller1 in the main process according to the event type and the initial display password, so that the main process can control the display state of the second application interface in the non-main process. At this time, Activity2 can undertake the role of information transmission in the controller of the process, and actually the main process adjusts the size and position of the system layer container taskFragment2 to modify the display position and size of the second application interface, that is, the display state of the second application interface in the non-main process is controlled by the controller Controller1 in the main process.

[0109] On this basis, the system can generate a target display password for the controller Controller1 in the main process according to the event type and the initial display password, and control the display state of the second application interface through the main process according to the target display password.

[0110] Further, in S902, "generating a target display password according to the event type and the initial display password" can include:

[0111] S9021, obtaining the interface control attribute parameter corresponding to the second application interface according to the initial display password;

[0112] S9022, obtaining the target display container in the target main process where the interface control attribute parameter is located, and obtaining the display password associated with the target display container;

[0113] S9023, determining a target display password according to the display password associated with the target display container and the event type.

[0114] In this embodiment, the system can find the corresponding ActivityRecord2 according to the initial display password, and then find the target system layer container taskFragment2 in the main process of the ActivityRecord2 through the ActivityRecord2.

[0115] It is worth noting that according to the above description, the display password actually refers to the Binder object in the event, which is associated with the application container TaskFragmentContainer and the system layer container TaskFragment, so that after the target system layer container taskFragment2 is determined, the display password associated with the target system layer container taskFragment2 can be obtained, and the target display password can be determined according to the display password and the event type.

[0116] Further, in S9023, "determining the target display password according to the display password associated with the target display container and the event type", can include:

[0117] Step a, if the event type is to exit full-screen display, the historical boundary parameter of the second application interface is obtained according to the interface control attribute parameter, wherein the historical boundary parameter is the boundary parameter of the second application interface when it was last displayed in non-full screen;

[0118] Step b, updating the initial display password to obtain a new display password according to the historical boundary parameter;

[0119] Step c, replacing the display password associated with the target display container with the new display password to obtain the target display password.

[0120] In this embodiment, if the event type is to exit full-screen display, the lastBound (i.e. the historical boundary parameter in this embodiment) of the ActivityRecord2 before the last full-screen display can be obtained after the corresponding ActivityRecord2 is found, and then the initial display password can be updated to obtain a new display password according to the historical boundary parameter, so that the new display password can contain the display parameters (including display position and display size, etc.) of the second application interface when it exits full-screen display, wherein when the system modifies the boundary of the ActivityRecord2 to full screen, the boundary lastBound of the ActivityRecord2 can be backed up in advance, so that the size and position before entering full screen can be restored when the second application interface exits full screen.

[0121] Further, the display password associated with the target system layer container taskFragment2 is replaced by the new display password to obtain a target display password.

[0122] Further, in S9023, determining the target display password according to the display password associated with the target display container and the event type, can include:

[0123] In step d, if the event type is full screen display, the display password associated with the target display container is replaced by the initial display password to obtain a target display password.

[0124] In this embodiment, if the event type of the operation event is exit full screen display, after the corresponding ActivityRecord2 is found and the target system layer container taskFragment2 in the main process where the ActivityRecord2 is located is found through the ActivityRecord2, the display password associated with the target system layer container taskFragment2 can be directly replaced by the initial display password to obtain a target display password.

[0125] Further, in S903, controlling the display state of the second application interface according to the target display password through the target main process, can include:

[0126] In S9031, the target display parameter of the target display container is obtained by analyzing the target display password.

[0127] In S9032, the display state of the second application interface is controlled according to the target display parameter.

[0128] In this embodiment, after the target display password is generated, the target display password can be analyzed to obtain the target display parameter of the target system layer container taskFragment2, such as display position and display size and the like. Further, the boundary of taskFragment2 can be modified.

[0129] For example, if the event type is exit full screen display, the boundary of taskFragment2 can be modified to lastBound, and the boundary of Activity2 following taskFragment2 is modified to lastBound to restore the size and position before entering full screen; if the event type is full screen display, the boundary of taskFragment2 can be modified to the screen size, and Activity2 following taskFragment2 is displayed in full screen.

[0130] In a specific embodiment, as shown in FIG. 7, the flow of non-main process interface requesting full screen operation can include:

[0131] (1) The process in which Activity2 is located is not the main process. Activity2 is in the display state. On the system side, ActivityRecord2 is managed by taskFragment2 of the main process. The user interacts with Activity2 to request full-screen operation.

[0132] (2) Identify the full-screen operation type. If it is to enter full-screen, proceed to (3); otherwise, proceed to (8).

[0133] (3) When the system changes the boundary of ActivityRecord2 to full screen, back up the boundary lastBound of ActivityRecord2;

[0134] (4) Encapsulate the operation event of Activity2 requesting fullscreen, including the event flag and the activity's password;

[0135] (5) Pass the event to Controller2 of the process where Activity2 is located, and Controller2 forwards the event to the system;

[0136] (6) The system parses the transmitted event, identifies the event flag as a request for fullscreen, and begins to execute the cross-process request for fullscreen operation, including finding ActivityRecord2 through Activity2's password, finding taskFragment2 through ActivityRecord2, finding Controller1's password through taskFragment2, replacing Controller2's password with Controller1's password, and generating an event to modify taskFragment2's boundary to fullscreen;

[0137] (7) The system modifies the boundary of taskFragment2 to full screen using the Controller1 password, and Activity2 follows taskFragment2 to be displayed in full screen, thus completing the full-screen request of Activity2;

[0138] (8) Encapsulate the operation event of Activity2 requesting fullscreen, including the event flag and the activity's password;

[0139] (9) Pass the event to Controller2 of the process where Activity2 is located, and Controller2 forwards the event to the system;

[0140] (10) The system analyzes the passed event, identifies the event flag as exiting full screen, and starts to perform the operation of cross-process request for exiting full screen, including finding ActivityRecord2 through the password of Activity2, obtaining the last bound of ActivityRecord2 before full screen, finding taskFragment2 through ActivityRecord2, finding the password of Controller1 through taskFragment2, replacing the password of Controller2 with Controller1, and generating an event of modifying the bound of taskFrgament2 to lastBound;

[0141] (11) The system modifies the bound of taskFragment to lastBound by means of the password of Controller1, and Activity2 modifies the bound to lastBound following taskFragment2, restores the size and position before full screen, and completes the request of Activity2 for exiting full screen;

[0142] (12) The request of full screen operation of Activity2 in a non-main process is completed.

[0143] Through the above supplement, when Activity2 in a non-main process requests full screen or exits full screen, the controller of the process where Activity2 is actually required to undertake the role of information transmission, and the size and position of taskFragment2 in the main process are actually modified, and the controller Controller1 in the main process is also actually used to control the interface.

[0144] In general, the embodiment can process the business requirement that the interface is in a non-main process and requests full screen, and can also process the business requirement that the interface in a non-main process requests to exit full screen after full screen, so that the interface is restored to the position and size before full screen.

[0145] Correspondingly, the embodiment of the application further provides an interface display control apparatus, as shown in FIG. 8, which comprises:

[0146] An obtaining device 1001 is configured to, in response to a trigger operation for pulling up a second application interface acting on a first application interface, obtain a first process of the first application interface; wherein the process of the first application interface and the process of the second application interface are different processes;

[0147] An intercepting device 1002 is configured to, in response to the first process not being a target main process, intercept an operation of the first process creating a container for controlling the display of the second application interface;

[0148] The creating means 1003 is configured to create a display container for the second application interface by the target main process to control display of the second application interface.

[0149] Optionally, the creating means 1003 further comprises:

[0150] In response to the first process being the target main process, the display container of the second application interface is created by the first process to control display of the second application interface.

[0151] Optionally, the display container comprises at least a system layer container.

[0152] The creating means 1003 is further configured to:

[0153] The system layer container of the second application interface is created by the target main process.

[0154] The interface control attribute parameter of the second application interface is added to a child node of the system layer container to control display of the second application interface.

[0155] Optionally, the display container further comprises an application layer container, and the creating means 1003 is further configured to:

[0156] The target instruction associated with the interface control attribute parameter in the control instruction is transmitted to the application layer container corresponding to the second application interface to control the second application interface to adjust the display parameter according to the target instruction.

[0157] Optionally, the interface display control apparatus further comprises:

[0158] The process creating means is configured to create a second process corresponding to the second application interface, and in response to the second process not being the target main process, the display container is created by the target main process.

[0159] Optionally, the interface display control apparatus further comprises:

[0160] The interface obtaining means is configured to obtain at least one application interface started in response to a trigger operation acting on a system interactive interface.

[0161] The process determining means is configured to set a process corresponding to a first started application interface in the application interfaces as the target main process.

[0162] Optionally, the interface display control apparatus further comprises:

[0163] The event obtaining means is configured to obtain an operation event for the displayed second application interface.

[0164] The display control device is configured to control, according to the operation event, a display state of the second application interface by the target main process.

[0165] Optionally, the display control device is further configured to:

[0166] The operation event is parsed to obtain an event type and an initial display password corresponding to the operation event;

[0167] The target display password is generated according to the event type and the initial display password;

[0168] The display state of the second application interface is controlled by the target main process according to the target display password.

[0169] Optionally, the display control device is further configured to:

[0170] The interface control attribute parameter corresponding to the second application interface is obtained according to the initial display password;

[0171] A target display container in the target main process in which the interface control attribute parameter is located is obtained, and a display password associated with the target display container is obtained;

[0172] The target display password is determined according to the display password associated with the target display container and the event type.

[0173] Optionally, the display control device is further configured to:

[0174] If the event type is an exit full-screen display, a backup history boundary parameter of the second application interface is obtained according to the interface control attribute parameter, wherein the history boundary parameter is a boundary parameter when the second application interface was last displayed in a non-full-screen mode;

[0175] A new display password is obtained by updating the initial display password according to the history boundary parameter;

[0176] The display password associated with the target display container is replaced by the new display password to obtain a target display password.

[0177] Optionally, the display control device is further configured to:

[0178] If the event type is a full-screen display, the display password associated with the target display container is replaced by the initial display password to obtain a target display password.

[0179] Optionally, the display control device is further configured to:

[0180] The target display parameter of the target display container is obtained by parsing the target display password;

[0181] According to the target display parameter, a display state of the second application interface is controlled.

[0182] The specific implementation of each operation can refer to the foregoing embodiments, which will not be described here.

[0183] Correspondingly, the embodiment of the present application also provides an electronic device, as shown in FIG. 9, which is a structural schematic diagram of an electronic device provided by the embodiment of the present application. The electronic device 1100 includes a processor 1101 having one or more processing cores, a memory 1102 having one or more computer readable storage media, and computer instructions stored in the memory 1102 and executable on the processor. Wherein, the processor 1101 is electrically connected with the memory 1102. Those skilled in the art can understand that the structure of the electronic device shown in the figure does not constitute a limitation on the electronic device, and can include more or fewer components than the figure, or combine certain components, or different component arrangements.

[0184] The processor 1101 is the control center of the electronic device 1100, which connects various parts of the entire electronic device 1100 through various interfaces and lines, executes various functions of the electronic device 1100 and processes data by running or loading software programs and / or parts stored in the memory 1102, and calling data stored in the memory 1102, thereby overall monitoring the electronic device 1100. The processor 1101 can be a processor (Central Processing Unit, CPU), a graphics processor (graphics processing unit, GPU), a network processor (Network Processor, NP), etc., which can realize or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.

[0185] In the embodiment of the present application, the processor 1101 in the electronic device 1100 will load the instructions corresponding to the processes of one or more application programs into the memory 1102, and run the application programs stored in the memory 1102 by the processor 1101, thereby realizing various functions, for example:

[0186] In response to a trigger operation for pulling up the second application interface acting on the first application interface, a first process of the first application interface is obtained; wherein the processes of the first application interface and the second application interface are different processes;

[0187] In response to the first process not being a target main process, an operation of intercepting the first process to create a container for controlling the display of the second application interface is intercepted;

[0188] A display container is created by the target main process to control display of the second application interface.

[0189] The specific implementation of the above operations can refer to the foregoing embodiments, which will not be described here again.

[0190] Optionally, as shown in FIG. 9, the electronic device 1100 further includes a touch display screen 1103, radio frequency circuit 1104, audio circuit 1105, input part 1106 and power supply 1107. The processor 1101 is electrically connected with the touch display screen 1103, radio frequency circuit 1104, audio circuit 1105, input part 1106 and power supply 1107 respectively. Those skilled in the art can understand that the structure of the electronic device shown in FIG. 9 does not constitute a limitation on the electronic device, and can include more or fewer components than shown, or combine certain components, or different component arrangements.

[0191] The touch display screen 1103 can be used to display a graphical user interface and receive operation instructions generated by user acting on the graphical user interface. The touch display screen 1103 can include a display panel and a touch panel. The display panel can be used to display information input by the user or information provided to the user and various graphical user interfaces of the electronic device, which can be composed of graphics, text, icons, video and any combination thereof. Optionally, the display panel can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. The touch panel can be used to collect touch operations (such as user operations on or near the touch panel using a finger, a stylus or any suitable object or accessory) of the user thereon or therearound, and generate corresponding operation instructions, and the operation instructions execute corresponding programs. Optionally, the touch panel can include two parts, a touch electronic device and a touch controller. The touch electronic device detects the touch position of the user and detects the signals generated by the touch operation, and transmits the signals to the touch controller; the touch controller receives the touch information from the touch electronic device, and converts it into touch coordinates, and sends it to the processor 1101, and can receive commands from the processor 1101 and execute them. The touch panel can cover the display panel, and when the touch panel detects a touch operation thereon or therearound, it transmits to the processor 1101 to determine the type of touch event, and then the processor 1101 provides corresponding visual output on the display panel according to the type of touch event. In the embodiments of the present application, the touch panel and the display panel can be integrated into the touch display screen 1103 to realize the input and output functions. However, in some embodiments, the touch panel and the touch panel can realize the input and output functions as two independent components. That is, the touch display screen 1103 can also realize the input function as part of the input part 1106.

[0192] The radio frequency circuit 1104 can be used to transceive radio frequency signals to establish wireless communication with network devices or other electronic devices, and transceive signals between network devices or other electronic devices.

[0193] The audio circuit 1105 can be used to provide an audio interface between a user and the electronic device through a speaker and a microphone. The audio circuit 1105 can convert received audio data into an electrical signal and transmit the electrical signal to the speaker for conversion into a sound signal and output; on the other hand, the microphone collects a sound signal and converts the sound signal into an electrical signal, which is received by the audio circuit 1105 and converted into audio data, and then output to the processor 1101 for processing, and then transmitted to another electronic device through the radio frequency circuit 1104, or output to the memory 1102 for further processing. The audio circuit 1105 can also include a headphone jack to provide communication between an external device and the electronic device.

[0194] The input unit 1106 can be used to receive inputted numbers, character information or user feature information (such as fingerprints, iris, face information, etc.), and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0195] The power supply 1107 is used to supply power to various components of the electronic device 1100. Optionally, the power supply 1107 can be logically connected to the processor 1101 through a power management device, so that the power management device can realize functions such as management of charging, discharging, and power consumption management. The power supply 1107 can also include one or more direct current or alternating current power supplies, rechargeable power supply fault detection circuits, power converters or inverters, power supply status indicators, and any other components.

[0196] Although not shown in FIG. 9, the electronic device 1100 can also include a camera, a sensor, a wireless fidelity device, a Bluetooth device, and the like, which are not described here.

[0197] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0198] Those of ordinary skill in the art can understand that all or part of the steps of the various methods of the above embodiments can be completed by instructions, or by instructions controlling related hardware, which can be stored in a computer readable storage medium and loaded and executed by a processor.

[0199] To this end, an embodiment of the present application provides a computer readable storage medium, which stores a plurality of computer instructions. The computer instructions can be loaded by a processor to execute any interface display control method provided by an embodiment of the present application. The computer instructions can execute the steps of the following interface display control method:

[0200] In response to a trigger operation for pulling up the second application interface acting on the first application interface, a first process of the first application interface is acquired; wherein the process of the first application interface and the process of the second application interface are different processes;

[0201] In response to the first process not being a target main process, an operation of the first process creating a container for controlling display of the second application interface is intercepted;

[0202] A display container is created through the target main process to control display of the second application interface.

[0203] The computer readable storage medium can include a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0204] Due to the computer instructions stored in the computer readable storage medium, any interface display control method provided by the embodiments of the present application can be executed, thus the beneficial effects of any interface display control method provided by the embodiments of the present application can be achieved, which are described in detail in the foregoing embodiments and will not be repeated here.

[0205] In the above apparatus, electronic device, vehicle, computer readable storage medium and computer instruction product, the description of each embodiment has its own focus, and the part not described in detail in a certain embodiment can be referred to the related description of other embodiments. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described apparatus, computer readable storage medium, electronic device, vehicle, computer instruction product and the corresponding part and the beneficial effects brought by them can be referred to the description of the interface display control method in the above embodiments, and will not be repeated here.

[0206] The above is only a preferred embodiment of the present application, and does not limit the present application in any form. Any simple modification, equivalent change and modification made to the above embodiment without departing from the technical solution of the present application and according to the technical essence of the present application still belongs to the scope of the technical solution of the present application.

Claims

1. An interface display control method in which, The interface display control method comprises: In response to a trigger operation for pulling up a second application interface acting on a first application interface, a first process of the first application interface is acquired; wherein the process of the first application interface and the process of the second application interface are different processes; In response to the first process not being a target main process, an operation of the first process creating a container for controlling the display of the second application interface is intercepted; and A display container is created through the target main process to control the display of the second application interface.

2. The method of claim 1, wherein, The method further comprises: In response to the first process being a target main process, a display container of the second application interface is created through the first process to control the display of the second application interface.

3. The method of claim 1 or 2, wherein, The display container at least comprises a system layer container; The creation of the display container through the target main process to control the display of the second application interface comprises: A system layer container of the second application interface is created through the target main process; and An interface control attribute parameter of the second application interface is added to a child node of the system layer container to control the display of the second application interface. The display container further comprises an application layer container, and the control of the display of the second application interface comprises:

4. The method of claim 3, wherein, A target instruction associated with the interface control attribute parameter in a control instruction is delivered to an application layer container corresponding to the second application interface to control the second application interface to adjust a display parameter according to the target instruction. Before the creation of the display container through the target main process, the method further comprises:

5. The method according to any one of claims 1 to 4, wherein, A second process corresponding to the second application interface is created; and In response to the second process not being a target main process, the step of creating the display container through the target main process is performed. Before the acquisition of the first process of the first application interface in response to a trigger operation for pulling up a second application interface acting on a first application interface, the method further comprises:

6. The method according to any one of claims 1 to 5, wherein, In response to a trigger operation acting on a system interaction interface, at least one application interface started is acquired; and A process corresponding to a first started application interface in the application interface is set as a target main process. After the creation of the display container through the target main process to control the display of the second application interface, the method further comprises:

7. The method according to any one of claims 1-6, wherein, An operation event of the displayed second application interface is acquired; and According to the operation event, the display state of the second application interface is controlled through the target main process. According to the operation event, the control of the display state of the second application interface through the target main process comprises:

8. The method of claim 7, wherein, The operation event is parsed to obtain an event type and an initial display password corresponding to the operation event; According to the event type and the initial display password, a target display password is generated; and According to the target display password, the display state of the second application interface is controlled through the target main process. According to the event type and the initial display password, the target display password is generated, which comprises:

9. The method of claim 8, wherein, According to the initial display password, an interface control attribute parameter corresponding to the second application interface is acquired; ​ acquire a target display container in the target main process where the interface control attribute parameter is located, and acquire a display password associated with the target display container; and determine a target display password according to the display password associated with the target display container and the event type.

10. The method of claim 9, wherein, The determining a target display password according to the display password associated with the target display container and the event type comprises: if the event type is an exit full-screen display, acquiring a backup historical boundary parameter of the second application interface according to the interface control attribute parameter, wherein the historical boundary parameter is a boundary parameter when the second application interface was last displayed in a non-full-screen mode; updating the initial display password to obtain a new display password according to the historical boundary parameter; and replacing the display password associated with the target display container with the new display password to obtain a target display password.

11. The method of claim 10, wherein, The determining a target display password according to the display password associated with the target display container and the event type comprises: if the event type is a full-screen display, replacing the display password associated with the target display container with the initial display password to obtain a target display password.

12. The method of claim 9, wherein, The controlling the display state of the second application interface by the target main process according to the target display password comprises: parsing the target display password to obtain a target display parameter of the target display container; and controlling the display state of the second application interface according to the target display parameter.

13. An electronic device, comprising: The electronic device comprises a processor and a memory, wherein the memory stores computer instructions, and when the computer instructions are executed by the processor, the processor executes the steps of the method in any one of claims 1 to 12.

14. A vehicle, wherein, The vehicle is provided with the electronic device in claim 13.

15. A computer-readable storage medium applicable to the interface display control method according to claim 1, wherein, The computer instructions are used to make the electronic device execute the steps of the method in any one of claims 1 to 12 when the computer instructions are run on the electronic device.

16. A computer instruction product for use in the interface display control method according to claim 1, wherein, The computer instructions are stored in a computer readable storage medium, and when a processor of an electronic device reads the computer instructions from the computer readable storage medium, the processor executes the computer instructions, so that the electronic device executes the steps of the method in any one of claims 1 to 12.

Images