Method and apparatus for switching views, device, and medium
By presenting multiple switching controls in the computer display area and responding to user interaction, the problem of inconvenience in view switching in the prior art is solved, and an efficient and user-friendly view switching experience is achieved.
Patent Information
- Application Number
- PCT/CN2024/128690
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-11-02
- Filing Date
- 2024-10-30
- Publication Date
- 2025-05-08
AI Technical Summary
The prior art is difficult to switch different views easily and quickly in the computer display area, especially when gesture complexity is high, affecting the user experience.
A number of switching controls are presented in the display area of the client device, each switching control corresponds to a view, switching the target view in response to user interaction.
It realizes that when multiple views are included, it can easily and quickly switch views through switching controls, improving the efficiency and user experience of view switching.
Smart Images

Figure CN2024128690_08052025_PF_FP_ABST
Abstract
Description
Method, apparatus, device and medium for switching views
[0001] This application claims priority to the Chinese invention patent application entitled “Method, apparatus, device and medium for switching views” filed on November 2, 2023, with application number 202311451824.6, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] Example implementations of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for switching views. Background Art
[0003] With the rapid development of computer technology, computers have become an indispensable tool in people's daily lives. Users typically place application icons, such as software icons or files, on the computer desktop and use the desktop to launch software or open files. Users can also use gestures, user interfaces, and other methods to display different content in the display area. In this context, it is desirable to switch between different content in the display area in a more convenient and efficient manner.
[0004] Summary of the Invention
[0005] In a first aspect of the present disclosure, a method for switching views is provided. In the method, a plurality of switch controls are presented in a display area of a client device, the plurality of switch controls corresponding to a plurality of views to be presented in the display area; and in response to receiving a first user interaction directed to a target switch control among the plurality of switch controls, a target view among the plurality of views corresponding to the target switch control is presented in the display area.
[0006] In a second aspect of the present disclosure, a device for switching views is provided. The device includes: a control rendering module configured to render multiple switch controls in a display area of a client device, the multiple switch controls corresponding to multiple views to be rendered in the display area; and a view rendering module configured to, in response to receiving a first user interaction directed to a target switch control among the multiple switch controls, render a target view corresponding to the target switch control among the multiple views in the display area.
[0007] In a third aspect of the present disclosure, an electronic device is provided. The electronic device includes: at least one processing unit; and at least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the electronic device to perform the method according to the first aspect of the present disclosure.
[0008] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the processor is enabled to implement the method according to the first aspect of the present disclosure.
[0009] It should be understood that the content described in this summary section is not intended to limit the key features or important features of the implementation of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easy to understand through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The above and other features, advantages and aspects of various implementations of the present disclosure will become more apparent hereinafter with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:
[0011] FIG1 illustrates a block diagram of an example environment in which implementations of the present disclosure can be implemented;
[0012] FIG2 illustrates a block diagram of a display area according to some implementations of the present disclosure;
[0013] FIG3 illustrates a block diagram of a desktop view according to some implementations of the present disclosure;
[0014] FIG4 illustrates a block diagram of a launch pad view according to some implementations of the present disclosure;
[0015] FIG5 illustrates a block diagram of a multitasking view according to some implementations of the present disclosure;
[0016] FIG6 illustrates a block diagram of a cross architecture according to some implementations of the present disclosure;
[0017] FIG7 illustrates a flowchart of a process for switching views according to some implementations of the present disclosure;
[0018] FIG8 shows a block diagram of an apparatus for switching views according to some implementations of the present disclosure; and
[0019] FIG9 illustrates a block diagram of an electronic device in which one or more implementations of the present disclosure may be implemented. DETAILED DESCRIPTION
[0020] The following describes implementations of the present disclosure in more detail with reference to the accompanying drawings. Although certain implementations of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the implementations described herein. Rather, these implementations are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and implementations of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.
[0021] In the description of the implementation of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "an implementation" or "the implementation" should be understood as "at least one implementation". The term "some implementations" should be understood as "at least some implementations". The following may also include other explicit and implicit definitions. As used herein, the term "model" can represent the association relationship between various data. For example, the above-mentioned association relationship can be obtained based on a variety of technical solutions currently known and / or to be developed in the future.
[0022] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) must comply with the requirements of relevant laws, regulations and relevant provisions.
[0023] It is understandable that before using the technical solutions disclosed in each implementation of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.
[0024] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.
[0025] As an optional but non-limiting implementation, in response to receiving a user's active request, a prompt message may be sent to the user, for example, in the form of a pop-up window, in which the prompt message may be presented in text form. Furthermore, the pop-up window may also include a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.
[0026] It is understandable that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.
[0027] As used herein, the term "in response to" refers to a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the timing of executing a subsequent action executed in response to the event or condition is not necessarily strongly correlated with the time when the event occurs or the condition is satisfied. For example, in some cases, a subsequent action may be executed immediately upon the occurrence of the event or the satisfaction of the condition; in other cases, the subsequent action may be executed some time after the occurrence of the event or the satisfaction of the condition.
[0028] Sample Environment
[0029] 1 shows a block diagram of an example environment 100 in which implementations of the present disclosure can be implemented. In this example environment 100, a client device 110 can present different content in its own display area 115, and a user 120 can operate the client device 110 through the client device 110 or a device attached to the client device 110 to present desired content in the display area 115.
[0030] In some implementations, at least one application may be installed in the client device 110. The user 120 may interact with the at least one application via the client device 110 and / or a device attached to the client device 110.
[0031] In some implementations, the client device 110 can be any type of mobile, fixed, or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a television receiver, a radio receiver, an e-book device, a gaming device, or any combination thereof, including accessories and peripherals thereof, or any combination thereof. In some implementations, the client device 120 can also support any type of interface for the user (such as "wearable" circuitry, etc.).
[0032] It should be understood that the structure and function of the various elements in the environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the present disclosure.
[0033] In response to a user's predetermined operation, client device 110 can present a view corresponding to the predetermined operation in display area 115. For example, it can present a corresponding view in response to a user gesture. However, client device 110 cannot reflect the view architecture of the view during the view switching process, nor can it closely integrate the gesture with the view architecture. Furthermore, the high complexity of the gesture affects the user experience. Therefore, how to quickly and conveniently implement view switching has become a difficult and hot topic in the field of computer technology.
[0034] Switching View Overview
[0035] In order to at least partially address the deficiencies in the prior art, according to an exemplary implementation of the present disclosure, a method for switching views is proposed. Some example implementations of the present disclosure will be described below with reference to the accompanying drawings. For ease of explanation, these example implementations will be described in conjunction with Figure 1. For ease of operation, different views can be presented in the display area. For example, a desktop view may include a predefined desktop, a launch pad view may include launch controls for installed applications, and a multitasking view may include management controls for managing and launching applications, and so on.
[0036] According to this solution, multiple switch controls corresponding to multiple views are presented in the display area 115 of the client device 110. Furthermore, upon receiving a user interaction with a target switch control among the multiple switch controls, the target view corresponding to the target switch control is presented in the display area 115. In this way, when multiple views are involved, view switching can be conveniently and quickly achieved using the switch controls, helping to improve the efficiency of view switching. Furthermore, switching views based on user interaction strengthens the connection between user interaction and view switching, thereby improving the user experience when switching views.
[0037] Detailed process of switching views
[0038] FIG2 shows a schematic diagram of a display area 115 according to some implementations of the present disclosure. The client device 110 can present multiple toggle controls (including a toggle control 202, a toggle control 204, and a toggle control 206) in the display area 115, and the multiple toggle controls correspond to multiple views to be presented in the display area 115. It will be understood that although only three toggle controls are shown in FIG2, the present disclosure does not limit the number of toggle controls. Alternatively and / or additionally, more or fewer toggle controls can be presented, and each toggle control can correspond to a view.
[0039] In some implementations, the client device 110 may directly present multiple toggle controls at any location in the display area 115. These multiple toggle controls may be centrally located in the same area of the display area 115 or dispersedly located in different areas of the display area 115. For example, the client device 110 may present some of the multiple toggle controls in the upper area of the display area 115 and present another portion of the multiple toggle controls in the left area of the display area 115.
[0040] In order to ensure the neatness of the display area 115, in some implementations, the client device 110 can present multiple switch controls in a specific area (also referred to as the first area) of the display area 115. The first area here can be located at the edge of the display area (the edge here can be any edge of the display area, such as the upper edge, lower edge, left edge and right edge, and the present disclosure is not limited to this), and the first area is always presented during the operation of the client device and is not blocked by the window of the application that has been started. As shown in Figure 2, the client device 110 can always present area 201, in which multiple switch controls are presented. In this way, it can be ensured that multiple switch controls are always presented in the display area 115, and the user can click on each switch control at any time to switch to the corresponding view.
[0041] In some implementations, the display area 115 also includes a taskbar display area 208. The client device 110 can present the application identifiers of the user's frequently used applications in the taskbar display area 208. The frequently used applications can be pre-set by the user or automatically determined by the client device 110 based on the user's historical application usage. In some implementations, the client device 110 can also present multiple toggle controls in the taskbar display area 208.
[0042] In some implementations, the display area 115 also includes a status bar display area. The status bar display area 209 can be used to present the status of the client device 110, such as the current time, network status, battery status, etc. In some implementations, the client device 110 can also present multiple toggle controls in the status bar display area.
[0043] Regarding the positional relationship between multiple toggle controls, in some implementations, the client device 110 may obtain a view architecture of multiple views and present the multiple toggle controls based on the positional relationship between the multiple views represented by the view architecture. The view architecture may be pre-set by the user of the client device 110 or may be a default setting of the client device 110.
[0044] For example, if three toggle controls need to be presented, and the views corresponding to these three toggle controls are positioned in a horizontally arranged left-center-right order in the view architecture, then these three toggle controls can be presented in area 201 according to the positional relationship of the corresponding views and in a horizontally arranged left-center-right order. Specifically, the toggle control for switching to the left view among the multiple views is located on the left side of area 201, the toggle control for switching to the middle view among the multiple views is located in the middle of area 201, and the toggle control for switching to the right view among the multiple views is located on the right side of area 201. In this case, area 201 can be located at the top or bottom edge of the display area.
[0045] It will be appreciated that if the three views are positioned vertically in the view architecture in the top, middle, and bottom positions, the corresponding three toggle controls can be presented in region 201 in the top, middle, and bottom order according to the positional relationship of the corresponding views. That is, the toggle control for switching to the top view is located at the top of region 201, the toggle control for switching to the middle view is located in the middle of region 201, and the toggle control for switching to the bottom view is located at the bottom of region 201. In this case, region 201 can be located at the left or right edge of the display area.
[0046] In some implementations, the user can adjust the positional relationship of multiple views. The client device 110 can also update the view architecture in response to receiving the adjustment of the positional relationship of multiple views by the user of the client device 110. Further, the client device 110 can update the presentation positions of multiple switch controls based on the updated view architecture. For example, if the user changes the position of the left view and the right view in the three horizontally arranged views, the client device 110 can change the position of the switch control on the left and the switch control on the right of the corresponding three switch controls in response to the user's adjustment. For the example in Figure 2, the order of the replaced switch controls can be switch controls 206, 204 and 202.
[0047] In some implementations, the multiple views corresponding to the multiple switch controls include at least a desktop view 210, which includes at least one desktop defined on the client device 110. Here, a desktop can represent a workspace in which a user operates the client device 110. For example, a user can open one or more applications on a desktop. By default, the client device 110 can include only one default desktop (also called a primary desktop), and the user can add one or more additional desktops based on their needs.
[0048] In some implementations, the multiple views further include at least one of an application platform view 220 and a multitasking view 230. The application platform view 220 includes a launch control for launching at least one application installed on the client device 110. The launch control may be, for example, an identifier (e.g., an icon) of the application. In response to receiving a selection operation (e.g., a click operation, a double-click operation, a slide operation, etc.) on the launch control, the client device 110 may launch the application corresponding to the launch control.
[0049] The multitasking view 230 includes management controls for managing applications that have been launched in at least one desktop defined on the client device 110. The management controls may, for example, include the user interface of the launched application. In response to receiving a selection operation on the management control, the client device 110 may switch to presenting the user interface of the application corresponding to the management control.
[0050] In some implementations, when multiple desktops are included, the multitasking view 230 also includes management controls for each of the multiple desktops. The management controls may be, for example, desktop thumbnails. The client device 110 may present different application user interfaces in response to selections of thumbnails corresponding to different desktops. For example, when a user selects a thumbnail for a file application, the user interface for the file application is presented; when a user selects a thumbnail for a chat application, the user interface for the chat application is presented, and so on.
[0051] In response to receiving a first user interaction with a target toggle control among the multiple toggle controls, the client device 110 presents a target view corresponding to the target toggle control among the multiple views in the display area 115. The first user interaction here may be, for example, a selection operation on the target toggle control, such as a click operation, a double-click operation, a slide operation, etc. In response to receiving the selection operation with respect to the target toggle control, the client device 110 may present the target view in the display area 115.
[0052] Regarding the presentation location of the target view, in some implementations, client device 110 presents the target view in a second area outside of the first area. As shown in FIG2 , client device 110 presents multiple toggle controls in area 201 and presents the target view in a portion of display area 115 not obscured by area 201.
[0053] More details about switching are described below in conjunction with Figures 3 to 5. Specifically, Figure 3 shows a block diagram 300 of a desktop view according to some implementations of the present disclosure. As shown in Figure 3, the client device 110 can present a desktop view 210 in the display area 115 in response to receiving a selection operation for the switch control 204. It should be noted that, in this case, the desktop view 210 includes the user interfaces of applications that have been launched in the desktop. For example, the user interface 310 of the chat application shown in Figure 3, the user interface 320 of the file application, ..., and the user interfaces 330 of other applications. At this time, the switch control of the currently presented view can be highlighted, for example, a dotted frame can be presented around the switch control 204 to indicate that the desktop view is currently being presented.
[0054] FIG4 shows a block diagram 400 of a launchpad view according to some implementations of the present disclosure. As shown in FIG4 , the client device 110 can present the application deck view 220 in the display area 115 in response to receiving a selection operation on the toggle control 202. A dashed frame can be presented around the toggle control 202 to indicate that the launchpad view is currently being presented.
[0055] FIG5 shows a block diagram 500 of a multitasking view according to some implementations of the present disclosure. As shown in FIG5 , client device 110 may present multitasking view 230 in display area 115 in response to receiving a selection operation on toggle control 206. Multitasking view 230 may include an area 510 for displaying desktop identifiers and an area 520 for displaying application management controls. As shown in FIG5 , already created desktops (e.g., Desktop 1 210-1, Desktop 2 210-2) may be presented in area 510 on the left side of multitasking view 230, and management controls for launched applications in each created desktop (e.g., management controls 522 for managing a chat application, management controls 524 for managing a file application, ..., management controls 526 for managing other applications) may be presented in area 520 on the right side of multitasking view 230. A dotted frame may be presented around toggle control 206 to indicate that the multitasking view is currently being presented.
[0056] In some implementations, in addition to the above-mentioned method of presenting the target view in response to the first user interaction, the client device 110 can also detect a second user interaction (for example, a sliding operation on the display area 115) and present the target view based on the second user interaction. Specifically, the client device 110 can determine the sliding direction of the second user interaction in response to detecting the second user interaction. The second user interaction here can be, for example, a sliding operation, a drag operation, etc. on the display area 115. The sliding direction of the second user interaction here includes any one of a horizontal direction and a vertical direction. The client device 110 can receive the second user interaction through a device such as a touch screen, a mouse, etc., and determine the sliding direction of the second user interaction.
[0057] The client device 110 can select the next target view corresponding to the second user interaction from multiple views based on the sliding direction, the target view, and the positional relationship. Specifically, the client device 110 can determine an opposite direction opposite to the sliding direction, and based on the positional relationship, select a view adjacent to the target view in the opposite direction from the multiple views as the next target view. For example, if the positional relationship of the multiple views is a horizontal arrangement, and if the sliding direction of the second user interaction is from left to right, the client device 110 can determine that the opposite direction is the left direction, and then select a view adjacent to the current target view and located to the left of the current target view from the multiple views as the next target view based on the positional relationship in the view architecture.
[0058] Specifically, assuming that the positional relationship of the three views is (left: launchpad view; middle: desktop view; right: multitasking view), and the target view currently being presented is the desktop view. A swipe to the right can trigger the presentation of the launchpad view, and a swipe to the left can trigger the presentation of the multitasking view. For another example, assuming that the target view currently being presented is the launchpad view, swiping to the right will no longer switch views, and a swipe to the left can trigger the presentation of the desktop view. For another example, assuming that the target view currently being presented is the multitasking view, swiping to the right can trigger the presentation of the desktop view, and a swipe to the left will no longer switch views.
[0059] In some implementations, the client device 110 may also determine the number of desktops included in the desktop view 210, and then present the corresponding desktops in the desktop view 210. Assuming that only one desktop is defined, that desktop may be presented directly when switching to the desktop view 210. In some implementations, the user is allowed to create a new desktop and / or delete an existing desktop. For example, the user may click button 530 in FIG5 to create a new desktop; alternatively and / or additionally, the user may select the desktop that is desired to be deleted and delete it in a menu that pops up when the right button is clicked (or in other ways).
[0060] If it is determined that multiple desktops are defined at the client device 110, the current desktop can be determined based on the default settings of the client device and / or the user settings of the user of the client device, and the current desktop can be presented in the display area 115. Specifically, the desktop with the default settings (e.g., the primary desktop) can be presented in the desktop view 210. If there are user settings, for example, if the user has activated another desktop different from the primary desktop in historical operations, the other desktop can be presented.
[0061] In some implementations, the view architecture may further include the positional relationship between multiple desktops. For example, multiple desktops may be arranged along the vertical direction. See FIG6 for more details about the view architecture, which shows a block diagram 600 of a cross architecture according to some implementations of the present disclosure. As shown in FIG6 , in the case of three desktops, the view architecture of multiple views may be a cross architecture. In such a view architecture, a certain desktop is the center of the cross architecture, and other desktops may be above and below it, and the launcher view and the multitasking view may be on the left and right.
[0062] 6 , the launcher view 220, the desktop view 210 (including multiple desktops 210-1, 210-2, and 210-3), and the multitasking view 230 may be arranged horizontally in the order of left, center, and right. The multiple desktops 210-1, 210-2, and 210-3 may be arranged vertically in the order of top, center, and bottom.
[0063] Furthermore, the client device 110 may determine the sliding direction of the third user interaction in response to detecting the third user interaction. Similarly, the third user interaction here may be, for example, a sliding operation, a dragging operation, etc. on the display area 115. The sliding direction of the third user interaction here includes any one of a horizontal direction and a vertical direction. In the example of FIG6 , the sliding direction of the third user interaction is a vertical direction. It should be noted that, compared to the second user interaction that can be received when any view is displayed in the display area 115, the third user interaction can only be received by the client device 110 when the display area 115 displays a desktop view. In other words, in the launcher view 220 and the multitasking view 230, a sliding operation along the vertical direction does not trigger a switch to other desktops.
[0064] The client device 110 can receive the third user interaction through a touch screen, a mouse, or other devices, and determine the sliding direction of the third user interaction. The client device 110 can then select an adjacent desktop adjacent to the current desktop from the multiple desktops based on the sliding direction of the third user interaction, and present the adjacent desktop in the display area. For example, if the positional relationship of the multiple desktops is a vertical arrangement relationship, and if the sliding direction is from top to bottom, the client device 110 can determine that the opposite direction is the upper direction, and then based on the positional relationship in the view architecture, select an adjacent desktop located above the current target desktop and adjacent to the current desktop from the multiple desktops included in the desktop view, and present the adjacent desktop in the display area.
[0065] If the target view is a view in the horizontal direction of the cross architecture and the second user interaction is in the horizontal direction, the client device 110 may, in response to detecting the second user interaction with respect to the display area 115, determine the next target view corresponding to the second user interaction from the launch pad view 220, desktop two 210-2, and multitasking view 230, and present the next target view in the display area 115. If the target view is a desktop in the vertical direction of the cross architecture and the third user interaction is in the vertical direction, the client device may, in response to detecting the third user interaction, determine the adjacent desktop corresponding to the third user interaction from desktop one 210-1, desktop two 210-2, and desktop three 210-3, and present the adjacent desktop in the display area 115.
[0066] It will be understood that the view architecture in Figure 6 is merely exemplary, and the view architecture can be defined in different ways. For example, the launcher view, desktop view, and multitasking view can be arranged in a vertical direction and in the order of top, middle, and bottom, and desktop one, desktop two, and desktop three can be arranged in a horizontal direction and in the order of left, middle, and right. At this time, multiple switching controls can be presented on the left edge or the right edge of the display area, the sliding direction of the second user interaction can be the vertical direction, and the sliding direction of the third user interaction can be the horizontal direction. Specifically, different views can be switched by sliding in the vertical direction, and in the desktop view, different desktops can be switched by sliding in the horizontal direction.
[0067] In some implementations, the view architecture of the multiple views can also be a ring architecture, a grid architecture (e.g., 3×3 or other formats), etc. The implementation of this application uses a cross architecture as an example, but is not limited to this. For example, under a 3×3 grid architecture, a view architecture including 9 different views can be predefined. In this case, the user can swipe diagonally to switch to the predefined view.
[0068] Using the exemplary implementation of the present disclosure, multiple switch controls corresponding to multiple views are presented in the display area 115 of the client device 110, and in response to receiving a user interaction with a target switch control among the multiple switch controls, a target view corresponding to the target switch control is presented in the display area 115. In this way, when multiple views are included, view switching can be conveniently and quickly achieved through the switch control, which helps to improve the efficiency of view switching. Furthermore, the user interaction at this time is associated with the positional relationship in the view architecture. Switching views based on user interaction can strengthen the association between user interaction and view switching, and can improve the user experience when switching views.
[0069] Example Process
[0070] Figure 7 shows a flowchart of a process 700 for switching views according to some implementations of the present disclosure. Process 700 can be implemented at a client device 110. For ease of discussion, process 700 will be described with reference to environment 100 of Figure 1. At box 710, multiple toggle controls are presented in a display area of the client device, and the multiple toggle controls correspond to multiple views to be presented in the display area. At box 720, it can be determined whether a first user interaction is received for a target toggle control among the multiple toggle controls. If a first user interaction is received, process 700 proceeds to box 730. At box 730, a target view corresponding to the target toggle control among the multiple views is presented in the display area.
[0071] In some implementations, the multiple views include: a desktop view including at least one desktop defined at the client device; and at least any of: a launch pad view including launch controls for launching at least one application installed at the client device; and a multitasking view including management controls for managing applications that have been launched in at least one desktop defined at the client device.
[0072] In some implementations, presenting the multiple switch controls includes: acquiring a view architecture of the multiple views, the view architecture representing a positional relationship between the multiple views; and presenting the multiple switch controls based on the positional relationship.
[0073] In some implementations, process 700 further includes: in response to detecting a second user interaction, determining a sliding direction of the second user interaction; based on the sliding direction, the target view, and the position relationship, selecting a next target view corresponding to the second user interaction from a plurality of views; and presenting the next target view in the display area.
[0074] In some implementations, selecting the next target view includes: determining an opposite direction opposite to the sliding direction; and selecting, from the plurality of views, a view adjacent to the target view along the opposite direction as the next target view based on a positional relationship.
[0075] In some implementations, presenting the target view in the display area further includes: in response to determining that multiple desktops are defined at the client device, determining a current desktop based on at least any of: a default setting of the client device, a user setting of a user of the client device; and presenting the current desktop in the display area.
[0076] In some implementations, process 700 further includes: in response to detecting a third user interaction, determining a sliding direction of the third user interaction; selecting an adjacent desktop adjacent to the current desktop from a plurality of desktops based on the sliding direction of the third user interaction; and presenting the adjacent desktop in the display area.
[0077] In some implementations, the sliding direction of the second user interaction includes any one of a horizontal direction and a vertical direction, and the sliding direction of the third user interaction includes the other one of the horizontal direction and the vertical direction.
[0078] In some implementations, process 700 further includes updating the view architecture in response to receiving an adjustment to the positional relationship by a user of the client device.
[0079] In some implementations, presenting the plurality of toggle controls includes presenting the plurality of toggle controls in a first area of the display area; and presenting the target view includes presenting the target view in a second area outside the first area of the display area.
[0080] In some implementations, the first area is located at an edge of the display area, and the first area is always presented during operation of the client device.
[0081] In some implementations, the first area is at least any one of a task bar and a status bar in the display area.
[0082] Example devices and equipment
[0083] 8 shows a block diagram of an apparatus 800 for switching views according to some implementations of the present disclosure. The apparatus 800 may be implemented in or included in the client device 110. Each module / component in the apparatus 800 may be implemented by hardware, software, firmware, or any combination thereof.
[0084] As shown in the figure, the apparatus 800 includes a control rendering module 810 configured to render a plurality of toggle controls in a display area of a client device, wherein the plurality of toggle controls respectively correspond to a plurality of views to be rendered in the display area. The apparatus 800 also includes a view rendering module 820 configured to, in response to receiving a first user interaction directed to a target toggle control among the plurality of toggle controls, render a target view corresponding to the target toggle control among the plurality of views in the display area.
[0085] In some implementations, the multiple views include: a desktop view including at least one desktop defined at the client device; and at least any of: a launch pad view including launch controls for launching at least one application installed at the client device; and a multitasking view including management controls for managing applications that have been launched in at least one desktop defined at the client device.
[0086] In some implementations, the control presentation module 810 includes: an architecture acquisition module configured to acquire a view architecture of multiple views, where the view architecture represents a positional relationship between the multiple views; and a switch control presentation module configured to present multiple switch controls based on the positional relationship.
[0087] In some implementations, the device 800 further includes: a first sliding direction determination module, configured to determine the sliding direction of the second user interaction in response to detecting the second user interaction; a view selection module, configured to select a next target view corresponding to the second user interaction from multiple views based on the sliding direction, target view and position relationship; and a first view presentation module, configured to present the next target view in the display area.
[0088] In some implementations, the view selection module includes: an opposite direction determination module configured to determine an opposite direction opposite to the sliding direction; and a second view presentation module configured to select a view adjacent to the target view along the opposite direction from multiple views as the next target view based on a positional relationship.
[0089] In some implementations, the first view presentation module further includes: a desktop determination module, configured to, in response to determining that multiple desktops are defined at the client device, determine the current desktop based on at least any one of: a default setting of the client device, a user setting of a user of the client device; and a desktop presentation module, configured to present the current desktop in the display area.
[0090] In some implementations, the device 800 further includes: a second sliding direction determination module, configured to determine the sliding direction of the third user interaction in response to detecting a third user interaction; an adjacent desktop selection module, configured to select an adjacent desktop adjacent to the current desktop from multiple desktops based on the sliding direction of the third user interaction; and an adjacent desktop presentation module, configured to present the adjacent desktop in the display area.
[0091] In some implementations, the sliding direction of the second user interaction includes any one of a horizontal direction and a vertical direction, and the sliding direction of the third user interaction includes the other one of the horizontal direction and the vertical direction.
[0092] In some implementations, the apparatus 800 further includes: a framework updating module configured to update the view framework in response to receiving an adjustment of the position relationship by a user of the client device.
[0093] In some implementations, the control rendering module 810 includes: a first rendering module configured to render multiple switching controls in a first area of the display area; and the view rendering module 820 includes: a second rendering module configured to render a target view in a second area outside the first area of the display area.
[0094] In some implementations, the first area is located at an edge of the display area, and the first area is always presented during operation of the client device.
[0095] In some implementations, the first area is at least any one of a task bar and a status bar in the display area.
[0096] FIG9 shows a block diagram of an electronic device 900 in which one or more implementations of the present disclosure may be implemented. It should be understood that the electronic device 900 shown in FIG9 is merely exemplary and should not be construed as limiting the functionality and scope of the implementations described herein. The electronic device 900 shown in FIG9 may be used to implement the terminal device 110 of FIG1 and / or the apparatus 800 of FIG8 .
[0097] As shown in FIG9 , electronic device 900 is a general-purpose electronic device. Components of electronic device 900 may include, but are not limited to, one or more processors or processing units 910, memory 920, storage device 930, one or more communication units 940, one or more input devices 950, and one or more output devices 960. Processing unit 910 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 920. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to enhance the parallel processing capabilities of electronic device 900.
[0098] The electronic device 900 typically includes a plurality of computer storage media. Such media can be any accessible media that can be obtained by the electronic device 900, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 920 can be a volatile memory (e.g., a register, a cache, a random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 930 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data (e.g., training data for training) and can be accessed within the electronic device 900.
[0099] The electronic device 900 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 9 , a disk drive for reading from or writing to a removable, non-volatile disk (e.g., a “floppy disk”) and an optical drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 920 may include a computer program product 925 having one or more program modules configured to perform various methods or actions of various implementations of the present disclosure.
[0100] The communication unit 940 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 900 can be implemented as a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device 900 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.
[0101] The input device 950 may be one or more input devices, such as a mouse, keyboard, or trackball. The output device 960 may be one or more output devices, such as a display, a speaker, or a printer. The electronic device 900 may also communicate with one or more external devices (not shown) through the communication unit 940 as needed, such as a storage device, a display device, or the like, with one or more devices that allow a user to interact with the electronic device 900, or with any device that allows the electronic device 900 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).
[0102] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is provided, on which a computer program is stored, and when the program is executed by a processor, the method described above is implemented.
[0103] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.
[0104] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.
[0105] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0106] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.
[0107] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, not exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.
Claims
1. A method for switching views, comprising: Presenting a plurality of switching controls in a display area of a client device, the plurality of switching controls respectively corresponding to a plurality of views to be presented in the display area; as well as In response to receiving a first user interaction with respect to a target switch control among the plurality of switch controls, presenting a target view among the plurality of views corresponding to the target switch control in the display area.
2. The method of claim 1, wherein the plurality of views comprises: a desktop view comprising at least one desktop defined at the client device; as well as At least one of the following: a launch pad view including a launch control for launching at least one application installed at the client device; as well as The multitasking view includes management controls for managing applications that have been launched in the at least one desktop defined at the client device.
3. The method of claim 1 , wherein presenting the plurality of toggle controls comprises: Acquire a view framework of the multiple views, where the view framework represents a positional relationship between the multiple views; as well as The plurality of switching controls are presented based on the positional relationship.
4. The method according to claim 3, further comprising: In response to the detected second user interaction, determining a sliding direction of the second user interaction; selecting, from the plurality of views, a next target view corresponding to the second user interaction based on the sliding direction, the target view and the position relationship; as well as The next target view is presented in the display area.
5. The method of claim 4, wherein selecting the next target view comprises: determining an opposite direction opposite to the sliding direction; as well as Based on the positional relationship, a view adjacent to the target view along the opposite direction is selected from the multiple views as the next target view.
6. The method according to claim 4, wherein presenting the target view in the display area further comprises: In response to determining that a plurality of desktops are defined at the client device, determining a current desktop based on at least any of: a default setting of the client device, a user setting of a user of the client device; as well as The current desktop is presented in the display area.
7. The method according to claim 6, further comprising: In response to the detected third user interaction, determining a sliding direction of the third user interaction; selecting an adjacent desktop adjacent to the current desktop from the multiple desktops based on the sliding direction of the third user interaction; as well as The adjacent desktop is presented in the display area. 8 . The method according to claim 7 , wherein the sliding direction of the second user interaction includes any one of a horizontal direction and a vertical direction, and the sliding direction of the third user interaction includes the other of the horizontal direction and the vertical direction.
9. The method according to claim 3, further comprising: In response to receiving an adjustment of the positional relationship by a user of the client device, the view framework is updated.
10. The method of claim 1, wherein: Presenting the plurality of switching controls comprises: presenting the plurality of switching controls in a first area in the display area; and Presenting the target view includes: presenting the target view in a second area outside the first area in the display area.
11. The method of claim 1, wherein the first area is located at an edge of the display area, and the first area is always presented during operation of the client device. 12 . The method according to claim 1 , wherein the first area is at least any one of a task bar and a status bar in the display area.
13. A device for switching views, comprising: A control presentation module, configured to present a plurality of switching controls in a display area of a client device, wherein the plurality of switching controls respectively correspond to a plurality of views to be presented in the display area; as well as The view presenting module is configured to present a target view corresponding to the target switch control among the multiple views in the display area in response to receiving a first user interaction with the target switch control among the multiple switch controls.
14. An electronic device comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 12 when executed by the at least one processing unit.
15. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 12.
Citation Information
Patent Citations
View switching method and device for touch screens and client equipment
CN107870720A
Display switching method and device and mobile terminal
CN112015309A
Method and device for interaction, equipment and medium
CN116820304A
Information Display Method, Electronic Device, And Non-Transitory Computer-Readable Storage Medium
US20230161458A1