#Windows 10 border size driver#
#Windows 10 border size code#
#Windows 10 border size windows#

* Use theme from app settings instead of system theme. * Use system metrics instead of hardcoding resize border height

#Windows 10 border size code#

* DRY shared code between conhost and new terminal * Add support for dark theme on the frame * Fix the window's position when maximized * Fix weird colors in drag bar and hide old title bar buttons Changing the colour, width or style of your page border in Microsoft Word is a creative way to customise your document. * Position the XAML island window correctly * Fix DwmExtendFrameIntoClientArea values I've also refactored a little bit the `NonClientIslandWindow` class. Removing complex code that was needed to handle the weird cases when the Most of this PR is comments to explain how the code works and also

#Windows 10 border size windows#

`DwmExtendFrameIntoClientArea` and then we put the XAML island and the If you decide on what to change the border thickness of standard windows in Windows 8.1, then you have to resort to some tricks, as such a possibility is. Wide top border back in the client area using (see `NonClientIslandWindow::_OnNcCalcSize`), then we put little 1 pixel We take the standard window frame except that we remove the top part Probably because the Windows Console is a hot mess of legacy spaghetti code ( itВ used toВ beВ aВ whole lotВ worse beforeВ 2014) andВ the WindowsВ Terminal hasВ toВ interface withВ it, soВ itВ needs toВ beВ a Win32В executable, as UWPВ apps are sandboxed, andВ therefore donвЂ™tВ haveВ access toВ systemВ internals (e.g.В the WindowsВ Console). Instead, revisit that requirement - why is it a requirement? Why does this app think it needs to be 'more special' than other Windows applications and thus inconsistent with them (and likely less compatible with other system-wide UI changes that may come in future major Windows revisions)? Can the problem that 'requirement' is trying to solve be better solved instead via some other design choice that avoids all the myriad technical issues created by the current approach? It's not due to ignorance that we're asking the questions that we a fairly simple UI with fairly simple requirements, but one of those requirements is 'have a custom color in our title bar.'ДЄnd from that 'requirement' stems the plethora of other problems. I spent almost my entire sunday trying to answer all of the questions that arise from this list.

we are driving dependencies on our internal partners to make this less of a heckscape.

we need to cut a hole in the Xaml island to allow titlebar and drag input to come back through (yes, this is silly).

there's some weird magic hit testing that we cannot replicate for the resize handles 'off the edge of the window'.

when we try to draw our own title bar, dwm gives up and says 'you don't want X? I'll take away Y, Z, A, B and C as well.

dwm shadows are a trick, the window border is actually 8px wide and the compositor eats 7 pixels off the edge to make a shadow.

we need to account for the theme part size of the window's elements.

we need to draw our own caption buttons.

We need to have the UI framework (here Xaml Islands) go edge-to-edge, which means:.

We need to draw the titlebar ourselves, in its entirety, which means:.

We're a fairly simple UI with fairly simple requirements, but one of those requirements is 'have a custom color in our title bar.' Unfortunately, that means:

#Windows 10 border size driver#

There's a lot of history here for us to unravel, the earliest part of which is 'why is it so hard to draw in the titlebar' and the latest part of which is 'now that we're drawing in the titlebar, why was it decided by the win32 kernel driver and desktop window compositor that we absolutely must handle all of this ourselves? it's like this system was never actually designed but instead organically grown.' There is slight delay in changing the title bar color as WEM places the registry value slightly after the published app launches but IE refreshes quickly enough.Д¬itrix support was contacted and I was informed the 1px white border and no visual effects was expected behavior but the 'issue' was bought to the development team to evaluate.Unfortunately, it is the right question to ask.

This untimately left the title bar alone with default colors while in a published desktop but turned the title bar gray when in a published app. Using WEM: (GPP cannot target on these conditions)Д¬ondition 1: This is a published desktop (disable)Д¬ondition 2: This is a published application (enable) Set the AccentColor, AccentColorInactive to a color i liked (FFD3D3D3) Using a GPP (WEM didn't do this fast enough): Type Settings in the search bar and choose the Settings option, as the following image is showing.

So I went about mitigating the issue using a GPP and WEM. To personalize window borders and shadows on Windows 10, follow this procedure step by step: Click the Search button. I really didn't want to change the entire color scheme just for the title bar. Users really liked the default visual effects and they do work while in a published desktop.