cheng/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Windows Theme support page

Browse Source 
(cherry picked from commit b112dfb4a054a5dbc61a1511b8711f80a2708866)
This commit is contained in:
PB 2022-11-01 19:08:42 +01:00 committed by Vadim Zeitlin
parent b45d47022c
commit 6d0ad7299a
1 changed files with 16 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
docs/msw/winxp.md
View File

@ -1,54 +1,25 @@
Microsoft Windows XP Support from wxWidgets {#plat_msw_winxp}
Microsoft Windows Theme Support from wxWidgets {#plat_msw_winxp}
-------------------------------------------
Windows XP introduces the themes (called "visual styles" in the Microsoft
documentation) in Windows world. As wxWidgets uses the standard Windows
controls for most of its classes, it can take advantage of it without
(almost) any effort from your part. The only thing you need to do if you
want your program to honour the visual style setting of Windows XP is to
Windows XP introduced the themes (called "visual styles" in the Microsoft
documentation) which have been used since then for Win32 controls.
As wxWidgets uses the standard Windows controls for most of its
classes, it can take advantage of it without (almost) any effort from your part.
The only thing you need to do if you want your program to honour the visual style is to
add the manifest file to your program (this is not at all specific to
wxWidgets programs but is required for all Windows applications).
wxWidgets now includes manifest resources in wx.rc, so it should be enough to
include "wx/msw/wx.rc" in your application's resource file and you get
XP look automatically. Notice that MSVC 2005 and later embed manifest in the
executables it produces and wxWidgets doesn't use its own manifest when using
this compiler. And if you don't want to use wxWidgets manifest with another
compiler you may define wxUSE_NO_MANIFEST as 1 prior to including wx/msw/wx.rc.
proper look automatically. Notice that MSVS automatically generates the manifest
and embeds it in the executables it produces. Therefore, wxWidgets by default doesn't
use its own manifest when using MSVC (i.e., wxUSE_RC_MANIFEST is not defined as 1).
If you don't want to use wxWidgets manifest with any compiler you may define wxUSE_NO_MANIFEST
as 1 prior to including wx/msw/wx.rc.
wxWidgets offers three manifests, differing only in which DPI-awareness mode they use.
Which of the three is used depends on the value of wxUSE_DPI_AWARE_MANIFEST define.
See more in @ref high_dpi_platform_msw "MSW Platform-Specific Build Issues" the High DPI guide.
Finally, if all else fails you may always use a manifest manually. For this you
need to create your own manifest file and put it in a file called
"yourapp.exe.manifest" in the same directory where "yourapp.exe" resides.
Alternatively, you can include the manifest in your applications resource
section. Please see the MSDN documentation at
http://msdn.microsoft.com/en-us/library/windows/desktop/bb773175
for more details.
Here is the example manifest which you can put into controls.exe.manifest
file to test theme support using the controls sample:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="0.64.1.0"
processorArchitecture="x86"
name="Controls"
type="win32"
/>
<description>Controls: wxWidgets sample application</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="*"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>
More information about application manifests is available at
https://learn.microsoft.com/en-us/windows/win32/controls/cookbook-overview#using-manifests-or-directives-to-ensure-that-visual-styles-can-be-applied-to-applications