Themes prevent Windows hook from being called

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi,

We're currently facing an issue using the Codejock CommandBars (v17.2.0) with any of the Office2013 or VS2015 themes. 

As soon as we enable one of those themes, a Windows Hook in our application of type WH_CALLWNDPROCRET is not called any more. It seems the commandBars filter that method? The issue occurs after calling the following methods:

CommandBars.EnableOffice2007Frame(false);
CommandBars.AllowFrameTransparency(false);
CommandBars.EnableOffice2007Frame(true);

After switching back to another theme, it works fine again. This issue can be reproduced in the RibbonSample solution aswell.
Does anyone have a solution or hint for this? 
Thank you!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
BK_ Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 05 October 2016 Status: Offline Points: 2	Post Options Post Reply Quote BK_ Report Post Thanks(0) Quote Reply Topic: Themes prevent Windows hook from being called Posted: 07 November 2016 at 4:06am
	Hi, We're currently facing an issue using the Codejock CommandBars (v17.2.0) with any of the Office2013 or VS2015 themes. As soon as we enable one of those themes, a Windows Hook in our application of type WH_CALLWNDPROCRET is not called any more. It seems the commandBars filter that method? The issue occurs after calling the following methods: CommandBars.EnableOffice2007Frame(false); CommandBars.AllowFrameTransparency(false); CommandBars.EnableOffice2007Frame(true); After switching back to another theme, it works fine again. This issue can be reproduced in the RibbonSample solution aswell. Does anyone have a solution or hint for this? Thank you!

astoyan Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 24 August 2013 Status: Offline Points: 284	Post Options Post Reply Quote astoyan Report Post Thanks(0) Quote Reply Posted: 22 November 2016 at 11:21pm
	Hi, it can be a conflict with frame shadow, please try to call XTPFrameShadowManager()->SetFlags(xtpFrameShadowsDisabled) before any window is created and see if it helps. If it does work then you can use this as a temporary workaround while the actual fix is added. Thank you. Regards, Alexander