Skin Framework - Skinframework crashing

Print Page | Close Window

Skinframework crashing

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=12650
Printed Date: 29 April 2024 at 12:42pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Skinframework crashing

Posted By: aggressor
Subject: Skinframework crashing
Date Posted: 10 November 2008 at 1:56pm

Hi,

We have a very strange Access Violation in the SkinFramework. We need to disable the skining for some time. The only one way that we found to do this is to set SetApllyOptions(0). But then we are calling the thing it's giving access violation. The stack is pointing to dbghlp.dll. We removed the linking to our Dbghelp.dll. But AV still happening, but now call stack is pointing somewhere in the imagehlp.dll.

What it can be?

Thank you.

Replies:

Posted By: ABuenger
Date Posted: 10 November 2008 at 5:18pm

Disable AutoApplyNewThreads or so, crashed here also always.

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

Posted By: aggressor
Date Posted: 11 November 2008 at 11:59am

Hi guys,

So what we can do with it? Giving you an example: 3rd party DLL has a TStatusBar control so we need to disable the skin totally. Disabling AutoApplyThreads and AutoApplyWindows not helping for some controls. So what we can do?

Posted By: Oleg
Date Posted: 11 November 2008 at 3:33pm

Hi,

try to disable skinning for all TStatusBar classes with

XTPSkinManager()->GetClassMap()->AddClass(_T("TStatusBar"), new CXTPSkinObjectClassInfo(NULL));

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

Posted By: aggressor
Date Posted: 12 November 2008 at 1:51pm

Hi,

There are plenty of Delphi controls there. It will be very hard to maintain the thing correctly on each release. Can you try to replicate the thing?

Thank you.

Posted By: aggressor
Date Posted: 12 November 2008 at 1:54pm

Just call SetApplyOptions(0) before any new dialog instance in the Main Frame. We also have the same thing for standart Win32 OpenDialog. If we call SetApplyOptions(0) before OpenDialog we have a crash. But if we do it after first call to OpenDialog all okay :).

Posted By: birinets
Date Posted: 14 November 2008 at 7:24am

HI all,

I have the same problem, I'm getting same Access Violations, using this methods. Do we have a solution?