IDE issue with high resolution screen with 0.95.006

[Jacques Nilo]

Hi all

I noticed that with the latest GCB release (v0.95.006) the IDE does not work when using an high resolution screen (in my case a Surface Pro 3 with default resolution set at 2160x1440). Lines are not set properly and are overlapping.

This seems to be related to the version of Synwrite being used in the latest GCB release (6.18.2135).
As a work around I replaced the synwrite subdir with the one from the previous release (GCB 0.94) using version 6.16.1970 of synwrite and everything is back to normal so far.

Jacques

Addendum: doing that makes you loose some of the capabilities of the new IDE: the help function does not work unless you use the Syn.ini file from 0.95.006 and move it over to 0.94 synwrite subdir. But there might be some other limitation I am not aware of. An issue for Frank S. ?

[Jacques Nilo]

Seems to be a Synwrite issue when you change default dpi to a number above 100%. I opened a topic in the bug section of the Synwrite forum.

[Anobium]

Thank you Jacques. This was a known issue but we failed to put on the known issue list.

There is also an issue with the lastest version of SynWrite when using with GCB.

You could try the the following - restore the latest build and simply replace Syn.exe. Does this resolve your issue?.

[Jacques Nilo]

Hi all/Evan
The issue does appears to be related to the Synwrite version but to a piece of code which was introduced in the synwrite.exe.manifest file.

  <asmv3:application xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
    <asmv3:windowsSettings
         xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
      <dpiAware>true</dpiAware>
    </asmv3:windowsSettings>
  </asmv3:application>

If that part of the code is removed then everything seems to be back to normal.
Jacques

[Anobium]

Great job!! Do I need to set dpiaware to false on the default installer?

[Jacques Nilo]

Yep. In synwrite.exe.manifest replacing

<dpiAware>true</dpiAware>

by

<dpiAware>false</dpiAware>

seems to solve the issue
Jacques

[Anobium]

I have changed to false. This will be the norm going forward.