{"id":12355,"date":"2016-07-05T08:00:11","date_gmt":"2016-07-05T15:00:11","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=12355"},"modified":"2016-07-07T10:09:59","modified_gmt":"2016-07-07T17:09:59","slug":"powershell-studio-2016-service-release-high-dpi-support","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2016\/07\/05\/powershell-studio-2016-service-release-high-dpi-support\/","title":{"rendered":"PowerShell Studio 2016 – Service Release & High DPI Support"},"content":{"rendered":"

We released a new service build of PowerShell Studio 2016 (v5.2.124)!<\/p>\n

\"PowerShell<\/a><\/p>\n

 <\/p>\n

Here\u2019s what\u2019s new:<\/span><\/p>\n

High DPI Support<\/span><\/strong><\/p>\n

We have added high DPI support to PowerShell Studio\u2019s UI. Those of you who previously ran PowerShell Studio on a high DPI monitor (Windows 10 in particular) probably noticed that the application appeared fuzzy. The fuzzy appearance is caused by Windows\u2019 scaling of non-DPI aware applications. The good news is that this no longer the case with PowerShell Studio 2016.<\/p>\n\n\n\n\n\n\n
Not DPI Aware<\/strong><\/td>\n<\/tr>\n
\"Fuzzy<\/a><\/td>\n<\/tr>\n
DPI Aware<\/strong><\/td>\n<\/tr>\n
\"DPI<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

High DPI Layouts<\/strong><\/p>\n

With high DPI screens, you will require high DPI layouts. When PowerShell Studio detects a high DPI environment (DPI > 96) it will automatically load (if present) the high DPI version of the selected layout.<\/p>\n

To create your own high DPI version of a custom layout, simply save the layout with the .HighDPI.layout extension:<\/p>\n\n\n\n\n
Low DPI file:<\/strong><\/td>\nHigh DPI file:<\/strong><\/td>\n<\/tr>\n
(Layout Name).layout<\/td>\n(Layout Name).HighDPI.layout<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

High DPI Designer<\/strong><\/p>\n

PowerShell Studio now ensures that your forms scale correctly in the designer. As a result, you can edit the same psf file in a low DPI environment and in a high DPI environment, while maintaining the form\u2019s scale (as oppose to Visual Studio where it is recommended to design the GUI in a 96 DPI environment because the form will not scale correctly when editing between different DPI environments.)<\/p>\n

Important: Older versions of PowerShell Studio will incorrectly scale forms created in high DPI environments. Therefore, psf files created or saved by this version of PowerShell Studio will not be backwards compatible<\/strong>.<\/span><\/p>\n

 <\/p>\n

High DPI Control Sets<\/strong><\/p>\n

Similar to the designer, Control Sets now support high DPI scaling and will scale correctly in low DPI settings.<\/p>\n

Important: Due to scaling compatibility, Control Sets created with this version will not be backwards compatible<\/strong> with older versions of PowerShell Studio.<\/span><\/p>\n

 <\/p>\n

High DPI Scripts<\/strong><\/p>\n

It is important that the GUIs you create display correctly when executed in high DPI environments. To ensure this, we updated the script generator to include the necessary code to allow your GUIs to scale correctly. Saving the psf file in this build is all that is needed.<\/p>\n

We will discuss how to design a GUI for high DPI environments in an upcoming article, because there are some design considerations you need to address in order for your controls to display correctly.<\/p>\n

Note: Displaying the GUI in high DPI depends on the executing host. The host running the script must be DPI aware, otherwise the form may have a fuzzy look to it. PowerShell Studio\u2019s internal hosts and the packager engines are all DPI aware.<\/p>\n

 <\/p>\n

Document Selector<\/strong><\/p>\n

When you press [Ctrl + Tab] to cycle between documents, the Document Selector appears. We added a new option to disable this feature, allowing you to directly cycle through the document tabs without opening the selector.<\/p>\n

\"Document<\/a><\/p>\n

Note: The Document Selector displays the documents in activation order instead of the tab order.<\/p>\n

You can modify the feature by checking\/unchecking the Show the document selector when navigating tabs<\/strong> option in Options->General:<\/p>\n

\"Options<\/a><\/p>\n

 <\/p>\n

Please continue providing your feedback. Many of the new features included in the service builds are suggestions from users like you. Therefore, if you have any suggestions or feature requests, please share them with us on our Wish List and Feature Requests<\/a> forum.<\/p>\n","protected":false},"excerpt":{"rendered":"

We released a new service build of PowerShell Studio 2016 (v5.2.124)!   Here\u2019s what\u2019s new: High DPI Support We have added high DPI support to PowerShell Studio\u2019s UI. Those of you who previously ran PowerShell Studio on a high DPI monitor (Windows 10 in particular) probably noticed that the application appeared fuzzy. The fuzzy appearance […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[703,624,21,25],"tags":[1146,28,1068,645],"class_list":["post-12355","post","type-post","status-publish","format-standard","hentry","category-powershell-studio","category-service-build","category-software-news","category-windows-powershell","tag-dpi","tag-powershell","tag-powershell-studio-2016","tag-service-build-2"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/12355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=12355"}],"version-history":[{"count":14,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/12355\/revisions"}],"predecessor-version":[{"id":12441,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/12355\/revisions\/12441"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=12355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=12355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=12355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}