CN116737037A

CN116737037A - Stack management method in interface display and related device

Info

Publication number: CN116737037A
Application number: CN202211202076.3A
Authority: CN
Inventors: 白院伟; 徐小坤
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-09-29
Filing date: 2022-09-29
Publication date: 2023-09-12

Abstract

The embodiment of the application provides a stack management method in interface display and a related device, and relates to the technical field of terminals. The method comprises the following steps: displaying a first interface, the first interface comprising: interface content corresponding to a first function of a first application, a first icon corresponding to the first function, and a second icon corresponding to a second function of a second application; receiving a first operation for switching a first application to a second application at a first interface; in response to the first operation, creating a new stack for the second application or multiplexing an old stack that the second application has created; displaying a second interface according to stack information of the second application, wherein the second interface comprises: interface content corresponding to a second function of a second application, a first icon, and a second icon. Therefore, the switching between the function pages of different applications can be realized in one interface, and the operation flow of switching between different application functions of a user is simplified, so that the time of the user can be saved, and the user experience is improved.

Description

Stack management method in interface display and related device

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a stack management method in interface display and a related device.

Background

With more and more functions in various application programs, when a user switches functions among different application programs, the user not only needs to switch the application, but also needs to open the application at one level under a plurality of directories, so that the function required by the user is found, and the complicated operation brings the problem of inconvenience in function searching for the user.

In some implementations, the terminal application may place some common functions as much as possible on the application's main interface, or provide a common function portal on the application's main interface.

However, in the above implementation, there are still problems that the applications are switched and the function that the user wants to use is not in the homepage or in the usual functions, and multi-level searching is required, which causes inconvenience to the user.

Disclosure of Invention

The embodiment of the application provides a stack management method and a related device in interface display, which can realize the switching between function pages of different applications in one interface, simplify the operation flow of switching between different application functions of a user, thereby saving the time of the user and improving the user experience.

In a first aspect, an embodiment of the present application provides a stack management method in interface display, where the method includes:

Displaying a first interface, the first interface comprising: interface content corresponding to a first function of a first application, a first icon corresponding to the first function, and a second icon corresponding to a second function of a second application; the first icon is in a selected state, and the second icon is in an unselected state; receiving a first operation for switching a first application to a second application at a first interface; in response to the first operation, creating a new stack for the second application, or multiplexing an old stack created by the second application; and displaying a second interface according to the stack information of the second application, wherein the second interface comprises: interface content corresponding to a second function of a second application, a first icon, and a second icon; the second icon is in a selected state, the first icon is in an unselected state, and the stack information of the second application is stack information in a new stack of the second application or stack information in an old stack of the second application. Therefore, the switching between the functional pages of different applications can be realized in one interface, the operation flow of switching between different application functions of a user is simplified, and the terminal equipment can realize the reasonable management of the stack by creating a stack management mode of a new stack and multiplexing an old stack, so that the memory resource utilization of the terminal equipment is more reasonable, and the management efficiency of the stack memory is improved.

In one possible implementation, before displaying the first interface, the method may include: the method includes receiving a preset operation for a preset area of the terminal device, including receiving a continuous tapping operation for a back plate of the terminal device. Responding to a preset operation, creating a new stack for the first application, or multiplexing an old stack created by the first application; displaying the first interface includes displaying the first interface according to stack information of the first application. Thus, the operation speed of opening the first interface by the user can be improved.

In one possible implementation, displaying the first interface may include: and displaying interface contents corresponding to the first function in the first interface in the form of a floating window or a split screen or a card. The first function may include any of the following: payment type function, scanning type function, navigation type function. Therefore, the functions required by the user can be displayed more flexibly, and more convenient application functions are provided for the user.

In a possible implementation manner, the first operation of the second application by the first application may include: triggering a second icon, or a sliding operation. Therefore, the operation experience of interface switching can be optimized, and a user is helped to operate the terminal equipment better, so that the operation speed of interface switching is improved.

In a possible implementation, creating a new stack for the second application, or multiplexing an old stack that has been created by the second application, may include: acquiring a value of a target field in the second application; if the value of the target field in the second application is the first preset value, a new stack is created for the second application; if the value of the target field in the second application is not the first preset value or the second preset value, inquiring whether the second application has created an old stack, multiplexing the old stack created by the second application if the second application has created the old stack, and creating a new stack for the second application if the second application has not created the old stack. Therefore, the memory resource utilization of the terminal equipment can be more reasonable, and the management efficiency of the stack memory is improved.

In a possible implementation manner, creating a new stack for the second application, or multiplexing an old stack created by the second application, may further include: determining whether the second application is running in the background; if the second application is not running in the background, a new stack is created for the second application; if the second application runs in the background, acquiring a value of a target field in the second application, and if the value of the target field in the second application is a first preset value, creating a new stack for the second application; and if the value of the target field in the second application is not the first preset value or the second preset value, multiplexing an old stack created by the second application of the stack. Therefore, the memory resource utilization of the terminal equipment can be more reasonable, and the management efficiency of the stack memory is improved.

In a possible implementation manner, multiplexing the old stack created by the second application may include: modifying the size of an old stack created by the second application according to page information corresponding to the second interface, and placing page information corresponding to the second interface in the old stack created by the second application; and displaying a second interface according to the stack information of the second application. Thus, more convenient function use service can be provided for the user.

In a possible implementation manner, after displaying the second interface, the method may further include: receiving a second operation for exiting the display of the second interface; and responding to the second operation, removing page information corresponding to the second interface in the old stack of the second application, and restoring the old stack of the second application to a state before the page information corresponding to the second interface is put in. Therefore, the use of the second application operated by the user is not influenced, and a quick and convenient interface display is provided for the user.

In one possible implementation, multiplexing the old stack that the second application has created may include: recording old stack information of an old stack created by the second application before the old stack is put into page information corresponding to the second interface, wherein the old stack information comprises: old stack top information and old stack size. Removing page information corresponding to the second interface in the old stack of the second application, and restoring the old stack of the second application to a state before the page information corresponding to the second interface is put in may include: and removing page information on the old stack top information, and recovering the old stack of the second application to be the old stack size.

In a possible implementation manner, displaying the second interface according to stack information of the second application includes: displaying a second interface according to page information corresponding to the second interface in a new stack of the second application; after the second interface is displayed, the method further comprises: receiving an operation for exiting the display of the second interface; and deleting the new stack of the second application in response to the operation for exiting the display of the second interface.

In a second aspect, an embodiment of the present application provides a stack management apparatus in interface display, where the stack management apparatus may be a terminal device, or may be a chip or a chip system in the terminal device. The stack management apparatus may include a processing unit and a display unit. The processing unit is configured to implement the first aspect or any method related to processing in any possible implementation manner of the first aspect. The display unit may be a display screen or the like, and the display unit may implement the first aspect or any step related to display in any one of the possible implementations of the first aspect based on the control of the processing unit. When the stack management means is a terminal device, the processing unit may be a processor. The stack management apparatus may further include a storage unit, which may be a memory. The storage unit is configured to store instructions, and the processing unit executes the instructions stored in the storage unit, so that the terminal device implements a method described in the first aspect or any one of possible implementation manners of the first aspect. The processing unit may be a processor when the means of stack management is a chip or a system of chips within the terminal device. The processing unit executes instructions stored by the storage unit to cause the terminal device to implement a method as described in the first aspect or any one of the possible implementations of the first aspect. The memory unit may be a memory unit (e.g., a register, a cache, etc.) in the chip, or a memory unit (e.g., a read-only memory, a random access memory, etc.) located outside the chip in the terminal device.

Exemplary, the display unit is configured to display a first interface, where the first interface includes: interface content corresponding to a first function of a first application, a first icon corresponding to the first function, and a second icon corresponding to a second function of a second application; a first operation is received at the first interface for switching the first application to the second application.

And the processing unit is used for responding to the first operation and creating a new stack for the second application or multiplexing an old stack created by the second application.

The display unit is further configured to display a second interface according to stack information of the second application, where the second interface includes: interface content corresponding to a second function of a second application, a first icon, and a second icon; the stack information of the second application is stack information in a new stack of the second application or stack information in an old stack of the second application.

In a possible implementation manner, the processing unit is further configured to receive a preset operation for a preset area of the terminal device, and create a new stack for the first application or multiplex an old stack created by the first application in response to the preset operation. The display unit is specifically configured to display a first interface according to stack information of the first application.

In a possible implementation, the processing unit is further specifically configured to receive a continuous tapping operation on the back plate of the terminal device.

In a possible implementation manner, the processing unit is configured to receive a first operation of switching a second application by a first application, where the first operation includes: triggering a second icon, or a sliding operation.

In a possible implementation manner, the display unit is further configured to display a first interface, where interface content corresponding to a first function in the first interface is displayed in a form of a floating window or a split screen or a card, and the first function may include any one of the following: payment type function, scanning type function, navigation type function.

In a possible implementation manner, the processing unit is configured to create a new stack for the second application, or multiplex an old stack that has been created by the second application, and specifically is further configured to obtain a value of a target field in the second application; if the value of the target field in the second application is the first preset value, a new stack is created for the second application; if the value of the target field in the second application is not the first preset value or the second preset value, inquiring whether the second application has created an old stack, multiplexing the old stack created by the second application if the second application has created the old stack, and creating a new stack for the second application if the second application has not created the old stack.

In a possible implementation manner, the processing unit is further configured to create a new stack for the second application, or multiplex an old stack that has been created by the second application, and specifically further configured to determine whether the second application runs in the background; if the second application is not running in the background, a new stack is created for the second application; if the second application runs in the background, acquiring a value of a target field in the second application, and if the value of the target field in the second application is a first preset value, creating a new stack for the second application; and if the value of the target field in the second application is not the first preset value or the second preset value, multiplexing an old stack created by the second application of the stack.

In a possible implementation manner, the processing unit is configured to multiplex an old stack created by the second application, specifically, modify a size of the old stack created by the second application according to page information corresponding to the second interface, and put page information corresponding to the second interface in the old stack created by the second application; and the display unit is specifically used for displaying the second interface according to the stack information of the second application.

In a possible implementation manner, the processing unit is further configured to receive a second operation for exiting the display of the second interface; and responding to the second operation, removing page information corresponding to the second interface in the old stack of the second application, and restoring the old stack of the second application to a state before the page information corresponding to the second interface is put in.

In a possible implementation manner, the processing unit is configured to multiplex an old stack created by the second application, record old stack information of the old stack created by the second application before the old stack is put into page information corresponding to the second interface, where the old stack information includes: old stack top information and old stack size; the method is specifically used for removing page information on old stack top information and restoring the old stack of the second application to be the old stack size.

In a possible implementation manner, the display unit is configured to display the second interface according to page information corresponding to the second interface in a new stack of the second application; the processing unit is also used for receiving an operation for exiting the display of the second interface; and deleting the new stack of the second application in response to the operation for exiting the display of the second interface.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory, the memory being configured to store code instructions, the processor being configured to execute the code instructions to perform the method described in the first aspect or any one of the possible implementations of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored therein a computer program or instructions which, when run on a computer, cause the computer to perform the stack management method in the interface display described in the first aspect or any one of the possible implementations of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the stack management method in the interface display described in the first aspect or any one of the possible implementations of the first aspect.

In a sixth aspect, the present application provides a chip or chip system comprising at least one processor and a communication interface, the communication interface and the at least one processor being interconnected by wires, the at least one processor being for running a computer program or instructions to perform the stack management method in the interface display described in the first aspect or any one of the possible implementations of the first aspect. The communication interface in the chip can be an input/output interface, a pin, a circuit or the like.

In one possible implementation, the chip or chip system described above further includes at least one memory, where the at least one memory has instructions stored therein. The memory may be a memory unit within the chip, such as a register, a cache, etc., or may be a memory unit of the chip (e.g., a read-only memory, a random access memory, etc.).

It should be understood that, the second aspect to the sixth aspect of the present application correspond to the technical solutions of the first aspect of the present application, and the advantages obtained by each aspect and the corresponding possible embodiments are similar, and are not repeated.

Drawings

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 2 is a schematic software structure of a terminal device according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a scenario for interface switching between different application functions according to an embodiment of the present application;

fig. 4 is a schematic diagram of creating a new task stack for an application by a terminal device according to an embodiment of the present application;

fig. 5 is a schematic flow chart of creating a new task stack by a terminal device according to an embodiment of the present application;

fig. 6 is a schematic diagram of an old task stack of a multiplexing application of a terminal device according to an embodiment of the present application;

Fig. 7 is a schematic flow chart of multiplexing an old task stack by a terminal device according to an embodiment of the present application;

fig. 8 is a schematic diagram of a terminal device removing a new task stack according to an embodiment of the present application;

fig. 9 is a schematic diagram of a terminal device restoring an old task stack according to an embodiment of the present application;

FIG. 10 is a diagram illustrating a stack management method in an interface display according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

In order to facilitate the clear description of the technical solutions of the embodiments of the present application, the following simply describes some terms and techniques involved in the embodiments of the present application:

1. activity: activity is an Application (APP) component that can provide a page on which operations are closely related to a user. Controls may be displayed on the page and monitored and responded to user events so that the user may interact to complete a task.

2. Launch Mode: the Activity starting mode comprises the following four modes:

standby: by default, each time an Activity is started, a new Activity instance is created.

singetop: if the Activity to be started is already at the top of the stack, then the Activity will not be recreated. If the Activity to be started is not at the top of the stack, then the instance of the Activity is recreated.

singetask: if the Activity to be started is already present in the stack to which it wants to be attached, then the Activity instance will not be created and all activities on the Activity in the stack will be popped. If the Activity to be launched does not exist in the stack to which it wants to be attached and the stack exists, then the instance of the Activity is recreated. If the stack to which the Activity to be started wants to belong does not exist, a new stack and the Activity instance are created, and the Activity instance is pushed into the new stack.

single element: basically similar to singetask, except that when an Activity is started, a new stack is created, then the Activity instance is created and pushed into the new stack, and the Activity instance exists in the new stack.

3. Stack management: the stack is a container for storing Activity pages, managing the lifecycle of the pages and switching between pages. The stack managed activities follow the principle of first-in last-out, and the application system displays the activities at the top of the stack, and it can be understood that the activities at the top of the stack may be last-opened activities.

4. Other terms

In embodiments of the present application, the words "first," "second," and the like are used to distinguish between identical or similar items that have substantially the same function and effect. For example, the first chip and the second chip are merely for distinguishing different chips, and the order of the different chips is not limited. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

5. Terminal equipment

The terminal device of the embodiment of the application can also be any form of electronic device, for example, the electronic device can include a handheld device with a stack management function, a vehicle-mounted device and the like. For example, some electronic devices are: a mobile phone, tablet, palm, notebook, mobile internet device (mobile internet device, MID), wearable device, virtual Reality (VR) device, augmented reality (augmented reality, AR) device, wireless terminal in industrial control (industrial control), wireless terminal in unmanned (self driving), wireless terminal in teleoperation (remote medical surgery), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, public computing device or other processing device connected to wireless modem, vehicle-mounted device, wearable device, terminal device in future communication network (public land mobile network), or land mobile communication network, etc. without limiting the application.

By way of example, and not limitation, in embodiments of the application, the electronic device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiment of the application, the electronic equipment can also be terminal equipment in an internet of things (internet of things, ioT) system, and the IoT is an important component of the development of future information technology, and the main technical characteristics of the IoT are that the article is connected with a network through a communication technology, so that the man-machine interconnection and the intelligent network of the internet of things are realized.

The electronic device in the embodiment of the application may also be referred to as: a terminal device, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, a user equipment, or the like.

In an embodiment of the present application, the electronic device or each network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like.

By way of example, fig. 1 shows a schematic diagram of an electronic device.

The electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device. In other embodiments of the application, the electronic device may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

It should be understood that the connection relationship between the modules illustrated in the embodiments of the present application is only illustrative, and does not limit the structure of the electronic device. In other embodiments of the present application, the electronic device may also use different interfacing manners, or a combination of multiple interfacing manners in the foregoing embodiments.

The electronic device implements display functions via a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The electronic device may implement shooting functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer-executable program code that includes instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device (e.g., audio data, phonebook, etc.), and so forth. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional applications of the electronic device and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor. For example, a stack management method in interface display of an embodiment of the present application may be performed.

Fig. 2 is a software configuration block diagram of a terminal device according to an embodiment of the present application. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages. As shown in fig. 2, the application package may include applications for cameras, calendars, phones, maps, games, and the like. For example, in the embodiment of the present application, the display of the interface and the interface interaction of the user may be implemented at the application layer.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions. For example, in the embodiment of the application, the system side can provide the bottom layer implementation of the shortcut application card, including related operations of creating, managing, removing and the like of the stack of the application program.

As shown in FIG. 2, the application framework layer may include a window manager, resource manager, notification manager, graphics rendering, and the like.

The window manager is used for managing window programs. The window manager may obtain the display screen size, determine if there is a status bar, lock screen, touch screen, drag screen, intercept screen, etc. For example, in an embodiment of the present application, a window manager may be used to implement operations related to interface display.

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in a status bar, giving out a prompt tone, vibrating a terminal device, flashing an indicator light, etc.

Graphics rendering is used to render graphics.

The graphic rendering is used for rendering the drawn graphic.

Android runtimes include core libraries and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing functions such as object life cycle management, stack management, thread management, security and exception management, garbage collection and the like, for example, the virtual machine can be used for executing related stack management operations such as creation, multiplexing, removal and the like of stacks corresponding to interface switching display in the embodiment of the application.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), graphics processing Libraries (e.g., openGL ES), graphics engines (e.g., SGL), graphics composition, etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

Graphics compositing is used to composite one or more rendered views into a display interface.

The kernel layer is a layer between hardware and software. The kernel layer may include display drivers, camera drivers, audio drivers, central processor drivers, and the like.

In order to improve user experience, applications with various functions are increasing, and when a user wants to switch between functions of different applications, the user needs to exit one application, find and open another application. In addition, the user also needs to find the corresponding application function under the multi-layer directory of the application program, and the complicated operation brings the problem of inconvenient function switching for the user.

In some implementations, the terminal application may place the user common functions as much as possible on the application's main interface, or provide a common function entry on the application's main interface. However, the user still needs to withdraw from one application and then open another application to find the corresponding function, and often too many functions cannot be displayed in the main interface or the common function entrance of the application, so that the user has complicated operation and wastes time when performing function switching between different applications, and inconvenience is caused to the use of the user.

In view of this, the stack management method in the interface display provided by the embodiment of the application can realize the switching between the function pages of different applications in one interface, and simplify the operation flow of switching between different application functions for the user, thereby saving the user time and improving the user experience.

The stack management method in the interface display according to the embodiment of the present application is described in detail below by way of specific embodiments. The following embodiments may be combined with each other or implemented independently, and the same or similar concepts or processes may not be described in detail in some embodiments.

Fig. 3 shows a scenario of interface switching between different application functions according to an embodiment of the present application.

For example, as shown in a of fig. 3, the terminal device may display any interface such as a main interface, and the user may tap on the back of the terminal device, and the terminal device may receive a tap operation of the user and enter the first interface shown in b of fig. 3 in response to the tap operation.

The tapping operation may be N continuous taps, and the specific number of taps N in the embodiment of the present application is not limited, for example, N may be 2. N can be set by default in the terminal equipment or can be set by user definition.

The first interface may include a status bar 301 and a page content display area 302 corresponding to the application function. The status bar 301 may display icons corresponding to different application functions, as well as the selected status of the function icons.

The status bar 301 and the page content display area 302 may be displayed through a floating window, or may be displayed in the form of a split screen or a card, and the size of the status bar 301 and the page content display area 302 may be smaller than or equal to the screen size of the terminal device. The specific display form and interface size of the status bar 301 and the page content display area 302 are not limited in this embodiment of the present application.

The status bar 301 may be displayed below the page content display area 302, may be displayed above or beside the page content display area 302, or may be displayed at any position of the first interface in a bubble manner, and the display form and the display position of the status bar 301 are not limited herein.

The status bar 301 may display a plurality of function icons of different applications, for example, an icon corresponding to a first function of a first application and an icon corresponding to a second function of a second application. The status bar 301 may display icons corresponding to different functions of the same application, for example, an icon corresponding to a first function of a first application and an icon corresponding to a third function of the first application, or an icon corresponding to a second function of a second application and an icon corresponding to a fourth function of the second application.

The function type of the application displayed in the status bar 301 may be an application function type set by default by the terminal device, and for example, the type of the application function may be a payment type function, a scan type function, a navigation type function, or the like. The function types of the applications displayed in the status bar 301 may also be application functions that are added by user customization, for example, the user may customize the commonly used application function types in setting the applications or other applications, and the specific application function types that are displayed are not limited herein.

It can be understood that the user can add the application function by self-defining, and the application function can be added in the application function adding item of the setting application of the terminal device; the addition of the application function may also be performed by entering an application function add-on through the setup function 304 in the first interface as shown in b of fig. 3; or the application may be added by other modes, and the embodiment of the present application is not limited herein. The application function added by the user in a self-defining way can be set based on the content displayed in the application function adding item. The application in the terminal equipment can be identified by calling the interface provided by the terminal equipment, so that the corresponding application function is displayed in the application function adding item, and the user can perform self-defined adding according to the displayed application function.

The application function icon displayed in the status bar 301 may be the same as the corresponding function icon in the application, or may be an enlarged version, a reduced version, or an icon displayed after other processing manners, or may be an icon style provided by the terminal device, or may be an application function icon style set by user definition. The application function icon style which is set by the user in a user-defined manner can be set by entering the application function adding item, and the embodiment of the application is not limited herein.

The order of the application function icons displayed in the status bar 301 may be an order set by default by the terminal device, or may be an order of application function icons set by user definition, for example, the terminal device or the user may set the display order of the icons according to the frequency of use of the application functions. The order of the application function icons set by the user may be set by entering the application function adding item, and the specific order of the application function icons is not limited herein.

The number of application functions displayed in the status bar 301 may be the number of application functions set by default by the terminal device, or may be the number of application functions set by user definition. The user may perform the user-defined setting by entering the application function adding item, and the number of the application functions specifically added is not limited herein. It will be appreciated that when the number of functions added by the user exceeds the number of application function icons displayed in the status bar 301, the first interface may provide the user with other ways or entries to display application functions. For example, the status bar 301 may be in a slidable state, so that the user may view the added application function through a sliding operation, or the status bar 301 may also display a multi-application function viewing icon, so that the user may view the added application function by clicking on the viewing icon, and the embodiment of the present application is not limited herein.

In the status bar shown in b of fig. 3, the icon 303 may be in a selected state, and the other icons may be in unselected states. The selected and unselected states of the icons can be distinguished by differences in the color, size, gray scale, etc. of the icons or the color, size, gray scale, etc. of the fonts. The difference between the specific selected state and the unselected state is not limited herein.

The content displayed in the page content display area 302 corresponding to the application function may be displayed as a corresponding function page according to the selected state of the function icon in the status bar 301. For example, in fig. 3 b, the icon 303 corresponding to the payment function of the first application may be in a selected state, and the page content display area 302 may display the page content corresponding to the payment function of the first application. The page content corresponding to the payment function of the first application may include a barcode and/or information related to payment such as a two-dimensional code, and other specific display details in the page content display area 302, which is not limited herein in this embodiment of the present application.

In the first interface shown in fig. 3 b, the user may click on other application function icons in the status bar 301, and the terminal device may receive a click operation of the user and perform an operation of switching the first interface to the second interface shown in fig. 3 c in response to the click operation. After the first interface switches to the second interface, icon 305 may be in a selected state and icon 303 and other icons may be in unselected states. The switching operation may be clicking an application function icon in the status bar 301, sliding left and right, or sliding up and down, or sliding in other directions, or may be through a user voice input, a designated gesture operation, a designated shaking or flipping terminal device operation, a user-defined operation, or other switching operations. The operation mode of the second interface is specifically switched by the first interface, and the embodiment of the application is not limited herein.

The implementation can be divided into two scenes, namely, scene one: the terminal device enters an interface corresponding to a first function of the first application of fig. 3 b from the interface of fig. 3 a, and a second scenario: the terminal device switches from the first function of the first application to the second function of the second application, and the terminal device can execute the stack management method in the embodiment of the application in both scenes. The manner of stack management specified by the terminal device in the first scenario is similar to that in the second scenario, and the method of stack management performed by the terminal device will be described below by taking the first scenario as an example.

When the terminal device will enter the first interface as shown in b of fig. 3 in response to a user's tapping operation, a new task stack may be created for the first application, or an old stack created by the first application may be multiplexed.

The terminal device may create a new task stack for the first application, where the new stack may store page information for displaying the first interface corresponding to the function of the first application, and display the corresponding first interface by loading the page information in the new stack. It will be appreciated that the new stack may be run in a separate task stack, as shown in fig. 4, and that the old task stacks corresponding to the first application may be isolated from each other and not affect each other.

In a possible way of creating a new stack, as shown in fig. 5, during the process of creating a new stack, an application side in a terminal device may be used to load a corresponding interface according to stack information of a first application, and a system side in the terminal device may be used to perform stack management, for example: related operations of creating a new stack, acquiring stack information, removing stack management of the new stack, and the like. For example, the system side may determine whether to create a new stack by determining whether the obtained value of the target field in the first application is a preset value. The value of the target field may be an integer, boolean, or other type of field, and embodiments of the present application are not limited herein. In one possible implementation manner of determining the target field value, the application side may determine according to a startup mode when the first application starts the Activity. For example, when the application side determines that the start mode of the Activity of the first application is standard, the target field value is transferred to the system side as a preset value, the system side obtains the target field value, and determines that a new stack can be created, and the stack manager of the system side can create a new stack for the first application.

In another possible way of creating the new stack, when the value of the target field in the first application acquired by the system side is not a preset value, the system side judges that the new stack is not created, and instructs the stack manager to query the reusable old stack. If no reusable old stack is queried, the stack manager may create a new stack for the first application. In one possible way of querying the old stack, the stack manager may query the stack for the name of the same Activity as the first application or an instance of the attribute in the Activity, and if the name of the same Activity as the first application or the instance of the attribute in the Activity is not queried, the stack manager may create a new stack for the first application. In another possible way of querying the old stack, the stack manager may query the reusable old stack according to the packet name or other associated attribute corresponding to the first application, and if the packet name or other associated attribute corresponding to the first application is not queried, the stack manager may create a new stack for the first application.

In another possible new stack creation manner, the system side may determine whether to create a new stack by querying whether the first application is running in the background, and if it is queried that the first application is not running in the background, the stack manager may create a new stack for the first application. In a possible mode of judging whether the first application is running in the background, the system side can query a currently running program or task stack through a calling interface or a function, and if the currently running program has no first application program or the task stack has no stack information of the first application, the system side can indicate that the first application is not running in the background. In another possible mode of judging whether the first application is running in the background, the system side can monitor the life cycle condition of the first application, and can indicate that the first application is not running in the background if the life cycle of all activities of the first application is finished by calling back the life cycle conditions of all activities of the first application through the interface or the function. In another possible mode of judging whether the first application is running in the background, the system side can acquire statistical information of all applications in the current time period and inquire whether information corresponding to the first application exists, and if the information of the first application is not inquired, the system side can indicate that the first application is not running in the background. The method for specifically determining whether the application is running in the background is not limited herein.

After the terminal device responds to the above switching operation, the old stack created by the first application may also be used, as shown in fig. 6, and before the first interface information corresponding to the function for displaying the first application is put in the old stack, the stack top information and the old stack size of the old stack may be recorded. The terminal device can distinguish the existing page information in the old stack from the page information corresponding to the first interface according to the stack top information of the old stack, and can modify the size of the old stack according to the page information corresponding to the first interface, and put the page information corresponding to the first interface in the old stack. It will be appreciated that the modified old stack size may be less than or equal to the size of the original old stack. And the application side displays the corresponding interface by loading the page information corresponding to the first interface put in the old stack.

In one possible way of multiplexing the old stack, as shown in fig. 7, for example, when the application side determines that the activation mode of the Activity of the first application is single task or single task, the application side may transfer the value of the target field of the old stack to the system side. After receiving the information of the multiplexed old stack, the system side indicates the stack manager to inquire whether the multiplexed old stack exists, and if the multiplexed old stack can be inquired, the old stack is multiplexed and the information of the current old stack is stored.

In another possible old stack multiplexing mode, the system side may query whether the first application is running in the background, and if the first application is queried to run in the background, the system side may determine whether to multiplex the old stack by determining whether the value of the target field in the first application is a preset value. When the value of the target field in the first application acquired by the system side is not a preset value, the system side judges that the old stack is multiplexed, and then instructs the stack manager to inquire whether the old stack which can be multiplexed exists. If the available old stack can be queried, multiplexing the old stack and saving the information of the current old stack. The method for determining whether the first application is running in the background is described in the above method for creating a new stack, and will not be described in detail herein.

Similarly, for the stack management method executed by the terminal device when the terminal device switches the first function of the first application to the second function of the second application in the second scenario, the stack management method described in the first scenario may be referred to, and the embodiments of the present application are not described herein again. It may be understood that, as shown in fig. 8, if the first application is to create a new stack, and the terminal device needs to create a new stack for the second when switching the first function of the first application to the second function of the second application, the stack manager on the system side may remove the stack created by the first application and create a new stack for the second application.

It can be understood that after the second interface corresponding to the second function of the second application is displayed, the switching operation of switching the second interface back to the first interface, or switching the second interface to the third interface, etc. may also be performed by referring to the stack management method described in the first scenario. For example, the switching between different interfaces may be performed by clicking on other application function icons in the status bar shown in fig. 3 c or by other switching operations.

In addition, the user may click on the exit icon 306 of b of fig. 3, and the terminal device may receive the click operation of the user and perform an operation of exiting the first interface shown in b of fig. 3 in response to the click operation. It is understood that the exit operation of the second interface or other interfaces is similar to the exit operation of the first interface, and will not be described herein. The exit operation may be clicking an exit icon, clicking a blank area in the interface of the terminal device, or performing a user voice input, a designated gesture operation, a user-defined operation, or other operations. The specific manner in which the interface is exited is not limited in this embodiment of the application.

After the terminal device responds to the first interface exit operation, if the task stack of the first application is a new stack, deleting the new stack of the first application. If the task stack of the first application is the old stack created by multiplexing, removing page information on the old stack top information of the first application, and recovering the old stack size before the first application, as shown in fig. 9. Correspondingly, the stack management method of the terminal device exiting the second interface or other interfaces is similar to the stack management method exiting the first interface, and the embodiments of the present application are not described herein again.

Fig. 10 illustrates a stack management method in an interface display according to an embodiment of the present application. The method comprises the following steps:

s1001, displaying a first interface, wherein the first interface comprises: interface content corresponding to a first function of a first application, a first icon corresponding to the first function, and a second icon corresponding to a second function of a second application; the first icon is in a selected state, and the second icon is in an unselected state.

For example, the first interface may be an interface as shown in b of fig. 3, and details of the specific display may be referred to the related description in the foregoing embodiment, which is not described herein.

The display of the first interface by the terminal device may be based on the triggering of the back of the terminal device by the user, or may be switched from other interfaces to the first interface by the user, which is not limited in particular.

S1002, a first operation for switching a first application to a second application is received at a first interface.

For example, in the first interface shown in fig. 3 b, the user may click on other application function icons in the status bar 301, and the terminal device may receive a click operation of the user and perform an operation of switching the first interface to the second interface in response to the click operation. The specific switching operation manner may be referred to the related description in the above embodiments, and will not be repeated here.

S1003, in response to the first operation, a new stack is created for the second application, or an old stack created by the second application is multiplexed.

For example, the terminal device may switch from the first interface shown in fig. 3 b to the second interface shown in fig. 3 c in response to a switching operation of the user, and may create a new task stack for the second application, or multiplex the old stack created by the second application. The specific stack management method executed by the terminal device may refer to the stack management method described in the first scenario in the above embodiment, and the embodiments of the present application are not described herein again.

S1004, displaying a second interface according to stack information of a second application, wherein the second interface comprises: interface content corresponding to a second function of a second application, a first icon, and a second icon; the second icon is in a selected state, the first icon is in an unselected state, and the stack information of the second application is stack information in a new stack of the second application or stack information in an old stack of the second application.

For example, the display of the second interface may be an interface as shown in c of fig. 3, and similar to the display of the first interface, the second interface may also include a status bar and a page content display area corresponding to the application function. The specific content displayed in the status bar and the page content display area may be referred to the related description in the above embodiments, and will not be described herein.

In the embodiment of the application, the related content of the application function displayed in the interface and the switching operation between the interfaces can be set by default through the terminal equipment or by user definition, so that more convenient application function and interface switching service can be provided for the user. The terminal equipment can create a new stack and multiplex the stack management mode of the old stack according to different use scenes, and the stack management method in interface display is realized, so that the memory resource of the terminal equipment is more reasonably utilized, and the management efficiency of the stack memory is improved.

Optionally, before displaying the first interface in S1001, on the basis of the embodiment corresponding to fig. 10, the method may include: and receiving a preset operation aiming at a preset area of the terminal equipment.

In the embodiment of the present application, the preset area may be any area on the surface of the terminal device, for example, may be a back area of the terminal device, may also be a side area of the terminal device, or may also be an area in a display screen of the terminal device, etc. For example, receiving a preset operation for a preset area of the terminal device may be receiving a continuous tapping operation for a back plate of the terminal device.

In the embodiment of the application, the first interface can be opened rapidly through default setting of the terminal equipment or preset operation of user-defined setting. The user-defined setting can be set according to the operation habit of the user, so that the operation speed of opening the first interface by the user is improved.

Optionally, based on the embodiment corresponding to fig. 10, displaying the first interface in S1001 may include: and displaying interface contents corresponding to the first function in the first interface in the form of a floating window or a split screen or a card. The first function may include any of the following: payment type function, scanning type function, navigation type function.

In the embodiment of the application, the first interface may include a status bar and a page content display area corresponding to the application function. The status bar and the page content display area can be displayed through a floating window or can be displayed in a split screen or card mode. The function types of the applications displayed in the status bar may be set by default by the terminal device, or may be added by user definition, and the specific display forms of the status bar and the page content display area and the types of the application functions may be referred to the related descriptions in the above embodiments, which are not described herein.

In the embodiment of the application, the related content of the application function displayed in the first interface can be set by default through the terminal equipment or can be set by user definition, so that the function required by the user can be displayed more flexibly, and more convenient application function use is provided for the user.

Optionally, based on the embodiment corresponding to fig. 10, the first operation of switching the second application by the first application in S1002 may include: triggering a second icon, or a sliding operation.

In the embodiment of the application, the user can switch the second application by triggering the second icon or sliding the second icon, so that the terminal equipment can receive the switching operation of the user and respond to the switching operation to execute the operation of switching the second application by the first application. The specific operation manner of switching the application function may be referred to the related description in the above embodiments, and the embodiments of the present application are not described herein again.

In the embodiment of the application, by providing different operation modes for switching application functions, the operation experience of interface switching can be optimized, and a user can be helped to operate terminal equipment better, so that the operation speed of interface switching is improved.

Optionally, on the basis of the embodiment corresponding to fig. 10, creating a new stack for the second application in S1003, or multiplexing the old stack created by the second application may include: acquiring a value of a target field in the second application; if the value of the target field in the second application is the first preset value, a new stack is created for the second application; if the value of the target field in the second application is not the first preset value or the second preset value, inquiring whether the second application has created an old stack, multiplexing the old stack created by the second application if the second application has created the old stack, and creating a new stack for the second application if the second application has not created the old stack.

Optionally, creating a new stack for the second application in S1003, or multiplexing the old stack created by the second application, may further include: determining whether the second application is running in the background; if the second application is not running in the background, a new stack is created for the second application; if the second application runs in the background, acquiring a value of a target field in the second application, and if the value of the target field in the second application is a first preset value, creating a new stack for the second application; and if the value of the target field in the second application is not the first preset value or the second preset value, multiplexing an old stack created by the second application of the stack.

In the embodiment of the application, when the terminal equipment responds to the switching operation of the user and is switched from the first interface to the second interface, a new task stack can be created for the second application, or an old stack created by the second application is multiplexed. The specific stack management method executed by the terminal device may refer to the stack management method described in the first scenario in the above embodiment, and the embodiments of the present application are not described herein again.

In the embodiment of the application, the new stack can be simply, independently and conveniently created, and the old stack can be reused to save stack memory resources. The terminal equipment can create a new stack and multiplex the stack management mode of the old stack according to different use scenes, and the stack management method in interface display is realized, so that the memory resource of the terminal equipment is more reasonably utilized, and the management efficiency of the stack memory is improved.

Optionally, on the basis of the embodiment corresponding to fig. 10, the multiplexing the old stack created by the second application in S1004 may include: modifying the size of an old stack created by the second application according to page information corresponding to the second interface, and placing page information corresponding to the second interface in the old stack created by the second application; and displaying a second interface according to the stack information of the second application.

In the embodiment of the application, before the page information corresponding to the second interface is put in the old stack created by the second application, the old stack information created by the second application is recorded, wherein the old stack information can comprise the old stack top information and the old stack size. The terminal equipment can display the second interface according to page information corresponding to the second interface in the old stack of the second application. The second interface may also include a status bar and a page content display area corresponding to the application function. The specific status bar and the related method of stack management for displaying the page content display area can be referred to the related description in the above embodiment, and the embodiments of the present application are not described herein again.

In the embodiment of the application, the second interface can display corresponding functions according to the requirements of different users, and can provide more convenient function using services for the users. The terminal equipment can save stack memory resources by multiplexing old stacks, and improve the management efficiency of stack memory.

Optionally, after displaying the second interface in S1004, on the basis of the embodiment corresponding to fig. 10, the method may further include: receiving a second operation for exiting the display of the second interface; and responding to the second operation, removing page information corresponding to the second interface in the old stack of the second application, and restoring the old stack of the second application to a state before the page information corresponding to the second interface is put in.

In the embodiment of the application, removing the page information corresponding to the second interface in the old stack of the second application may be removing the page information on the old stack top information, and restoring the old stack of the second application to the state before the page information corresponding to the second interface is placed may be restoring the old stack size of the second application.

It can be understood that if the page information corresponding to the second interface is displayed by creating a new stack of the second application, and when an operation for exiting the display of the second interface is received after the second interface is displayed, the terminal system responds to the operation for exiting the display of the second interface, and deletes the new stack of the second application.

In the embodiment of the present application, the operation mode of specifically exiting the second interface and the method executed by the terminal device after responding to the operation of exiting the second interface are similar to the operation of exiting the first interface in the first scenario of the above embodiment, and the embodiment of the present application is not described herein again.

In the embodiment of the application, the page information on the old stack top information is removed, and the old stack information and the old stack size of the second application are restored, so that the use of the second application operated by the user before is not influenced, and quick and convenient interface display is provided for the user.

The foregoing description of the solution provided by the embodiments of the present application has been mainly presented in terms of a method. To achieve the above functions, it includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the present application may be implemented in hardware or a combination of hardware and computer software, as the method steps of the examples described in connection with the embodiments disclosed herein. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application can divide the functional modules of the device for realizing the stack management method in the interface display according to the method example, for example, each functional module can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.

Fig. 11 is a schematic structural diagram of a chip according to an embodiment of the present application. Chip 1100 includes one or more (including two) processors 1101, communication lines 1102, a communication interface 1103, and a memory 1104.

In some implementations, the memory 1104 stores the following elements: executable modules or data structures, or a subset thereof, or an extended set thereof.

The method described in the above embodiments of the present application may be applied to the processor 1101 or implemented by the processor 1101. The processor 1101 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuitry in hardware in the processor 1101 or instructions in software. The processor 1101 may be a general purpose processor (e.g., a microprocessor or a conventional processor), a digital signal processor (digital signal processing, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), an off-the-shelf programmable gate array (field-programmable gate array, FPGA) or other programmable logic device, discrete gates, transistor logic, or discrete hardware components, and the processor 1101 may implement or perform the methods, steps, and logic blocks related to the disclosed processes in the embodiments of the present application.

The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a state-of-the-art storage medium such as random access memory, read-only memory, programmable read-only memory, or charged erasable programmable memory (electrically erasable programmable read only memory, EEPROM). The storage medium is located in the memory 1104, and the processor 1101 reads information in the memory 1104 and performs the steps of the above method in combination with its hardware.

The processor 1101, the memory 1104, and the communication interface 1103 may communicate with each other via a communication line 1102.

In the above embodiments, the instructions stored by the memory for execution by the processor may be implemented in the form of a computer program product. The computer program product may be written in the memory in advance, or may be downloaded in the form of software and installed in the memory.

Embodiments of the present application also provide a computer program product comprising one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL), or wireless (e.g., infrared, wireless, microwave, etc.), or semiconductor medium (e.g., solid state disk, SSD)) or the like.

The embodiment of the application also provides a computer readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. Computer readable media can include computer storage media and communication media and can include any medium that can transfer a computer program from one place to another. The storage media may be any target media that is accessible by a computer.

As one possible design, the computer-readable medium may include compact disk read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disk memory; the computer readable medium may include disk storage or other disk storage devices. Moreover, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, digital versatile disc (digital versatile disc, DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims

1. A stack management method in interface display, applied to a terminal device, the method comprising:

displaying a first interface, the first interface comprising: interface content corresponding to a first function of a first application, a first icon corresponding to the first function, and a second icon corresponding to a second function of a second application; wherein the first icon is in a selected state and the second icon is in an unselected state;

Receiving a first operation for switching the first application to the second application at the first interface;

creating a new stack for the second application or multiplexing an old stack created by the second application in response to the first operation;

displaying a second interface according to the stack information of the second application, wherein the second interface comprises: interface content corresponding to the second function of the second application, the first icon, and the second icon; the second icon is in a selected state, the first icon is in an unselected state, and the stack information of the second application is stack information in a new stack of the second application or stack information in an old stack of the second application.

2. The method of claim 1, wherein the creating a new stack for the second application or multiplexing an old stack that the second application has created comprises:

acquiring a value of a target field in the second application;

if the value of the target field in the second application is a first preset value, a new stack is created for the second application;

if the value of the target field in the second application is not the first preset value or the second preset value, inquiring whether the second application has created an old stack, if the second application has created an old stack, multiplexing the old stack created by the second application, and if the second application has not created an old stack, creating a new stack for the second application.

3. The method of claim 1, wherein the creating a new stack for the second application or multiplexing an old stack that the second application has created comprises:

determining whether the second application is running in the background;

if the second application is not running in the background, a new stack is created for the second application;

if the second application runs in the background, acquiring a value of a target field in the second application, and if the value of the target field in the second application is a first preset value, creating a new stack for the second application; and multiplexing an old stack created by the second application if the value of the target field in the second application is not the first preset value or the second preset value.

4. A method according to any of claims 1-3, wherein said multiplexing old stacks that have been created by said second application comprises:

modifying the size of an old stack created by the second application according to the page information corresponding to the second interface, and placing the page information corresponding to the second interface in the old stack created by the second application;

and displaying a second interface according to the stack information of the second application, including: and displaying a second interface according to page information corresponding to the second interface in the old stack of the second application.

5. The method of claim 4, wherein after displaying the second interface, the method further comprises:

receiving a second operation for exiting the display of the second interface;

and responding to the second operation, removing page information corresponding to the second interface in the old stack of the second application, and restoring the state of the old stack of the second application before the page information corresponding to the second interface is put in.

6. The method of claim 5, wherein multiplexing the old stack that the second application has created further comprises:

recording old stack information of an old stack created by the second application before the old stack is put into page information corresponding to the second interface, wherein the old stack information comprises: old stack top information and old stack size;

the removing the page information corresponding to the second interface in the old stack of the second application, and recovering the old stack of the second application to a state before the page information corresponding to the second interface is put in includes:

and removing page information on the old stack top information, and recovering the old stack of the second application to be the old stack size.

7. A method according to any of claims 1-3, wherein displaying a second interface according to stack information of the second application comprises: displaying a second interface according to page information corresponding to the second interface in a new stack of the second application;

After the second interface is displayed, the method further comprises:

receiving an operation for exiting the display of the second interface;

and deleting the new stack of the second application in response to the operation for exiting the display of the second interface.

8. The method of any of claims 1-7, wherein prior to displaying the first interface, further comprising:

receiving a preset operation aiming at a preset area of the terminal equipment;

responding to the preset operation, creating a new stack for the first application, or multiplexing the created old stack of the first application;

the displaying a first interface includes: and displaying the first interface according to the stack information of the first application.

9. The method of claim 8, wherein the receiving a preset operation for the preset area of the terminal device comprises:

a continuous tapping operation is received for a back plate of the terminal device.

10. The method of any of claims 1-9, wherein the first application switching a first operation of the second application comprises: triggering the second icon or sliding operation.

11. The method according to any one of claims 1 to 10, wherein in the first interface, interface content corresponding to the first function is displayed in the form of a floating window or a split screen or a card; and in the second interface, the interface content corresponding to the second function is displayed in a floating window or split screen or card form.

12. The method of any one of claims 1-11, wherein the first function or the second function comprises any one of the following: payment type function, scanning type function, navigation type function.

13. A terminal device, comprising: a memory for storing a computer program and a processor for executing the computer program to perform the stack management method in an interface display according to any one of claims 1-12.

14. A computer readable storage medium storing instructions that, when executed, cause a computer to perform the stack management method in an interface display of any one of claims 1-12.

15. A computer program product comprising a computer program which, when run, causes an electronic device to perform the stack management method in an interface display of any one of claims 1-12.