Print Page | Close Window

CXTPFrameShadow covers the whole application

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Toolkit Pro
Forum Description: Topics Related to Codejock Toolkit Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=23710
Printed Date: 16 October 2018 at 3:00pm


Topic: CXTPFrameShadow covers the whole application
Posted By: Fredrik
Subject: CXTPFrameShadow covers the whole application
Date Posted: 10 September 2018 at 11:34am
Hi, 

after upgrading to 18.5 I get a shadow over the whole application when it opens on another monitor than the primary (I save window position) and call EnableFrameTheme. I found that if I set m_hOwner to NULL as suggested in http://forum.codejock.com/forum_posts.asp?TID=23639 the problem disappears, but I see that in 18.5 m_hOwner is still passed to CWnd::CreateEx? 

Should m_hOwner be NULL in this case?

The shadow causes the whole application to be unresponsive and cannot be used... 

I haven't been able to reproduce it with the RibbonSample unfortunately.


-------------
Windows 10, Visual Studio 20157, Toolkit Pro 18.3.0



Replies:
Posted By: sbinder
Date Posted: 02 October 2018 at 2:44am
And only if FrameTheme is enalbed!


Posted By: Fredrik
Date Posted: 05 October 2018 at 11:24am
Thanks  - yes I know, I was able to temporarily fix the problem by calling 

XTPFrameShadowManager()->SetFlags(xtpFrameShadowsDisabled);

(Or DisableShadow as you posted)

But then there will not be a shadow around the application which all other programs have. I still hope for a fix from CodeJock - it did work in 18.4.


-------------
Windows 10, Visual Studio 20157, Toolkit Pro 18.3.0


Posted By: astoyan
Date Posted: 09 October 2018 at 10:18am
The bug has been fixed for the next update which is due in about a week or so. Please re-test with a new update once it's available and confirm it fixes it for you.

Regards,
   Alexander


Posted By: markr
Date Posted: 09 October 2018 at 8:13pm
> The bug has been fixed for the next update which is due in about a week or so

Can you share any information on why some applications are experiencing this and not others?

Many thanks!

- Mark R.


Posted By: astoyan
Date Posted: 10 October 2018 at 10:09am
It worked properly in 18.4 because it did not clip the overlapped portion of the shadow which lead to a number of performance related complains, so it's been fixed in 18.5, but the fix introduced a new issue and unfortunately it was not noticed during 18.5 build testing

It happens when DPI is above 96 (100%) for DPI unaware applications only. In fact it has turned out to be a bug in Microsoft's DwmGetWindowAttribute with DWMWA_EXTENDED_FRAME_BOUNDS flag, which does not virtualize DPI as it should, which all other SDK functions do properly. This lead to a workaround being added.

Regards


Posted By: markr
Date Posted: 10 October 2018 at 7:13pm
> It happens when DPI is above 96 (100%) for DPI unaware applications only.

Thanks for the clarification.

- Mark R.



Print Page | Close Window