blocks|key|1590923|text|1-手动编写XAML，不要使用Visual+Studio设计器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1590924|1590925|设计器会生成固定大小的固定位置UI+(ala+winforms)，如果您需要独立于分辨率，它将不再有用。|unordered-list-item|1590926|1590927|2-也不要自己固定UI元素的大小和位置。|1590928|1590929|不要做像<TextBox+Width="56"+Margin="50,30,10,5"/>这样的事情。相反，将UI放在与分辨率无关的布局容器中，如Grid或DockPanel。在网格中也使用星形尺寸。|offset|length|style|CODE|1590930|1590931|编辑：添加了@Viv的评论，这是如此重要，我决定将其作为答案的一部分：|BOLD|1590932|就像编程中的其他事情一样，对第一点持保留态度。不要再说“在MVVM中，代码隐藏中的任何代码都是错误的”。使用设计器(VS/Blend)来生成模板、修改故事板、VSM、导入Illustrator/Photoshop文件是完全合理的。知道您正在处理的是什么，即使在这种情况下您得到了恒定的维度，也要相应地调整xaml以消除它，而不是完全忽略它的每一个方面|1590933|entityMap|0|LINK|mutability|MUTABLE|url|http://wpftutorial.net/GridLayout.html^0|0|0|0|0|0|0|4|15|21|4|26|9|21|4|0|0|0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|15|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|17|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|19|8|@$L|1A|M|1B|N|O]|$L|1C|M|1D|N|O]|$L|1E|M|1F|N|O]]|9|@$L|1G|M|1H|1|1I]]|A|$]]|$1|P|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1K|8|@$L|1L|M|1M|N|S]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1N|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]]]

1 - Write your XAML by hand and don't use the Visual Studio designer.

<ul>
<li>The designer produces fixed-size fixed-position UIs (ala winforms) and will not be useful if you need resolution independence.</li>
</ul>

2 - Do not fix the sizes and positions of the UI elements yourself either.

<ul>
<li>Don't do things such as <code>&lt;TextBox Width="56" Margin="50,30,10,5"/&gt;</code>. Instead of that, place your UI inside resolution independent layout containers such as <a href="http://wpftutorial.net/GridLayout.html" rel="nofollow"><code>Grid</code></a> or <code>DockPanel</code>. Use Star Sizes in your Grids, too.</li>
</ul>

Edit: Adding @Viv's comment, which is so important I decided to make it part of the answer:

Like everything else in programming, take point 1 with a grain of salt. Don't make it another statement like "In MVVM ANY code in code-behind is wrong". Using the Designer(VS/Blend) for things like generating Template's, Modifying Storyboards, VSM, Importing Illustrator/Photoshop files is perfectly reasonable. Know what you're dealing with and even if in such cases you get constant dimensions, tweak the xaml accordingly to get rid of it than totally neglect every aspect of it

blocks|key|3175499|text|首先，这在某种程度上取决于应用程序的性质，但是您指定的分辨率在总体上并没有太大的不同(如果您比较640x480和2560x1600，那么您可能会有更大的顾虑！)，因此，如果您选择了正确的组件，它们可能会自动组织起来(或者更恰当地说，操作系统会在幕后组织它们)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3175500|选择WPF意味着你在如何渲染UI元素上有很大的灵活性，因为WPF本身就是一个基于矢量的渲染引擎，而不是Windows+Forms+(GDI/GDI%2B)，后者是一个基于DPI/每像素的渲染引擎。|3175501|但是，让我们更深入地研究一下这个问题，好吗？|3175502|比方说，你正在Windows+Forms中设计你的UI，它需要在窗体上有一个ToolStrip，然后你需要1000个按钮到ToolStrip。好吧，在一个巨大的显示器上，你可能只能看到全部1000个按钮，但在你的bog标准1080p显示器上，你可能只看到其中的30个按钮；那么其余的会发生什么呢？-+Windows会将这些按钮放在ToolStrip末尾的一个子菜单中，这样即使它们不在ToolStrip的主(可见)部分，你仍然可以访问它们。我非常确定，同样的原则也将适用于WPF，通过它，您可能会更好地控制事物的渲染和显示方式！|3175503|WPF通过矢量渲染为桌面带来了一件伟大的事情:分辨率独立性。这使您可以灵活地决定是否要将元素渲染为“固定”大小(对于任何分辨率，它将始终使用相同的像素)，或者允许引擎根据分辨率动态调整元素的大小(在低分辨率下，元素将使用较少的像素进行渲染，但质量较低时会受到影响，或者在高分辨率时，将使用更多的像素进行渲染，并具有更高的质量)。|3175504|为了让你开始，这里有一个来自SyncFusion的免费的WPF+eBook+(说真的，看看他们，他们提供了相当多的免费的，像样的东西！)|3175505|WPF+Succinctly|offset|length|3175506|entityMap|0|LINK|mutability|MUTABLE|url|http://www.syncfusion.com/resources/techportal/ebooks/wpf^0|0|0|0|0|0|0|0|E|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@$N|14|O|15|1|16]]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

Firstly, it depends somewhat on the nature of the application, however the resolutions you specify are not MASSIVELY different in the grand scheme of things (if you were comparing 640x480 to 2560x1600, then you might have even bigger concerns!), so likely, if you choose the right components, they will organise themselves (or more aptly, the OS will organise them behind the scenes) for you.

The fact that you've chosen WPF means that you have massive flexibility with how UI elements will render, as WPF is natively a vector based rendering engine, as opposed to Windows Forms (GDI/GDI+) which was a DPI/per-pixel based rendering engine.

But lets delve a little deeper into this shall we?

Say for example you were designing your UI in Windows Forms, and it required a ToolStrip on the form, and then you all 1000 buttons to the ToolStrip. Okay, on a massive monitor, you might just see all 1000 buttons, but on your bog standard 1080p monitor, you might only see 30 of them; so what happens to the rest? - Windows will put these in a sub-menu for you, at the end of the ToolStrip, so that you can still access them, even though they are not on the main (visible) section of the ToolStrip. I'm pretty sure that the same principle will apply to WPF, through you will likely have even greater control over how things render, and appear!

The great thing that WPF brought to the table, through vector rendering, was resolution independence. This gives you the flexibility to decide if you want your elements to render as a "fixed" size (across any resolution, it will always use the same pixels), or, allow the engine to dynamically resize the element according to the resolution (on a low resolution the element will render using less pixels but will suffer with lesser quality, or on a high resolution, will render using more pixels and will have a much higher quality).

To get you started, here's a free WPF eBook from SyncFusion (seriously, check them out, they give away quite a bit of free, decent stuff!)

<a href="http://www.syncfusion.com/resources/techportal/ebooks/wpf" rel="nofollow">WPF Succinctly</a>

I'm designing and implementing the GUI for special application.

I'm using WPF on C#, 

I intend to apply this app for different monitor resolutions (1366x768 or 1920x1080,...).

But I don't have any experience for this. I don't know how to implement the flexible GUI that can display on any resolution well.

Someone can give me the ideas?

How to design GUI for different monitor resolutions?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我正在为特殊的应用程序设计和实现GUI。我在C#上使用WPF，我打算将此应用程序应用于不同的显示器分辨率(1366x768或1920x1080，...)。但我对此没有任何经验。我不知道如何实现灵活的GUI，它可以在任何分辨率下很好地显示。有人能给我点子吗？

问如何为不同的显示器分辨率设计GUI？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何为不同的显示器分辨率设计GUI？EN