WO2024109286A1 - 多窗口切换方法及装置、电子设备以及计算机可读存储介质 - Google Patents
多窗口切换方法及装置、电子设备以及计算机可读存储介质 Download PDFInfo
- Publication number
- WO2024109286A1 WO2024109286A1 PCT/CN2023/119188 CN2023119188W WO2024109286A1 WO 2024109286 A1 WO2024109286 A1 WO 2024109286A1 CN 2023119188 W CN2023119188 W CN 2023119188W WO 2024109286 A1 WO2024109286 A1 WO 2024109286A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- target application
- window
- mode
- support
- window mode
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 74
- 238000007667 floating Methods 0.000 claims description 43
- 230000000694 effects Effects 0.000 claims description 20
- 238000001514 detection method Methods 0.000 claims description 10
- 230000000875 corresponding effect Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 5
- 230000004913 activation Effects 0.000 claims description 4
- 230000002596 correlated effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000009471 action Effects 0.000 description 4
- 238000013528 artificial neural network Methods 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 101001121408 Homo sapiens L-amino-acid oxidase Proteins 0.000 description 3
- 101000827703 Homo sapiens Polyphosphoinositide phosphatase Proteins 0.000 description 3
- 102100026388 L-amino-acid oxidase Human genes 0.000 description 3
- 102100023591 Polyphosphoinositide phosphatase Human genes 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 101100012902 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) FIG2 gene Proteins 0.000 description 2
- 101100233916 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) KAR5 gene Proteins 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
Definitions
- the present disclosure relates to the field of computer technology, and in particular to a multi-window switching method and device, an electronic device, and a computer-readable storage medium.
- multiple applications in the terminal can be displayed in a multi-window mode.
- the purpose of the present disclosure is to provide a multi-window switching method and device, an electronic device, and a storage medium, thereby overcoming the problem of having many steps for switching multi-window modes due to limitations and defects of related technologies, at least to a certain extent.
- a multi-window switching method including: detecting a gesture touch operation acting on a target application in a terminal, and determining the support status of the target application for the multi-window mode; if the support status of the target application is to support the multi-window mode, displaying the target application through the multi-window mode.
- a multi-window switching device including: a touch operation detection module, used to detect a gesture touch operation acting on a target application in a terminal, and determine the support status of the target application for the multi-window mode; a multi-window mode activation module, used to display the target application through the multi-window mode if the support status of the target application is to support the multi-window mode.
- an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the first A multi-window switching method and possible implementation thereof.
- a computer-readable storage medium on which a computer program is stored.
- the computer program is executed by a processor, the multi-window switching method and possible implementation methods thereof of the first aspect are implemented.
- the technical solution provided in the embodiments of the present disclosure can display the target application using the multi-window mode according to the support status of the target application when a gesture touch operation acting on the target application is detected, thereby switching to the multi-window mode.
- a gesture touch operation acting on the target application is detected, thereby switching to the multi-window mode.
- only one gesture touch operation is required, which reduces the operation steps of switching to the multi-window mode, reduces the difficulty of operation, and improves the operation efficiency of opening the multi-window mode for the application.
- the multi-window mode can be switched directly by performing a gesture touch operation on the target application displayed in the terminal, compared with the related art, the object to be executed can be quickly determined, which improves convenience and operability.
- any terminal can be switched to the multi-window mode by a gesture touch operation acting on the target application, the scope of application is increased and the versatility is improved.
- FIG. 1 is a schematic diagram showing a method of entering a multi-window mode in the related art.
- FIG. 2 is a schematic diagram showing a multi-window switching method and an application scenario of the multi-window switching method to which an embodiment of the present disclosure can be applied.
- FIG3 schematically shows a schematic diagram of a multi-window switching method according to an embodiment of the present disclosure.
- FIG. 4 schematically shows a schematic diagram of enabling a multi-window mode for a target application in an embodiment of the present disclosure.
- FIG5 schematically shows a schematic diagram of a system architecture in an embodiment of the present disclosure.
- FIG. 6 schematically shows a first schematic diagram of enabling a multi-window mode for multiple target applications in an embodiment of the present disclosure.
- FIG. 7 schematically shows a second schematic diagram of enabling a multi-window mode for multiple target applications in an embodiment of the present disclosure.
- FIG8 schematically shows a flowchart of opening a multi-window mode according to an embodiment of the present disclosure.
- FIG. 9 schematically shows a block diagram of a multi-window switching device in an embodiment of the present disclosure.
- FIG. 10 schematically shows a block diagram of an electronic device in an embodiment of the present disclosure.
- multiple windows can be switched in the following two ways: Referring to the first way shown in FIG1 A, the steps of entering multiple windows from the sidebar and displaying multiple windows include: swiping out the sidebar; clicking on the application to be displayed in the sidebar; and displaying the application in a floating frame. Referring to the second way shown in FIG1 B, the steps of entering multiple windows from a multi-tasking card and displaying multiple windows include: entering multi-tasking; clicking on the floating button in the upper right corner of a card; and displaying the application in a floating frame.
- the user needs to perform multiple operation steps to switch to the multi-window mode; and the operation of switching to the multi-window mode is not very convenient and has poor convenience.
- different layouts need to be switched in different ways, so the versatility is poor.
- FIG2 shows a schematic diagram of the system architecture of the multi-window switching method and device of the embodiment of the present disclosure.
- the system architecture may include: a user 210 and a terminal 220.
- the terminal 220 may be any type of device, such as a computer, a smart phone, a smart TV, a tablet computer, a smart wearable device (such as AR glasses), a robot, a drone, and the like.
- the user 210 may use the terminal 220 to perform various operations.
- Various types of applications may be installed in the terminal, so that the user may perform corresponding operations on the application to enter the multi-window mode.
- the multi-window switching method provided in the embodiment of the present disclosure may be executed by the terminal 220 .
- FIG3 schematically shows a multi-window switching method in an embodiment of the present disclosure, which specifically includes the following steps:
- Step S310 detecting a gesture touch operation on a target application in the terminal, and determining a support status of the target application for a multi-window mode
- Step S320 If the support status of the target application is to support the multi-window mode, the target application is displayed in the multi-window mode.
- the target application may be any application in the terminal.
- the gesture touch operation may be a swipe up operation. If a gesture touch operation acting on the target application in the terminal is detected, the support status of the target application may be determined to determine whether the target application supports the multi-window mode. The support status is used to indicate whether the target application supports the multi-window mode. Further, based on the support status of the target application, the target application may be opened in the multi-window mode to display the target application, for example, the multi-window mode may be opened in a floating control mode or a split-screen mode to display the target application.
- the target application since the target application can be displayed using the multi-window mode according to the support status of the target application when the gesture touch operation acting on the target application is detected, the target application is switched to the multi-window mode.
- the target application is switched to the multi-window mode.
- only one gesture touch operation is required, which reduces the operation steps of switching to the multi-window mode, reduces the difficulty of operation, and improves the operation efficiency of opening the multi-window mode for the application.
- the multi-window mode can be switched directly by performing a gesture touch operation on the target application displayed in the terminal, compared with the related art, the object to be executed can be quickly determined, which improves convenience and operability.
- any terminal can be switched to the multi-window mode through a gesture touch operation acting on the target application, the scope of application is increased and the versatility is improved.
- step S310 if a gesture touch operation acting on a target application in the terminal is detected, a support status of the target application for the multi-window mode is determined.
- the terminal may be any type of device capable of installing applications and performing corresponding operations on the applications.
- the terminal may be a smart device such as a smartphone, a tablet computer, a smart TV, a wearable device, an access control device, etc.
- it may also include smart vehicle-mounted devices, such as a smart cockpit entertainment system of a car, etc.
- the terminal is described as a smartphone as an example.
- the application can be an application of the terminal itself or an application provided by a third party, such as a game application, a video application, and a social application, which are not specifically limited here.
- the target application can be any one or more of the applications, that is, the target application can be one application or multiple applications.
- the application can be displayed in the display interface of the terminal, and the display interface can include icons corresponding to multiple applications arranged in sequence. For example, as shown in reference FIG4, application 401, application 402, and application 403 can be displayed in sequence on the display interface 400 of the terminal. As shown in reference FIG6, application 601, application 602, and application 603 can be displayed in sequence on the display interface 600 of the terminal.
- the gesture touch operation may be a touch operation performed by the user and acting on a certain application, and is used to control the application selected by the user to switch to the multi-window mode or to start the multi-window mode.
- the gesture touch operation may be any type of touch operation, such as a sliding operation or a sliding pressing operation, etc., or an air gesture or any other
- the gesture touch operation of sliding upward is taken as an example to illustrate.
- FIG5 schematically shows a schematic diagram of a system architecture of a terminal.
- the terminal may include a kernel layer 501 , a system layer 502 , an application framework layer 503 and an application layer 504 .
- the kernel layer 501 may include display driver, camera driver, audio driver and sensor driver.
- the system layer 502 may include surface manager, 3D graphics processing library, 2D graphics engine, media library and Android runtime.
- the application framework layer 503 may include window manager, content manager, phone manager, gesture manager, activity manager, view manager and resource manager, etc.
- the application layer 504 may include camera, calendar, wmShell in SystemUI, settings, desktop, gallery, notification, navigation, Bluetooth, video, etc.
- the window manager is responsible for managing the window hierarchy and window positions in multi-window mode.
- the activity manager is responsible for managing the activity stack, as well as the size and configuration of windows.
- the gesture manager is responsible for triggering actions such as swiping up on a window.
- the wmShell module in SystemUI is responsible for displaying multiple windows.
- the settings module is responsible for dynamically setting the gesture switch.
- the gesture manager of the application framework layer 503 can be used to trigger gesture actions such as sliding up the window. Based on this, the operation acting on the target application can be detected based on the gesture manager to determine whether the target application has received the gesture touch operation. Specifically, the gesture manager can first detect whether the operation acting on the target application is received, and further, according to the position of the starting touch point and the ending touch point of the operation and the positional relationship between different touch points, it can be determined whether the received gesture touch operation meets the touch condition to determine whether it is a gesture touch operation to open the multi-window mode.
- the touch condition can be set according to actual needs, for example, the position of the starting touch point and the ending touch point can be different, and the ordinate of the starting touch point is less than the ordinate of the ending touch point.
- the position of the starting touch point is at the position of the icon of the target application, and the starting touch point is different from the ending touch point, it can be considered that the sliding operation is detected, and the direction of the sliding operation can be further determined according to the positional relationship between the starting touch point and the ending touch point.
- the gesture touch operation is a sliding operation
- the gesture touch operation can be considered successful.
- there is no specific limitation on the track length of the gesture touch operation as long as it is a swipe up operation.
- the number of target applications may be one or more, which is determined according to actual needs. For example, it is possible to detect whether a gesture touch operation acting on one target application is received, or it is possible to detect whether a gesture touch operation acting on multiple target applications is received. Furthermore, the gesture touch operations acting on different target applications may be the same or different.
- the gesture touch operation acting on the target application can be determined according to the display state of the terminal.
- the display state can be the number of applications included in the display interface, or it can be other information. If the display state of the terminal meets the display condition, the gesture touch operation is an upward sliding operation; if the display state does not meet the display condition, the gesture touch operation can be other touch operations, such as pressing and sliding operations, etc.
- the number of applications on the display interface is less than the quantity threshold, it can be considered that the display state meets the display condition.
- the quantity threshold can be six or ten, etc.
- a touch gesture operation acting on target application 401 is detected;
- a touch gesture operation acting on target application 601 and target application 602 is detected.
- the support status of the target application for the multi-window mode can be further determined, that is, the support status is used to indicate whether the target application supports the multi-window mode.
- the support status may be the same or different due to their own application properties.
- the support status of each application is set in advance according to its own application properties.
- Multi-window mode refers to a mode in which the target application is displayed in multiple scenes. Multi-window mode may include but is not limited to floating window mode, split-screen mode, and picture-in-picture mode, etc., and the floating window mode and split-screen mode are used as examples for explanation.
- the floating window mode refers to displaying the target application that receives the gesture touch operation in a floating layer on the display interface.
- the split-screen mode refers to dividing the display interface into multiple screen areas to display the target application that receives the gesture touch operation through multiple screen areas.
- the activity manager of the application framework layer 503 can be used to determine the support status of the target application through the attribute information of the target application.
- whether the support status of the target application is to support the multi-window mode can be determined by whether the attribute information is the first identifier or the second identifier.
- the attribute information can be represented by android:resizeableActivity.
- the first identifier can be true for representing a correct value, and the second identifier can be false for representing an incorrect value.
- the target application When the attribute information of the target application is determined to be the first identification by the activity manager, it can be considered that the target application supports the multi-window mode, that is, supports the use of floating windows or the use of split-screen mode display.
- the attribute information of the target application is determined to be the second identification by the activity manager, it can be considered that the target application does not support the multi-window mode, that is, the target application does not support the use of floating windows or the use of split-screen mode display.
- step S320 if the support status of the target application is to support the multi-window mode, the target application is displayed in the multi-window mode.
- different methods can be selected to display the target application according to the support status of the target application. For example, if the support status of the target application is to support multi-window mode, the target application can be opened in multi-window mode to display the target application, that is, the target application is switched to multi-window mode for display. If the support status of the target application is not to support multi-window mode, the display mode of the target application can be kept unchanged, and prompt information for displaying the support status of the target application for multi-window mode is provided.
- the number of target applications can be one or more, and the number of target applications can be determined according to actual needs.
- the number of target applications is different, and the display method of displaying the target applications through the multi-window mode is also different.
- the display method of displaying the target application can include a floating control method (floating window) and a split screen method, in addition to which it can also include a picture-in-picture mode or other modes, etc.
- the target application when the number of target applications is one, if a gesture touch operation acting on the target application is detected, and it is determined that the support state of the target application is to support multi-window mode, the target application can be switched to multi-window mode using a floating control to display the target application in multi-window mode. That is. Use the floating control to turn on the multi-window mode of the target application.
- the floating control can be located at the top layer of the display interface, that is, the layer above the display interface.
- the floating control can be a floating window, which can be located at any suitable position on the display interface, and the floating control can display the detailed content of the target application that receives the gesture touch operation.
- the size of the floating control can be determined according to the default parameters, or it can be customized and adjusted, which is not limited here.
- multiple applications are displayed on the display interface. If the gesture manager detects a gesture touch operation acting on the target application 401, and the activity manager determines that the support state of the target application 401 is to support the multi-window mode through the attribute information android:resizeableActivity is true. On this basis, as shown in reference to FIG4 , the target application is started in the floating window mode through the activity manager, and a floating control 404 can be provided at any position on the display interface, and the detailed content of the target application 401 is displayed in the floating control 404, so as to display the detailed content of the target application through the floating window.
- the display mode of each target application can be determined according to the support status of each target application, thereby determining the display mode of the multiple target applications, and then switching the multiple target applications to multi-window mode for display through the display mode.
- the display mode can be determined according to the number of target applications whose support status is to support the multi-window mode.
- the display mode can be a split-screen mode; wherein the target applications that support the multi-window mode can be all the applications in the target applications that receive the gesture touch operation, or can be part of them.
- the number of target applications that receive gesture touch operations can be 4.
- the number can be 2, 3 or 4, which can be determined by the activity manager based on the value of the attribute information of each application.
- each target application can be displayed in a split-screen manner.
- the display interface of the terminal can be divided into multiple screen areas according to the number of target applications that support multi-window mode, so that each target application can be displayed independently through each screen area.
- the sizes of the multiple screen areas can be the same or different, and can be determined according to actual needs.
- the length and width of each screen area can be determined according to the size of the display interface.
- the size of the screen area can be determined according to the application information of each target application.
- the application information can be the memory occupied by the target application, the click frequency, etc.
- the size of the screen area is positively correlated with the size of the application information of the target application. For example, when clicking, the screen area is positively correlated with the size of the application information of the target application.
- the target application with the highest frequency has the largest screen area, and the target application with the lowest click frequency has the smallest screen area.
- the arrangement of the multiple screen areas may be the same as or different from the arrangement order of the multiple target applications displayed on the display interface, which is not specifically limited here.
- the display mode of the target application can be a floating control mode.
- the target application that supports multi-window mode can be displayed using a floating control, while the display mode of other target applications that receive gesture touch operations but do not support multi-window mode remains unchanged, that is, for target applications that do not support multi-window mode, they are still only displayed as small icons on the display interface of the terminal.
- a prompt message can be provided at any position for the target application that does not support multi-window mode to indicate that the support status of the target application is that multi-window mode is not supported.
- the prompt message can be a text mark, an image mark, etc., which is not specifically limited here.
- the size of the floating control and the size of the screen area must be determined, so stacking and setting the stack boundary are required.
- the size of each Task in it is controlled by setting the stack boundary, and the size of the Task ultimately determines the size of the window.
- the stack boundary is represented by Rect(left, top, right, bottom), which stores four values, representing the positions of the four sides of the rectangle from the coordinate axis.
- the size of the window displayed on the screen is ultimately determined by the size of the Stack boundary.
- a plurality of applications are displayed on the display interface, for example, application 601, application 602, and application 603.
- the gesture manager detects a gesture touch operation acting on application 601 and application 602, the target applications can be considered to be application 601 and application 602.
- the attribute information of application 601 and application 602 are both first identifiers, it can be considered that the support status of both is to support multi-window mode, and application 601 and application 602 can open the multi-window mode in a split-screen manner to display the applications.
- the detailed content of application 601 is displayed in screen area 604, and the detailed content of application 602 is displayed in screen area 605.
- the sizes of screen area 604 and screen area 605 can be the same or different, and are not specifically limited here.
- a plurality of applications are displayed on the display interface, for example, application 701, application 702, and application 703.
- the gesture manager detects a gesture touch operation acting on application 701 and application 702
- the target applications can be considered to be application 701 and application 702.
- the attribute information of application 701 is a first identifier
- the attribute information of application 702 is a second identifier
- it can be considered that the support status of application 701 is to support multi-window mode
- the support status of application 702 is not to support multi-window mode. Therefore, it can be considered that the number of target applications that support multi-window mode among the multiple target applications is one, and based on this, the display method of the target application can be a floating control method.
- a floating control 704 can be provided, and the target application 701 that supports multi-window mode can be displayed using the floating control 704, while the display mode of other applications 702 that receive gesture touch operations but do not support multi-window mode remains unchanged, that is, for the target application 702 that does not support multi-window mode, it is still only displayed as a small icon on the display interface of the terminal.
- a prompt message 705 may be provided for the application 702 that does not support the multi-window mode to remind the user of the support status corresponding to the target application that receives the gesture touch operation but does not support the multi-window mode.
- the target application after receiving a gesture touch operation on a target application, when the target application supports the multi-window mode, the target application can be switched to the multi-window mode to display the target application, thereby avoiding the cumbersome operation of clicking a window through a sidebar or clicking a window from a multi-task card in the related art, reducing the operation steps, and improving the efficiency of switching to the multi-window mode.
- it since it is achieved through a gesture touch operation on the target application, it avoids the problem of requiring multiple steps to display multiple windows, thereby improving convenience.
- FIG8 schematically shows a flow chart of switching to the multi-window mode.
- the flow chart mainly includes the following steps:
- step S810 enter the desktop application.
- step S820 the application is controlled through a gesture touch operation.
- the touch gesture operation may include but is not limited to a swipe up operation, or may be other types of touch operations, which are determined according to actual needs.
- step S830 it is determined whether the gesture touch operation is successful. If so, the process goes to step S840; if not, the process goes to step S860.
- the gesture manager can be used to determine whether a gesture touch operation is successful based on the type and direction of the received gesture touch operation. For example, when the position of the starting touch point is at the position of the application icon, and the starting touch point is different from the ending touch point, it can be considered that a sliding operation is detected, and the direction of the sliding operation can be further determined based on the positional relationship between the starting touch point and the ending touch point. For example, if the gesture touch operation is an upward sliding operation, when the direction of the sliding operation is determined to be from bottom to top, the gesture touch operation can be considered successful. If the positional relationship between the starting touch point and the ending touch point does not meet the touch condition or the position of the starting touch point and the ending touch point itself does not meet the touch condition, the gesture touch operation can be considered to have failed.
- step S840 it is determined whether the target application supports the multi-window mode. If yes, the process goes to step S850; if no, the process goes to step S860.
- the activity manager can detect whether the application supports the multi-window mode by using the attribute information android:resizeableActivity to determine whether the application supports the multi-window mode. If the first identifier is true, the application is considered to support the multi-window mode. If the attribute information is false, the application is considered not to support the multi-window mode.
- step S850 enter the multi-window mode.
- the target application when a user swipes up on an application icon and the gesture management successfully detects the gesture, if the target application supports multi-window mode, the target application is started as a floating control.
- the activity manager determines the support status of the two applications through attribute information, and can determine the display mode according to the support status of each application, thereby displaying each target application based on the display mode, specifically including the following situations:
- both target applications support multi-window mode
- the two target applications are started in split-screen mode through the activity manager; 2. If only one target application supports multi-window mode, the target application is displayed in a floating window, and a prompt message is provided on the display interface to prompt the user that the other target application does not support multi-window mode; 3. If both target applications do not support multi-window mode, a prompt message is provided to remind the user that the target application does not support multi-window mode, and the display mode of the target application is kept unchanged without performing any other actions.
- step S860 the display mode is kept unchanged.
- a prompt message is provided to the target application to remind the user that the target application does not support multi-window mode display such as floating windows.
- the original display mode of the target application can be kept unchanged without opening the target application in multi-window mode.
- the technical solution provided in the embodiment of the present disclosure determines whether to open the target application through the multi-window mode through the gesture touch operation acting on the target application and the support status of the target application.
- the target application can be displayed using the multi-window mode according to the support status of the target application, thereby switching to the multi-window mode.
- only one gesture touch operation is required, which reduces the operation steps of switching to the multi-window mode, reduces the difficulty of operation, and improves the operation efficiency.
- the multi-window mode can be switched directly to the target application displayed in the terminal by performing a gesture touch operation, compared with the related art, the object to be executed can be quickly determined, which improves the convenience and operability of opening the multi-window mode.
- any terminal can switch to the multi-window mode through a gesture touch operation acting on the target application to realize the opening of the target application, the scope of application is increased and the versatility is improved.
- the multi-window switching device 900 may include:
- a touch operation detection module 901 is used to detect a gesture touch operation acting on a target application in the terminal, and determine a support status of the target application for the multi-window mode;
- the multi-window mode enabling module 902 is configured to display the target application in the multi-window mode if the target application is in a support state of supporting the multi-window mode.
- the touch operation detection module includes: a detection control module for detecting The gesture manager determines that the position information of the starting touch point and the ending touch point of the gesture touch operation meets the touch condition, and determines to detect the gesture touch operation acting on the target application.
- the touch operation detection module includes: a first state determination module, which is used to determine, based on the activity manager, that the attribute information of the target application is a first identifier, and determine that the support state of the target application is to support the multi-window mode; and a second state determination module, which is used to determine, based on the activity manager, that the attribute information of the target application is a second identifier, and determine that the support state of the target application is to not support the multi-window mode.
- the number of target applications is one;
- the multi-window mode activation module includes: a floating control display module, which is used to switch the target application to multi-window mode for display using a floating control when the support state is to support multi-window mode.
- the number of the target applications is multiple;
- the multi-window mode activation module includes: a display method determination module, which is used to determine the display method of multiple target applications based on the support status of each target application, and switch the multiple target applications to multi-window mode for display through the display method.
- a display method determination module includes: a first display module, which is used to display multiple target applications in a split-screen manner if there are multiple target applications whose support status is to support multi-window mode; and a second display module, which is used to display one target application in a floating control manner if there is a target application whose support status is to support multi-window mode.
- the device also includes: a display mode maintaining module, which is used to keep the display mode of the target application unchanged if the support status of the target application is not to support the multi-window mode, and provide prompt information for the target application to display the support status.
- a display mode maintaining module which is used to keep the display mode of the target application unchanged if the support status of the target application is not to support the multi-window mode, and provide prompt information for the target application to display the support status.
- the exemplary embodiments of the present disclosure also provide an electronic device.
- the electronic device may be the above-mentioned terminal 220.
- the electronic device may include a processor and a memory, the memory is used to store executable instructions of the processor, and the processor is configured to execute the above-mentioned method by executing the executable instructions.
- the mobile terminal 1000 may specifically include: a processor 1001, a memory 1002, a bus 1003, a mobile communication module 1004, an antenna 1, a wireless communication module 1005, an antenna 2, a display screen 1006, a camera module 1007, an audio module 1008, a power module 1009 and a sensor module 1010.
- the processor 1001 may include one or more processing units.
- the processor 1001 may include an AP (Application Processor), a modem processor, a GPU (Graphics Processing Unit), ISP (Image Signal Processor), controller, encoder, decoder, DSP (Digital Signal Processor), baseband processor and/or NPU (Neural-Network Processing Unit), etc.
- the method in this exemplary embodiment can be executed by AP, GPU or DSP.
- NPU can load neural network parameters and execute neural network-related algorithm instructions.
- the encoder can encode (i.e. compress) an image or video to reduce the data size for easy storage or transmission.
- the decoder can decode (i.e. decompress) the encoded data of the image or video to restore the image or video data.
- the mobile terminal 1000 can support one or more encoders and decoders, for example: image formats such as JPEG (Joint Photographic Experts Group), PNG (Portable Network Graphics), BMP (Bitmap), and video formats such as MPEG (Moving Picture Experts Group) 1, MPEG10, H.1063, H.1064, and HEVC (High Efficiency Video Coding).
- the processor 1001 may be connected to the memory 1002 or other components via a bus 1003 .
- the memory 1002 may be used to store computer executable program codes, which may include instructions.
- the processor 1001 executes various functional applications and data processing of the mobile terminal 1000 by running the instructions stored in the memory 1002.
- the memory 1002 may also store application data, such as images, videos, and other files.
- the communication function of the mobile terminal 1000 can be implemented by the mobile communication module 1004, antenna 1, wireless communication module 1005, antenna 2, modulation and demodulation processor and baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.
- the mobile communication module 1004 can provide 3G, 4G, 5G and other mobile communication solutions applied to the mobile terminal 1000.
- the wireless communication module 1005 can provide wireless communication solutions such as wireless LAN, Bluetooth, near field communication, etc. applied to the mobile terminal 1000.
- the display screen 1006 is used to implement display functions, such as displaying user interfaces, images, videos, etc.
- the camera module 1007 is used to implement shooting functions, such as shooting images, videos, etc., and the camera module may include a color temperature sensor array.
- the audio module 1008 is used to implement audio functions, such as playing audio, collecting voice, etc.
- the power module 1009 is used to implement power management functions, such as charging the battery, powering the device, monitoring the battery status, etc.
- the sensor module 1010 may include one or more sensors for implementing corresponding sensing detection functions.
- the sensor module 1010 may include an inertial sensor, which is used to detect the motion posture of the mobile terminal 1000 and output inertial sensing data.
- a computer-readable storage medium is also provided in an embodiment of the present disclosure.
- the computer-readable storage medium may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device.
- the computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples of computer readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory, or a computer program product. (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
- computer readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
- Computer-readable storage media can send, propagate or transmit programs for use by or in conjunction with an instruction execution system, apparatus or device.
- the program code contained on the computer-readable storage medium can be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
- the computer-readable storage medium carries one or more programs.
- the electronic device implements the method described in the following embodiments.
- the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.
- a non-volatile storage medium which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.
- a computing device which can be a personal computer, a server, a terminal device, or a network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
本公开实施例是关于一种多窗口切换方法及装置、电子设备、存储介质，涉及计算机技术领域，该多窗口切换方法包括：检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态；若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。本公开实施例中的技术方案，能够提高利用多窗口模式开启目标应用的操作效率和便捷性。
Description
优先权信息
本申请要求2022年11月23日提交的中国申请号202211477846.5的优先权，全部内容通过引用并入本文。
本公开涉及计算机技术领域，具体而言，涉及一种多窗口切换方法及装置、电子设备以及计算机可读存储介质。
在终端的使用过程中，可以将终端中的多个应用通过多窗口模式进行显示。
相关技术中，可以通过点击侧边栏中的某个应用进入多窗口，或者是通过多任务卡片中的悬浮按钮进入多窗口。上述步骤中，需要多个步骤才可以显示多窗口，并且开启多窗口的入口隐藏比较深，操作步骤较繁琐，且便利性较低，通用性较差。
需要说明的是，在上述背景技术部分公开的信息仅用于加强对本公开的背景的理解，因此可以包括不构成对本领域普通技术人员已知的现有技术的信息。
发明内容
本公开的目的在于提供一种多窗口切换方法及装置、电子设备、存储介质，进而至少在一定程度上克服由于相关技术的限制和缺陷而导致的切换多窗口模式的步骤较多的问题。
本公开的其他特性和优点将通过下面的详细描述变得显然，或部分地通过本公开的实践而习得。
根据本公开的第一方面，提供一种多窗口切换方法，包括：检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态；若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。
根据本公开的第二方面，提供一种多窗口切换装置，包括：触控操作检测模块，用于检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态；多窗口模式开启模块，用于若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。
根据本公开的第三方面，提供一种电子设备，包括：处理器；以及存储器，用于存储所述处理器的可执行指令；其中，所述处理器配置为经由执行所述可执行指令来执行上述第一
方面的多窗口切换方法及其可能的实现方式。
根据本公开的第四方面，提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述第一方面的多窗口切换方法及其可能的实现方式。
本公开实施例中提供的技术方案，一方面，由于可以在检测到作用在目标应用的手势触控操作的情况下，根据目标应用的支持状态，使用多窗口模式对目标应用进行展示，从而切换至多窗口模式。相比于相关技术中需要多个步骤进行多窗口切换的过程而言，只需要进行一次手势触控操作，减少了切换至多窗口模式的操作步骤，降低了操作难度，且提高了对应用开启多窗口模式的操作效率。另一方面，由于可以直接对终端中显示的目标应用执行手势触控操作来切换多窗口模式，相比于相关技术而言，能够快速确定要执行的对象，提高了便捷性和可操作性。再一方面，由于对任何终端都可以通过作用在目标应用上的手势触控操作来切换至多窗口模式，增加了应用范围，提高了通用性。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了相关技术中进入多窗口模式的示意图。
图2示出了可以应用本公开实施例的多窗口切换方法及多窗口切换方法的应用场景的示意图。
图3示意性示出本公开实施例一种多窗口切换方法的示意图。
图4示意性示出本公开实施例中对一个目标应用开启多窗口模式的示意图。
图5示意性示出本公开实施例中***架构的示意图。
图6示意性示出本公开实施例中对多个目标应用开启多窗口模式的第一种示意图。
图7示意性示出本公开实施例中对多个目标应用开启多窗口模式的第二种示意图。
图8示意性示出本公开实施例的开启多窗口模式的流程示意图。
图9示意性示出本公开实施例中一种多窗口切换装置的框图。
图10示意性示出本公开实施例中电子设备的框图。
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施方式使得本公开将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施方式中。在下面的描述中，提供许多具体细节从而给出对本公开的实施方式的充分理解。然而，本领域技术人员将意识到，可以实践本公开的技术方案而省略所述特定细节中的一个或更多，或者可以采用其它的方法、组元、装置、步骤等。在其它情况下，不详细示出或描述公知技术方案以避免喧宾夺主而使得本公开的各方面变得模糊。
此外，附图仅为本公开的示意性图解，并非一定是按比例绘制。图中相同的附图标记表示相同或类似的部分，因而将省略对它们的重复描述。附图中所示的一些方框图是功能实体，不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
相关技术中，参考图1中所示，可以通过以下两种方式来切换多窗口：参考图1中的图A所示的方式一，从侧边栏点击进入多窗口并显示多窗口的步骤包括：划出侧边栏；点击侧边栏想要显示的应用；以悬浮框显示该应用。参考图1中的图B所示的方式二，从多任务卡片进入多窗口并显示多窗口的步骤包括：进入多任务；点击某个卡片的右上角的悬浮按钮；以悬浮框方式显示该应用。
上述方式中，需要用户执行多个操作步骤才能切换至多窗口模式；并且，切换至多窗口模式的操作不是很方便，便利性较差。除此之外，不同布局需要采用不同的方式来切换，因此通用性较差。
为了解决相关技术中的技术问题，本公开实施例中提供了一种多窗口切换方法，可以应用于对终端中的任意应用开启多窗口模式的应用场景中。图2示出了可以应用本公开实施例的多窗口切换方法及装置的***架构的示意图。
如图2所示，该***架构可以包括：用户210以及终端220。终端220可以为任何类型设备，例如可以为计算机、智能手机、智能电视、平板电脑、智能可穿戴设备(如AR眼镜)、机器人、无人机等设备。用户210可以使用终端220执行各种操作。终端中可以安装各种类型的应用程序，以便于用户对应用程序执行对应操作从而进入多窗口模式。
需要说明的是，本公开实施例所提供的多窗口切换方法可以由终端220执行。
图3中示意性示出了本公开实施例中的多窗口切换方法，具体包括以下步骤：
步骤S310，检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态；
步骤S320，若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。
本公开实施例中，目标应用可以为终端中的任意一个应用程序。手势触控操作可以为上滑操作。如果检测到作用在终端中的目标应用上的手势触控操作，可以确定目标应用的支持状态，以确定目标应用是否支持多窗口模式。支持状态用于表示目标应用是否支持多窗口模式。进一步可以根据目标应用的支持状态，利用多窗口模式开启目标应用以对目标应用进行展示，例如以悬浮控件方式或者是分屏方式开启多窗口模式对目标应用进行展示。
上述技术方案中，一方面，由于可以在检测到作用在目标应用的手势触控操作的情况下，根据目标应用的支持状态，使用多窗口模式对目标应用进行展示，从而切换至多窗口模式。相比于相关技术中需要多个步骤进行多窗口切换的过程而言，只需要进行一次手势触控操作，减少了切换至多窗口模式的操作步骤，降低了操作难度，且提高了对应用开启多窗口模式的操作效率。另一方面，由于可以直接对终端中显示的目标应用执行手势触控操作来切换多窗口模式，相比于相关技术而言，能够快速确定要执行的对象，提高了便捷性和可操作性。再一方面，由于对任何终端都可以通过作用在目标应用上的手势触控操作来切换至多窗口模式，增加了应用范围，提高了通用性。
接下来，参考图3所示，对本公开实施例中的多窗口切换方法的具体步骤进行详细说明。
在步骤S310中，若检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态。
本公开实施例中，终端可以为任意类型的能够进行安装应用程序以及对应用程序执行对应操作的设备。例如，终端可以为智能手机、平板电脑、智能电视、可穿戴设备、门禁设备等智能设备；除此之外，还可以包含智能车载设备，例如汽车的智能座舱娱乐***等等；此处以终端为智能手机为例进行说明。
终端中可以安装各种类型的应用程序，应用程序可以为终端本身的应用程序，也可以为第三方提供的应用程序，例如游戏类应用程序、视频类应用程序以及社交类应用程序，此处不作具体限定。目标应用可以为应用程序中的任意一个或多个，即目标应用可以为一个应用程序，也可以为多个应用程序。应用程序可以显示在终端的显示界面中，显示界面中可以包括依次排列的多个应用程序对应的图标。例如参考图4中所示，可以在终端的显示界面400上依次显示应用401、应用402以及应用403。参考图6中所示，可以在终端的显示界面600上依次显示应用601、应用602以及应用603。
手势触控操作可以为由用户执行且作用在某一个应用程序上的触控操作，用于控制用户选择的应用程序切换至多窗口模式或者是开启多窗口模式。手势触控操作可以为任意类型的触控操作，例如可以为滑动操作或者是滑动按压操作等等，也可以为隔空手势或者是其它任
意类型的手势，此处以手势触控操作为向上滑动为例进行说明。
图5中示意性示出了终端的***架构的示意图，参考图5中所示，终端中可以包含内核层501、***层502、应用程序框架层503以及应用程序层504。
其中，内核层501可以包括显示驱动、摄像头驱动、音频驱动以及传感器驱动。***层502可以包括表面管理器、三维图形处理库、二维图形引擎、媒体库以及安卓运行时。应用程序框架层503可以包括窗口管理器、内容管理器、电话管理器、手势管理器、活动管理器、视图管理器以及资源管理器等。应用程序层504可以包括相机、日历、SystemUI里的wmShell、设置、桌面、图库、通知、导航、蓝牙、视频等等。
其中，窗口管理器负责多窗口模式下的窗口层级管理以及窗口的位置。activity活动管理器负责activity栈的管理，以及窗口的尺寸size管理、configuration管理等。手势管理器用于负责触发窗口上划手势等动作。SystemUI里的wmShell模块负责多窗口的显示。设置模块负责手势的动态设置开关。
基于上述架构，应用程序框架层503的手势管理器可以用于负责触发窗口上滑等手势动作。基于此，可以基于手势管理器检测作用于目标应用上的操作，以确定目标应用是否接收到手势触控操作。具体地，手势管理器可先检测是否接收到作用于目标应用上的操作，进一步可以根据操作的起始触控点以及结束触控点的位置以及不同触控点之间的位置关系，判断接收到的手势触控操作是否满足触控条件以判断是否为开启多窗口模式的手势触控操作。触控条件可以根据实际需求进行设置，例如可以为起始触控点和结束触控点的位置不同，且起始触控点的纵坐标小于结束触控点的纵坐标。示例性地，当起始触控点的位置处于目标应用的图标的位置，且起始触控点与结束触控点不同时，可认为检测到滑动操作，进一步可以根据起始触控点和结束触控点之间的位置关系来确定滑动操作的方向。例如，若手势触控操作为上滑操作，当确定滑动操作的方向为从下向上时，可认为手势触控操作成功。本公开实施例中，对手势触控操作的轨迹长度不作具体限定，只要其属于上滑操作即可。
其中，目标应用的数量可以为一个或者是多个，具体根据实际需求进行确定。例如，可以只检测是否接收到作用于一个目标应用上的手势触控操作，也可以检测是否接收到作用于多个目标应用上的手势触控操作。并且，作用于不同目标应用的手势触控操作可以相同或不同。
在一些实施例中，可以根据终端的显示状态确定作用于目标应用的手势触控操作。显示状态可以为显示界面上包括的应用程序的数量，也可以为其他信息。若终端的显示状态满足显示条件，手势触控操作为向上的滑动操作；若显示状态不满足显示条件，手势触控操作可以为其他触控操作，例如按压滑动操作等等。当显示界面上的应用程序的数量小于数量阈值时，可认为显示状态满足显示条件。数量阈值可以为六个或者是十个等等。
举例而言，参考图4中所示，可认为检测到作用于目标应用401的手势触控操作；参考图6中所示，也可以认为检测到作用于目标应用601以及目标应用602的手势触控操作。
在检测到作用于目标应用上的手势触控操作的情况下，可以继续确定目标应用的针对于多窗口模式的支持状态，即支持状态用于表示目标应用是否支持多窗口模式。对于不同的应用程序，由于其本身的应用属性，支持状态可能相同或不同。并且，每个应用程序的支持状态是根据其自身的应用属性事先设置的。多窗口模式指的是在多个场景中显示目标应用的模式。多窗口模式可以包括但不限于悬浮窗口模式、分屏模式以及画中画模式等等，此处以悬浮窗口模式以及分屏模式为例进行说明。其中，悬浮窗口模式指的是在显示界面上通过浮层的方式显示接收到手势触控操作的目标应用。分屏模式指的是将显示界面划分为多个屏幕区域，以通过多个屏幕区域显示接收到手势触控操作的目标应用。
基于图5中所示的终端的架构，可以利用应用程序框架层503的活动管理器，通过目标应用的属性信息来确定目标应用的支持状态。示例性地，可以通过属性信息为第一标识还是第二标识来确定目标应用的支持状态是否为支持多窗口模式。属性信息可以用android:resizeableActivity来表示。第一标识可以为用于表示正确值的true，第二标识可以为用于表示错误值的false。
当利用活动管理器确定目标应用的属性信息为第一标识时，可以认为该目标应用支持多窗口模式，即支持使用悬浮窗口或者是使用分屏模式显示。当利用活动管理器确定目标应用的属性信息为第二标识时，可以认为该目标应用不支持多窗口模式，即该目标应用不支持使用悬浮窗口或者是不支持使用分屏模式显示。
接下来，在步骤S320中，若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。
本公开实施例中，在得到目标应用的支持状态之后，可以根据目标应用的支持状态，选择不同的方式对目标应用进行展示。示例性地，如果目标应用的支持状态为支持多窗口模式，则可以通过多窗口模式开启目标应用以对目标应用进行展示，即将目标应用切换为多窗口模式以进行展示。如果目标应用的支持状态为不支持多窗口模式，可以保持目标应用的展示模式不变，并提供用于展示目标应用针对于多窗口模式的支持状态的提示信息。
在一些实施例中，由于手势触控操作可以作用于每一个应用程序上，因此目标应用的数量可以为一个或者是多个，目标应用的数量具体可根据实际需求进行确定。并且，目标应用的数量不同，通过多窗口模式对目标应用进行展示的展示方式也不同。对目标应用进行展示的展示方式可以包括悬浮控件方式(悬浮窗口)以及分屏方式，除此之外还可以包括画中画模式或者是其他模式等等。
例如，当目标应用的数量为一个时，可以使用悬浮控件方式将目标应用切换为多窗口模
式进行展示；当目标应用的数量为多个时，可以使用悬浮控件方式或分屏方式将多个目标应用切换为多窗口模式进行展示。
在一些实施例中，在目标应用的数量为一个的情况下，如果检测到作用于目标应用的手势触控操作，且确定目标应用的支持状态为支持多窗口模式，可以利用悬浮控件方式将目标应用切换为多窗口模式，以通过多窗口模式对目标应用进行展示。即。利用悬浮控件开启目标应用的多窗口模式。悬浮控件可以位于显示界面的最上层，即位于显示界面之上的图层。悬浮控件可以为一个悬浮窗口，可以位于显示界面的任意合适的位置，悬浮控件中可以显示接收到手势触控操作的目标应用的详细内容。悬浮控件的大小可以根据默认参数确定，也可以自定义调整，此处不作限定。
参考图4中所示，显示界面上显示多个应用程序，若手势管理器检测到作用于目标应用401的手势触控操作，且活动管理器通过属性信息android:resizeableActivity为true确定目标应用401的支持状态为支持多窗口模式。在此基础上，参考图4中所示，通过活动管理器以悬浮窗口的模式启动该目标应用，可以在显示界面上的任意位置处提供一个悬浮控件404，并在悬浮控件404中显示目标应用401的详细内容，以通过悬浮窗口对目标应用的详细内容进行展示。
在一些实施例中，在目标应用的数量为多个的情况下，如果检测到作用于多个目标应用的手势触控操作，可根据每个目标应用的支持状态来确定每个目标应用的展示方式，从而确定出多个目标应用的展示方式，进而通过展示方式将多个目标应用切换为多窗口模式进行展示。示例性地，可以根据支持状态为支持多窗口模式的目标应用的数量来确定展示方式。例如，当多个目标应用中支持多窗口模式的目标应用的数量为多个时，展示方式可以为分屏方式；其中，支持多窗口模式的目标应用可以为接收到手势触控操作的目标应用中的所有应用，也可以为其中的一部分应用。
举例而言，接收到手势触控操作的目标应用的数量可以为4个，在支持多窗口模式的目标应用的数量为多个时，该数量可以为2个、3个或4个，具体可利用活动管理器基于每个应用的属性信息的数值而确定。
当多个目标应用中支持多窗口模式的目标应用的数量为多个时，可以对每个目标应用使用分屏方式进行展示。示例性地，可以根据支持多窗口模式的目标应用的数量将终端的显示界面划分为多个屏幕区域，以通过每个屏幕区域独立展示每个目标应用。多个屏幕区域的大小可以相同，也可以不同，具体可以根据实际需求进行确定。当多个屏幕区域的大小相同时，每个屏幕区域的长度和宽度可以根据显示界面的大小而确定。当多个屏幕区域的大小不同时，可以根据每个目标应用的应用信息确定屏幕区域的大小。应用信息可以为目标应用的占用内存、点击频率等等。并且，屏幕区域的大小与目标应用的应用信息的大小正相关，例如点击
频率最高的目标应用的屏幕区域最大，点击频率最低的目标应用的屏幕区域最小。多个屏幕区域的排列方式可以与显示界面上展示的多个目标应用的排列顺序相同，也可以不同，此处不作具体限定。
在一些实施例中，当多个目标应用中支持多窗口模式的目标应用的数量为一个时，该目标应用的展示方式可以为悬浮控件方式。示例性地，可以将该支持多窗口模式的目标应用使用悬浮控件的方式进行展示，而将其他接收到手势触控操作但是不支持多窗口模式的目标应用的展示模式的保持不变，即对于不支持多窗口模式的目标应用而言，依然只在终端的显示界面上以小图标的方式进行展示即可。与此同时，可以在任意位置处对不支持多窗口模式的目标应用提供一个提示信息，以用于表示目标应用的支持状态为不支持多窗口模式。提示信息可以为文字标识，也可以为图像标识等等，此处不作具体限定。
需要补充的是，在切换为多窗口模式时，无论是通过悬浮控件还是分屏方式展示目标应用，均需要确定悬浮控件的大小以及屏幕区域的大小，因此需要进行分栈和设置栈边界。在多窗口模式中，通过设置栈的边界来控制里面每个Task的大小，最终Task的大小决定了窗口的大小。栈边界通过Rect(left,top,right,bottom)来表示，存储了四个值，分别表示矩形的4条边离坐标轴的位置，最终显示在屏幕上窗口的大小是根据Stack(栈)边界的大小来决定的。
参考图6中所示，显示界面上显示多个应用，例如应用601、应用602以及应用603。如果手势管理器检测到作用于应用601以及应用602的手势触控操作，则可以认为目标应用为应用601以及应用602。如果应用601和应用602的属性信息均为第一标识，可以认为二者的支持状态均为支持多窗口模式，则应用601和应用602可以通过分屏方式开启多窗口模式以对应用进行展示。例如图6中所示，屏幕区域604中显示应用601的详细内容，屏幕区域605中显示应用602的详细内容。其中，屏幕区域604和屏幕区域605的大小可以相同，也可以不同，此处不作具体限定。
参考图7中所示，显示界面上显示多个应用，例如应用701、应用702以及应用703。如果手势管理器检测到作用于应用701、应用702的手势触控操作，则可以认为目标应用为应用701以及应用702。如果应用701的属性信息为第一标识，应用702的属性信息为第二标识，此时可以认为应用701的支持状态为支持多窗口模式，应用702的支持状态为不支持多窗口模式。因此可以认为多个目标应用中支持多窗口模式的目标应用的数量为一个，基于此，该目标应用的展示方式可以为悬浮控件方式。示例性地，可以提供一个悬浮控件704，将该支持多窗口模式的目标应用701使用悬浮控件704的方式进行展示，而将其他接收到手势触控操作但是不支持多窗口模式的应用702的展示模式的保持不变，即对于不支持多窗口模式的目标应用702而言，依然只在终端的显示界面上以小图标的方式进行展示即可。除此
之外，还可以为不支持多窗口模式的应用702提供一个提示信息705，以用于提醒用户，该接收到手势触控操作但是不支持多窗口模式的目标应用对应的支持状态。
本公开实施例中，在接收到作用在目标应用上的手势触控操作后，可在目标应用针对于多窗口模式的支持状态为支持多窗口模式时，将目标应用切换为多窗口模式以对目标应用进行展示，避免了相关技术中通过侧边栏点击窗口或者是从多任务卡片中点击窗口的操作较繁琐的问题，减少了操作步骤，提高了切换至多窗口模式的效率。除此之外，由于是通过作用于目标应用上的手势触控操作来实现，避免了需要多步操作才能显示多窗口的问题，提高了便捷性。
图8中示意性示出了切换至多窗口模式的流程图，参考图8中所示，主要包括以下步骤：
在步骤S810中，进入桌面应用。
即，进入终端的用于呈现所有应用程序的显示界面。在显示界面中可以显示多个应用程序，所有的应用程序以小图标的形式进行排序展示。
在步骤S820中，通过手势触控操作控制应用。
本步骤中，检测作用于目标应用的手势触控操作。手势触控操作可以包括但不限于上滑操作，也可以为其他类型的触控操作，具体根据实际需求来进行确定。
在步骤S830中，判断手势触控操作是否成功。若是，转至步骤S840；若否，则转至步骤S860。
示例性地，可通过手势管理器，根据接收到的手势触控操作的类型以及的方向来确定手势触控操作是否成功。例如，当起始触控点的位置处于应用程序的图标的位置，且起始触控点与结束触控点不同时，可认为检测到滑动操作，进一步可以根据起始触控点和结束触控点之间的位置关系来确定滑动操作的方向。例如，若手势触控操作为上滑操作，当确定滑动操作的方向为从下向上时，可认为手势触控操作成功。如起始触控点与结束触控点之间的位置关系不满足触控条件或者是起始触控点与结束触控点的位置本身不满足触控条件，则可以认为手势触操作失败。
在步骤S840中，判断目标应用的支持状态是否为支持多窗口模式。若是，则转至步骤S850；若否，则转至步骤S860。
本步骤中，活动管理器可以利用属性信息android:resizeableActivity是否是第一标识来检测该应用是否支持多窗口模式。第一标识为true则认为应用支持多窗口模式。若属性信息为第二标识false，则认为应用不支持多窗口模式。
在步骤S850中，进入多窗口模式。
本步骤中，可通过活动管理器以悬浮控件的方式或者是分屏方式启动支持多窗口模式的应用。其中，可以包括以下几种场景：
例如，在桌面界面下，当用户在某个应用图标上做上滑操作，且手势管理成功检测到该手势。如果该目标应用支持多窗口模式，则以悬浮控件的方式启动该目标应用。
在一些实施例中，在桌面界面下，当用户在某两个应用图标上进行上滑操作，且手势管理器成功检测到该手势。活动管理器通过属性信息确定两个应用的支持状态，可以根据每个应用的支持状态来确定展示方式，从而基于展示方式来对每个目标应用进行展示，具体包括以下几种情况：
一、如果两个目标应用都支持多窗口模式，则通过活动管理器以分屏方式启动两个目标应用；二、如果只有一个目标应用支持多窗口模式，则以浮窗方式显示该目标应用，并且在显示界面上提供一个提示信息，以便于提示用户另一个目标应用不支持多窗口模式；三、如果两个目标应用均不支持多窗口模式，则提供一个提示信息，以提醒用户目标应用的不支持多窗口模式，并且保持目标应用的显示模式不变，不进行任何类型的其他动作。
在步骤S860中，保持展示模式不变。
本步骤中，如果根据活动管理器确定目标应用的属性信息android:resizeableActivity为第二标识false，则为目标应用提供一个提示信息以提醒用户该目标应用不支持悬浮窗等多窗口模式显示，此时可以保持目标应用原本的展示模式不变，而无需通过多窗口模式开启目标应用。
本公开实施例中提供的技术方案，通过作用在目标应用的手势触控操作以及目标应用的支持状态来确定是否通过多窗口模式开启目标应用，一方面，由于可以在检测到作用在目标应用的手势触控操作的情况下，根据目标应用的支持状态，使用多窗口模式对目标应用进行展示，从而切换至多窗口模式。相比于相关技术中需要多个步骤进行多窗口切换的过程而言，只需要进行一次手势触控操作，减少了切换至多窗口模式的操作步骤，降低了操作难度，且提高了操作效率。另一方面，由于可以直接对终端中显示的目标应用执行手势触控操作来切换多窗口模式，相比于相关技术而言，能够快速确定要执行的对象，提高了开启多窗口模式的便捷性和可操作性。再一方面，由于对任何终端都可以通过作用在目标应用上的手势触控操作来切换至多窗口模式实现目标应用的开启，增加了应用范围，提高了通用性。
本公开实施例中提供了一种多窗口切换装置，参考图9中所示，该多窗口切换装置900可以包括：
触控操作检测模块901，用于检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态；
多窗口模式开启模块902，用于若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。
在本公开的一种示例性实施例中，触控操作检测模块包括：检测控制模块，用于基于手
势管理器确定手势触控操作的起始触控点以及结束触控点的位置信息满足触控条件，确定检测作用于所述目标应用上的手势触控操作。
在本公开的一种示例性实施例中，触控操作检测模块包括：第一状态确定模块，用于基于活动管理器确定所述目标应用的属性信息为第一标识，确定所述目标应用的支持状态为支持多窗口模式；第二状态确定模块，用于基于活动管理器确定所述目标应用的属性信息为第二标识，确定所述目标应用的支持状态为不支持多窗口模式。
在本公开的一种示例性实施例中，所述目标应用的数量为一个；多窗口模式开启模块包括：悬浮控件展示模块，用于在所述支持状态为支持多窗口模式的情况下，利用悬浮控件方式将所述目标应用切换为多窗口模式进行展示。
在本公开的一种示例性实施例中，所述目标应用的数量为多个；多窗口模式开启模块包括：展示方式确定模块，用于基于每个目标应用的支持状态确定多个目标应用的展示方式，并通过所述展示方式对所述多个目标应用切换为多窗口模式进行展示。
在本公开的一种示例性实施例中，展示方式确定模块包括：第一展示模块，用于若存在多个目标应用的支持状态为支持多窗口模式，通过分屏方式对所述多个目标应用进行展示；第二展示模块，用于若存在一个目标应用的支持状态为支持多窗口模式，通过悬浮控件方式对所述目标应用进行展示。
在本公开的一种示例性实施例中，所述装置还包括：展示模式保持模块，用于若所述目标应用的支持状态为不支持多窗口模式，保持所述目标应用的展示模式不变，且对所述目标应用提供用于展示支持状态的提示信息。
需要说明的是，上述多窗口切换装置中各部分的具体细节在多窗口切换方法的部分实施方式中已经详细说明，未披露的细节内容可以参见方法部分的实施方式内容，因而不再赘述。
本公开的示例性实施方式还提供一种电子设备。该电子设备可以是上述终端220。一般的，该电子设备可以包括处理器与存储器，存储器用于存储处理器的可执行指令，处理器配置为经由执行可执行指令来执行上述方法。
下面以图10中的移动终端1000为例，对该电子设备的构造进行示例性说明。本领域技术人员应当理解，除了特别用于移动目的的部件之外，图10中的构造也能够应用于固定类型的设备。
如图10所示，移动终端1000具体可以包括：处理器1001、存储器1002、总线1003、移动通信模块1004、天线1、无线通信模块1005、天线2、显示屏1006、摄像模块1007、音频模块1008、电源模块1009与传感器模块1010。
处理器1001可以包括一个或多个处理单元，例如：处理器1001可以包括AP(Application Processor，应用处理器)、调制解调处理器、GPU(Graphics Processing Unit，图形处理器)、
ISP(Image Signal Processor，图像信号处理器)、控制器、编码器、解码器、DSP(Digital Signal Processor，数字信号处理器)、基带处理器和/或NPU(Neural-Network Processing Unit，神经网络处理器)等。本示例性实施方式中的方法可以由AP、GPU或DSP来执行，当方法涉及到神经网络相关的处理时，可以由NPU来执行，例如NPU可以加载神经网络参数并执行神经网络相关的算法指令。
编码器可以对图像或视频进行编码(即压缩)，以减小数据大小，便于存储或发送。解码器可以对图像或视频的编码数据进行解码(即解压缩)，以还原出图像或视频数据。移动终端1000可以支持一种或多种编码器和解码器，例如：JPEG(Joint Photographic Experts Group，联合图像专家组)、PNG(Portable Network Graphics，便携式网络图形)、BMP(Bitmap，位图)等图像格式，MPEG(Moving Picture Experts Group，动态图像专家组)1、MPEG10、H.1063、H.1064、HEVC(High Efficiency Video Coding，高效率视频编码)等视频格式。
处理器1001可以通过总线1003与存储器1002或其他部件形成连接。
存储器1002可以用于存储计算机可执行程序代码，可执行程序代码包括指令。处理器1001通过运行存储在存储器1002的指令，执行移动终端1000的各种功能应用以及数据处理。存储器1002还可以存储应用数据，例如存储图像，视频等文件。
移动终端1000的通信功能可以通过移动通信模块1004、天线1、无线通信模块1005、天线2、调制解调处理器以及基带处理器等实现。天线1和天线2用于发射和接收电磁波信号。移动通信模块1004可以提供应用在移动终端1000上3G、4G、5G等移动通信解决方案。无线通信模块1005可以提供应用在移动终端1000上的无线局域网、蓝牙、近场通信等无线通信解决方案。
显示屏1006用于实现显示功能，如显示用户界面、图像、视频等。摄像模块1007用于实现拍摄功能，如拍摄图像、视频等，且摄像模块中可以包含色温传感器阵列。音频模块1008用于实现音频功能，如播放音频，采集语音等。电源模块1009用于实现电源管理功能，如为电池充电、为设备供电、监测电池状态等。传感器模块1010可以包括一种或多种传感器，用于实现相应的感应检测功能。例如，传感器模块1010可以包括惯性传感器，其用于检测移动终端1000的运动位姿，输出惯性传感数据。
需要说明的是，本公开实施例中还提供了一种计算机可读存储介质，该计算机可读存储介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。
计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的***、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器
(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本公开中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行***、装置或者器件使用或者与其结合使用。
计算机可读存储介质可以发送、传播或者传输用于由指令执行***、装置或者器件使用或者与其结合使用的程序。计算机可读存储介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、RF等等，或者上述的任意合适的组合。
计算机可读存储介质承载有一个或者多个程序，当上述一个或者多个程序被一个该电子设备执行时，使得该电子设备实现如下述实施例中所述的方法。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本公开实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、终端装置、或者网络设备等)执行根据本公开实施方式的方法。
此外，上述附图仅是根据本公开示例性实施例的方法所包括的处理的示意性说明，而不是限制目的。易于理解，上述附图所示的处理并不表明或限制这些处理的时间顺序。另外，也易于理解，这些处理可以是例如在多个模块中同步或异步执行的。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本公开的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
本领域技术人员在考虑说明书及实践这里公开的内容后，将容易想到本公开的其他实施例。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由权利要求指出。应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限。
Claims (20)
- 一种多窗口切换方法，其特征在于，包括：检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态；若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。
- 根据权利要求1所述的多窗口切换方法，其特征在于，所述检测到作用在终端中目标应用上的手势触控操作，包括：基于手势管理器确定手势触控操作的起始触控点以及结束触控点的位置信息满足触控条件，确定检测作用于所述目标应用上的手势触控操作。
- 根据权利要求2所述的多窗口切换方法，其特征在于，所述触控条件为所述起始触控点和所述结束触控点的位置不同，且所述起始触控点的纵坐标小于所述结束触控点的纵坐标。
- 根据权利要求1所述的多窗口切换方法，其特征在于，所述检测到作用在终端中目标应用上的手势触控操作，包括：根据所述终端的显示状态确定作用于目标应用的手势触控操作。
- 根据权利要求4所述的多窗口切换方法，其特征在于，所述根据所述终端的显示状态确定作用于目标应用的手势触控操作，包括：若终端的所述显示状态满足显示条件，所述手势触控操作为向上的滑动操作；若所述显示状态不满足所述显示条件，所述手势触控操作为按压滑动操作。
- 根据权利要求1所述的多窗口切换方法，其特征在于，所述确定所述目标应用的针对于多窗口模式的支持状态，包括：基于活动管理器确定所述目标应用的属性信息为第一标识，确定所述目标应用的支持状态为支持多窗口模式；基于活动管理器确定所述目标应用的属性信息为第二标识，确定所述目标应用的支持状态为不支持多窗口模式。
- 根据权利要求6所述的多窗口切换方法，其特征在于，所述属性信息为android:resizeableActivity，所述第一标识为true，所述第二标识为false。
- 根据权利要求1所述的多窗口切换方法，其特征在于，所述目标应用的数量为一个；所述通过所述多窗口模式对所述目标应用进行展示，包括：在所述支持状态为支持多窗口模式的情况下，利用悬浮控件方式将所述目标应用切换为多窗口模式进行展示。
- 根据权利要求8所述的多窗口切换方法，其特征在于，所述悬浮控件中显示接收到所述手势触控操作的所述目标应用的详细内容。
- 根据权利要求1所述的多窗口切换方法，其特征在于，所述目标应用的数量为多个；所述通过所述多窗口模式对所述目标应用进行展示，包括：基于每个目标应用的支持状态确定多个目标应用的展示方式，并通过所述展示方式对所述多个目标应用切换为多窗口模式进行展示。
- 根据权利要求10所述的多窗口切换方法，其特征在于，所述基于每个目标应用的支持状态确定多个目标应用的展示方式，并通过所述展示方式对所述多个目标应用进行展示，包括：若存在多个目标应用的支持状态为支持多窗口模式，通过分屏方式对所述多个目标应用进行展示；若存在一个目标应用的支持状态为支持多窗口模式，通过悬浮控件方式对所述目标应用进行展示。
- 根据权利要求11所述的多窗口切换方法，其特征在于，所述通过分屏方式对所述多个目标应用进行展示，包括：根据支持多窗口模式的目标应用的数量将所述终端的显示界面划分为多个屏幕区域，以通过每个所述屏幕区域独立展示每个目标应用。
- 根据权利要求12所述的多窗口切换方法，其特征在于，所述方法还包括：根据每个所述目标应用的应用信息确定对应的屏幕区域的大小。
- 根据权利要求13所述的多窗口切换方法，其特征在于，所述屏幕区域的大小与对应的所述目标应用的应用信息的大小正相关，所述应用信息包括所述目标应用的点击频率。
- 根据权利要求1所述的多窗口切换方法，其特征在于，所述方法还包括：若所述目标应用的支持状态为不支持多窗口模式，保持所述目标应用的展示模式不变，且对所述目标应用提供用于展示支持状态的提示信息。
- 一种多窗口切换装置，其特征在于，包括：触控操作检测模块，用于检测到作用在终端中目标应用上的手势触控操作，确定所述目标应用的针对于多窗口模式的支持状态；多窗口模式开启模块，用于若所述目标应用的支持状态为支持多窗口模式，通过所述多窗口模式对所述目标应用进行展示。
- 根据权利要求16所述的多窗口切换装置，其特征在于，所述触控操作检测模块包括：检测控制模块，用于基于手势管理器确定所述手势触控操作的起始触控点以及结束触控点的位置信息满足触控条件，确定检测作用于所述目标应用上的手势触控操作。
- 根据权利要求16所述的多窗口切换装置，其特征在于，所述触控操作检测模块包括：第一状态确定模块和第二状态确定模块；所述第一状态确定模块用于基于活动管理器确定所述目标应用的属性信息为第一标识，确定所述目标应用的支持状态为支持多窗口模式；所述第二状态确定模块用于基于活动管理器确定所述目标应用的属性信息为第二标识，确定所述目标应用的支持状态为不支持多窗口模式。
- 一种电子设备，其特征在于，包括：处理器；以及存储器，用于存储所述处理器的可执行指令；其中，所述处理器配置为经由执行所述可执行指令来执行权利要求1-15任意一项所述的多窗口切换方法。
- 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1-15任意一项所述的多窗口切换方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211477846.5A CN118068993A (zh) | 2022-11-23 | 2022-11-23 | 多窗口切换方法及装置、电子设备、存储介质 |
| CN202211477846.5 | 2022-11-23 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024109286A1 true WO2024109286A1 (zh) | 2024-05-30 |
Family
ID=91095933
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2023/119188 WO2024109286A1 (zh) | 2022-11-23 | 2023-09-15 | 多窗口切换方法及装置、电子设备以及计算机可读存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN118068993A (zh) |
| WO (1) | WO2024109286A1 (zh) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104571844A (zh) * | 2013-10-28 | 2015-04-29 | 联想(北京)有限公司 | 一种信息处理方法及电子设备 |
| CN106919302A (zh) * | 2017-02-16 | 2017-07-04 | 北京小米移动软件有限公司 | 移动终端的操作控制方法及装置 |
| CN111625154A (zh) * | 2019-12-23 | 2020-09-04 | 蘑菇车联信息科技有限公司 | 一种应用显示方法及装置 |
| US20220050582A1 (en) * | 2018-09-10 | 2022-02-17 | Huawei Technologies Co., Ltd. | Method for quickly invoking small window when video is displayed in full screen, graphic user interface, and terminal |
| CN114168029A (zh) * | 2021-11-30 | 2022-03-11 | 深圳市鸿合创新信息技术有限责任公司 | 显示方法、装置、设备及介质 |
| CN114416227A (zh) * | 2021-11-16 | 2022-04-29 | 华为技术有限公司 | 窗口切换方法、电子设备及可读存储介质 |
-
2022
- 2022-11-23 CN CN202211477846.5A patent/CN118068993A/zh active Pending
-
2023
- 2023-09-15 WO PCT/CN2023/119188 patent/WO2024109286A1/zh unknown
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104571844A (zh) * | 2013-10-28 | 2015-04-29 | 联想(北京)有限公司 | 一种信息处理方法及电子设备 |
| CN106919302A (zh) * | 2017-02-16 | 2017-07-04 | 北京小米移动软件有限公司 | 移动终端的操作控制方法及装置 |
| US20220050582A1 (en) * | 2018-09-10 | 2022-02-17 | Huawei Technologies Co., Ltd. | Method for quickly invoking small window when video is displayed in full screen, graphic user interface, and terminal |
| CN111625154A (zh) * | 2019-12-23 | 2020-09-04 | 蘑菇车联信息科技有限公司 | 一种应用显示方法及装置 |
| CN114416227A (zh) * | 2021-11-16 | 2022-04-29 | 华为技术有限公司 | 窗口切换方法、电子设备及可读存储介质 |
| CN114168029A (zh) * | 2021-11-30 | 2022-03-11 | 深圳市鸿合创新信息技术有限责任公司 | 显示方法、装置、设备及介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN118068993A (zh) | 2024-05-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022022495A1 (zh) | 一种跨设备的对象拖拽方法及设备 | |
| AU2013204564B2 (en) | Method and apparatus for processing multiple inputs | |
| CN115097981B (zh) | 处理内容的方法及其电子设备 | |
| CN109089138B (zh) | 图像显示装置及操作其的方法 | |
| KR102221034B1 (ko) | 컨텐츠 표시 제어 방법 및 그 전자 장치 | |
| US11853543B2 (en) | Method and apparatus for controlling display of video call interface, storage medium and device | |
| KR102148001B1 (ko) | 디스플레이 장치 및 디스플레이 장치의 제어 방법 | |
| WO2019233280A1 (zh) | 用户界面显示方法、装置、终端及存储介质 | |
| EP2667629B1 (en) | Method and apparatus for multi-playing videos | |
| US20150363091A1 (en) | Electronic device and method of controlling same | |
| CN113014987A (zh) | 屏幕录制方法、装置、电子设备以及存储介质 | |
| CN114157889A (zh) | 一种显示设备及触控协助交互方法 | |
| CN110088719B (zh) | 移动设备的显示方法和移动设备 | |
| US9787746B2 (en) | Method and apparatus for processing multimedia content on a graphic cloud | |
| WO2024037563A1 (zh) | 内容展示方法、装置、设备及存储介质 | |
| WO2024109286A1 (zh) | 多窗口切换方法及装置、电子设备以及计算机可读存储介质 | |
| CN112926420B (zh) | 一种显示设备和菜单文字识别方法 | |
| CN116980554A (zh) | 一种显示设备及视频会议界面显示方法 | |
| CN114827708A (zh) | 视频播放方法、装置以及电子设备 | |
| CN115550717A (zh) | 一种显示设备及多指触控显示方法 | |
| CN109710359B (zh) | 动图显示方法、装置、计算机可读存储介质和终端 | |
| CN115390702A (zh) | 显示设备、触摸点定位方法及装置 | |
| CN115525182A (zh) | 电子设备及其虚拟键盘的手指活动区域调整方法 | |
| CN115712340A (zh) | 电子设备及人机交互方法 | |
| CN115185392A (zh) | 显示设备、图像处理方法及装置 |