Skin Framework - DestroyWindow() -> Run-Time Check Failure #0

Print Page | Close Window

DestroyWindow() -> Run-Time Check Failure #0

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Skin Framework
Forum Description: Topics Related to Codejock Skin Framework
URL: http://forum.codejock.com/forum_posts.asp?TID=7714
Printed Date: 23 November 2024 at 12:30pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: DestroyWindow() -> Run-Time Check Failure #0

Posted By: dbrulhart
Subject: DestroyWindow() -> Run-Time Check Failure #0
Date Posted: 02 August 2007 at 1:40pm

Hi all,

When calling DestroyWindow() on either a CMDIChildWnd or CMDIFrameWnd (called by MFC in OnClose()) produces the following crash in CXTPSkinManagerApiHook::ThreadProcHook()

Error: Run-Time Check Failure #0 - The value of ESP was not properly saved across a function call.

Just upgraded to toolkit 11.1.3 and observing this one. Was fine under 10.3.1.

An other application that I just skinned by adding only the two following lines (and nothing else at all) produces the same issue.

XTPSkinManager()->SetApplyOptions(xtpSkinApplyFrame | xtpSkinApplyColors | xtpSkinApplyMetrics);

XTPSkinManager()->LoadSkin(_T("d:\\XtremeToolkitPro\\Bin\\vc71\\Styles\\Vista.cjstyles"), _T("NormalBlack.ini"));

Am I missing something ?

Thanks for your help

Dominique

Replies:

Posted By: ABuenger
Date Posted: 02 August 2007 at 4:01pm

Is this a multithreaded app? I had several problems when the MDI main frame terminates a thread after OnClose has been called.

-------------
Codejock support

Posted By: dbrulhart
Date Posted: 02 August 2007 at 4:38pm

Yes, it is a heavily multithreaded application.

However, what is strange is that it seems that it worked fine under 10.3.1...

Posted By: Oleg
Date Posted: 03 August 2007 at 3:33am

Hello,

As temporary workaround you can disable auto apply new threads:

XTPSkinManager()->SetAutoApplyNewThreads(FALSE);

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: dbrulhart
Date Posted: 03 August 2007 at 10:01am

Hi Oleg,

Works now. Thanks for the fix.

By temporary workaround, do you mean this will have an impact on performances (or some other impact) on multithreaded apps or we can live with this solution more or less permanently ?

Thanks again

Dominique

Posted By: Oleg
Date Posted: 04 August 2007 at 2:20am

Hello,

Only one difference - it will skin only main thread - if you create dialogs in another threads they will be not skinned.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: dbrulhart
Date Posted: 07 August 2007 at 10:23am

Hi Oleg,

We have another issue/question with skinning.

We have many .exe and .dll that have to be skinned and we have many base classes derived from CMDIFrameWnd, CFrameWnd, CPropertySheet and CDialog.

What would be convenient is to call the LoadSkin in each of these classes constructors, so all would be automatic.

I've tried to check.

It seems working fine for MDI frame (there's only one per app), but I observe some refresh and flicking everytime we open any of these frame, dialog or sheet in an application already skinned.

Is it OK to call LoadSkin everytime for every window or does this eats GDI resources... or even may cause some of the performance issues related in thread #24926 ?

Is ther any better way ? I would like to avoid to add the LoadSkin() in every application or dll, but only once, etc... Would be much easier to have it automatic.

Thanks for your thoughts

Dominique

Posted By: Oleg
Date Posted: 08 August 2007 at 2:16am

Hello,

You only need call LoadSkin in main application.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: dbrulhart
Date Posted: 08 August 2007 at 5:24am

Hi Oleg,

That's what I expect, but I'm also trying to keep a generic code for all our apps based on the base classes we already have, without tweaking all apps.

Is the SkinManager dependant of the the CWnd class ? I see in your examples than you seem always call it from the CMainFrame class.

Would it be possible to all LoadSkin from CWinApp::InitInstance() or is it too early ?

Thank for your support

Dominique