2018 VLIDE not high DPI aware

[JamesMaeding]

For those excited about not having to make an acad.exe.manifest file for 2018 to deal with high dpi settings, oh well.

Have fun with the little iddy bitty icons if you have font scaled in windows:

Autodesk, remember, the ONE, possibly ONLY thing missing in Bricscad is the VLIDE (debugger).

Shall we tie a ribbon on your finger?

[rkmcswain]

I think I remember reading some time ago, that the VLIDE was never, or maybe it was "probably never" going to be updated. Maybe Lee can comment on this?

[JamesMaeding]

What if I post it on the Idea Station though? Think it might have a chance?

[rkmcswain]

It can't hurt, but which one? There is no Idea Station for AutoCAD.

I do know someone reads the generic Autodesk feedback form.

[JamesMaeding]

Pretty soon, there will be sub-idea stations that you must start with, and work your way to the real one, and then where? Here?

Can't they just read their own forum?

[JamesMaeding]

So I thought "ok, I'll just use an acad.exe.manifest to deal with the vlide issues, worked great for 2015".

Nope, looks horrible.

Maybe my settings are wrong in it, as I don't know the contents well:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">

<dependency>
  <dependentAssembly>
    <assemblyIdentity
      type="win32"
      name="Microsoft.Windows.Common-Controls"
      version="6.0.0.0" processorArchitecture="*"
      publicKeyToken="6595b64144ccf1df"
      language="*">
    </assemblyIdentity>
  </dependentAssembly>
</dependency>

<dependency>
  <dependentAssembly>
    <assemblyIdentity
      type="win32"
      name="Microsoft.VC90.CRT"
      version="9.0.21022.8"
      processorArchitecture="amd64"
      publicKeyToken="1fc8b3b9a1e18e3b">
    </assemblyIdentity>
  </dependentAssembly>
</dependency>

<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
  <security>
    <requestedPrivileges>
      <requestedExecutionLevel
        level="asInvoker"
        uiAccess="false"/>
    </requestedPrivileges>
  </security>
</trustInfo>

<asmv3:application>
  <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
    <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware>
  </asmv3:windowsSettings>
</asmv3:application>

</assembly>

[JamesMaeding]

I just noticed something that changes things.

2018 VLIDE has the default font size set at 15, which made things look really ugly when I used the manifest file.

When I changed back to 11, which all previous acad releases used by default, things looked good.

For some reason, the higher font size is really grainy, that fooled me as fonts scale smoothly usually.

So I have changed my conclusion that 2018 VLIDE does not run correct with an acad.exe.manifest file.

No one cares about this right now, I know. Future readers will though so just mentioning the font size change.

Users that scal fonts at non-even ratios, like 175% might really like the dpi awareness of 2018.

Users that use say 200% scaling will not notice much, if any difference between using an acad.exe.manifest file, and not.

I encourage people to look up the usage of acad.exe.manifest as I missed to for a while and it was right in front of me.

I was changing my screen to 1/2 resolution to use acad 2015 for a while.