blocks|key|131647|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|131648|有没有人知道微软的开发人员是怎么做到的？|blockquote|131649|131650|131651|这有一个相当令人失望的答案。使用Alin+Constantin的WinCheat并检查计算器的顶层窗口，我看到窗口大小为320x576，客户端大小也是320x576。|offset|length|131652|换句话说，Microsoft通过隐藏窗口的非工作区，而将所有内容都放在工作区中，完全避免了这个问题。要想让这个工作对你很好，可能需要自定义标题栏的绘制。|131653|值得注意的是，计算器和Windows资源管理器的标题栏颜色不同。计算器对标题栏进行自定义绘制可以很好地解释这一点。|131654|entityMap|0|LINK|mutability|MUTABLE|url|http://alinconstantin.dynu.com/^0|0|0|0|0|G|F|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|W|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|Z|7|@]|8|@$H|10|I|11|1|12]]|9|$]]|$1|J|3|K|4|5|6|13|7|@]|8|@]|9|$]]|$1|L|3|M|4|5|6|14|7|@]|8|@]|9|$]]|$1|N|3|-4|4|5|6|15|7|@]|8|@]|9|$]]]|O|$P|$4|Q|R|S|9|$T|U]]]]

<blockquote>
 Does anyone how the devs at MS did this?
</blockquote>

This has a pretty disappointing answer. Using <a href="http://alinconstantin.dynu.com/">Alin Constantin</a>'s WinCheat and inspecting the top-level window of Calculator, I see a window size of 320x576, and a client size that is also 320x576.

In other words, Microsoft entirely avoids the problem by suppressing the non-client area of the window, putting everything in the client area instead. Making this work well for you may involve custom drawing of the title bar.

Something worth noting is that Calculator and e.g. Windows Explorer don't use the same colour for the title bars. Calculator doing custom drawing of the title bar would explain that perfectly.

blocks|key|131166|text|documentation说：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|131167|131168|请注意，支持每个显示器的DPI的应用程序的非工作区不会被窗口缩放，并且在高DPI显示上会按比例变小。|blockquote|131169|131170|131171|您链接的Microsoft应用程序通过删除非客户端区并使客户端区覆盖整个窗口来处理此问题。|131172|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/windows/desktop/dd162743.aspx^0|0|D|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|-4|5|6|7|X|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|Y|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]]]

The <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/dd162743.aspx" rel="nofollow">documentation</a> says:

<blockquote>
 Note that the non-client area of a per monitor–DPI aware application is not scaled by Windows, and will appear proportionately smaller on a high DPI display.
</blockquote>

The Microsoft apps that you link to deal with this by removing the non-client area and making the client area cover the entire window.

blocks|key|131192|text|更新：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|131193|在清单中添加新的<dpiAwarness>声明就足以解决所有这些问题。here就是一个例子。|CODE|131194|以前调查的残留物(过时)：|131195|对这个问题进行更多的调查。|131196|系统设置:两个显示器，一个是96+dpi，另一个是267+dpi+(Microsoft+Surface+4)。|131197|测试窗口移至辅助96+dpi显示器：|131198|下面是在清单中使用<dpiAware>true/pm</dpiAware>进行渲染(错误，IMO)：|131199|​|131200|📷|atomic|131201|131202|注意标题栏的巨大尺寸和错误的窗口图标大小。|131203|下面是使用<dpiAware>true</dpiAware>进行的正确渲染|131204|131205|131206|131207|我怀疑MSDN文档对PROCESS_DPI_AWARENESS的价值有明显的误导性。我看不出<dpiAware>true</dpiAware>和<dpiAware>true/pm</dpiAware>在消息和样式上有什么不同。后者只是让标题变得更大。在这两种情况下，应用程序在具有不同DPI的监视器之间移动时都会收到WM_DPICHANGED消息。|131208|叹一口气。|131209|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/c-smile/sciter-sdk/blob/master/demos/usciter/win-res/dpi-aware.manifest#L7|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/450e23d81c7b5556bab52bcab6c23f02.png|imageAlt|2|https://ask.qcloudimg.com/http-save/yehe-900000/dec01c7330ba331860f754ef52c12c64.png|3|https://msdn.microsoft.com/en-us/library/windows/desktop/dn280512(v=vs.85).aspx)^0|0|3|0|8|D|Z|4|0|0|5|8|0|0|0|0|9|S|0|0|0|1|1|0|0|0|5|P|0|0|0|1|2|0|0|1A|P|20|S|A|L|3|0|0^^$0|@$1|2|3|4|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1U|8|@$9|1V|A|1W|B|H]]|D|@$9|1X|A|1Y|1|1Z]]|E|$]]|$1|I|3|J|5|6|7|20|8|@$9|21|A|22|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|23|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|24|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|25|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|26|8|@$9|27|A|28|B|H]]|D|@]|E|$]]|$1|S|3|T|5|6|7|29|8|@]|D|@]|E|$]]|$1|U|3|V|5|W|7|2A|8|@]|D|@$9|2B|A|2C|1|2D]]|E|$]]|$1|X|3|T|5|6|7|2E|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2F|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|2G|8|@$9|2H|A|2I|B|H]]|D|@]|E|$]]|$1|12|3|T|5|6|7|2J|8|@]|D|@]|E|$]]|$1|13|3|V|5|W|7|2K|8|@]|D|@$9|2L|A|2M|1|2N]]|E|$]]|$1|14|3|T|5|6|7|2O|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|2P|8|@$9|2Q|A|2R|B|H]|$9|2S|A|2T|B|H]]|D|@$9|2U|A|2V|1|2W]]|E|$]]|$1|17|3|18|5|6|7|2X|8|@]|D|@]|E|$]]|$1|19|3|-4|5|6|7|2Y|8|@]|D|@]|E|$]]]|1A|$1B|$5|1C|1D|1E|E|$1F|1G]]|1H|$5|1I|1D|1J|E|$1K|1L|1M|-4]]|1N|$5|1I|1D|1J|E|$1K|1O|1M|-4]]|1P|$5|1C|1D|1E|E|$1F|1Q]]]]

UPDATE:

It is enough to add new <code>&lt;dpiAwarness&gt;</code> declaration to manifest to solve all this mess. Example is <a href="https://github.com/c-smile/sciter-sdk/blob/master/demos/usciter/win-res/dpi-aware.manifest#L7" rel="nofollow noreferrer">here</a>.

Remnants of former investigations (obsolete):

More investigations on the subject.

System setup: two monitors, one is 96 dpi another one is 267 dpi (Microsoft Surface 4). 

Testing window is moved to secondary 96 dpi monitor:

Here is rendering (wrong, IMO) with <code>&lt;dpiAware&gt;true/pm&lt;/dpiAware&gt;</code> in manifest:

<a href="https://i.stack.imgur.com/k6gxJ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/k6gxJ.png" alt="enter image description here"></a>

Note huge size of caption bar and wrong sizes of window icons.

And here is correct rendering using <code>&lt;dpiAware&gt;true&lt;/dpiAware&gt;</code>

<a href="https://i.stack.imgur.com/ADTzf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ADTzf.png" alt="enter image description here"></a>

And I suspect that MSDN documentation is plainly misleading about values of <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/dn280512(v=vs.85).aspx" rel="nofollow noreferrer">PROCESS_DPI_AWARENESS</a>. I do not see any differences in messages and styles between <code>&lt;dpiAware&gt;true&lt;/dpiAware&gt;</code> and <code>&lt;dpiAware&gt;true/pm&lt;/dpiAware&gt;</code>. The later one just makes caption larger. In both case application receives WM_DPICHANGED message while moving between monitors with different DPI.

Sigh.

blocks|key|131211|text|Windows10周年纪念更新(Windows10周年纪念更新)增加了一个新的v1607，您必须调用它才能对非客户端区域进行缩放：EnableNonClientDpiScaling。当接收到WM_NCCREATE时，应调用此函数。在窗口创建期间，消息被发送到窗口的过程回调。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|131212|示例：|131213|case+WM_NCCREATE:
{
++++if+(!EnableNonClientDpiScaling(hWnd))
++++{
++++++++//+Error+handling
++++++++return+FALSE;
++++}

++++return+DefWindowProcW(...);
}|code-block|syntax|javascript|131214|如果应用程序的DPI感知上下文为DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2，则应该省略调用EnableNonClientDpiScaling，因为它不会有任何效果，尽管函数仍将成功返回。|131215|来自the+documentation|131216|默认情况下，顶级窗口的|131217|非客户端伸缩未启用。您必须调用此API，以便为您希望自动缩放其非工作区的每个单独的顶级窗口启用它。一旦你这样做了，就没有办法禁用它。启用非客户端缩放意味着系统为窗口绘制的所有区域都将自动缩放，以响应窗口上的DPI更改。包括标题栏、滚动条和菜单栏等区域。当您希望操作系统负责根据监视器的应用编程接口以正确的大小自动呈现这些区域时，您需要调用EnableNonClientDpiScaling。|blockquote|131218|131219|131220|有关Windows10AU中DPI缩放更改的其他信息，请参阅this+blog+post。|131221|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/windows/desktop/mt748621(v=vs.85).aspx)|1|https://msdn.microsoft.com/en-us/library/windows/desktop/ms632635(v=vs.85).aspx|2|3|https://blogs.technet.microsoft.com/askcore/2016/08/16/display-scaling-changes-for-the-windows-10-anniversary-update/^0|1T|P|2N|B|1T|P|0|2N|B|1|0|0|0|G|16|1U|P|0|2|H|2|0|0|4P|P|0|0|0|U|E|3|0^^$0|@$1|2|3|4|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@$9|1H|A|1I|1|1J]|$9|1K|A|1L|1|1M]]|E|$]]|$1|F|3|G|5|6|7|1N|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1O|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1P|8|@$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1U|8|@]|D|@$9|1V|A|1W|1|1X]]|E|$]]|$1|Q|3|R|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|S|3|T|5|U|7|1Z|8|@$9|20|A|21|B|C]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|22|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|23|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|24|8|@]|D|@$9|25|A|26|1|27]]|E|$]]|$1|Z|3|-4|5|6|7|28|8|@]|D|@]|E|$]]]|10|$11|$5|12|13|14|E|$15|16]]|17|$5|12|13|14|E|$15|18]]|19|$5|12|13|14|E|$15|16]]|1A|$5|12|13|14|E|$15|1B]]]]

The Windows 10 Anniversary Update (v1607) has added a new API you must call to enable DPI scaling of the non-client areas: <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/mt748621(v=vs.85).aspx" rel="nofollow noreferrer"><code>EnableNonClientDpiScaling</code></a>. This function should be called, when <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/ms632635(v=vs.85).aspx" rel="nofollow noreferrer"><code>WM_NCCREATE</code></a> is received. The message is sent to the window's procedure callback during window creation.

Example:

<pre><code>case WM_NCCREATE:
{
 if (!EnableNonClientDpiScaling(hWnd))
 {
 // Error handling
 return FALSE;
 }

 return DefWindowProcW(...);
}
</code></pre>

If the application's DPI-awareness context is <code>DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2</code>, then calling <code>EnableNonClientDpiScaling</code> should be omitted, as it won't have any effect, although the function will still return successfully.

From <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/mt748621(v=vs.85).aspx" rel="nofollow noreferrer">the documentation</a>:

<blockquote>
 Non-client scaling for top-level windows is not enabled by default. You must call this API to enable it for each individual top-level window for which you wish to have the non-client area scale automatically. Once you do, there is no way to disable it. Enabling non-client scaling means that all the areas drawn by the system for the window will automatically scale in response to DPI changes on the window. That includes areas like the caption bar, the scrollbars, and the menu bar. You want to call <code>EnableNonClientDpiScaling</code> when you want the operating system to be responsible for rendering these areas automatically at the correct size based on the API of the monitor.
</blockquote>

See <a href="https://blogs.technet.microsoft.com/askcore/2016/08/16/display-scaling-changes-for-the-windows-10-anniversary-update/" rel="nofollow noreferrer">this blog post</a> for additional information about DPI scaling changes in Windows 10 AU.

I am making my app dpi-aware per monitor by setting <code>&lt;dpiAware&gt;True/PM&lt;/dpiAware&gt;</code> in the manifest file. I can verify with process explorer that this is indeed working or by calling GetProcessDpiAwareness. 

This is all working fine and I can scale anything in the client area fine in my code. However, my only problem is that if I drag my app from a system-dpi monitor to a non-system dpi monitor, the title bar and any system menu would either become too big or too small. This isn't the case for most built-in apps (e.g. calc, edge browser, etc..) so there must be away to scale it properly. Does anyone how the devs at MS did this? 

The screenshot below should explain my problem better. Also notice, that the padding between the close, min, and max button is different when it's scaled (96dpi).

<img src="https://i.imgur.com/YzWht8U.png" alt="Screenshot">

<a href="https://dl.dropboxusercontent.com/u/3209117/DpiAwareness.zip">Sample app</a> I'm attaching a very simple app that is per-monitor dpi aware.

How do you scale the title bar on a DPI aware win application?

Windows

我通过在清单文件中设置<dpiAware>True/PM</dpiAware>，使我的应用程序能够识别每个监视器的dpi。我可以使用process explorer验证这是否确实有效，或者调用GetProcessDpiAwareness。这一切都运行得很好，我可以在我的代码中很好地缩放客户端区中的任何内容。然而，我唯一...

问如何在支持DPI的win应用程序上缩放标题栏？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在支持DPI的win应用程序上缩放标题栏？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在支持DPI的win应用程序上缩放标题栏？
EN