http://forum.codejock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Wed, 13 May 2026 12:23:42 +0000 Tue, 05 Dec 2017 22:03:18 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 forum.codejock.com/RSS_post_feed.asp?TID=23518 http://forum.codejock.com/forum_images/codejock-logo.gif http://forum.codejock.com/ http://forum.codejock.com/forum_posts.asp?TID=23518&PID=76372&title=solved-qat-controls-wont-draw-with-office-2013#76372 Author: olebed
Subject: 23518
Posted: 05 December 2017 at 10:03pm

Hello rdhd,

Thank you for bringing this to our attention. I have added this to our task list for next release.

Regards,
 Oleksandr Lebed]]> Tue, 05 Dec 2017 22:03:18 +0000 http://forum.codejock.com/forum_posts.asp?TID=23518&PID=76372&title=solved-qat-controls-wont-draw-with-office-2013#76372 http://forum.codejock.com/forum_posts.asp?TID=23518&PID=76361&title=solved-qat-controls-wont-draw-with-office-2013#76361 Author: rdhd
Subject: 23518
Posted: 01 December 2017 at 4:59pm

I just traced another problem down where users are claiming they cannot see the drop arrow on popup controls we build into the QAT. Our undo/redo (added out-of-the-box) to the QAT have no drop arrows. You can click where they reside and the control will pop. If I customize and add a popup control from the ribbon to the QAT, you can see the same thing. My code change to DraqQuickAccessControl where I comment out all the code except the call to pControl->Draw fixes that too. The user work-around until I roll this out is to move the QAT so it is below the ribbon.
]]> Fri, 01 Dec 2017 16:59:38 +0000 http://forum.codejock.com/forum_posts.asp?TID=23518&PID=76361&title=solved-qat-controls-wont-draw-with-office-2013#76361 http://forum.codejock.com/forum_posts.asp?TID=23518&PID=76359&title=solved-qat-controls-wont-draw-with-office-2013#76359 Author: rdhd
Subject: 23518
Posted: 01 December 2017 at 10:43am

We have upgraded to V 18.0.1. We use the office 2013 ribbon theme. Now I have yet another "breaking" change in this upgrade. CXTPRibbonbar::DrawCommandBar used to call the Draw method on the controls on the QAT. But now there is a CXTPRibbonOffice2013Theme::DrawQuickAccessControl.

In that method, the code looks to see if the control has an icon. If it does not, it simply exits! The result is the customers that have QAT entries that have text but no icon see nothing. There are just big gaps where the controls would draw. The measure/sizing code cares nothing about the icon not existing and measures the text size, hence the gaps I see where the controls should be drawing.

IN V17, like with Microsoft Office 2013, controls that only have text would draw the text just fine. So why has CJ broken something that has worked for a number of years? Is this a bug? If so, is it fixed in a later release like 18.3?

Breaking changes like this are quite frustrating :( Upgrading CJ should be as smooth as upgrading to a new Visual Studio MFC version.
]]> Fri, 01 Dec 2017 10:43:29 +0000 http://forum.codejock.com/forum_posts.asp?TID=23518&PID=76359&title=solved-qat-controls-wont-draw-with-office-2013#76359