Display method and electronic equipment

Abstract

The invention provides a display method and electronic equipment, and is applied to the technical field of terminal display. The display method comprises the steps that a target application window is displayed on a display screen, and the target application window has an initial size; in response to a first operation for the target application window, determining a target boundary of the target application window, the first operation being capable of changing the size and / or position of the target application window; and if the target boundary exceeds the display boundary of the display screen, zooming the display content of the target application window at least based on the target boundary, so that the zoomed display content is partially invisible.

Description

Technical Field

[0001] This disclosure relates to the field of terminal display technology, and in particular to a display method and electronic device. Background Technology

[0002] Currently, most applications only adapt to "full-screen" scenarios when displaying task windows, rarely considering layout and interaction in "multi-window" scenarios (such as split-screen, floating windows, free windows, and floating small windows). Due to the lack of multi-window adaptation, these applications are prone to interface display problems when not in full-screen mode, resulting in a poor user experience. Summary of the Invention

[0003] In view of the above, this disclosure provides a display method and an electronic device.

[0004] According to a first aspect of this disclosure, a display method is provided, comprising: displaying a target application window on a display screen, the target application window having an initial size; determining a target boundary of the target application window in response to a first operation on the target application window, the first operation being capable of changing the size and / or position of the target application window; and scaling the display content of the target application window at least based on the target boundary if the target boundary exceeds the display boundary of the display screen, such that a portion of the scaled display content is not visible.

[0005] A second aspect of this disclosure provides an electronic device, comprising: a display screen having a display area having display boundaries; a first service module disposed at an application layer and configured to display a target application window on the display screen, the target application window having an initial size; and a second service module disposed at the display layer and configured to, in response to a first operation on the target application window, determine a target boundary of the target application window, the first operation being capable of changing the size and / or position of the target application window; and if the target boundary exceeds the display boundaries of the display screen, scaling the display content of the target application window at least based on the target boundary, such that a portion of the scaled display content is invisible.

[0006] A third aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the above-described display method.

[0007] A fourth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described display method.

[0008] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] The above and other objects, features and advantages of this disclosure will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0010] Figure 1 A flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically;

[0011] Figure 2 One of the schematic diagrams of a display method according to an embodiment of the present disclosure is shown;

[0012] Figure 3 A second schematic diagram illustrating a display method according to an embodiment of the present disclosure is shown;

[0013] Figure 4 A schematic diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0014] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details.

[0015] This disclosure provides a display method and an electronic device. Before introducing the technical solutions provided by this disclosure, the relevant technologies involved in this disclosure will be described first.

[0016] Currently, most third-party applications only adapt to "full-screen" scenarios when displaying task windows, rarely considering layout and interaction in "multi-window" scenarios (such as split-screen, floating windows, free windows, and floating small windows). Due to the lack of multi-window adaptation, these third-party applications are prone to interface display problems when not in full-screen mode, resulting in a poor user experience.

[0017] For example, issues include incomplete interface display: content is cropped, exceeds the visible area, or key buttons cannot be scrolled to or are not visible. Display stacking issues include pop-ups and dialog boxes overlapping with other elements, obscuring content; or improper handling of status bar / navigation bar height causing overlap.

[0018] To improve the usability of applications in multi-window environments, related technologies propose a general compatibility approach of "proportional scaling": without requiring changes to the application's layout logic, the application continues to render at its predetermined full-screen or fixed size, and the system then proportionally scales and places the image content into the target window area during the compositing and display phase. This approach can avoid most layout problems caused by application incompatibility at a lower cost. For example, addressing anomalies such as image stretching, jitter, and misalignment that occur when users adjust the floating window ratio or window size, optimized display methods and devices are proposed to improve visual consistency and stability during window scaling interactions.

[0019] While the above solutions have some effect, they still have shortcomings: 1. When the window size decreases, the system scales down the entire application screen proportionally, causing interface text, icons, and interactive controls to become too small, resulting in decreased readability and clickability, affecting accessibility and efficiency. 2. When the user drags the window to resize it and restore readability, if a fixed logical rendering reference or proportional mapping is maintained, some application content may extend beyond the screen or target display area, making edge content invisible or causing layout stretching.

[0020] In one example, let's consider an application launched in floating window mode. The application's native design works as follows: when displayed, the application has a task boundary attribute, representing its position on the screen. When the application's task window is moved or resized, the task changes, and the application is notified in real-time to redraw the window. After the application completes the redraw, the system display layer displays the application. For example, if the task boundary of the application at startup is (x=100, y=100, w=300, h=600), the application perceives its position on the screen as being within this rectangular area, and its actual drawing on the screen is also limited to this area.

[0021] The problem lies in real-time layout during window repositioning or resizing. The default layout upon application startup is relatively easy, as it's been tested by the application itself. However, achieving a perfect rearrangement during default size changes is actually quite difficult for an application. For example, consider a complex Word document with mixed text and images. If the paper width changes continuously, the amount of content that can be accommodated on that width will vary, requiring many text and images to wrap to the next line or back to the previous line. If the document's image and text structure is complex, handling line breaks perfectly during paper width changes is challenging, easily leading to layout errors. The same applies to content layout within an application; rearranging during window resizing can easily cause layout problems, overlapping images and text, or excessive blank space.

[0022] Before providing a further detailed description of the embodiments of this disclosure, the nouns and terms involved in the embodiments of this disclosure will be explained, and the nouns and terms involved in the embodiments of this disclosure shall be interpreted as follows.

[0023] Task window boundaries: In a system, a task is a container that manages a group of related pages that have a sequential relationship. For example, when you open an application, go from the homepage to the details page, and then to the settings page, these pages are placed in the same task, and the system uses a back stack to manage their order. The system not only manages which pages are in this task and how they are switched in order, but also specifies how much screen space the task occupies and where it is placed. The key parameter used to describe this displayable area is called the task boundary. You can think of the task boundary as a rectangle drawn on the screen: all pages in the task can only be displayed and respond to touch, gestures, and other operations within this rectangle. In full-screen mode, this rectangle is usually the entire screen; in split-screen, floating windows, free windows, or external screens, this rectangle may only be a part of the screen, or a movable and scalable window. Changing the size or position of this rectangle will affect all pages in the task. For example, when a user drags an application's task window to the left side of the screen (occupying 50% of the width), the system will set a task boundary for that application's task window (0, 0, screen width / 2, screen height); all active pages within the task (such as homepage → details page) will be displayed strictly within this boundary and will not cross the boundary into the area of ​​another window, ensuring that the interfaces under multiple windows do not interfere with each other.

[0024] The following will be through Figures 1-3 The display method of the embodiments of this disclosure will be described in detail.

[0025] Figure 1 A flowchart illustrating a display method according to an embodiment of the present disclosure is shown schematically.

[0026] like Figure 1 As shown, the display method of this embodiment includes operations S210 to S230.

[0027] When operating S210, the target application window is displayed on the screen, and the target application window has an initial size.

[0028] In operation S220, in response to a first operation on the target application window, the target boundary of the target application window is determined, and the first operation can change the size and / or position of the target application window.

[0029] In operation S230, if the target boundary exceeds the display boundary of the screen, the display content of the target application window is scaled at least based on the target boundary so that the scaled display content is not visible.

[0030] For example, a display screen can be a display device capable of displaying images or interfaces. A display screen can be a physical display panel, such as a mobile phone screen, tablet screen, laptop display, desktop monitor, or in-vehicle central control screen. A display screen can also be a display area in a virtual display environment, such as a virtual screen in a remote desktop or a single logical display area in a multi-screen splicing system.

[0031] The target application window can be the graphical user interface of an application that the user is currently interacting with or that the system is processing. For example, the target application window can be within the operating system or application framework, corresponding to the graphical user interface of a specific application. Examples of suitable targets include browser windows, floating bubble windows, split-screen windows, etc.

[0032] The initial size of the target application window can be its initial display size and position on the screen, usually preset by the system or the application. For example, when a multitasking pop-up window appears on a mobile phone, the system sets the window size to 70% of the screen width and 50% of the screen height; this setting is the initial size of the pop-up window.

[0033] The initial size of the target application window can be determined based on the display mode. For example, when an application is set to floating window mode, it has an initial floating window size. When the application is set to split-screen mode, its window size has the size corresponding to the split screen.

[0034] The first operation can be an action performed by the user or system on the target application window that causes a change in the window's size and / or position. The first operation can change the size of the target application window, change its position, or both simultaneously. Here, position can be the location of the center point of the target application window on the display screen. For example, the first operation can be a user input event: touch, drag, zoom gestures, mouse drag, keyboard shortcuts, etc. For instance, a user on a mobile device (such as a tablet / phone) can press and drag a floating window, moving its position on the screen. Using two fingers to zoom in and out on a floating video window on a mobile device may slightly shift the window's center position with the gesture, thus changing both the window's size and position. The first operation can also be a system-triggered adjustment operation: the system automatically rearranging the layout based on screen orientation changes. For example, when the screen rotates from portrait to landscape, the system rearranges and resizes the original portrait floating window to fit the landscape orientation.

[0035] The target boundary can be the expected boundary range of the target application window corresponding to the first operation. After detecting the first operation, the system calculates the theoretical rectangular area that the window should be in after performing the operation, i.e., the target boundary, based on the operation parameters (such as drag distance, gesture scaling ratio, final pointer position, etc.). For example, a floating window on a mobile phone is initially located in the center of the screen, with a width of 60% of the screen width. The user drags it entirely to the lower right corner, so that the final coordinates of the upper left corner are (300, 800). The new area calculated by the system based on this, plus the original width and height, is the target boundary. It should be noted that the target boundary does not have to be limited to within the display boundary; it can partially extend beyond the display boundary.

[0036] The display boundary of a screen is the effective area where content can be displayed, generally the visible area of ​​the screen. In scenarios with notch screens, punch-hole screens, status bars, navigation bars, etc., the display boundary can be determined according to the safe display area defined by the system, rather than the entire physical pixel area. For example, for a mobile phone screen with a resolution of 2400×1080, if we do not consider obstructions such as the status bar, the display boundary is x∈[0, 1080], y∈[0, 2400].

[0037] A target boundary exceeding the display boundary can mean that a portion of the target application window's target boundary falls outside the display boundary. In other words, any edge of the target boundary that extends beyond the display boundary is considered to indicate that the target boundary exceeds the display boundary. For example, if a user drags the target application window to the bottom right corner of the screen and zooms in, resulting in the bottom right corner of the target application window being at coordinates (1300, 2600), then it exceeds the screen's (1080, 2400) display boundary.

[0038] The displayed content can be content rendered by the application itself, such as web pages, documents, images, etc.

[0039] If the target boundary exceeds the display boundary of the screen, the displayed content can be scaled to fit within the area defined by the target boundary. In other words, the scaling of the displayed content is not limited by the display boundary of the screen, but by the target boundary. Since the target application window is scaled at least based on the target boundary, if the target boundary exceeds the display boundary, at least some content in the scaled target application window will be obscured or extend beyond the display boundary. That is, some content in the scaled target application window cannot be displayed within the display boundary. This can be understood as part of the scaled target application window's content being within the display boundary and another part being outside. The part within the display boundary is visible to the user, while the part outside is not. For example, if a user drags a browser window to the right edge of the screen and zooms in, the system zooms in on the entire displayed content by 2 times based on the target boundary. This results in a small area of ​​the zoomed-in content being outside the screen; for example, the right 50-pixel area and the bottom 30-pixel area of ​​the zoomed-in content are not visible, meaning this part of the scaled-in content cannot be seen by the user in the current state.

[0040] Understandably, when the position and / or size of an application window are changed, if the target boundary of the changed application window exceeds the display boundary, the display content of the target application window should be scaled at least based on the target boundary, so that a portion of the scaled display content is allowed to lie outside the display boundary. This allows the application window to flexibly adjust the scaling ratio of the display content without being restricted by the display boundary, better meeting the scaling needs expressed by the user's operation, thereby improving the readability of the content and the naturalness of the interaction.

[0041] As described above, in operation S220, in response to a first operation on the target application window, a target boundary of the target application window is determined. In one possible implementation, the operation may further include the operation of displaying an alternative window identical to the target application window in response to a second operation on the target application window, wherein the first operation acts on the alternative window, and the second operation is the same as or different from the first operation, wherein the target application window has a first boundary restricting the drawing of the target application window, and the alternative window has a second boundary restricting the drawing of the alternative window, the second boundary being the same as or different from the first boundary.

[0042] For example, the second operation could be triggering the switching of the target application window on the display screen to an alternative window. It should be noted that the second operation can be the first operation, i.e., triggering the switching of the target application window on the display screen to an alternative window through the first operation, and then performing the scaling of the window display content corresponding to the first operation. The second operation can also be an operation different from the first operation, i.e., the user first triggers the switching of the target application window on the display screen to an alternative window through a second operation different from the first operation, and then performs the scaling of the window display content corresponding to the first operation. The second operation can be an operation initiated by the user, such as clicking a window switching button, changing the position and / or size of the window, etc. The second operation can also be an operation automatically triggered by the system, such as detecting a window size adjustment command, etc. For example, if a user clicks the window switching button on a browser window, this click operation is the second operation; subsequently, if the user drags and resizes the browser window on the display screen, this dragging operation can be the first operation. As another example, if a user drags a floating window for video playback on a mobile phone to change the position of the floating window, this dragging operation can be either the first or the second operation.

[0043] An alternative window can be visually identical or substantially identical to the target application window. The content displayed in the alternative window can be the same as the target application window, making it visually indistinguishable to the user. The alternative window can be a new display entity created by the system after detecting a second operation, used to replace the target application window on the display screen and take over its display tasks. In other words, upon detecting a second operation targeting the target application window, an identical alternative window is created and used to replace the target application window displayed on the screen. For example, when an image browsing application switches from full-screen mode to floating window mode, the system can create an alternative window with content identical to the application's interface. This alternative window continues to display the image the original application was browsing, maintaining a continuous view for the user, but the actual display control has shifted from the target application window to the alternative window.

[0044] The alternative window and the target application window can be managed by two different modules. For example, the target application window can be managed by the application layer, and the alternative window can be managed by the display layer. The first operation on the target application window is applied to the alternative window, causing the display layer to control the scaling of the content displayed in the alternative window. The content displayed in the alternative window is a mapping of the content displayed in the target application window. Since the layout of the content displayed in the target application window remains unchanged, when the content displayed in the alternative window is scaled, the layout of the content displayed in the alternative window will not change; only the pixels of the content displayed in the alternative window will be enlarged or reduced.

[0045] The first boundary can be the drawing boundary registered by the target application window in the application framework or window management service. The first boundary defines the area within which the target application window can render content. The first boundary is typically maintained and managed by the operating system's window management module; the available drawing area perceived by the application is the area defined by the first boundary. For example, in the Android system, the first boundary can correspond to the task boundary of a task in the task stack, defining the drawing range of all active pages within that task. For instance, when an image browsing application runs in split-screen mode, its first boundary can be the left half of the screen. Assuming a screen resolution of 2400×1080 pixels, the coordinates of the top-left corner of the first boundary are (0, 1080), and the coordinates of the bottom-right corner are (1200, 0).

[0046] The second boundary can be the drawing boundary used by the alternative window. The second boundary can be set and adjusted independently of the first boundary, and is not restricted by the application framework or window management service. For example, the second boundary can be dynamically determined by the display control module based on user operations or system policies. For instance, when an image browsing application switches to floating window mode, the second boundary of the alternative window created by the system is used, and the content of the alternative window is displayed within the second boundary. The second boundary can be the same as or different from the first boundary. When the first and second boundaries are the same, it can be understood that the system detects a second operation, creates an alternative window on the display to replace the target application window, the target application window and the alternative window display the same content, and the first boundary of the target application window and the second boundary of the alternative window are in the same position and size. Then, the second boundary is adjusted according to the first operation to obtain the target boundary, and the display content of the alternative window is adjusted according to the target boundary. When the first and second boundaries are different, it can be understood that the system detects a second operation, creates an alternative window on the display to replace the target application window, the target application window and the alternative window display the same content, but the first boundary of the target application window and the second boundary of the alternative window are in different positions and sizes, and can be any position on the display screen. Then, adjust the second boundary according to the first operation to obtain the target boundary, and adjust the display content of the replacement window according to the target boundary.

[0047] In one example, a user is viewing a technical document containing text and images using a document editing app on a tablet. The app initially runs in split-screen mode. The tablet screen resolution is 2560×1600 pixels. The first boundary of the document editing app is defined by the top-left corner coordinates (0, 1600), the bottom-right corner coordinates (1280, 0), a width of 1280 pixels, and a height of 1600 pixels. At this point, the document editing app perceives its drawable area as the complete area defined by this first boundary and renders the document content within this area, including interface elements such as the top toolbar, the middle document browsing area, and the bottom page number indicator.

[0048] While viewing a document, users need to zoom in to observe the content. Therefore, the user uses two fingers to perform a pinch-to-zoom gesture on the alternate window to further enlarge the window size. This finger swipe is the second operation. At this point, the first operation is the same as the second operation. After the system detects this second operation, it immediately creates an alternate window. The content displayed in this alternate window is exactly the same as the current interface of the document editing application, still showing the same page of the technical document that the user is viewing, including the same text paragraphs, image positions, and toolbar status.

[0049] The system sets the second boundary of the alternative window to have the top-left corner coordinates (0, 1600), the bottom-right corner coordinates (1280, 0), a width of 1280 pixels, and a height of 1600 pixels. At this time, the second boundary of the alternative window is the same in position and size as the original first boundary of the document editing application.

[0050] After the alternative window is created and displayed, based on the user's first action (the user uses two fingers to perform a spread gesture on the alternative window to further enlarge its size), the system performs a first action on the alternative window. The system then updates the second boundary of the alternative window in real time based on this first action to obtain the target boundary. Based on this target boundary, the system enlarges the alternative content displayed in the alternative window that is identical to the content displayed in the document editing application window. Meanwhile, the first boundary perceived by the document editing application itself remains unchanged: the initial top-left corner coordinates (0, 1600), the bottom-right corner coordinates (1280, 0), the width (1280 pixels), and the height (1600 pixels). The displayed content of the document editing application window also remains unchanged. The application is unaware that its displayed content has actually been presented to the user in different positions and sizes through the alternative window. In this way, the system can flexibly adjust the actual display effect of the window without notifying the application to rearrange the layout, avoiding problems such as interface redraw delays and content layout errors that occur when the application frequently resizes the window, thereby improving the user experience and interface stability in multi-window scenarios.

[0051] As described above, in operation S220, in response to the first operation on the target application window, the target boundary of the target application window is determined. In one possible implementation, this operation may further include the operation that, in response to the second operation, the display control module of the electronic device takes over the replacement window based on the second boundary, wherein the first boundary is managed based on the window management service of the electronic device, and the initial display size does not exceed the first boundary.

[0052] For example, the display control module can be a functional module in an electronic device responsible for controlling window display. The display control module can run in the operating system's display layer, independent of the application layer's window management service. The display control module is responsible for receiving window display parameters and controlling the actual presentation of the window on the display screen based on these parameters. For instance, in the Android system, the display control module can be a display management service running in the system service layer, which is responsible for interacting with the underlying graphics compositing module to control the final display effect of each window.

[0053] A window management service is a system service in an electronic device responsible for managing the lifecycle and layout of application windows. It can run at the application framework layer of the operating system, assigning drawing boundaries to each application window and managing window creation, destruction, and switching. The window management service maintains the first boundary of application windows and notifies the application to rearrange the layout when the first boundary changes. For example, in Android, the window management service might correspond to the window manager service, which manages the task stack, window hierarchy, and drawing area of ​​all windows in the system. The window management service can also respond to user window operation commands, such as split-screen requests and floating window mode switching, and set appropriate drawing boundaries for the corresponding application windows.

[0054] Taking over the display of an alternative window based on a second boundary allows the display control module to acquire control of the alternative window's display, using the second boundary as the boundary parameter for controlling its display. After taking over, the display of the alternative window no longer depends on the window management service's management of the first boundary; instead, it is directly controlled by the display control module based on the second boundary. The display control module can adjust the display position, size, and scaling of the content of the alternative window in real time based on changes in the second boundary, without notifying the target application window to rearrange its layout. For example, when the display control module takes over the alternative window, user dragging, scaling, and other operations on the alternative window will directly affect the second boundary. The display control module immediately updates the display effect of the alternative window based on the changed second boundary, while the target application window's perception of the first boundary and the layout of its content remain unchanged.

[0055] The first boundary, managed by the window management service of the electronic device, can be maintained and updated by the window management service. The window management service can set an initial value for the first boundary of the target application window based on the system's window layout strategy, and adjust the first boundary according to changes in window mode under normal circumstances. In traditional window display mechanisms, the window management service notifies the application when the first boundary changes, and the application re-layouts and redraws the window content according to the new first boundary. For example, when a user switches an application from full-screen mode to split-screen mode, the window management service calculates the application's drawing area in split-screen mode and notifies the application of this area as the first boundary. Upon receiving the notification, the application adjusts the interface layout according to the new first boundary, such as adjusting text layout or reducing image size.

[0056] "Initial display size not exceeding the first boundary" means that, in its initial display state, the entire area of ​​the target application window's displayed content is contained within the region defined by the first boundary. The initial display size can be the display size when the target application window is first displayed or when switching to a new window mode. "Not exceeding the first boundary" means that all visible content of the target application window is within the range of the first boundary, and no content extends beyond it.

[0057] In one example, a user watches a movie using an online video playback application on a smartphone. The application initially runs in full-screen mode. The smartphone screen resolution is 2400×1080 pixels. In full-screen mode, the window management service sets the first boundary for the video playback application as the top-left corner coordinates (0, 2400) and the bottom-right corner coordinates (1080, 0), covering the entire screen area. At this time, the video playback application perceives its drawable area as the complete screen area defined by this first boundary and renders the video, playback control bar, progress indicator, and other interface elements within this area. The initial display size is entirely within the first boundary and does not exceed it.

[0058] A user needs to reply to an instant message while watching a movie, so they want to switch the video playback application to floating window mode to view both the chat application and the video content simultaneously. The user swipes down from the top of the screen to bring up the multitasking management interface and clicks the floating window mode button on the video playback application window; this click is the second action. After the system detects this second action, the display control module immediately creates an alternative window. The content displayed in this alternative window is exactly the same as the current interface of the video playback application, still showing the movie screen the user is watching and the playback control bar.

[0059] The initial values ​​for the second boundary set by the display control module for the alternative window are: top-left corner coordinates (800, 1800), bottom-right corner coordinates (1080, 1200), width 280 pixels, and height 600 pixels. This second boundary corresponds to the default window size in the system's preset floating window mode. Upon creation of the alternative window, the display control module takes over its display based on this second boundary. From this moment on, the display position, size, and scaling of the content of the alternative window are entirely controlled by the display control module according to the second boundary, no longer relying on the window management service to manage the first boundary.

[0060] Meanwhile, the window management service continues to maintain the first boundary of the video playback application, keeping it in its initial full-screen state, i.e., the top-left corner coordinates (0, 2400) and the bottom-right corner coordinates (1080, 0) remain unchanged. The drawable area perceived by the video playback application itself is still the complete screen area defined by this first boundary. The application is unaware that its displayed content has actually been presented as a smaller floating window in the bottom right corner of the screen through an alternative window. The application continues to render the video and control interface according to the full-screen mode layout, and will not trigger a rearrangement logic due to switching to floating window mode.

[0061] After the display control module takes over the replacement window, it scales down the entire content drawn by the video playback application within the first boundary according to the size of the second boundary (280×600 pixels), and displays the scaled content within the floating window area defined by the second boundary. The user sees a small window in the lower right corner of the screen, displaying the movie image and control bar in the same layout as in full-screen mode, only the overall size is reduced, and the relative positions of all interface elements remain unchanged.

[0062] Users can continue watching movies in floating window mode while interacting with the chat application. When a user needs to adjust the position of the floating window, they can press and hold the window with their finger and drag it to the upper left; this dragging operation is the first action. The display control module detects this first action and updates the position coordinates of the second boundary in real time. Suppose the user drags the floating window to the upper left corner of the screen, exceeding the display boundary. The display control module immediately adjusts the display position of the alternative window on the screen according to the updated second boundary. At this time, the portion of the content in the alternative window that exceeds the display boundary is not displayed; the user can only see the portion of the content within the display boundary. For the window management service, it is always assumed that the content of the video playback window is still displayed within the first boundary in full-screen mode.

[0063] Understandably, by having the display control module take over the replacement window based on the second boundary, the system achieves flexible control over window display. When the user switches window modes or adjusts window position and size, the application does not need to be aware of these changes, avoiding issues such as interface flickering, content misalignment, and playback stuttering that can result from frequent application layout changes. Simultaneously, the window management service continues to manage the logical state of application windows based on the first boundary, ensuring the integrity and compatibility of the system's window management mechanism. This significantly improves display quality and user experience in multi-window scenarios without modifying existing applications.

[0064] Figure 2 One of the schematic diagrams of a display method according to an embodiment of the present disclosure is shown.

[0065] As described above, in operation: the display control module of the electronic device takes over the replacement window based on a second boundary. In one possible implementation, the operation may further include: in response to a first operation, applying a first parameter corresponding to the first operation to the second boundary to obtain a target boundary; scaling the display content of the replacement window based on the target boundary, and displaying the scaled replacement display content within the target boundary.

[0066] For example, the first parameter can be a numerical value or a combination of parameters describing the degree of influence of the first operation on the alternative window. The first parameter may include numerical information such as position offset, size change, and scaling ratio. The first parameter can be calculated by the system in real time based on the user's input operation. For example, when the user performs a two-finger pinch gesture to zoom in on the alternative window on the touchscreen, the system detects that the distance between the two touch points increases from the initial 200 pixels to 400 pixels, and calculates the scaling ratio as 2.0, which is the first parameter. As another example, when the user drags the alternative window from the center of the screen to the lower right corner, the system detects that the coordinates of the window's center point change from (540, 1200) to (900, 2100), and calculates that the horizontal position offset is 360 pixels and the vertical position offset is 900 pixels, and the parameter group consisting of these two offsets is the first parameter.

[0067] The target boundary can be the boundary parameters of the final drawing of the display content of the substitute window, calculated after applying the first parameter to the second boundary of the substitute window. The target boundary can also be the actual boundary used by the display control module to control the display of the substitute window. The coordinates and dimensions of the target boundary can be the expected position and size that the substitute window should reach after the first operation. For example, in the above drag operation example, the new boundary obtained after applying the first parameter to the second boundary, namely the top-left corner coordinates (300, 1200), the bottom-right corner coordinates (600, 600), the width of 300 pixels, and the height of 600 pixels, is the target boundary.

[0068] Scaling the content of an alternate window based on target boundaries can involve adjusting the size of the content displayed within the alternate window according to the dimensions of the target boundaries. Scaling the content of an alternate window can include enlarging or shrinking all visible content within the alternate window, including text, images, and interface elements.

[0069] In one example, such as Figure 2 As shown, Figure 2 This illustrates the relationship between window boundaries and displayed content in the application and display layers. In the application layer, the target task window is located within a first boundary, which defines the drawing range of the target task window. For ease of understanding, the first boundary of the application layer and the target task window are shown here. In actual applications, when a substitute window appears, the first boundary of the application layer and the target task window are no longer displayed but are stored as data in the application layer. After detecting the second operation, the display layer creates a substitute window. In the display layer, the substitute window is initially located within a second boundary, represented by a dashed box. The display boundary defines the visible area of ​​the display screen. When the user performs the first operation, the system applies the first parameter to the second boundary to obtain the target boundary. The target boundary is represented by a solid box, located in the display layer, and its size is larger than the second boundary. The magnified substitute window is located within the target boundary, and the displayed content is scaled, resulting in an increased overall size. Because a portion of the target boundary extends beyond the display boundary, the portion of the magnified substitute window that extends beyond the display boundary is not visible; the user can only see the portion of the displayed content within the display boundary on the screen.

[0070] In one example, a user views a landscape photo using an image browsing app on a tablet computer, which runs in floating window mode. The tablet screen has a resolution of 2560×1600 pixels, with the display boundaries defined by the top-left corner (0, 1600) and the bottom-right corner (2560, 0). The window management service sets the first boundary for this image browsing app to be the top-left corner (0, 1600) and the bottom-right corner (2560, 0), covering the entire screen area.

[0071] The user wants to zoom in on a photo to observe details more clearly, so they use two fingers to perform a spread gesture on the alternate window. The distance between the two touch points is 300 pixels at the start of the gesture and 600 pixels at the end; this spread gesture is the first operation. After detecting this first operation, the system calculates a zoom ratio of 2, which is the first parameter. Simultaneously, the system detects that the center point of the user's two-finger gesture is located at the center of the alternate window, at coordinates (1280, 1100), and this center point coordinate remains unchanged during the zooming process.

[0072] The display control module responds to the first operation by creating an alternative window. The created alternative window is initially located within a second boundary, defined by the top-left corner coordinates (1000, 1400) and the bottom-right corner coordinates (1560, 800), with a width of 560 pixels and a height of 600 pixels, corresponding to the default window size in floating window mode. At this time, the landscape photo displayed in the alternative window is a scaled-down version of the complete photo drawn within the first boundary. Elements such as mountains, lakes, and trees in the photo are clearly visible, but the overall size is smaller.

[0073] In response to the first operation, the display control module applies the first parameter to the second boundary. Specifically, the display control module multiplies the width of the second boundary (560 pixels) by a scaling factor of 2.0, resulting in a new width of 1120 pixels, and multiplies the height of the second boundary (600 pixels) by a scaling factor of 2.0, resulting in a new height of 1200 pixels. To keep the scaling center point coordinates (1280, 1100) unchanged, the display control module calculates that the new top-left corner coordinates should be (720, 1700), and the new bottom-right corner coordinates should be (1840, 500). Thus, the target boundary is obtained with top-left corner coordinates (720, 1700), bottom-right corner coordinates (1840, 500), a width of 1120 pixels, and a height of 1200 pixels.

[0074] Because the top-left corner coordinate of the target boundary is 1700 in the vertical direction, exceeding the maximum vertical coordinate of the display boundary (1600), the target boundary extends 100 pixels vertically beyond the display boundary. The display control module scales the content displayed in the replacement window based on the target boundary. Before scaling, the landscape photo displayed in the replacement window is 560 pixels wide and 600 pixels high. After scaling, the photo width becomes 1120 pixels and the height becomes 1200 pixels. All elements in the photo are magnified by 2 times; a mountain peak that originally occupied 50 pixels wide now occupies 100 pixels wide, and a sun icon that originally had a diameter of 30 pixels becomes 60 pixels in diameter after scaling.

[0075] The display control module displays the scaled content within the target boundary. Since the top-left corner of the target boundary is 1700 vertically, exceeding the display boundary by 100 pixels, the top 100-pixel portion of the scaled landscape photo is not visible. The alternative window seen by the user is located slightly to the left of the center of the screen. The visible area of ​​the window has top-left corner coordinates of (720, 1600), bottom-right corner coordinates of (1840, 500), a width of 1120 pixels, and a visible height of 1100 pixels. The landscape photo displayed in the window is magnified by 2 times overall, but the sky portion at the top of the photo, i.e., the 100-pixel high area, is outside the display boundary and is not visible to the user. Users can clearly see the magnified details of elements such as mountains, lakes, and trees in the photo, such as the texture of rocks on mountains, the ripples on the lake surface, and the veins of leaves, significantly improving the viewing experience.

[0076] Throughout the zoom-in process, the first boundary perceived by the image browsing application remains unchanged at the top-left corner coordinates (0, 1600) and the bottom-right corner coordinates (2560, 0). The application continues to draw the complete landscape photo within this first boundary, without triggering any layout or redraw logic due to the user's zooming operation. The display control module completely controls the display of the alternative window based on the target boundary, responding to the user's zooming gestures in real time and adjusting the zoom ratio and display position of the content. The entire operation is smooth and natural, without any interface flickering or content misalignment.

[0077] By applying the first parameter to the second boundary to obtain the target boundary, and scaling and positioning the display content of the replacement window based on the target boundary, the system enables flexible movement and scaling of the window on the screen. Users can freely adjust the position and size of the window according to their needs to observe details of interest. Throughout the entire operation, the application does not need to be aware of the actual display changes of the window, avoiding performance overhead and display problems that may occur when the application frequently adjusts the window, significantly improving the operating experience and display quality in multi-window scenarios.

[0078] Understandably, by applying the first parameter to the second boundary to obtain the target boundary, and scaling the content displayed in the replacement window based on the target boundary, flexible scaling and positioning of the window's content are achieved. This allows the actual display effect of the window to be adjusted in real time in response to the user's operational intentions. The display control module directly controls the display of the replacement window based on the target boundary, without notifying the application to rearrange the layout. This avoids potential interface redraw delays and content misalignment issues that may occur during window scaling, improving the smoothness of window operations and the stability of the displayed content.

[0079] As described above, the display method of this embodiment may further include the following operations: if the first size ratio of the first boundary is not the same as the second size ratio of the target boundary; determine the second size of the target boundary based on the first size and the first size ratio of the target boundary; determine the adjusted target boundary based on the first size and the second size; scale the display content of the alternative window based on the adjusted target boundary, and display the scaled display content of the alternative window in the scaled target boundary.

[0080] For example, the first size ratio of the first boundary can be the ratio between the width and height of the first boundary. The first size ratio can reflect the aspect ratio when the application window draws content in the application layer. For instance, if the width of the first boundary is 1080 pixels and the height is 2400 pixels, then the first size ratio is 0.45, which can also be expressed as an aspect ratio of 9:20.

[0081] The second aspect ratio of the target boundary can be the ratio between the width and height of the target boundary. This second aspect ratio reflects the aspect ratio of the substitute window in the display layer after user interaction. For example, if the target boundary is 800 pixels wide and 600 pixels high, the second aspect ratio is 1.33, which can also be expressed as an aspect ratio of 4:3.

[0082] The difference between the first and second aspect ratios can be caused by a discrepancy between the aspect ratio of the first boundary and the target boundary. This difference can lead to stretching or compression distortion of the content displayed in the alternative window when presented within the target boundary. For example, if the first aspect ratio is 0.45 and the second aspect ratio is 1.33, content drawn within the first boundary with an aspect ratio of 9:20 will be stretched horizontally and compressed vertically if directly scaled to fill the target boundary with an aspect ratio of 4:3, resulting in distortion of the interface elements.

[0083] The first dimension can be either the width or the height of the target boundary. The second dimension can be either the width or the height of the target boundary. If the first dimension is the width, the second dimension is the height; if the first dimension is the height, the second dimension is the width.

[0084] Scaling the content of an alternative window based on the adjusted target boundary involves scaling the content within the alternative window according to the dimensions of the adjusted target boundary. Since the adjusted target boundary has the same aspect ratio as the first boundary, the scaling process can use the same scaling ratio in both the horizontal and vertical directions, thus maintaining the original proportions of the displayed content and preventing content distortion.

[0085] In one example, a user browses friends' updates on a social media app on a smartphone, which runs in full-screen mode. The smartphone screen has a resolution of 1080×2400 pixels and uses a portrait display with an aspect ratio of 9:20. The window management service sets the first boundary for this social media app at the top-left corner coordinates (0, 2400) and the bottom-right corner coordinates (1080, 0), with a width of 1080 pixels and a height of 2400 pixels, covering the entire screen area. The first dimension ratio of the first boundary, i.e., the width-to-height ratio, is 0.45. The social media app draws its interface content within this first boundary, and all interface elements are laid out according to the 9:20 aspect ratio. For example, the image display area for each update is 1000 pixels wide and 1500 pixels high, maintaining an aspect ratio of 2:3.

[0086] A user receives an email notification while browsing their feed and needs to view the email immediately. Therefore, they want to switch the social media app to floating mode so they can view both the email app and their social media feed simultaneously. The user swipes up from the bottom of the screen and pauses to bring up the multitasking interface, then clicks the floating mode button on the social media app window. Upon detecting this action, the system's display control module creates an alternative window, setting its second boundary to top-left corner coordinates (300, 2100), bottom-right corner coordinates (780, 1500), width 480 pixels, and height 600 pixels, corresponding to the system's default floating window size. The aspect ratio of the second boundary is 0.8.

[0087] The user wants to adjust the size of the floating window to view dynamic content more clearly, so they use two fingers to perform a pinch-to-zoom gesture on the alternative window. The distance between the two touch points is 250 pixels at the start of the gesture and 583 pixels at the end. This pinch-to-zoom gesture is the first operation. After detecting this first operation, the system calculates a scaling ratio of 2.33, which is the first parameter. Simultaneously, the system detects that the center point of the user's two-finger gesture is located at the center of the alternative window, at coordinates (540, 1800).

[0088] In response to the first operation, the display control module applies the first parameter to the second boundary. The display control module multiplies the width of the second boundary (480 pixels) by a scaling factor of 2.33, resulting in a new width of approximately 1118 pixels, rounded to 1120 pixels for ease of calculation. It also multiplies the height of the second boundary (600 pixels) by a scaling factor of 2.33, resulting in a new height of approximately 1398 pixels, rounded to 1400 pixels for ease of calculation. To keep the scaling center point coordinates (540, 1800) unchanged, the display control module calculates the target boundary as having upper-left corner coordinates (-20, 2500), lower-right corner coordinates (1100, 1100), a width of 1120 pixels, and a height of 1400 pixels. The second dimension ratio of the target boundary, i.e., the aspect ratio, is 0.8.

[0089] The system determines that the first dimension ratio of the first boundary (0.45) is different from the second dimension ratio of the target boundary (0.8). If the display content of the replacement window is scaled directly based on the target boundary, the content originally drawn within the first boundary with an aspect ratio of 9:20 will be distorted when presented within the target boundary with an aspect ratio of 0.8. Specifically, the scaling ratio of the display content in the horizontal direction is approximately 1.037, and the scaling ratio in the vertical direction is approximately 0.583. The difference in scaling ratios in the two directions causes the display content to be slightly enlarged in the horizontal direction and severely compressed in the vertical direction. The original dynamic image with an aspect ratio of 2:3 will become a flat shape with an aspect ratio of approximately 1.78:1, and the interface elements will be severely distorted.

[0090] To avoid content distortion, the system determines a second dimension of the target boundary based on its first dimension and aspect ratio. The system keeps the target boundary width of 1120 pixels as the first dimension and calculates the second dimension (height) to be 2489 pixels based on the first dimension's aspect ratio of 0.45. The system then determines the adjusted target boundary based on the first dimension of 1120 pixels and the second dimension of 2489 pixels. To maintain the center point coordinates (540, 1800) of the adjusted target boundary, the system calculates the top-left corner coordinates as (1100, 555.5), the width as 1120 pixels, and the height as 2489 pixels. The aspect ratio of the adjusted target boundary is 0.45, the same as the first boundary.

[0091] Since the adjusted target boundary has a vertical coordinate of 3044.5 for the top left corner and a maximum vertical coordinate of 2400 for the top of the display boundary, exceeding the top of the display boundary by 644.5 pixels, and a vertical coordinate of 555.5 for the bottom right corner and a minimum vertical coordinate of 0 for the bottom of the display boundary, exceeding the bottom of the display boundary by 555.5 pixels, while the horizontal coordinate of the top left corner is -20 for the top left corner and a minimum horizontal coordinate of 0 for the bottom of the display boundary, exceeding the left side of the display boundary by 20 pixels, the adjusted target boundary exceeds the display boundary by a total of 1200 pixels vertically and 20 pixels horizontally.

[0092] The display control module scales the content displayed in the replacement window based on the adjusted target boundary. The horizontal scaling ratio is 1.037, and the vertical scaling ratio is also 1.037, with the scaling ratios in both directions being the same. The display control module scales all interface content drawn within the first boundary of the social media application proportionally by 1.037 in both the horizontal and vertical directions. An animated image originally 1000 pixels wide, 1500 pixels high, and with an aspect ratio of 2:3 becomes 1037 pixels wide and 1555.5 pixels high after scaling, while maintaining the 2:3 aspect ratio, preserving the original proportions of the image without stretching or compression distortion.

[0093] The display control module displays the scaled content within the adjusted target boundary. Since the adjusted target boundary extends 644.5 pixels vertically beyond the top of the display boundary and 555.5 pixels vertically beyond the bottom of the display boundary, and 20 pixels horizontally beyond the left side of the display boundary, the portion of the scaled content with a top height of 644.5 pixels, a bottom height of 555.5 pixels, and a left width of 20 pixels exceeds the display boundary and is therefore invisible. The visible area of ​​the alternative window seen by the user on the screen has its top-left corner coordinates at (0, 2400) and its bottom-right corner coordinates at (1100, 0), with a visible width of 1100 pixels and a visible height of 2400 pixels, almost occupying the entire screen.

[0094] The social media content displayed in the window has been enlarged proportionally, approximately 1.037 times, but all interface elements maintain their original aspect ratios and relative positions. Users can see the enlarged animated images, text, buttons, etc. Images are not stretched or compressed, text is not distorted, and buttons retain their original circular or rounded rectangular shapes. Because some content at the top and bottom of the adjusted target boundary exceeds the display boundary, users cannot see part of the topmost navigation bar content and part of the bottommost function buttons.

[0095] By determining whether the first size ratio of the first boundary is the same as the second size ratio of the target boundary, and adjusting the size of the target boundary to maintain the same width-to-height ratio as the first boundary when they are different, the system achieves proportional scaling of the content displayed in the replacement window, effectively avoiding the problem of stretching and deformation of interface elements that may occur when users adjust the window size or switch window modes.

[0096] Understandably, by determining whether the first size ratio of the first boundary is the same as the second size ratio of the target boundary, and adjusting the size of the target boundary according to the first size ratio when they are different, proportional scaling of the content displayed in the replacement window is achieved, avoiding the problem of stretched and distorted display content caused by mismatched aspect ratios. The adjusted target boundary maintains the same aspect ratio as the first boundary, ensuring that content drawn at a specific ratio within the first boundary can be presented at the same ratio within the adjusted target boundary. This guarantees the original shape and relative position of interface elements, improving the visual quality of the window display content and the user experience.

[0097] As described above, the display method of this embodiment may further include the following operations: determining a scaling ratio based on a first boundary and a target boundary; scaling the alternative window according to the scaling ratio to obtain a scaled alternative window.

[0098] For example, determining the scaling ratio based on the first boundary and the target boundary can be done by calculating the scaling factor that the replacement window should undergo based on the ratio between the size of the first boundary and the size of the target boundary. The scaling ratio can include a horizontal scaling ratio and a vertical scaling ratio. The scaling ratio can be calculated separately for both the width and height dimensions. The scaling ratio can be a single uniform scaling ratio, or it can be independent scaling ratios in the horizontal and vertical directions. A uniform scaling ratio ensures that the displayed content of the replacement window maintains its original aspect ratio during scaling, without stretching or compression deformation.

[0099] The alternative window is scaled according to a scaling ratio to obtain a scaled alternative window. This can be achieved by applying a calculated scaling ratio to the displayed content within the alternative window, adjusting the size of the displayed content. The scaling operation can include enlarging or shrinking all visible elements in the alternative window, such as images, text, and UI controls. The scaled alternative window maintains the relative positions and original proportions of all UI elements.

[0100] Understandably, by determining the scaling ratio based on the first boundary and the target boundary, and scaling the substitute window accordingly, a precise match between the content displayed in the substitute window and the size of the target boundary is achieved. The scaling operation is executed directly at the display layer by the display control module. The application still draws content based on the first boundary at the application layer, without needing to be aware of the actual scaling process of the substitute window. This avoids the layout recalculation and interface redrawing overhead that may occur when the window size changes frequently, significantly improving the response speed and smoothness of the window scaling operation.

[0101] In one example, a user watches a movie on a tablet using a video playback application running in full-screen mode. The tablet screen has a resolution of 2560×1600 pixels and uses a landscape orientation with an aspect ratio of 16:10. The window management service sets the first boundary for this video playback application at the top-left corner coordinates (0, 1600) and the bottom-right corner coordinates (2560, 0), with a width of 2560 pixels and a height of 1600 pixels, covering the entire screen area. The first dimension ratio of the first boundary, i.e., the aspect ratio, is 1.6. The video playback application draws its interface content within this first boundary, including the central video display area, the playback control bar at the bottom, and the title bar at the top. The video display area has a width of 2560 pixels and a height of 1440 pixels, maintaining an aspect ratio of 16:9, and is vertically centered within the first boundary, with 80-pixel black borders at the top and bottom.

[0102] Users need to take notes while watching movies, so they want to switch the video playback application to floating window mode to watch the movie and edit notes simultaneously. The user clicks the floating window mode button on the video screen. Upon detecting this action, the system displays a replacement window created by the control module, setting its second boundary to top-left corner coordinates (1600, 1400), bottom-right corner coordinates (2400, 600), width 800 pixels, and height 800 pixels, corresponding to the system's default video floating window size. The aspect ratio of the second boundary is 1.0.

[0103] The system determines that the first dimension ratio of 1.6 for the first boundary is different from the second dimension ratio of 1.0 for the second boundary. If the display content of the window is directly scaled based on the second boundary, the interface content originally drawn within the first boundary with an aspect ratio of 16:10 will be distorted when presented within the second boundary with an aspect ratio of 1:1. Specifically, the horizontal scaling ratio is 0.3125, and the vertical scaling ratio is 0.5. The difference in scaling ratios in the two directions will cause the video image to be over-compressed horizontally and slightly compressed vertically. The original 16:9 aspect ratio video image will become a narrow and elongated shape with an aspect ratio of approximately 0.56:1, resulting in severe distortion.

[0104] To avoid content distortion, the system determines the second dimension of the second boundary based on its first dimension and aspect ratio. The system keeps the width of the second boundary at 800 pixels as the first dimension and calculates the second dimension (height) to be 500 pixels based on the aspect ratio of 1.6. The system then determines the adjusted target boundary based on the first dimension of 800 pixels and the second dimension of 500 pixels. The system maintains the top-left corner coordinates of the adjusted target boundary at (1600, 1400), the same as the second boundary, and calculates the bottom-right corner coordinates as (2400, 900) based on the width of 800 pixels and the height of 500 pixels. The adjusted target boundary has top-left corner coordinates of (1600, 1400), bottom-right corner coordinates of (2400, 900), a width of 800 pixels, a height of 500 pixels, and an aspect ratio of 1.6, the same as the first boundary.

[0105] The display control module determines the scaling ratio based on the first boundary and the adjusted target boundary. The horizontal scaling ratio is 0.3125, the vertical scaling ratio is 0.3125, and the scaling ratio in both directions is the same, i.e., a uniform scaling ratio of 0.3125. The display control module scales the replacement window according to this scaling ratio.

[0106] During the scaling process, all interface content drawn by the video playback application within the first boundary is scaled down proportionally by 0.3125 times. The video display area, originally 2560 pixels wide, 1440 pixels high, and with an aspect ratio of 16:9, becomes 800 pixels wide and 450 pixels high after scaling, while maintaining the 16:9 aspect ratio, preserving the original proportions of the video image without stretching or compression distortion.

[0107] After obtaining the scaled replacement window, the display control module displays the scaled content within the adjusted target boundary. Since the upper left corner of the adjusted target boundary is (1600, 1400) and the lower right corner is (2400, 900), which are completely within the range of the display boundary (0, 1600) to (2560, 0), the scaled content is fully visible.

[0108] While watching the movie in floating window mode, users can open a notes application on the left side of the screen to edit their viewing experience. During viewing, if a user wants to zoom in on the video floating window for a clearer view of details, they can use two fingers to perform a pinch-to-zoom gesture on the alternative window. The distance between the two touch points is 400 pixels at the start of the gesture and 800 pixels at the end; this pinch-to-zoom gesture is the first operation. After detecting this first operation, the system calculates a zoom ratio of 2.0, which is the first parameter. Simultaneously, the system detects that the center point of the user's two-finger gesture is located at the center of the alternative window, at coordinates (2000, 1150).

[0109] In response to the first operation, the display control module applies the first parameter to the currently adjusted target boundary. The currently adjusted target boundary has the following coordinates: top left corner (1600, 1400), bottom right corner (2400, 900), width 800 pixels, and height 500 pixels. The display control module multiplies the target boundary width of 800 pixels by a scaling factor of 2.0 to obtain a new width of 1600 pixels, and multiplies the target boundary height of 500 pixels by a scaling factor of 2.0 to obtain a new height of 1000 pixels. To keep the scaling center point coordinates (2000, 1150) unchanged, the display control module calculates a new target boundary with the following coordinates: top left corner (1200, 1650), bottom right corner (2800, 150), width 1600 pixels, and height 1000 pixels.

[0110] The system determines that the first dimension ratio of the first boundary (1.6) is the same as the second dimension ratio of the new target boundary (1600 ÷ 1000 = 1.6), therefore no adjustment to the target boundary size is needed. The display control module determines the scaling ratio based on the first boundary and the new target boundary. The horizontal scaling ratio is 0.625, and the vertical scaling ratio is also 0.625, the same in both directions, i.e., a uniform scaling ratio of 0.625. The display control module then scales the replacement window according to this scaling ratio.

[0111] During the scaling process, all interface content drawn by the video playback application within the first boundary is scaled down proportionally by 0.625 times. The video display area, originally 2560 pixels wide and 1440 pixels high, becomes 1600 pixels wide and 900 pixels high after scaling, while maintaining the aspect ratio of 16:9.

[0112] Because the top-left corner of the new target boundary is vertically at 1650, and its maximum vertical extension beyond the display boundary is 1600, exceeding the top of the display boundary by 50 pixels; and the bottom-right corner is horizontally at 2800, and its maximum horizontal extension beyond the display boundary is 2560, exceeding the right side of the display boundary by 240 pixels, the new target boundary extends 50 pixels vertically and 240 pixels horizontally beyond the display boundary. The display control module will display the scaled content within the new target boundary. The top 50-pixel high portion and the right 240-pixel wide portion of the scaled content extend beyond the display boundary and are therefore invisible.

[0113] The top-left corner of the alternative window visible to the user on the screen is (1200, 1600), and the bottom-right corner is (2560, 150), with a visible width of 1360 pixels and a visible height of 1450 pixels. The video displayed in the window has a visible width of 1360 pixels and a visible height of 900 pixels. Because the scaled video frame is 1600 pixels wide, with the right 240 pixels exceeding the display boundary and becoming invisible, the user can only see a portion of the video frame on the left side (1360 pixels wide), with approximately 15% of the right side invisible. The scaled top title bar is 50 pixels high, completely exceeding the display boundary and therefore invisible to the user. Despite some content exceeding the display boundary, the visible portion of the video frame still maintains its original 16:9 aspect ratio without distortion, resulting in good image quality. Users can view details in the movie more clearly than before.

[0114] Understandably, by determining a uniform scaling ratio based on the first boundary and the target boundary, and scaling the alternative window proportionally according to this scaling ratio, the system achieves flexible adjustment of the content displayed in the alternative window at different sizes and positions, while ensuring the original aspect ratio of the displayed content and avoiding deformation of interface elements.

[0115] As described above, the display method of this embodiment may further include the operation of generating a functional component corresponding to the target boundary if the target boundary exceeds the display boundary of the display screen, so as to use the functional component to view the invisible part of the scaled display content.

[0116] For example, a functional component can be an interactive component or interface element used to assist users in accessing or controlling invisible portions of the zoomed-out display content. Functional components can be visual controls, such as scrollbars, sliders, navigation buttons, etc. They can also be touch gesture-responsive areas, such as transparent interactive layers that support swiping. Functional components can also be system-level tools, such as thumbnail navigation windows, content preview overlays, etc. For instance, when a user zooms in on a browser window beyond the screen's display boundaries, the system automatically generates a vertical scrollbar on the right edge of the window; this scrollbar is the functional component. The user can drag the scrollbar's slider to view the webpage content extending beyond the bottom of the screen. As another example, if a user drags an image editing application window to the bottom right corner of the screen and zooms in, causing some content on the right and bottom edges of the window to extend beyond the display boundaries, the system generates a vertical scrollbar on the right side of the window and a horizontal scrollbar on the bottom edge. The user can use these two scrollbars to control the vertical and horizontal scrolling of the content, respectively, to view the complete image editing area.

[0117] The functional component corresponding to the target boundary can be dynamically generated based on the characteristics of the target boundary. The generation of the functional component can be determined according to the specific circumstances of the target boundary exceeding the display boundary, such as the direction of the exceedance, the distance of the exceedance, and the proportion of the exceedance area. For example, when the target boundary exceeds the display boundary only on the right side, the system generates a vertical scroll bar; when the target boundary exceeds the display boundary on both the right and bottom sides, the system generates both a vertical scroll bar and a horizontal scroll bar; when the area of ​​the target boundary exceeding the display boundary is small (e.g., less than 10% of the total area of ​​the target boundary), the system generates a simplified scroll bar; when the exceedance area is large (e.g., greater than 30% of the total area of ​​the target boundary), the system generates a standard scroll bar with an additional content position indicator.

[0118] Viewing invisible portions of scaled content using widgets can be achieved by interacting with the widgets, moving content that was originally outside the display boundaries into the visible area. For example, clicking on a blank area below the scroll bar scrolls the window's content up one screen, bringing content previously off-screen into view. Similarly, pressing and sliding on a touchscreen moves the entire window to the left, bringing content previously off-screen to the right into view.

[0119] It's important to note that the creation of widgets does not affect the boundaries or scaling of the target application window itself. In other words, widgets are auxiliary interactive components attached to or overlaid on top of the target application window; the content displayed in the target application window remains scaled based on the target window's boundaries.

[0120] In one example, a user opens a document editing application on a tablet. The application is displayed in a floating window mode, with an initial window size of 50% of the screen width and 60% of the screen height, centered on the screen. The document content is displayed normally within the window, and the window's target boundary is (540, 432, 1380, 1728), which is entirely within the tablet's display boundary (0, 0, 1920, 2560). No functional components are generated by the system.

[0121] The user wants to zoom in to view table details in a document, so they use two fingers to perform a zoom gesture, stretching the window width to 80% of the screen width and the height to 75% of the screen height. The system responds to this first operation, calculating the target boundary as (192, 320, 1728, 2240). Since the right coordinate of the target boundary (1728) is less than the right coordinate of the display boundary (1920) and the bottom coordinate (2240) is less than the bottom coordinate of the display boundary (2560), the target boundary still does not exceed the display boundary. The system scales the document content based on the target boundary, proportionally enlarging the text and tables, allowing the user to clearly view the table content. The system has not yet generated any functional components.

[0122] The user further drags the window to the lower right corner and continues to use gestures to enlarge the window to 110% of the screen width and 120% of the screen height. The system responds to this first operation, calculating the new target boundary as (400, 300, 2512, 3372). At this point, the right coordinate of the target boundary (2512) exceeds the right coordinate of the display boundary (1920) by 592 pixels, and the lower coordinate (3372) exceeds the lower coordinate of the display boundary (2560) by 812 pixels. The system determines that the target boundary exceeds the display boundary and scales the document content based on the target boundary, enlarging the document content to approximately 2.2 times its original size. After scaling, the 592-pixel wide area on the right and the 812-pixel high area on the bottom of the document are outside the display boundary, and this portion of the content is not visible.

[0123] The system detects that the target boundary extends beyond the display boundary on both the right and bottom sides, and automatically generates corresponding functionalities: a vertical scroll bar is generated at the right edge of the window, with its slider size set according to the ratio of the visible area height to the total height of the target boundary; a horizontal scroll bar is generated at the bottom edge of the window, with its slider size set according to the ratio of the visible area width to the total width of the target boundary. The vertical scroll bar slider is initially located at the top, indicating that the upper part of the document is currently displayed; the horizontal scroll bar slider is initially located at the left, indicating that the left part of the document is currently displayed.

[0124] To view the table columns that extend beyond the screen on the right side of the document, the user drags the horizontal scroll bar slider to the left. In response, the system moves the entire document content to the left, gradually bringing the table columns, previously outside the right edge of the display boundary, into the visible area, while the previously visible content on the left moves out of the display boundary. When the slider is dragged to the far right of the horizontal scroll bar, the entire rightmost content of the document is now displayed on the screen, allowing the user to successfully view the previously invisible table data.

[0125] The user then wanted to view the notes at the bottom of the document, so they dragged the vertical scroll bar upwards. The system responded by moving the entire document content upwards, gradually bringing the notes, previously outside the display boundaries, into the visible area. The user then used the widget to view all the previously invisible parts of the zoomed-out content.

[0126] Understandably, by generating functional components corresponding to the target boundary when the target boundary exceeds the display boundary, users can easily access the invisible parts of the content displayed after scaling. This avoids the problem of users being unable to view some content after it exceeds the screen due to window scaling. It ensures both the flexibility of window scaling and the complete accessibility of content, thereby improving the user's operating experience and content browsing efficiency in multi-window scenarios.

[0127] Figure 3 A second schematic diagram of a display method according to an embodiment of the present disclosure is shown.

[0128] As described above, in one possible implementation, the display method of this embodiment may further include the operation of: in response to a sliding operation on the scaled alternative window, displaying the portion of the scaled alternative window that extends beyond the display boundary within the display boundary, wherein the functional component is used to implement the sliding operation on the scaled alternative window.

[0129] In one example, a slider is used as the functional component. (See reference...) Figure 3 A user opens a document editing application on a tablet computer. The application is displayed in a floating window mode, with an initial window size of 50% of the screen width and 60% of the screen height, centered on the screen. The document content is displayed normally within the window, with a target boundary of (540, 432, 1380, 1728). This boundary is completely within the display boundary of the tablet screen (0, 0, 1920, 2560), and the system does not generate any functional components.

[0130] The user drags the window to the bottom right corner and uses a gesture to enlarge it to 110% of the screen width and 120% of the screen height. The system responds to this first operation, calculating the new target boundary as (400, 300, 2512, 3372). At this point, the right coordinate of the target boundary (2512) exceeds the right coordinate of the display boundary (1920) by 592 pixels, and the bottom coordinate (3372) exceeds the bottom coordinate of the display boundary (2560) by 812 pixels. The system determines that the target boundary exceeds the display boundary and scales the document content based on this boundary, enlarging it to approximately 2.2 times its original size. After scaling, the 592-pixel wide area on the right and the 812-pixel high area on the bottom of the document are outside the display boundary and are therefore invisible.

[0131] The system detects that the target boundary extends beyond the display boundary on both the right and bottom sides, and automatically generates corresponding functionalities: a vertical scroll bar is generated at the right edge of the window, with its slider size set according to the ratio of the visible area height to the total height of the target boundary; a horizontal scroll bar is generated at the bottom edge of the window, with its slider size set according to the ratio of the visible area width to the total width of the target boundary. The vertical scroll bar slider is initially located at the top, indicating that the upper part of the document is currently displayed; the horizontal scroll bar slider is initially located at the left, indicating that the left part of the document is currently displayed.

[0132] To view the table columns that extend beyond the screen on the right side of the document, the user drags the horizontal scroll bar slider to the left. In response, the system moves the entire document content to the left, gradually bringing the table columns, previously outside the right edge of the display boundary, into the visible area, while the previously visible content on the left moves out of the display boundary. When the slider is dragged to the far right of the horizontal scroll bar, the entire rightmost content of the document is now displayed on the screen, allowing the user to successfully view the previously invisible table data.

[0133] The user then wanted to view the notes at the bottom of the document, so they dragged the vertical scroll bar upwards. The system responded by moving the entire document content upwards, gradually bringing the notes, previously outside the display boundaries, into the visible area. The user then used the widget to view all the previously invisible parts of the zoomed-out content.

[0134] As described above, the display method of this embodiment may further include the following operations: determining a second parameter in response to a third operation on the scaled alternative window; applying the second parameter to target data corresponding to the target application window to obtain an updated target application window, wherein the updated target application window has different display content from the target application window; and replacing the scaled alternative window in the target boundary with the updated target application window.

[0135] For example, a third action can be an interactive operation performed by the user on a scaled-up alternative window that causes a change in the application's internal state or displayed content. The third action can be a touch operation, such as clicking, double-clicking, long-pressing, or swiping. It can also be a mouse operation, such as single-clicking, right-clicking, or scrolling. Furthermore, it can be a keyboard input operation, such as text input or pressing a keyboard shortcut. For instance, a user clicking a hyperlink in a scaled-up alternative window of a browser window is a third action. Similarly, a user swiping up to view historical messages in a scaled-up alternative window of a social media application is a third action. And a user clicking the play button in a scaled-up alternative window of a video playback application is a third action.

[0136] The second parameter can be a parameter calculated based on the third operation and used to update the state or content of the target application window. The second parameter can include touch coordinate parameters, scroll distance parameters, input text parameters, operation type parameters, etc. The specific form of the second parameter depends on the type of the third operation and the application's response requirements. For example, when a user clicks at coordinates (800, 600) in the scaled-up alternate window, the system maps these screen coordinates back to the logical coordinate system of the target application window, calculating the second parameter as the target application window coordinates (200, 150). This coordinate parameter informs the application of the logical location of the user's click. As another example, when a user swipes up 200 pixels in the scaled-up alternate window, the system calculates the second parameter as a logical scroll distance of 100 pixels based on the scaling ratio. This distance parameter informs the application of the actual content distance to be scrolled.

[0137] It's important to note that after the alternative window appears, the target application window will not be displayed. Applying the second parameter to the target application window can mean passing the second parameter to the application corresponding to the target application window, which then updates the target data corresponding to the target application window based on the second parameter. After receiving the second parameter, the application processes it according to its own business logic, which may trigger operations such as interface navigation, content loading, and playback control. For example, after receiving the click coordinate parameter, the browser application determines that there is a hyperlink at that coordinate location and loads the new webpage corresponding to the link.

[0138] The updated target application window can be the window state updated by the application based on the second parameter. The updated target application window maintains the same border size as the target application window, but its internal content changes. This change can be a change in the state of interface elements, such as a button changing from "play" to "pause." It can also be a complete replacement of page content, such as navigating from the homepage to a details page. Furthermore, it can be a partial update of a content area, such as adding a new message item to a chat history list. For example, when a user clicks a hyperlink in a browser window, the updated target application window displays the new webpage content linked to, instead of the original webpage. Similarly, when a user clicks the play button in a video playback window, the video in the updated target application window changes from a static cover image to a playing video, and the play button icon changes from a triangle to a pause symbol.

[0139] Replacing a scaled-down alternative window within the target boundary with an updated target application window can be achieved at the display level by switching the display of the alternative window to that of the updated target application window, while maintaining the target boundary and scaling ratio. The replacement operation changes the window content seen by the user from the static cached image of the alternative window to the real-time updated image of the target application window. After the replacement, the target boundary displays the updated, actually rendered content of the application, which is still scaled according to the previously determined scaling ratio. For example, if a user clicks a hyperlink in the scaled-down alternative window, the system switches the displayed content at that window location from the cached old webpage image to the new webpage image rendered in real-time by the application, with the new webpage content still scaled according to the scaling ratio of the alternative window.

[0140] It's important to note that during the replacement process, parameters and components such as target boundaries, scaling ratios, and functionalities remain unchanged; only the content displayed within the window updates according to the application's response. In other words, the replacement operation does not trigger a window rearrangement or rescaling, ensuring continuity and smoothness in user interaction.

[0141] In one example, a user opens an online shopping app on a tablet. The app is displayed in a floating window mode, with an initial window size of 40% of the screen width and 50% of the screen height, located in the top left corner of the screen. The app is currently displaying a product list page. The target application window boundary, i.e., the first boundary, is (100, 100, 868, 1380), which is completely within the tablet display's display boundary (0, 0, 1920, 2560). The application believes it is operating within the boundary (100, 100, 868, 1380), and the product list images and text display correctly at this size.

[0142] The user wanted to zoom in to view product image details, so they used two fingers to zoom in on the window, stretching the window width to 75% of the screen width and the height to 80% of the screen height, and then dragged the window to the right side of the screen. The system responded to this first operation, calculating the target boundary as (480, 256, 1920, 2304). The target boundary did not exceed the display boundary.

[0143] In response to the user's second operation of window scaling, the system creates an alternative window, which is then taken over by the display control module. The second boundary of the alternative window is set to the target boundary (480, 256, 1920, 2304), while the first boundary of the target application window remains unchanged at the initial boundary (100, 100, 868, 1380). The system calculates the scaling ratio based on the first boundary and the target boundary: the width scaling ratio is 1.875 times, and the height scaling ratio is 1.6 times. The system detects an inconsistency in the scaling ratios in the two directions and recalculates the height of the target boundary to 2400 pixels based on the aspect ratio of the first boundary (768:1280) and the width of the target boundary (1440).

[0144] The system detected that the recalculated bottom coordinates of the target boundary were 2656, exceeding the display boundary by 2560 (96 pixels). The system determined that the target boundary exceeded the display screen's boundaries and scaled the content of the replacement window by a uniform scaling factor of 1.875. In the scaled product list, product images were enlarged to 1.875 times their original size, and text was enlarged proportionally, allowing users to clearly view product details. However, because the scaled content height was 2400 pixels, while the actual display area height was only 2304 pixels, the bottom 96 pixels of content were not visible.

[0145] The system detects that the target boundary extends beyond the display boundary at the bottom and generates a vertical scrollbar widget at the bottom edge of the window. The scrollbar slider size is set according to the ratio of the visible height (2304) to the total content height (2400), and the slider is initially located at the top of the scrollbar. At this time, the window displays scaled-down alternative window content, which is a cached image of the product list page rendered by the application within the first boundary (100, 100, 868, 1380), scaled down by 1.875 and displayed within the target boundary (480, 256, 1920, 2560).

[0146] A user sees a product of interest in the zoomed-out alternative window and wants to view its details, so they tap the product image area with their finger. The screen coordinates of the tap are (1200, 800), and this tap is the third operation. The system detects that this third operation is performed on the zoomed-out alternative window and needs to map the operation back to the target application window for processing.

[0147] In response to this third operation, the system begins determining the second parameter. First, the system converts the clicked screen coordinates (1200, 800) into coordinates relative to the target boundary, calculating the relative coordinates as (720, 544). Since the content of the substitute window is displayed at a 1.875x scaling ratio, the system divides these relative coordinates by the scaling factor, obtaining the logical coordinates (384, 290) corresponding to the first boundary coordinate system. The system adds these logical coordinates to the starting coordinates of the first boundary, resulting in the second parameter: the target application window coordinates (484, 390). This coordinate parameter indicates that the user clicked at position (484, 390) within the logical coordinate system of the target application window.

[0148] The system applies the second parameter (484, 390) to the target application window, passing this coordinate parameter to the shopping application. Upon receiving the click coordinate parameter, the application determines that the coordinates (484, 390) are located in the image area of ​​the third product in the product list. According to the application's business logic, this click operation should trigger a redirect to the product's details page. The application loads the product's detailed information from the server, including multiple product images, a detailed description, price, reviews, etc., and renders the product details page within the first boundary (100, 100, 868, 1380) of the target application window.

[0149] The updated target application window still has the first boundary (100, 100, 868, 1380), but its content has changed from the product list page to the product details page, and the two displays are completely different. The product details page displays the main product image at the top, and below it are interface elements such as product name, price, specification selection buttons, and add-to-cart button, with a user review list at the bottom.

[0150] The system replaces the scaled alternative window within the target boundary (480, 256, 1920, 2560) with the updated target application window. Specifically, the system stops displaying the cached product list page and instead retrieves the product details page content rendered by the application in real time, scaling this content by 1.875 times before displaying it within the target boundary (480, 256, 1920, 2560). Users see a smooth transition from the product list to the product details page, with the main product image magnified to 1.875 times, and the product name, price, and other text enlarged proportionally, allowing for clear reading of product information.

[0151] Because the product details page is quite long, the total height after scaling remains 2400 pixels, exceeding the actual display area height by 2304 pixels. The review list content in the bottom 96-pixel area is therefore invisible. The vertical scrollbar at the bottom of the window remains visible, allowing users to view the complete product details. Throughout the replacement process, parameters and components such as the target boundary, scaling ratio, and scrollbar remain unchanged; only the content displayed within the window updates from the product list page to the product details page, providing users with a smooth page transition experience.

[0152] As the user continues browsing product details and wishes to view user reviews, they drag the vertical scroll bar upwards with their finger. In response, the system moves the entire product details page upwards, gradually bringing the review list, which was previously outside the display boundaries, into the visible area.

[0153] Understandably, by responding to a third user action on the scaled alternative window, the operation parameters are mapped and applied to the target application window, enabling the application to respond normally to user interaction and update the displayed content. The updated content is then replaced back at the target boundary for scaling display. This maintains the stability of the window scaling state while ensuring the integrity of the application's interactive functions, allowing users to use the application's various functions normally in the scaled window. This achieves an organic combination of window scaling display and application interaction response, improving the user experience and application usability in multi-window scenarios.

[0154] Based on the above display method, this disclosure also provides an electronic device 200. The following will be combined with... Figure 4 The electronic device 200 is described in detail.

[0155] Figure 4 A schematic diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0156] like Figure 4 As shown, the electronic device 200 includes: a display screen 210, a first service module 220, and a second service module 230.

[0157] The display screen 210 has a display area, and the display area has a display boundary 211.

[0158] The first service module 220, located at the application layer, is configured to display a target application window on the display screen 210, the target application window having an initial size.

[0159] The second service module 230, located in the display layer, is configured to respond to a first operation on the target application window, determine the target boundary of the target application window, the first operation being able to change the size and / or position of the target application window; if the target boundary exceeds the display boundary of the display screen, scale the display content of the target application window at least based on the target boundary, so that the scaled display content portion is not visible.

[0160] Exemplarily, the display method of this embodiment is applied to an electronic device. The electronic devices involved in this disclosure include terminals with displays, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminal devices can be mobile phones, smart TVs, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on. This disclosure does not limit the specific technologies or device forms used in the electronic devices.

[0161] The first service module can be a software module or service process running at the application layer in the operating system of an electronic device. The first service module is responsible for managing the operation and window display of the application, including creating application windows, managing window lifecycles, and responding to application UI update requests. For example, the first service module can be the application layer components of ActivityManagerService and WindowManagerService in the Android system, responsible for managing the creation and display of Activity windows. Another example is the window management component of the UIKit framework in the iOS system, responsible for managing the display of application view controllers. Yet another example is the user-mode window manager component in the Windows system, responsible for handling application window requests.

[0162] The application layer can be considered the application runtime layer within an operating system's software architecture. Located above the operating system kernel layer and system service layer, it's the layer where application code runs and the user interface is presented. Modules in the application layer typically run as user-mode processes or services, possessing high privileges and resource access capabilities. For example, in the Android system architecture, the application layer includes system applications and third-party applications, running in the Dalvik virtual machine or ART runtime environment. Similarly, in a layered embedded system architecture, the application layer is the top layer, directly interacting with the user, followed by the middleware layer, operating system layer, and driver layer.

[0163] The second service module can be a software module or service process running in the display layer of an electronic device's operating system. This second service module is responsible for handling low-level graphics operations such as window display control, scaling, transformation, and compositing / rendering, and typically has direct access to display hardware and graphics buffers. For example, the second service module could be the SurfaceFlinger service in the Android system, responsible for compositing the Surface of each application window and outputting it to the display screen. Another example is the Compositor component in the graphics system, responsible for window compositing, effects, and display output. Yet another example is the DisplayServer in the display subsystem, responsible for managing window buffers and display devices.

[0164] The display layer can be a layer in the operating system software architecture responsible for graphics display and compositing. Located below the application layer and above the hardware abstraction layer, the display layer receives display content from the application layer, performs graphics compositing, scaling, rotation, and other transformations, and finally outputs it to the display hardware. The display layer typically runs at the system service permission level and has access to the graphics driver and display device. For example, in the Android system architecture, the display layer includes components such as the SurfaceFlinger service and HardwareComposerHAL, responsible for compositing the Surfaces of various applications into the final framebuffer output. Similarly, in the Linux graphics stack, the display layer includes WaylandCompositor or XServer, responsible for window management and graphics compositing.

[0165] It's important to note that the first service module runs at the application layer, responsible for window management and content rendering, and maintaining the logical state of the windows. The second service module runs at the display layer, responsible for window display control and graphics compositing, handling the actual display effect of the windows. The two modules communicate through a system interface. The first service module passes the rendered graphics content to the second service module, which then scales and transforms the content before outputting it to the display screen.

[0166] For other technical features, please refer to the above description of the display method; they will not be repeated here.

[0167] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0168] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A display method, comprising: Display the target application window on the screen, the target application window having an initial size; In response to a first operation on the target application window, a target boundary of the target application window is determined, wherein the first operation is capable of changing the size and / or position of the target application window; If the target boundary exceeds the display boundary of the display screen, the display content of the target application window is scaled based at least on the target boundary, so that the scaled display content portion is not visible.

2. The method of claim 1, wherein determining the target boundary of the target application window in response to a first operation on the target application window includes: In response to a second operation on the target application window, an alternative window identical to the target application window is displayed, the first operation being applied to the alternative window, and the second operation being the same as or different from the first operation, wherein the target application window has a first boundary restricting the drawing of the target application window, and the alternative window has a second boundary restricting the drawing of the alternative window, the second boundary being the same as or different from the first boundary.

3. The method of claim 2, wherein, in response to a second operation on the target application window, an alternative window identical to the target application window is displayed, comprising: In response to the second operation, the display control module of the electronic device takes over the alternative window based on the second boundary, wherein the first boundary is managed based on the window management service of the electronic device, and the initial display size does not exceed the first boundary.

4. The method according to claim 3, wherein the display control module of the electronic device takes over the alternative window based on the second boundary, comprising: In response to the first operation, the first parameter corresponding to the first operation is applied to the second boundary to obtain the target boundary; The display content of the alternative window is scaled based on the target boundary, and the scaled alternative display content is displayed within the target boundary.

5. The method according to claim 2, further comprising: If the first size ratio of the first boundary is not the same as the second size ratio of the target boundary; Determine the second dimension of the target boundary based on the first dimension and the first dimension ratio of the target boundary; Based on the first dimension and the second dimension, determine the adjusted target boundary; The display content of the alternative window is scaled based on the adjusted target boundary, and the scaled display content of the alternative window is displayed within the scaled target boundary.

6. The method according to claim 2 or 5, further comprising: Determine the scaling ratio based on the first boundary and the target boundary; The alternative window is scaled according to the scaling ratio to obtain a scaled alternative window.

7. The method according to claim 1, further comprising: If the target boundary exceeds the display boundary of the display screen, a functional component corresponding to the target boundary is generated so that the invisible part of the scaled display content can be viewed using the functional component.

8. The method according to claim 7, further comprising: In response to a sliding operation on the scaled alternative window, the portion of the scaled alternative window that extends beyond the display boundary is displayed within the display boundary. The functional component is used to implement the sliding operation on the scaled alternative window.

9. The method according to claim 1, further comprising: In response to a third operation on the scaled alternative window, a second parameter is determined; The second parameter is applied to the target data corresponding to the target application window to obtain an updated target application window, the updated target application window having different display content from the original target application window; Replace the scaled alternative window in the target boundary with the updated target application window.

10. An electronic device, comprising: A display screen having a display area, the display area having a display boundary; The first service module, located at the application layer, is configured to display a target application window on the display screen, the target application window having an initial size; The second service module, located in the display layer, is configured to, in response to a first operation on the target application window, determine the target boundary of the target application window, wherein the first operation can change the size and / or position of the target application window; if the target boundary exceeds the display boundary of the display screen, scale the display content of the target application window at least based on the target boundary, such that the scaled display content portion is not visible.

Images