<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: 2018 VLIDE not high DPI aware in Visual LISP, AutoLISP and General Customization Forum</title>
    <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973361#M121929</link>
    <description>It can't hurt, but which one? There is no Idea Station for AutoCAD. &lt;BR /&gt;&lt;BR /&gt;I do know someone reads the generic Autodesk feedback form.</description>
    <pubDate>Sat, 25 Mar 2017 21:20:52 GMT</pubDate>
    <dc:creator>rkmcswain</dc:creator>
    <dc:date>2017-03-25T21:20:52Z</dc:date>
    <item>
      <title>2018 VLIDE not high DPI aware</title>
      <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973336#M121926</link>
      <description>&lt;P&gt;For those excited about not having to make an acad.exe.manifest file for 2018 to deal with high dpi settings, oh well.&lt;/P&gt;
&lt;P&gt;Have fun with the little iddy bitty icons if you have font scaled in windows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="whoops.jpg" style="width: 705px;"&gt;&lt;img src="https://forums.autodesk.com/t5/image/serverpage/image-id/337570iD083161691CD7D1B/image-size/large?v=v2&amp;amp;px=999" role="button" title="whoops.jpg" alt="whoops.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Autodesk, remember, the ONE, possibly ONLY thing missing in Bricscad is the VLIDE (debugger).&lt;/P&gt;
&lt;P&gt;Shall we tie a ribbon on your finger?&lt;/P&gt;</description>
      <pubDate>Sat, 25 Mar 2017 20:55:47 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973336#M121926</guid>
      <dc:creator>JamesMaeding</dc:creator>
      <dc:date>2017-03-25T20:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: 2018 VLIDE not high DPI aware</title>
      <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973349#M121927</link>
      <description>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?</description>
      <pubDate>Sat, 25 Mar 2017 21:10:00 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973349#M121927</guid>
      <dc:creator>rkmcswain</dc:creator>
      <dc:date>2017-03-25T21:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: 2018 VLIDE not high DPI aware</title>
      <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973353#M121928</link>
      <description>&lt;P&gt;What if I post it on the Idea Station though? Think it might have a chance?&lt;/P&gt;</description>
      <pubDate>Sat, 25 Mar 2017 21:17:16 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973353#M121928</guid>
      <dc:creator>JamesMaeding</dc:creator>
      <dc:date>2017-03-25T21:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: 2018 VLIDE not high DPI aware</title>
      <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973361#M121929</link>
      <description>It can't hurt, but which one? There is no Idea Station for AutoCAD. &lt;BR /&gt;&lt;BR /&gt;I do know someone reads the generic Autodesk feedback form.</description>
      <pubDate>Sat, 25 Mar 2017 21:20:52 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973361#M121929</guid>
      <dc:creator>rkmcswain</dc:creator>
      <dc:date>2017-03-25T21:20:52Z</dc:date>
    </item>
    <item>
      <title>Re: 2018 VLIDE not high DPI aware</title>
      <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973378#M121930</link>
      <description>&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;Can't they just read their own forum?&lt;/P&gt;</description>
      <pubDate>Sat, 25 Mar 2017 21:49:47 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973378#M121930</guid>
      <dc:creator>JamesMaeding</dc:creator>
      <dc:date>2017-03-25T21:49:47Z</dc:date>
    </item>
    <item>
      <title>Re: 2018 VLIDE not high DPI aware</title>
      <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973385#M121931</link>
      <description>&lt;P&gt;So I thought "ok, I'll just use an acad.exe.manifest to deal with the vlide issues, worked great for 2015".&lt;/P&gt;
&lt;P&gt;Nope, looks horrible.&lt;/P&gt;
&lt;P&gt;Maybe my settings are wrong in it, as I don't know the contents well:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3"&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;dependency&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;dependentAssembly&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;assemblyIdentity&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; type="win32"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; name="Microsoft.Windows.Common-Controls"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; version="6.0.0.0" processorArchitecture="*"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; publicKeyToken="6595b64144ccf1df"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; language="*"&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/assemblyIdentity&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;/dependentAssembly&amp;gt;&lt;BR /&gt;&amp;lt;/dependency&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;dependency&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;dependentAssembly&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;assemblyIdentity&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; type="win32"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; name="Microsoft.VC90.CRT"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; version="9.0.21022.8"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; processorArchitecture="amd64"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; publicKeyToken="1fc8b3b9a1e18e3b"&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/assemblyIdentity&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;/dependentAssembly&amp;gt;&lt;BR /&gt;&amp;lt;/dependency&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;security&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;requestedPrivileges&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;requestedExecutionLevel&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; level="asInvoker"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; uiAccess="false"/&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/requestedPrivileges&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;/security&amp;gt;&lt;BR /&gt;&amp;lt;/trustInfo&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;asmv3:application&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;asmv3:windowsSettings xmlns="&lt;A href="http://schemas.microsoft.com/SMI/2005/WindowsSettings" target="_blank"&gt;http://schemas.microsoft.com/SMI/2005/WindowsSettings&lt;/A&gt;"&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="&lt;A href="http://schemas.microsoft.com/SMI/2005/WindowsSettings&amp;quot;&amp;gt;false&amp;lt;/ms_windowsSettings:dpiAware" target="_blank"&gt;http://schemas.microsoft.com/SMI/2005/WindowsSettings"&amp;gt;false&amp;lt;/ms_windowsSettings:dpiAware&lt;/A&gt;&amp;gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;/asmv3:windowsSettings&amp;gt;&lt;BR /&gt;&amp;lt;/asmv3:application&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;/assembly&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Mar 2017 22:02:48 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6973385#M121931</guid>
      <dc:creator>JamesMaeding</dc:creator>
      <dc:date>2017-03-25T22:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: 2018 VLIDE not high DPI aware</title>
      <link>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6976274#M121932</link>
      <description>&lt;P&gt;I just noticed something that changes things.&lt;/P&gt;
&lt;P&gt;2018 VLIDE has the default font size set at 15, which made things look really ugly when I used the manifest file.&lt;/P&gt;
&lt;P&gt;When I changed back to 11, which all previous acad releases used by default, things looked good.&lt;/P&gt;
&lt;P&gt;For some reason, the higher font size is really grainy, that fooled me as fonts scale smoothly usually.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So I have changed my conclusion that 2018 VLIDE does not run correct with an acad.exe.manifest file.&lt;/P&gt;
&lt;P&gt;No one cares about this right now, I know. Future readers will though so just mentioning the font size change.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Users that scal fonts at non-even ratios, like 175% might really like the dpi awareness of 2018.&lt;/P&gt;
&lt;P&gt;Users that use say 200% scaling will not notice much, if any difference between using an acad.exe.manifest file, and not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I encourage people to look up the usage of acad.exe.manifest&amp;nbsp;as I missed to for a while and it was right in front of me.&lt;/P&gt;
&lt;P&gt;I was changing my screen to 1/2 resolution to use acad 2015 for a while.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2017 17:02:52 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/2018-vlide-not-high-dpi-aware/m-p/6976274#M121932</guid>
      <dc:creator>JamesMaeding</dc:creator>
      <dc:date>2017-03-27T17:02:52Z</dc:date>
    </item>
  </channel>
</rss>

