| |
|
|
|
|
|
Forum
Please
Log In
to post a new message or reply to an existing one. If you are not registered, please
register.
NOTE: Some forums may be read-only if you are not currently subscribed to
our technical support services.
|
Subject |
Author |
Date |
|
|
Christan HIRIGOYEN
|
Nov 4, 2015 - 11:53 AM
|
Hello,
I am moving to 3.2.0.5 and I cannot have same behaviour than with 3.01.
The DwmIsCompositionEnabled is always false. the reason seems for me, that the proc name is wrong. You try to retrieve the proc address for ExtDwmIsCompositionEnabled. in 3.1, it works with DwmIsCompositionEnabled.
is it a bug introduced when you have renamed all methods of class CExtDWM with Ext as preffix?
or is this feature deprecated ?
Can I use this feature.?
Regards,
|
|
|
Art Wilkes
|
Nov 5, 2015 - 9:36 AM
|
The code has a wrong initialization value for DwmIsCompositionEnabled function. Replace this line of code:
{ (FARPROC*)&m_pfnDwmIsCompositionEnabled, "ExtDwmIsCompositionEnabled" },
with this one:
{ (FARPROC*)&m_pfnDwmIsCompositionEnabled, "DwmIsCompositionEnabled" },
But, according to MSDN (https://msdn.microsoft.com/en-us/library/windows/desktop/hh848042.aspx),
"According to Desktop Window Manager is always on (Windows) on MSDN:
In Windows 8, Desktop Window Manager (DWM) is always ON and cannot be disabled by end users and apps.
In Windows 8, DWM desktop composition is a core operating system component and cannot be disabled. With a few exceptions, desktop composition is always on; it’s started before the user logon and remains active for the duration of a session.
All of the options for disabling desktop composition that exist in Window 7 are removed
Apps cannot use DwmEnableComposition to disable desktop composition. In order to maintain backward compatibility, a call to this API will return success; however, desktop composition is not disabled"
Prof-UIS Support
|
|