Display device and display control method for a display

Abstract

The application relates to the technical field of display devices, and particularly discloses a display device and a display control method of a display, which obtains display adjustment layout parameters and mode enabling information, determines a target effective display area, and adjusts a target application window to the target effective area for rendering display according to a corresponding adjustment mode. The display device can flexibly set the target effective display area of the display according to parameters, supports switching of different adjustment modes, and meets diversified scene requirements such as edge avoidance of a curved screen, local display of an industrial / vehicle-mounted screen, screen projection scaling and the like.

Description

Technical Field

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

[0002] In the Android operating system, the window management service provides unified control over application window layout, screen rendering, and input event distribution.

[0003] With the widespread application of irregularly shaped screens, automotive screens, and industrial display equipment, demands such as content avoidance, screen scaling adaptation, and window differentiation management have emerged.

[0004] Although the Android system natively provides DisplayCutout and WindowInsets mechanisms to adapt to irregularly shaped screens, this solution only applies to fixed hardware cutout areas (such as the part of the display screen that is deliberately avoided to reserve physical space for electronic components such as the front camera and earpiece), and cannot dynamically define the effective display area of ​​the screen, resulting in insufficient adaptation flexibility. Summary of the Invention

[0005] This application provides a display control method for a display device and a monitor, which can flexibly set the target effective display area of ​​the monitor and support switching between different adjustment modes, thereby improving the flexibility of adaptation.

[0006] In a first aspect, a display device is provided, comprising: A display for showing a window of an application, the window being used to display the interface of the application; The controller, which is communicatively connected to the display, is configured to: Obtain the user-configured display adjustment layout parameters and mode activation information, wherein the mode activation information is used to indicate the currently used adjustment mode; The target effective display area of ​​the display is obtained by adjusting the layout parameters according to the display. According to the adjustment mode corresponding to the mode activation information, the window adjustment algorithm corresponding to the adjustment mode is invoked to adjust the window of the target application to the target effective display area for rendering and display.

[0007] The display device provided in this application embodiment determines the target effective display area by acquiring display adjustment layout parameters and mode activation information, and adjusts the target application window to the target effective area for rendering and display according to the corresponding adjustment mode. It can flexibly set the target effective display area of ​​the display according to the parameters and supports switching between different adjustment modes to meet the diverse needs of scenarios such as curved screen edge avoidance, partial display of industrial / vehicle screens, and projection scaling.

[0008] In some embodiments, the controller, based on the mode enable information, calls the adjustment mode corresponding to the adjustment mode to adjust the window of the target application to the target effective display area for rendering and display, and is configured as follows: When the adjustment mode indicated by the mode enable information is the proportional shrinkage mode, a global scaling factor is calculated based on the screen size of the display and the display adjustment layout parameters. The window of the target application is scaled and translated based on the global scaling factor to adjust the window of the target application to be rendered and displayed within the target effective display area.

[0009] The display device provided in this application embodiment, when enabling the proportional shrinking mode, calculates a global scaling factor based on the screen size and layout parameters, and uses the global scaling factor to scale and translate the window to adapt to the target effective display area. It can perform geometric transformations only on the screen layer without changing the application's logical window boundaries, so the application is unaware of the area adjustment. It is suitable for screen projection and whole-device screen scaling scenarios, achieving overall uniform scaling of the full-screen image by relying on a unified global scaling factor.

[0010] In some embodiments, the controller is further configured to: Obtain the scaling matrix for scaling the window of the target application, and the translation matrix for translating it; The contraction matrix and translation matrix are concatenated to the original window transformation matrix to generate a composite transformation matrix; If a user touch event is detected in the target valid display area, the touch coordinates of the touch event are obtained; The touch coordinates are inversely operated on based on the composite transformation matrix to obtain logical coordinates, and the touch event is responded to based on the logical coordinates.

[0011] Conventional global scaling solutions often require intrusive modifications to the input service to achieve coordinate compensation, resulting in high system coupling and significant costs for version upgrades and adaptations. The display device provided in this application constructs a shrinking matrix and a translation matrix, which are then combined with the native window transformation matrix to form a composite transformation matrix. Using the inverse operation of the composite transformation matrix, screen touch coordinates are converted into logical coordinates within the application window and events are responded to. By reusing the native window transformation chain, merging the transformation matrices, and relying on native inverse operations to complete the coordinate transformation, no modifications to the underlying input module are required. This achieves synchronization between screen changes and touch interaction, eliminates touch offset issues, and reduces system modification costs.

[0012] In some embodiments, before scaling and translating the window of the target application based on the global scaling factor, the controller is further configured to: Get the scaling mode whitelist; The application displayed in the foreground that is not recorded in the scaling mode whitelist is identified as the target application.

[0013] The display device provided in this application embodiment sets a scaling mode whitelist. Applications within the whitelist maintain their original size and position, while other applications are scaled as target applications. This solves the defect of not being able to differentiate window control in a globally uniform scaling scenario. It allows critical system windows such as the status bar and floating pop-ups to remain unaffected by screen scaling, maintaining normal interactive sizes; it balances the overall screen scaling requirements with the original display requirements of special windows, improving system interface consistency and usability.

[0014] In some embodiments, the controller scales and translates the window of the target application based on the global scaling factor to display the window of the target application within the target valid display area, and is configured as follows: The translation and scaling matrices of the surface control layers in the target application are uniformly set to display the surface control layers in the target effective display area, so that the surface control layers remain in a constant relative position within the application window.

[0015] Configuring transformation parameters for each child window individually can easily lead to misalignment of the relative positions of multiple windows within the same application, making development and maintenance cumbersome. The display device provided in this application applies a uniform transformation to the layers, causing all sub-layers within the application to transform synchronously, preserving the relative layout relationships between windows, simplifying layer scheduling logic, and improving the stability of multi-window rendering.

[0016] In some embodiments, when the target application includes a desktop wallpaper application, the controller scales and translates the window of the target application based on the global scaling factor to adjust the window of the target application to be rendered and displayed within the target effective display area, and is configured as follows: Calculate the center point of the target's effective display area; The scaling size of the desktop wallpaper is calculated based on the original size of the wallpaper in the desktop wallpaper application and the global scaling factor; The absolute placement coordinates of the desktop wallpaper are calculated based on the center point and the scaling dimensions; Based on the absolute placement coordinates and the scaling size, the window of the desktop wallpaper application is adjusted to the target effective display area for rendering and display.

[0017] Wallpaper layers are typically larger than the screen, and scaling with the top-left corner aligned can cause image shift and parallax scrolling failure. The display device provided in this application calculates the center point of the target effective area, combines the original wallpaper size with the scaling factor to obtain the scaled size, solves the absolute placement coordinates of the wallpaper, and completes the display. The wallpaper is placed with the center as the anchor point, ensuring it remains centered during scaling, avoiding image misalignment, and guaranteeing the proper functioning of the desktop wallpaper's visual effects and parallax effects.

[0018] In some embodiments, the controller, based on the mode enable information, calls the adjustment mode corresponding to the adjustment mode to adjust the window of the target application to the target effective display area for rendering and display, and is configured as follows: When the adjustment mode indicated by the mode enable information is margin indentation mode, the window boundaries of the target application window that are less than a preset distance threshold from the screen edge are indented. Based on the indented window boundaries, the window of the target application is adjusted to the target effective display area for rendering and display.

[0019] The display device provided in this application embodiment enables a margin indentation mode, performing indentation only on window boundaries close to the screen edge, based on boundary correction rendering. This differs from globally uniform forced indentation on all four sides, only avoiding indentation on boundaries that fit the screen edge. In split-screen scenarios, adjacent boundaries between split screens do not need indentation, avoiding unnecessary blank gaps caused by windows on both sides of the dividing line simultaneously indenting; in curved screen and irregularly shaped screen scenarios, it achieves safe content avoidance at screen edges, balancing display safety and screen utilization.

[0020] In some embodiments, the controller acquires the target application, configured to: Identify the application that is in a split-screen scenario as the target application; The application displayed in the foreground that is not in a split-screen scenario and is not recorded in the margin mode whitelist is identified as the target application.

[0021] The display device provided in this application disables the margin mode whitelist in split-screen scenarios, and all windows uniformly implement indentation; in non-split-screen scenarios, it relies on the whitelist to select target applications. When multiple windows are displayed side by side in split-screen mode, if some windows are exempt from indentation while others are indented, it will cause inconsistent widths between the left and right windows, resulting in a chaotic interface layout. The exemption mechanism is forcibly disabled in split-screen scenarios to ensure that the layout rules of all split-screen windows are consistent; the exemption capability is retained in non-split-screen scenarios to take into account the differentiated needs of single-window scenarios, balancing visual regularity and configuration flexibility.

[0022] In some embodiments, the display adjustment layout parameters include: the pixel values ​​of the margins on all four sides, and the controller, based on the display adjustment layout parameters, obtains the target effective display area corresponding to the display, and is configured as follows: Based on the pixel values ​​of the margins of the four sides, the original layout boundaries of the display are adjusted to obtain the target effective display area.

[0023] The display device provided in this application directly corrects the window layout boundaries at the pixel level. After the application obtains the updated effective area, it actively reflows the layout content, eliminating the image blurring problem caused by layer scaling. It supports dynamically customizing arbitrary pixel margins, breaking through the limitation that native display cutouts can only use hardware-fixed avoidance areas, and adapting to various custom safety area scenarios.

[0024] Secondly, embodiments of this application provide a display control method for a display, comprising: Obtain the user-configured display adjustment layout parameters and mode activation information, wherein the mode activation information is used to indicate the currently used adjustment mode; The target effective display area of ​​the monitor is obtained by adjusting the layout parameters according to the display. According to the adjustment mode corresponding to the mode activation information, the window adjustment algorithm corresponding to the adjustment mode is invoked to adjust the window of the target application to the target effective display area for rendering and display. Attached Figure Description

[0025] Figure 1 A flowchart of a control method in a display device provided in an embodiment of this application; Figure 2 This is a schematic diagram of a target effective display area provided in an embodiment of this application; Figure 3 This application provides a schematic diagram illustrating the implementation process of a control method in a display device according to an embodiment of the present application. Figure 4 A schematic diagram illustrating a split-screen mode display provided in an embodiment of this application; Figure 5 This is a schematic diagram illustrating the implementation process of step S113 provided in an embodiment of this application. Detailed Implementation

[0026] To make the objectives and implementation methods of this application clearer, the exemplary implementation methods of this application will be clearly and completely described below with reference to the accompanying drawings of the exemplary embodiments of this application. Obviously, the exemplary embodiments described are only some embodiments of this application, and not all embodiments.

[0027] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0028] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0029] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0030] The display device provided in this application can have various implementation forms. The display device refers to terminal hardware equipped with an Android window management system, including in-vehicle displays, industrial touch terminals, irregularly shaped screen smart devices, tablets, etc.; the hardware has graphics rendering, window management, and touch input capabilities. The control method for the display device provided in this application can be implemented by a controller for the display device. The controller controls the operation of the display device and responds to user operations through various software control programs stored in the memory. The controller controls the overall operation of the display device.

[0031] In some embodiments, the controller includes at least one of a central processing unit (CPU), a video processor, an audio processor, a graphics processing unit (GPU), RAM (Random Access Memory), etc., for input / output, a first to an nth interface, a communication bus, etc. The display device includes a display for presenting images, a driving component for driving image display, a component for receiving image signals output from the controller, displaying video content, image content, and a menu control interface, and a user-controlled UI interface. The display can be a liquid crystal display, an OLED display, or a projection display, and can also be a projection device and a projection screen. The display shows the window of an application, which is used to display the interface of the application. The interface is the window layer image corresponding to each application and system component (status bar, wallpaper, floating window) in the Android system. The window is the basic carrier unit for system graphics rendering.

[0032] To facilitate a further understanding of the technical solutions in some embodiments of this application, the technical solutions of the display device and how these solutions solve the aforementioned technical problems are described in detail below with reference to specific embodiments and accompanying drawings. The embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of this application.

[0033] Figure 1 A flowchart of a control method in a display device provided in an embodiment of this application is shown below. Figure 1 As shown, the controller is configured to perform the following steps: Step S101: Obtain the user-configured display adjustment layout parameters and mode activation information.

[0034] In this embodiment, the display adjustment layout parameters are user-configured area constraint parameters, including two types of mode parameters: margin indentation mode (pixel margins on the left, top, right, and bottom edges of the screen); and proportional shrinkage mode (shrinking the inner margins on all four sides), used to calculate the scaling range. Mode activation information indicates the currently used adjustment mode (i.e., identifies which adjustment mode is currently active). In this embodiment, the above adjustment modes may include: margin indentation mode and proportional shrinkage mode. The two adjustment modes are independent of each other and can be selectively enabled or both disabled.

[0035] In this embodiment, dynamic configuration is supported, which can be configured via ADB commands, the system configuration interface, and upper-layer service commands. After receiving the command, the controller saves the four side margins / shrinking inner margins to the corresponding management object (DisplayContent) of the display, and records the current mode activation information. The display layout parameters and mode activation information can be dynamically modified at runtime without restarting the system.

[0036] Step S102: Obtain the target effective display area corresponding to the display by adjusting the layout parameters according to the display.

[0037] In this embodiment, the target effective display area is a rectangular area within the physical screen of the display that allows the application window to normally display interactive content; curved edges, obstructed areas, and other screen areas unsuitable for interaction are excluded. Figure 2 This is a schematic diagram of a target effective display area provided in an embodiment of this application, such as... Figure 2 As shown, 1 represents the physical screen area, and 2 represents the target effective display area, which is dynamically adjusted according to the display layout parameters.

[0038] In this embodiment, the controller reads the display adjustment layout parameters and calculates them based on the original screen resolution rectangle: If the margin indentation mode is enabled, the original screen boundaries are superimposed / subtracted by the margin pixels of the four sides to calculate the effective rectangle available for window layout; if the proportional shrinking mode is enabled, the target rectangle after layer scaling is calculated by shrinking the inner margins of the four sides from the full-screen rectangle inward. The same display supports independent calculation of a set of parameters, and multi-display scenarios can each configure independent area parameters.

[0039] Step S103: According to the adjustment mode corresponding to the mode activation information, call the window adjustment algorithm corresponding to the adjustment mode to adjust the window of the target application to the target effective display area for rendering and display.

[0040] In this embodiment, the adjustment mode includes two modes: a margin indentation mode for modifying window layout boundaries, where the application actively rearranges the page; and a proportional shrinking mode for scaling and panning the layer matrix, where the application's logical size remains unchanged. The target application's window is a whitelisted window that requires display area adjustment; exempted windows are not part of the target application's window and maintain their original display state. Rendering and display are performed by the controller using the Surface layer mechanism to composite the window image and push it to the display for output.

[0041] In this embodiment, the controller identifies the current mode activation information and uses the corresponding window adjustment algorithm to complete the window adjustment. For the margin indentation mode, the window adjustment algorithm includes: correcting the window boundaries, driving the application to receive the size change signal, and reflowing and rearranging the content within the new boundary; and filtering target windows based on whitelists and split-screen rules. For the proportional shrinking mode, the window adjustment algorithm includes: calculating the global scaling factor, achieving overall window scaling and translation through SurfaceControl matrix transformation; synchronously updating the window transformation matrix to ensure correct touch coordinate mapping, and applying an inverse transformation to whitelisted windows. Finally, all target application windows are constrained within the target effective display area to complete layer compositing and output to the display.

[0042] The display device provided in this application embodiment determines the target effective display area by acquiring display adjustment layout parameters and mode activation information, and adjusts the target application window to the target effective area for rendering and display according to the corresponding adjustment mode. It can flexibly set the target effective display area of ​​the display according to the parameters and supports switching between different adjustment modes to meet the diverse needs of scenarios such as curved screen edge avoidance, partial display of industrial / vehicle screens, and projection scaling.

[0043] In some embodiments, when the enabled adjustment mode is a proportional shrinkage mode, step S103 can be implemented through the following steps: Step S1031: When the adjustment mode indicated by the mode enable information is the proportional shrinkage mode, calculate the global scaling factor based on the screen size of the display and the display adjustment layout parameters.

[0044] In this embodiment, the screen size of the display is the physical resolution of the display, including the original screen width and original height, which are fixed base pixel values. The display layout adjustment parameters in this mode specifically refer to the four-sided shrinkage inner margins (left, top, right, and bottom white space pixels), used to define the blank areas that need to be left around the screen. The global scaling factor is divided into a horizontal scaling factor (scaleX) and a vertical scaling factor (scaleY). These represent the overall scaling ratio of the image; they are obtained by dividing the target effective area size by the original screen size. All target windows on the entire display share the same scaling factor, ensuring a uniform image scaling ratio.

[0045] In this embodiment, the controller reads the original screen width (displayW) and original height (displayH); and reads the left, top, right, and bottom margins of the collapsed layout. First, the target effective area size is calculated: target area width targetW = displayW left Right, target area height targetH = displayH top Next, calculate the scaling factors: scaleX = targetW / displayW; scaleY = targetH / displayH. These factors are globally uniform parameters for the display and are reused by all target windows on the same screen, eliminating the need for individual calculations for each window. When parameters change dynamically, the calculation is re-executed, synchronously updating the transformation parameters of all windows.

[0046] Step S1032: Scaling and translating the window of the target application based on the global scaling factor, so as to adjust the window of the target application to the target effective display area for rendering and display.

[0047] In this embodiment, the window of the target application is a window that has been whitelisted and requires layer scaling and translation transformation; the exempted window does not execute this scaling logic, and scaling and translation are implemented by relying on the affine transformation of the Android graphics system SurfaceControl: scaling controls the size of the screen, and translation moves the shrunk overall screen to the starting coordinate position of the target effective area.

[0048] In this embodiment, the controller generates a two-dimensional affine transformation matrix, in which scaleX and scaleY are loaded to achieve proportional scaling of the image; simultaneously, translation offsets (left, top) are configured to shift the scaled image to the right and down, ensuring the entire image falls within the target effective area. The transformation is applied to the Surface layer corresponding to the window.

[0049] Existing technologies, when requiring the image to be scaled down to a specific area of ​​the screen, generally use the method of modifying the window layout boundaries, which triggers application page reflow and results in poor compatibility. The display device provided in this application pre-calculates a globally unified scaling factor based on the screen size and layout parameters, and uses layer scaling + translation to achieve screen constraints. The application logic window size remains unchanged, avoiding display anomalies caused by frequent application redraws; all target windows use a uniform scaling ratio, ensuring consistent multi-window display and meeting the needs of business scenarios requiring overall screen scaling, such as projection, industrial displays, and multi-screen collaboration. When the proportional shrinking mode is enabled, the global scaling factor is calculated based on the screen size and layout parameters, and the scaling factor is used to scale and translate the window to adapt to the target effective display area. It avoids modifying the application logic window boundaries, only performing geometric transformations on the screen layers, so the application is unaware of the area adjustment. It is suitable for projection and whole-device screen scaling scenarios, achieving overall uniform scaling of the entire screen image by relying on a unified global scaling factor.

[0050] In some embodiments, after step S103 Figure 3 This application provides a schematic diagram illustrating the implementation flow of a control method in a display device, as shown in the embodiment. Figure 3 As shown, the controller is also configured to perform the following steps: Step S104: Obtain the shrinking matrix for scaling the window of the target application, and the translation matrix for translating.

[0051] In this embodiment, the shrinking matrix is ​​a two-dimensional affine transformation matrix, carrying global scaling coefficients scaleX and scaleY, used to achieve proportional scaling of the entire window screen. The translation matrix is ​​a two-dimensional affine transformation matrix, carrying the target region's initial offset (insets.left, insets.top), used to translate the scaled screen to the target's effective display area.

[0052] In this embodiment, the controller constructs a shrinkage matrix using the calculated global scaling factor and a translation matrix using the shrinkage inner margin. The two matrix parameters are dynamically updated following the layout configuration; when the user modifies the display layout parameters, the two sets of matrices are regenerated.

[0053] Step S105: The shrinkage matrix and translation matrix are concatenated into the original window transformation matrix to generate a composite transformation matrix.

[0054] In this embodiment, the native window transformation matrix is ​​the inherent transformation matrix of the Android system window itself, used to carry the inherent transformations of the window itself, such as displacement, rotation, and layer offset; it is natively maintained by the system window management module. Concatenation (matrix multiplication / postConcat) is a computer graphics matrix operation method that superimposes the shrinking and translation transformations onto the original window transformations to form a unified transformation result. The composite transformation matrix is ​​the final complete transformation matrix that merges the native window transformations, shrinking transformations, and translation transformations, and is bound to the corresponding window.

[0055] In this embodiment, the controller, within the window transformation matrix acquisition interface, sequentially concatenates the shrinkage matrix and translation matrix to the native window transformation matrix according to the affine transformation operation rules to obtain a composite transformation matrix. This composite transformation matrix is ​​then associated with the current window for the Android input subsystem to read. This differs from simply replacing the window matrix: it retains all original window transformation effects and only adds global display shrinkage capabilities.

[0056] Step S106: If a user touch event is detected in the target effective display area, the touch coordinates of the touch event are obtained.

[0057] In this embodiment, the touch event is an input event generated by the user touching the display, which is reported by the hardware to the system input subsystem. The touch coordinates (screen physical coordinates) are the original screen pixel coordinates with the upper left corner of the display screen as the origin, which are the original coordinates of the human touch position.

[0058] In this embodiment, when a user touches the screen, the touch hardware reports the original screen coordinates; the input subsystem identifies the window corresponding to the touch point, and the controller reads the original screen touch coordinates, with the coordinate reference being the physical screen coordinate system.

[0059] Step S107: Perform inverse operation on the touch coordinates based on the composite transformation matrix to obtain logical coordinates, and respond to the touch event based on the logical coordinates.

[0060] In this embodiment, the inverse operation (inverse matrix transformation) is to obtain the inverse matrix of the composite transformation matrix, thereby achieving a reverse coordinate conversion. The logical coordinates inside the window are the window coordinates recognized by the application itself; the application determines the click position of buttons and controls based on these coordinates.

[0061] In this embodiment, the controller uses a composite transformation matrix to obtain the inverse matrix, reverses the original screen coordinates, eliminates the coordinate offset caused by scaling and translation, and converts the coordinates to window logical coordinates that the application can recognize. The system encapsulates the converted coordinates into a touch event and sends it to the application, which then executes the control click response normally.

[0062] Conventional global scaling solutions often require intrusive modifications to the input service to achieve coordinate compensation, resulting in high system coupling and significant costs for version upgrades and adaptations. The display device provided in this application constructs a shrinking matrix and a translation matrix, which are then combined with the native window transformation matrix to form a composite transformation matrix. Using the inverse operation of the composite transformation matrix, screen touch coordinates are converted into logical coordinates within the application window and events are responded to. By reusing the native window transformation chain, merging the transformation matrices, and relying on native inverse operations to complete the coordinate transformation, no modifications to the underlying input module are required. This achieves synchronization between screen changes and touch interaction, eliminates touch offset issues, and reduces system modification costs.

[0063] In some embodiments, prior to step S103, the controller is further configured to perform the following steps: Step S1: Obtain the scaling mode whitelist; In this embodiment, the scaling mode whitelist is a separate list specifically for the proportional shrinking mode, storing window matching rules (window title, title prefix, etc.) that need to be exempted from global scaling transformation. The scaling mode whitelist is independent of the margin indentation mode whitelist; the two adjustment mode configurations are isolated from each other and take effect independently.

[0064] In this embodiment, the controller reads a pre-configured scaling mode whitelist; it supports dynamically adding, deleting, and querying matching rules via external commands. During the window rendering traversal phase, the information of the current window is matched one by one with the list in the scaling mode whitelist to determine whether the current window belongs to the exemption object.

[0065] Step S2: Apply an inverse scaling matrix and an inverse translation matrix to the application in the scaling mode whitelist to maintain the original display size and position of the application in the scaling mode whitelist.

[0066] In this embodiment, the inverse scaling matrix is ​​the inverse of the global scaling matrix, with scaling factors invScaleX = 1 / scaleX and invScaleY = 1 / scaleY. Its function is to counteract the globally applied screen shrinkage effect. The inverse translation matrix is ​​used to counteract the global translation offset transformation matrix, eliminating the coordinate offset caused by the initial whitespace of the target area. The combination of the inverse scaling matrix and the inverse translation matrix forms an inverse transformation, counteracting the TDA global scaling and translation transformation uniformly applied by the upper layer; the compensated window is unaffected by the global shrinkage strategy.

[0067] In this embodiment, the coordinates after inverse transformation can be represented as: newPosX = (surfacePosition.x - insets.left) / scaleX; newPosY = (surfacePosition.y - insets.top) / scaleY. The reverse scaling matrix and reverse translation matrix can be represented as: transaction.setMatrix(surfaceControl, invScaleX, 0, 0, invScaleY), transaction.setPosition(surfaceControl, newPosX, newPosY).

[0068] In this embodiment, the system applies a global scaling and translation matrix to the display area of ​​most applications, causing windows on the whitelist to shrink accordingly. After the controller identifies a whitelisted window, it overlays an additional inverse transformation matrix: using reverse scaling to offset the shrinking effect and reverse translation to offset the whitespace offset. The two transformations cancel each other out, ultimately restoring the window to its original screen size and coordinates. Simultaneously, the global shrinkage matrix is ​​no longer added to the window transformation matrix interface, ensuring that touch coordinates are synchronously restored to their original logic and preventing touch misalignment.

[0069] Step S3: Identify the application that is not in the application and is not in the scaling mode whitelist as the target application.

[0070] In this embodiment, the target application is a window that needs to undergo global scaling and translation transformations and be included in the target's effective display area for rendering; it is a window that is not on the whitelist.

[0071] In this embodiment, if the match is successful, an inverse transformation is applied, and global scaling is exempted; if the match fails, it is determined to be the target application, and scaling, translation, and touch coordinate conversion logic are executed.

[0072] The display device provided in this application embodiment sets a scaling mode whitelist, applies inverse scaling and translation matrices to applications within the whitelist to maintain their original size and position, and performs scaling on other applications as target applications. This solves the defect of not being able to differentiate window control in a globally uniform scaling scenario. It can ensure that critical system windows such as status bars and floating pop-ups are not affected by screen scaling, maintaining normal interactive sizes; it takes into account both the overall screen scaling requirements and the original display requirements of special windows, improving the consistency of the system interface and the usability of interaction.

[0073] In some embodiments, the controller scales and translates the window of the target application based on the global scaling factor to adjust the window of the target application to be rendered and displayed within the target effective display area, and is configured as follows: The translation and scaling matrices of the surface control layers in the target application are uniformly set to display the surface control layers in the target effective display area, so that the surface control layers remain in a constant relative position within the application window.

[0074] In this embodiment, the surface control layer corresponds to the Android system's SurfaceControl, a core object used by the system to manage layer rendering, position, and transformation. An application task contains multiple window sub-layers, all managed by the surface control layer. The translation and scaling matrices are uniformly set so that transformations are not configured individually for each sub-window layer, but rather a set of global transformation parameters is applied upwards to the higher-level surface control layer. The relative positions of the surface control layer remain unchanged, ensuring that the left-right and up-down relative coordinate relationships between multiple sub-windows and sub-layers within the same application task are not disrupted by scaling and translation.

[0075] In this embodiment, for windows not within the target's effective display area (such as system overlays), the transformation is calculated and applied separately in the `applyDisplayContractTransform` method of `WindowState`: `absX` (absolute X coordinates) = `surfacePosition.x` + `surfaceInsetsOffset.x` + `parentOffset.x`; `absY` (absolute Y coordinates) = `surfacePosition.y` + `surfaceInsetsOffset.y` + `parentOffset.y`; newAbsX = insets.left + absX scaleX newAbsY = insets.top + absY scaleY; newRelX = newAbsX - surfaceInsetsOffset.x - parentOffset.x; newRelY = newAbsY - surfaceInsetsOffset.y - parentOffset.y; Here, `surfacePosition.x` and `surfacePosition.y` represent the current layer's base position relative to its parent layer, and `surfaceInsetsOffset.x` and `surfaceInsetsOffset.y` represent the layer's internal margin offset. `parentOffset.x` and `parentOffset.y` represent the layer offset from the parent layer; when multiple layers are nested, the coordinate offset generated by the upper parent layer. `insets.left` and `insets.top` represent the global translation offset of the top-left corner of the target's effective area in proportional shrinking mode (the top-left offset value of the screen's shrinkage and whitespace). `newAbsX` and `newAbsY` are the layer's new absolute screen coordinates after global scaling and translation calculations, and `newRelX` and `newRelY` are the layer's new relative coordinates relative to its parent layer after the update, used to finally assign values ​​to the layer's rendering parameters.

[0076] In this embodiment, the controller locates the top-level surface control layer that carries the target application task; it generates a scaling matrix based on a global scaling factor and a translation matrix based on shrinking inner margins, and directly sets a uniform matrix transformation for this top-level surface control layer. After the transformation is applied to the top-level layer, all child windows and sub-layers under this task automatically inherit the scaling and translation effects. Since all sub-layers transform synchronously with the same parent layer, the offset difference between layers remains constant, and the relative positions of each window within the same application remain unchanged.

[0077] Configuring transformation parameters for each child window individually can easily lead to misalignment of the relative positions of multiple windows within the same application, making development and maintenance cumbersome. The display device provided in this application applies a uniform transformation to the layers, causing all sub-layers within the application to transform synchronously, preserving the relative layout relationships between windows, simplifying layer scheduling logic, and improving the stability of multi-window rendering.

[0078] In some embodiments, when the target application includes a desktop wallpaper application, the controller can perform step S103 by the following steps: Step S1033: Calculate the center point of the target effective display area.

[0079] In this embodiment, the desktop wallpaper application is a special window layer corresponding to the Android system wallpaper service; the original size of the wallpaper layer is usually larger than the physical screen size, used to achieve the desktop parallax scrolling effect, and is a special window that is different from ordinary applications. The center point of the target effective display area is the geometric center coordinate of the visible rectangular area defined by the inner margins of the four sides in the proportional shrinking mode, which serves as the reference anchor point for wallpaper placement.

[0080] In this embodiment, the contracted inner margin and the width and height of the target effective area are read and calculated using the following formula: Center x-coordinate = left inner margin + target effective area width / 2; Center ordinate = Top inner margin + Target effective area height / 2; In this embodiment of the application, the coordinates of the center point of the target visible area obtained by solving can be used as the wallpaper positioning reference.

[0081] Step S1034: Calculate the scaling size of the desktop wallpaper based on the original size of the wallpaper application and the global scaling factor.

[0082] In this embodiment, the original size of the wallpaper is the width and height in pixels of the wallpaper layer material itself, and is not constrained by the screen resolution. The scaled size is the width and height of the wallpaper layer obtained after scaling it proportionally according to a global scaling factor.

[0083] In this embodiment of the application, the scaling size may include: the scaled wallpaper width and the scaled wallpaper height, wherein the scaling wallpaper width is calculated as: scaled wallpaper width = original wallpaper width × scaleX, and the scaling wallpaper height is calculated as: scaled wallpaper height = original wallpaper height × scaleY.

[0084] In this embodiment, the wallpaper layer is scaled proportionally according to a globally uniform scaling factor to ensure that the wallpaper image is not stretched or distorted.

[0085] Step S1035: Calculate the absolute placement coordinates of the desktop wallpaper application based on the center point and the scaling size.

[0086] In this embodiment, the absolute placement coordinates are the screen pixel coordinates of the final placement of the wallpaper layer, with the top left corner of the screen as the origin.

[0087] In this embodiment, the absolute placement coordinates of the wallpaper are calculated backward from the center point of the target area. The absolute placement coordinates include the coordinates of the top left corner. The formula for calculating the top left corner coordinate is: Top left corner X coordinate of wallpaper = x-coordinate of the center point of the area. After scaling, the wallpaper width is divided by 2, and the Y-coordinate of the top-left corner of the wallpaper equals the ordinate of the center point of the area. Wallpaper height after scaling / 2.

[0088] Wallpapers can be centered using absolute placement coordinates.

[0089] Step S1036: Based on the absolute placement coordinates and the scaling size, adjust the window of the desktop wallpaper application to the target effective display area for rendering and display.

[0090] In this embodiment, the placement based on absolute placement coordinates abandons the conventional top-left corner alignment strategy, ensuring that the geometric center of the scaled wallpaper layer coincides with the center of the target effective area.

[0091] In this embodiment, the controller sends the calculated placement coordinates and scaling dimensions to the graphics compositing module to complete the wallpaper layer rendering and positioning; the center of the wallpaper layer always fits the center of the target area.

[0092] Wallpaper layers are typically larger than the screen, and scaling with the top-left corner aligned can cause image shift and parallax scrolling failure. The display device provided in this application calculates the center point of the target effective area, combines the original wallpaper size with the scaling factor to obtain the scaled size, solves the absolute placement coordinates of the wallpaper, and completes the display. The wallpaper is placed with the center as the anchor point, ensuring it remains centered during scaling, avoiding image misalignment, and guaranteeing the proper functioning of the desktop wallpaper's visual effects and parallax effects.

[0093] In some embodiments, step S103 can be implemented by the following steps: Step S11: When the adjustment mode indicated by the mode enable information is margin indentation mode, the window boundary of the target application window that is less than the screen edge by a preset distance threshold is indented.

[0094] In this embodiment, the display layout adjustment parameters may include screen margin parameters. These margin parameters are specific to the margin indentation mode and consist of pixel values ​​for the left, top, right, and bottom edges where a buffer zone needs to be reserved. These parameters define the safe buffer zone at the screen edges. The margin indentation mode differs from the layer transformation of the proportional shrinking mode; this mode directly modifies the window layout boundaries. Applications can recognize boundary changes and actively rearrange interface content, eliminating image scaling and blurring issues. The target application is a selected window that requires boundary indentation adjustment; exempted windows do not undergo boundary correction.

[0095] In this embodiment, a preset distance threshold is used to determine whether the window boundary is close to the physical edge of the screen. In the actual implementation, the threshold is set to 0: when the window boundary is close to the screen edge, it is determined that the condition is met, corresponding to the intelligent split-screen determination logic in the scheme. Window boundary indentation is to correct the original layout rectangle boundary of the window, move it inward by a specified margin of pixels, and reduce the usable layout range of the window.

[0096] In this embodiment, the controller determines the positional relationship between the four boundaries of the target window and the four sides of the screen one by one: if a certain boundary of the window is close to the edge of the screen (the distance is less than a threshold), then the corresponding margin is applied inward in that direction; if the window boundary is close to the split line and far from the edge of the screen, then no indentation is performed in that direction.

[0097] In this embodiment, in the split-screen mode, the middle boundary between two adjacent windows is not indented; only the boundaries of the left and right outer edges of the screen are indented to avoid creating double blank gaps along the dividing line. Figure 4 This is a schematic diagram illustrating a split-screen mode display provided in an embodiment of this application, as shown below. Figure 4 As shown, Applications 3 and 4 only indent the window boundaries that are attached to the outer edge of the screen, but do not indent the middle boundaries.

[0098] Step S13: Based on the indented window boundary, adjust the window of the target application to the target effective display area for rendering and display.

[0099] In this embodiment, the indented window boundary is the corrected effective window layout rectangle, which serves as the constraint boundary for the application rendering content.

[0100] In this embodiment, the controller sends the corrected boundary to the window layout calculation module; the application senses the change in the available window size, autonomously completes page layout reflow and content rearrangement, and the application content is constrained to be rendered and displayed within the indented boundary.

[0101] The display device provided in this application embodiment, when enabling the margin indentation mode, only performs indentation on the window boundaries close to the screen edge, based on boundary correction rendering. This differs from globally uniform forced indentation on all four sides; it only avoids indentation on boundaries that fit the screen edge. In split-screen scenarios, adjacent boundaries of the split screen do not need indentation, avoiding unnecessary blank gaps caused by simultaneous indentation of windows on both sides of the dividing line. In curved screen and irregularly shaped screen scenarios, it achieves safe content avoidance at the screen edge, balancing display safety and screen utilization.

[0102] In some embodiments, before the controller indents the window boundary of the target application whose distance from the screen edge is less than a preset distance threshold, it is configured to: Step S111: Determine whether the application is in a split-screen scenario.

[0103] In this embodiment, the split-screen scenario is the multi-tasking operation mode of the Android system, where two or more windows are displayed side by side on the screen, and there are split-screen dividing lines between the windows.

[0104] In this embodiment, the controller reads the task area information to which the window belongs, identifies the window layout, determines whether the current window belongs to a split-screen multi-task layout with left and right or top and bottom side by side, and distinguishes between split-screen scenarios and full-screen single-window scenarios.

[0105] Step S112: Identify the application in the split-screen scenario as the target application.

[0106] In this embodiment, the margin mode whitelist is a separate list dedicated to margin indentation mode, which stores window matching rules that need to be exempted from boundary indentation adjustment; it is independent of the proportional shrinkage mode whitelist and does not interfere with each other.

[0107] In this embodiment, when a split-screen scenario is detected, the whitelist matching process is skipped, and all split-screen windows are identified as the target application, with margin indentation logic being executed uniformly. If a split-screen scenario allows some windows to be exempt from indentation while others are indented, the effective widths of the side-by-side windows will be inconsistent, resulting in inconsistent interface layout lengths and visual clutter.

[0108] Step S113: Among the applications displayed in the foreground, those that are not in a split-screen scenario and are not recorded in the margin mode whitelist are identified as the target applications.

[0109] In this embodiment of the application, in a full-screen single-window scenario, the whitelist matching mechanism is enabled normally; the window information is compared with the whitelist rules, and if the match is successful, indentation is exempted; if the match fails, it is determined to be the target application, and boundary indentation is performed.

[0110] The display device provided in this application disables the margin mode whitelist in split-screen scenarios, and all windows uniformly implement indentation; in non-split-screen scenarios, it relies on the whitelist to select target applications. When multiple windows are displayed side by side in split-screen mode, if some windows are exempt from indentation while others are indented, it will cause inconsistent widths between the left and right windows, resulting in a chaotic interface layout. The exemption mechanism is forcibly disabled in split-screen scenarios to ensure that the layout rules of all split-screen windows are consistent; the exemption capability is retained in non-split-screen scenarios to take into account the differentiated needs of single-window scenarios, balancing visual regularity and configuration flexibility.

[0111] In some embodiments, the display adjustment layout parameters include: the pixel values ​​of the margins on all four sides, and the controller, based on the display adjustment layout parameters, obtains the target effective display area corresponding to the display, and is configured as follows: Based on the pixel values ​​of the margins of the four sides, the original layout boundaries of the display are adjusted to obtain the target effective display area.

[0112] In this embodiment, the pixel values ​​of the four side margins can include: the pixel values ​​of the left side margin, the top side margin, the right side margin, and the bottom side margin, all using pixels as the unit of measurement and supporting independent configuration of values. The original layout boundary is the rectangular boundary corresponding to the full screen of the display, with the top left corner of the screen as the origin, representing the full-screen rectangular area without any indentation adjustment. Overlaying the corresponding side margin pixel values ​​involves shifting the original left boundary coordinates to the right and the original top boundary coordinates downward, shrinking the usable area of ​​the window inward. Subtracting the corresponding side margin pixel values ​​involves shifting the original right boundary coordinates to the left and the original bottom boundary coordinates upward, shrinking the usable area of ​​the window inward. The target effective display area is the rectangular area obtained after the four-side indentation calculation, serving as the constraint range for the layout content of the target application window.

[0113] In this embodiment, the controller reads the original layout boundary coordinates of the screen: original left = 0, original top = 0, original right = screen width, original bottom = screen height; Read the pixel values ​​of the left, top, right, and bottom margins; New left boundary = Original left boundary + Left margin; New top boundary = Original top boundary + Top side margin; New right boundary = Original right boundary Right margin; New lower boundary = Original lower boundary Bottom margin; The rectangle formed by the four coordinates of new left, new top, new right, and new bottom constitutes the effective display area of ​​the target.

[0114] This calculation is performed during the window layout refresh phase; it supports modifying the margin values ​​of the four sides at runtime and recalculating and updating the effective area.

[0115] The display device provided in this application directly corrects the window layout boundaries at the pixel level. After the application obtains the updated effective area, it actively reflows the layout content, eliminating the image blurring problem caused by layer scaling. It supports dynamically customizing arbitrary pixel margins, breaking through the limitation that native display cutouts can only use hardware-fixed avoidance areas, and adapting to various custom safety area scenarios.

[0116] In some embodiments, Figure 5 This application provides a schematic diagram of the implementation process of step S113, as shown in the embodiment. Figure 5 As shown, the controller execution step S113 is configured as follows: Step S1131: Obtain the target information of the application displayed in the foreground, the target information including: window title and / or prefix.

[0117] In this embodiment of the application, the target information is the identification information used to identify the window, which includes two types: complete window title and window title prefix.

[0118] In this embodiment, during the window layout processing stage, the controller reads the window title string corresponding to the application displayed in the foreground and extracts the title content as a matching criterion. The window title is provided externally by the Android window management service and does not depend on the application package name.

[0119] Step S1132: Match the target information with the target information of the application in the margin mode whitelist.

[0120] In this embodiment of the application, the matching is divided into two rules: exact matching of the complete title and wildcard matching of the title prefix.

[0121] In this embodiment, the controller iterates through the matching rules stored in the margin mode whitelist, supporting two comparison logics: exact match: the current window title is exactly the same as the string in the list; prefix match: the starting part of the window title matches the prefix rule in the list. A successful match is determined if either condition is met.

[0122] Step S1133: The application that matches successfully is determined as an exemption window and excluded, while the application that fails to match is determined as the target application.

[0123] In this embodiment, the exempted window is a window that does not require margin indentation adjustment and maintains its original layout boundaries. The target application is a window that fails to match and requires window boundary indentation adjustment.

[0124] In this embodiment of the application, if the match is successful, the window is exempted, the margin indentation process is skipped, and the original layout boundary is used; if the match fails, it is determined to be the target application, and the boundary indentation processing logic is executed.

[0125] Conventional whitelists mostly only support exact package name matching, making batch configuration of similar windows cumbersome. The display device provided in this application supports batch prefix matching, which can quickly set exemption rules for a type of floating window and system component; the matching object uses the window title, adapting to some dynamic package names and third-party floating application scenarios, expanding the scope of whitelist application and improving the convenience of configuration and debugging.

[0126] In some embodiments, the controller is also configured to support hot parameter updates: in the running state where the device system does not restart and the window is not destroyed, it monitors the user's updated display adjustment layout parameters and mode activation information in real time; when a parameter change is detected, it recalculates the target effective display area and updates the window transformation matrix and window layout boundary so that the changed display rules take effect immediately.

[0127] In some embodiments, the margin indentation mode and the proportional shrinkage mode support mutual exclusion verification and joint compatibility switching; when both modes are detected to be enabled at the same time, the controller defaults to prioritizing the margin indentation mode, blocking layer scaling transformation, and only retaining the layout boundary correction effect, so as to avoid display errors and touch failure caused by the superposition of dual transformations.

[0128] In some embodiments, the controller is also configured with multi-window hierarchical protection logic: In split-screen scenarios, the system identifies the window hierarchy of the top-level floating window, status bar, and navigation bar. For top-level system windows that are higher than application windows, margin indentation adjustment is automatically exempted, and margin adaptation is only uniformly performed on lower-level application windows to ensure the complete display of system interactive controls.

[0129] In some embodiments, the controller is configured with adaptive scene switching and multi-level priority coverage control logic, specifically configured as follows: Real-time monitoring of the current device operating scenarios, including: split-screen multitasking scenario, full-screen single application scenario, wallpaper desktop scenario, and screen projection scaling scenario; The optimal adjustment mode is automatically matched according to different scenarios: the default mode for split-screen scenarios is margin indentation mode, the default mode for screen casting scenarios is proportional shrinkage mode, and the wallpaper center anchoring correction logic is enabled separately for desktop wallpaper scenarios. Execution mode priority determination: Automatic configuration in system scenarios has higher priority than manual configuration by users, and whitelist exemption has higher priority than automatic configuration by system. When there is a conflict between automatic mode and user manual mode, the current window state, whitelist matching results, and split screen flag are read to perform a triple composite judgment and dynamically override the low priority rule. Automatically perform fault-tolerant reset for scenarios involving abnormal parameters, out-of-bounds scaling factors, or overflowing margin values, restoring the default safe display area.

[0130] In some embodiments, the controller is also configured as wallpaper parallax offset dynamic correction logic: obtain the wallpaper parallax scroll offset, and combine it with the global scaling factor to perform proportional compensation correction on the parallax offset; so that after the wallpaper is scaled to adapt to the effective display area of ​​the target, the parallax scroll displacement ratio remains consistent with the native screen, avoiding abnormal parallax sliding amplitude and asymmetrical screen offset after scaling.

[0131] Based on the foregoing embodiments, this application provides a specific example of a margin indentation mode, including: Step 1: Use the Shell command to set the display layout parameters and enable the mode information: adb shell wmmargin 50,100,50,100 -d 0, which means setting the left margin to 50px, top margin to 100px, right margin to 50px, and bottom margin to 100px on the default monitor.

[0132] Step 2: The WindowManagerService receives the command, calls DisplayContent.setDisplayMargin(50,100,50,100), sets mDisplayMargin and marks mIsDisplayMarginSet = true.

[0133] Step 3: Call reconfigureDisplayLocked() to trigger a re-layout of all windows.

[0134] Step 4: In DisplayPolicy.layoutWindowLw(), for each non-whitelisted window: Get the original bounds (e.g., [0, 0, 1080, 2400] for a full-screen window); after applying margins, get the adjusted bounds [50, 100, 1030, 2300]; use the adjusted bounds to call WindowLayout.computeFrames() to calculate the window frames. Step 5: The application receives the new Configuration and rearranges the content within the shrunken area.

[0135] Based on the foregoing embodiments, this application further provides a specific example of a proportional shrinkage mode (Contract mode), including: Step 1: Set the display layout parameters and mode enable information using Shell commands: adb shell wmcontract 100,200,100,200 -d 0, which means setting the left, top, right, and bottom padding to 100px, 200px, 100px, and 200px on the default monitor.

[0136] Step 2: WindowManagerService receives the command, calls DisplayContent.setDisplayContract(100, 200, 100, 200), sets mDisplayContractInsets and marks mIsDisplayContractEnabled = true.

[0137] Step 3: Call requestTraversal() to trigger Surface traversal and update.

[0138] Step 4: Calculate the scaling factor. Assuming the screen size is 1080×2400, the result is as follows: targetW = 1080 - 100 - 100 = 880; targetH = 2400 - 200 - 200 = 2000; scaleX = 880 / 1080 ≈ 0.815; scaleY = 2000 / 2400 ≈ 0.833; Step 5: In TaskDisplayArea.prepareSurfaces: Set the position (100, 200) and matrix (0.815, 0, 0, 0.833) of the SurfaceControl of the TDA. All child windows will automatically inherit this transformation.

[0139] Step 6: In WindowState.getTransformationMatrix(): Multiply the shrink matrix by the window transformation matrix. InputFlinger reads this matrix and automatically completes the inverse mapping of touch coordinates. Step 7: The user touches the screen coordinates (500, 800). InputFlinger calculates the coordinates within the window through inverse transformation: windowX = (500 - 100) / 0.815 ≈ 491; windowY = (800 - 200) / 0.833 ≈ 720; the application receives the correct touch event coordinates.

[0140] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0141] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that, include: A display for showing a window of an application, the window being used to display the interface of the application; The controller, which is communicatively connected to the display, is configured to: Obtain the user-configured display adjustment layout parameters and mode activation information, wherein the mode activation information is used to indicate the currently used adjustment mode; The target effective display area of ​​the display is obtained by adjusting the layout parameters according to the display; According to the adjustment mode corresponding to the mode activation information, the window adjustment algorithm corresponding to the adjustment mode is invoked to adjust the window of the target application to the target effective display area for rendering and display.

2. The display device according to claim 1, characterized in that, The controller, based on the mode activation information, calls the adjustment mode corresponding to the adjustment mode, and adjusts the window of the target application to the target effective display area for rendering and display. This is configured as follows: When the adjustment mode indicated by the mode enable information is the proportional shrinkage mode, a global scaling factor is calculated based on the screen size of the display and the display adjustment layout parameters. The window of the target application is scaled and translated based on the global scaling factor to adjust the window of the target application to be rendered and displayed within the target effective display area.

3. The display device according to claim 2, characterized in that, The controller is also configured to: Obtain the scaling matrix for scaling the window of the target application, and the translation matrix for translating it; The contraction matrix and translation matrix are concatenated to the original window transformation matrix to generate a composite transformation matrix; If a touch event is detected targeting the effective display area of ​​the target, the touch coordinates of the touch event are obtained; The touch coordinates are inversely operated on based on the composite transformation matrix to obtain logical coordinates, and the touch event is responded to based on the logical coordinates.

4. The display device according to claim 2, characterized in that, The controller is also configured to: Get the scaling mode whitelist; Apply an inverse scaling matrix and an inverse translation matrix to the application in the scaling mode whitelist to maintain the original display size and position of the application in the scaling mode whitelist. Applications that are not in the application list or in the scaling mode whitelist are identified as the target application.

5. The display device according to claim 2, characterized in that, The controller scales and translates the target application's window based on the global scaling factor to adjust the target application's window to fit within the target effective display area for rendering and display, and is configured as follows: The translation and scaling matrices of the surface control layers in the target application are uniformly set to display the surface control layers in the target effective display area, so that the surface control layers remain in a constant relative position within the application window.

6. The display device according to claim 2, characterized in that, When the target application includes a desktop wallpaper application, the controller scales and translates the window of the target application based on the global scaling factor to adjust the window of the target application to be rendered and displayed within the target effective display area, and is configured as follows: Calculate the center point of the target's effective display area; The scaling size of the desktop wallpaper is calculated based on the original size of the wallpaper in the desktop wallpaper application and the global scaling factor; The absolute placement coordinates of the desktop wallpaper application are calculated based on the center point and the scaling size; Based on the absolute placement coordinates and the scaling size, the window of the desktop wallpaper application is adjusted to the target effective display area for rendering and display.

7. The display device according to claim 1, characterized in that, The controller, based on the mode activation information, calls the adjustment mode corresponding to the adjustment mode, and adjusts the window of the target application to the target effective display area for rendering and display. This is configured as follows: When the adjustment mode indicated by the mode enable information is margin indentation mode, the window boundaries of the target application window that are less than a preset distance threshold from the screen edge are indented. Based on the indented window boundaries, the window of the target application is adjusted to the target effective display area for rendering and display.

8. The display device according to claim 7, characterized in that, Before the controller indents the window boundaries of the target application whose distance from the screen edge is less than a preset distance threshold, it is also configured to: Identify the application that is in a split-screen scenario as the target application; The application displayed in the foreground that is not in a split-screen scenario and is not recorded in the margin mode whitelist is identified as the target application.

9. The display device according to claim 7, characterized in that, The display adjustment layout parameters include: the pixel values ​​of the margins on all four sides. The controller obtains the target effective display area corresponding to the display based on the display adjustment layout parameters and is configured as follows: Based on the pixel values ​​of the margins of the four sides, the original layout boundaries of the display are adjusted to obtain the target effective display area.

10. A display control method for a monitor, characterized in that, include: Obtain the user-configured display adjustment layout parameters and mode activation information, wherein the mode activation information is used to indicate the currently used adjustment mode; The target effective display area of ​​the monitor is obtained by adjusting the layout parameters according to the display. According to the adjustment mode corresponding to the mode activation information, the window adjustment algorithm corresponding to the adjustment mode is invoked to adjust the window of the target application to the target effective display area for rendering and display.

Images