Toolkit Pro - v17 VS2015 XTP_IDC_FONT

Print Page | Close Window

v17 VS2015 XTP_IDC_FONT_CODEJOCK

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=22850
Printed Date: 06 May 2024 at 11:27am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: v17 VS2015 XTP_IDC_FONT_CODEJOCK

Posted By: ojones
Subject: v17 VS2015 XTP_IDC_FONT_CODEJOCK
Date Posted: 18 January 2016 at 6:33am

HI,

I've just installed and integrated the latest version with my app. In Debug I keep hitting the following assert too frequently and it is hindering all debug development work.

ASSERT(NULL != hResModule); // line 3091 in void CXTPPrimitiveDrawer::InitFont() in the file XTPDrawHeplers.

void CXTPPrimitiveDrawer::InitFont()

{

if (NULL == m_hCodejockMemFont)

{

::EnterCriticalSection(&m_fontAccess);

if (NULL == m_hCodejockMemFont

&& NULL != m_pfnAddFontMemResourceEx)

{

HMODULE hResModule = AfxFindResourceHandle(

MAKEINTRESOURCE(XTP_IDC_FONT_CODEJOCK), RT_FONT);

ASSERT(NULL != hResModule);

The resource reference seems to be located in "rc" file Source\Common\Resource-Neutral.rc

and the resource is located @ "Common/res/Codejock.ttf"

XTP_IDC_FONT_CODEJOCK FONT DISCARDABLE "Common/res/Codejock.ttf"

The solutions provided don't seem to load any resources except those from ToolkitPro.rc which is basically the version.

I don't really want to have to mess about with the default installation to be rid of hitting this annoying ASSERT and it doesn't appear to be a problem if it doesn't load it when running the Release build.

Any ideas?

Replies:

Posted By: ericchubb
Date Posted: 28 July 2016 at 6:30am

I'm having the same issue - it only appears in debug mode but can be very annoying! Any help would be appreciated

-------------
Eric

Product: Xtreme Toolkit Version 22.0

Platform: Windows 11 (64bit) -

Language: Visual C++ 2022 /C# .NET 2/3.5/4/5/6/7

Posted By: Cedric_ar
Date Posted: 17 February 2017 at 2:09pm

I have the same problem with V17.3.1 how can i handle that. I really annoying. I'm using Xtp in dll mode no unicode.