1

Topic: The form "parts".

Gain, already what forces does not remain. I work on 4 the monitor. Grouped the form. I start application in 200 %  (Windows 10), on width of norms, on height approximately 3/4 from the size in design to a mode. I switch system  to 100 % - the form looks normally, all in the sizes. AutoScaleMode = Dpi. Where still it is possible to look?

2

Re: The form "parts".

Hello, dosik, you wrote: D> Gain, already what forces does not remain. I work on 4 the monitor. Grouped the form. I start application in 200 %  (Windows 10), on width of norms, on height approximately 3/4 from the size in design to a mode. I switch system  to 100 % - the form looks normally, all in the sizes. AutoScaleMode = Dpi. Where still it is possible to look? WPF or WinForms? If WinForms I would try to expose the size forcedly after an application launch.

3

Re: The form "parts".

Hello, BlackEric, you wrote: BE> WPF or WinForms? WinForms BE> If WinForms I would try to expose the size forcedly after an application launch. And that such crutches that? The most interesting that all was normal, while I simply did not reboot the form in editor VS, all problems then went.

4

Re: The form "parts".

Hello, dosik, you wrote: D> the Most interesting that all was normal, while I simply did not reboot the form in editor VS, all problems then went. Well so look in the monitoring system of versions that there the editor directed.

5

Re: The form "parts".

Hello, BlackEric, you wrote: BE> If WinForms I would try to expose the size forcedly after an application launch. While so: Size current = Size; Size = new Size (current. Width, 1311 * current. Width / 1912); But I consider extremely not elegant.

6

Re: The form "parts".

Hello, Jack128, you wrote: J> well so look in the monitoring system of versions that there the editor directed. I already there itself on on rules, now from flies not to separate a cutlet already.