15,979
社区成员
发帖
与我相关
我的任务
分享vs2008 C++ SDK 程序按钮不是 windows7 风格的
XP 下用 VS2008 开发的 C++ SDK 程序，在 windows7 下运行时，主窗口能显示为 windows7 风格，主窗口的最小化、最大化、关闭按钮都是 windows7 风格，但是窗口内部的按钮不是，只是很朴素的普通按钮。怎么改成 windows7 风格？
...全文
请发表友善的回复…
发表回复
tangliang22 2009-11-22
- 打赏
- 举报
[Quote=引用 6 楼 tr0j4n 的回复:]
Try Embed Manifest。Not Only for the XP Style
[/Quote]
多谢。没搜对，搜 vista 风格就好了。找到了 vs 2008 manifest
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='x86' publicKeyToken='6595b64144ccf1df' language='*'\"")
现在好看多了 :-)
Try Embed Manifest。Not Only for the XP Style
[/Quote]
多谢。没搜对，搜 vista 风格就好了。找到了 vs 2008 manifest
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='x86' publicKeyToken='6595b64144ccf1df' language='*'\"")
现在好看多了 :-)
MoXiaoRab 2009-11-21
- 打赏
- 举报
Win32程序？
healer_kx 2009-11-21
- 打赏
- 举报
UP
MoXiaoRab 2009-11-21
- 打赏
- 举报
Try Embed Manifest。Not Only for the XP Style
An assembly’s manifest file typically has a name that includes the name of the assembly,
version information, some text that represents a unique signature, and the extension “.manifest”.
The manifests are stored in \Windows\Winsxs\Manifests, and the rest of the assembly’s resources
are stored in subdirectories of \Windows\Winsxs that have the same name as the corresponding
manifest files, with the exception of the trailing .manifest extension.
An example of a shared assembly is version 6 of the Windows common controls DLL,
comctl32.dll. Its manifest file is named \Windows\Winsxs\Manifests\x86_Microsoft.Windows.
Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.manifest. It has an associated
catalog file (which is the same name with the .cat extension) and a subdirectory of Winsxs that
includes comctl32.dll.
Version 6 of Comctl32.dll added integration with Windows themes, and because applications
not written with theme support in mind might not appear correctly with the new DLL, it’s
available only to applications that explicitly reference the shared assembly containing it—the
version of Comctl32.dll installed in \Windows\System32 is an instance of version 5.x, which is
not theme aware. When an application loads, the loader looks for the application’s manifest, and if
one exists, loads the DLLs from the assemblies specified. DLLs not included in assemblies
referenced in the manifest are loaded in the traditional way. Legacy applications, therefore, link
against the version in \Windows\System32, whereas theme-aware applications can specify the new
version in their manifest.
An assembly’s manifest file typically has a name that includes the name of the assembly,
version information, some text that represents a unique signature, and the extension “.manifest”.
The manifests are stored in \Windows\Winsxs\Manifests, and the rest of the assembly’s resources
are stored in subdirectories of \Windows\Winsxs that have the same name as the corresponding
manifest files, with the exception of the trailing .manifest extension.
An example of a shared assembly is version 6 of the Windows common controls DLL,
comctl32.dll. Its manifest file is named \Windows\Winsxs\Manifests\x86_Microsoft.Windows.
Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.manifest. It has an associated
catalog file (which is the same name with the .cat extension) and a subdirectory of Winsxs that
includes comctl32.dll.
Version 6 of Comctl32.dll added integration with Windows themes, and because applications
not written with theme support in mind might not appear correctly with the new DLL, it’s
available only to applications that explicitly reference the shared assembly containing it—the
version of Comctl32.dll installed in \Windows\System32 is an instance of version 5.x, which is
not theme aware. When an application loads, the loader looks for the application’s manifest, and if
one exists, loads the DLLs from the assemblies specified. DLLs not included in assemblies
referenced in the manifest are loaded in the traditional way. Legacy applications, therefore, link
against the version in \Windows\System32, whereas theme-aware applications can specify the new
version in their manifest.
tangliang22 2009-11-21
- 打赏
- 举报
[Quote=引用 3 楼 fakemajia 的回复:]
manifest?
[/Quote]
查了下 manifest 文件的，但是只查到使用 XP 风格的
manifest?
[/Quote]
查了下 manifest 文件的，但是只查到使用 XP 风格的
tangliang22 2009-11-21
- 打赏
- 举报
[Quote=引用 1 楼 healer_kx 的回复:]
UP
[/Quote]
多谢！
[Quote=引用 2 楼 tr0j4n 的回复:]
Win32程序？
[/Quote]
对，win32 sdk
网上查了下，好像跟 WPF 的实现原理有关——李建忠：WPF内核机制揽胜。
"WPF的主窗口仍然使用经典的windows的消息循环机制。但是它只负责处理WPF主窗口，对于主窗口之上的其他控件，Windows消息将被转化为WPF控件所独有的事件模型，并根据WPF控件的体系层层传递，直到被处理或被忽略。换言之WPF绝大多数控件没有自己的Hwnd，只共享父窗口的Hwnd。 "
但是 Editplus 好像不受影响
UP
[/Quote]
多谢！
[Quote=引用 2 楼 tr0j4n 的回复:]
Win32程序？
[/Quote]
对，win32 sdk
网上查了下，好像跟 WPF 的实现原理有关——李建忠：WPF内核机制揽胜。
"WPF的主窗口仍然使用经典的windows的消息循环机制。但是它只负责处理WPF主窗口，对于主窗口之上的其他控件，Windows消息将被转化为WPF控件所独有的事件模型，并根据WPF控件的体系层层传递，直到被处理或被忽略。换言之WPF绝大多数控件没有自己的Hwnd，只共享父窗口的Hwnd。 "
但是 Editplus 好像不受影响
fakemajia 2009-11-21
- 打赏
- 举报
manifest?
