|
Skinframework crashing |
Post Reply 
|
| Author | |
aggressor 
Groupie 
Joined: 15 August 2007 Location: United States Status: Offline Points: 27 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Skinframework crashingPosted: 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. |
|
 |
|
|
ABuenger
Newbie 
Joined: 02 February 2006 Status: Offline Points: 1075 |
Post Options
Thanks(0)
Quote Reply
Posted: 10 November 2008 at 5:18pm |
|
Disable AutoApplyNewThreads or so, crashed here also always.
|
|
|
Codejock support
|
|
|
|
|
aggressor
Groupie
Joined: 15 August 2007 Location: United States Status: Offline Points: 27 |
Post Options
Thanks(0)
Quote Reply
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? |
|
|
|
|
Oleg
Admin Group 
Joined: 21 May 2003 Location: United States Status: Offline Points: 11234 |
Post Options
Thanks(0)
Quote Reply
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 |
|
|
|
|
aggressor
Groupie
Joined: 15 August 2007 Location: United States Status: Offline Points: 27 |
Post Options
Thanks(0)
Quote Reply
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. |
|
|
|
|
aggressor
Groupie
Joined: 15 August 2007 Location: United States Status: Offline Points: 27 |
Post Options
Thanks(0)
Quote Reply
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 :).
|
|
|
|
|
birinets
Newbie
Joined: 09 April 2008 Location: Ukraine Status: Offline Points: 4 |
Post Options
Thanks(0)
Quote Reply
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? |
|
|
|
|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options