These apps have no frame or borders, and typically have heavily customized UI. Note, however, that the API is a hint to the system and does not guarantee rounding, depending on the customizations.Īpps that cannot ever be rounded, even if they call the opt-in API. If you address these issues in your app or call the opt-in API, described in the following section, then it's possible for the system to round your app's window. Although we did try to round as many apps as possible with our system heuristics, there are some combinations of customizations that we can't predict so we provided a manual opt-in API for those cases. Other customizations, such as extra non-child windows used for custom shadowsĬhanging one of these things will break automatic rounding.If your app is not rounded by policy, it could be caused by one of the following things: It also includes apps that provide enough information to the system so it can properly round them, such as setting the WS_THICKFRAME and WS_CAPTION window styles or providing a 1-pixel non-client area border that the system can use to round the corners.Īpps that are not rounded by policy, but can be rounded.Īpps in this category generally want to customize the majority of the window frame but still want the system-drawn border and shadow, such as Microsoft Office. This includes apps that want a complete system-provided frame and caption-controls (min/max/close buttons), like Notepad. Apps fall into three main categories from the perspective of the Desktop Window Manager (DWM): If your app's main window doesn't receive automatic rounding, it's because you've customized your frame in a way that prevents it. By design, apps are not rounded when maximized, snapped, running in a Virtual Machine (VM), running on a Windows Virtual Desktop (WVD), or running as a Windows Defender Application Guard (WDAG) window.
0 Comments
Leave a Reply. |