Manifest

[karinha]

WINDOWS10.MANIFEST

Code: Select all | Expand

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> 
  <dependency optional="yes"> 
    <dependentAssembly> 
      <assemblyIdentity name="Microsoft.Windows.Common-Controls" 
        version="6.0.0.0" publicKeyToken="6595b64144ccf1df" 
        type="win32" processorArchitecture="*" language="*" /> 
    </dependentAssembly> 
  </dependency> 
  <application xmlns="urn:schemas-microsoft-com:asm.v3"> 
     <windowsSettings> <dpiAware      xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true/PM</dpiAware>                     </windowsSettings> 
     <windowsSettings> <dpiAwareness  xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2,PerMonitor</dpiAwareness> </windowsSettings> 
     <windowsSettings> <longPathAware xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">true</longPathAware>                   </windowsSettings> 
     <windowsSettings> <heapType      xmlns="http://schemas.microsoft.com/SMI/2020/WindowsSettings">SegmentHeap</heapType>                 </windowsSettings> 
  </application> 
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> 
    <security> 
      <requestedPrivileges> 
        <requestedExecutionLevel level="asInvoker" uiAccess="false" /> 
      </requestedPrivileges> 
    </security> 
  </trustInfo> 
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> 
    <application> 
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" /> 
      <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}" /> 
      <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" /> 
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" /> 
      <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" /> 
    </application> 
  </compatibility> 
</assembly>
 

Regards, saludos.

[Jimmy]

hi,

Code: Select all | Expand

processorArchitecture="*"

YES, that will work with "x86" an "amd64"

[Enrico Maria Giordano]

Right, great, thank you!

[TimStone]

Going back to my original question, DO WE REALLY NEED TO USE A MANIFEST ?

I have tried the many suggestions here, including the default ones shipped with FWH. In many cases, the suggested formats work with 32 bit, but I have not found any that work with 64 bit. Some will produce errors with both builds.

I put in a lot of time, and cannot achieve success. My program seems to run without a manifest file, but maybe something would be better if I include one.

Finally, If I specify the manifest file name in the .rc, does that mean the file itself is then linked into the application ? Do I still need to have the file in the program execution directory ?

[Jimmy]

hi Tim,

do you want that your App look under Windows XP, 7, 8, 10, 11 like "other" Control ?

than you need Manifest for "Visual Style"
Fivewin does have

WindowsXP.Manifest
WindowsXP.Manifest64
Windows10.Manifest

Windows10.Manifest have enhance Setting for OS > VISTA where we got DWM and those transparency Look
but it is for 32 Bit

Code: Select all | Expand

processorArchitecture="x86"

---

use this enhance Manifest from karinha
https://forums.fivetechsupport.com/view ... 0&start=15
and save it as Windows11.Manifest

it does use

Code: Select all | Expand

processorArchitecture="*"

so it work for 32 Bit and 64 Bit

it also have Setting for DPIaware so your App will not react when User set SCALE to 200 %

it will work with your last Version Setting when include this line before

Code: Select all | Expand

1 24 "Windows11.Manifest"
1 VERSIONINFO
...

---

what you can NOT do, when using Manifest and Visual Style, are Color of Control
these Colors might not "visible" while "Visual Style" does "over-paint" it e.g. BUTTON.

so if you try to use "Dark Mode" there will be a lot Parts which can not (simple) "color it"

[TimStone]

Thank you. I resolved the VERSIONINFO yesterday, and that manifest works.

I have one more question.

I notice when having winapi.ch in my .rc file, there are a huge list of redefinitions. Is this file still required ?

[Jimmy]

hi Tim,

I resolved the VERSIONINFO yesterday, and that manifest works.?

fine

I notice when having winapi.ch in my .rc file, there are a huge list of redefinitions. Is this file still required ?

delete it and you will see what happens ...

it might be that you have try to use Constant from winapi.ch for VERSIONINFO ... but using HEX Value you need no Constant

[TimStone]

I had no consequence for deleting winapi.ch.

When including it, the .mak script returns lots of warnings as values are redefined.
Without it, there are no warnings.
So far I see no difference in appearance or performance.

So it appears to be OK ...