Disable skinning for task dialogs
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=6904
Printed Date: 27 September 2024 at 9:25pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Disable skinning for task dialogs
Posted By: ABuenger
Subject: Disable skinning for task dialogs
Date Posted: 17 April 2007 at 12:21pm
If you enable skinning and then disable it only for the task dialog (XTPSkinManager()->SetAutoApplyNewWindows(FALSE);), the dialog still gets partially skinned.  Why do the command links - which are basically just buttons - get completely skinned while the other buttons not? ------------- Codejock support |
Replies:
Posted By: ABuenger
Date Posted: 17 April 2007 at 1:15pm
Disabling xtpSkinApplyColors also doesn't help: ------------- Codejock support |
Posted By: Oleg
Date Posted: 17 April 2007 at 2:08pm
|
Hello,
Afraid CXTPWinThemeWrapper::IsAppThemeReady will return always TRUE if skinframework used. What problem to use skin for TaskDialog? ------------- Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS |
Posted By: ABuenger
Date Posted: 17 April 2007 at 5:51pm
Like in Office I do not want to skin (modal) dialogs, which looks odd. You can't really distinguish the dialog from the main frame, the unskinned dialog has a better contrast to the main frame. I'd say the Task Dialog behavior is a bug, isn't it? ------------- Codejock support |
oleg wrote:Posted By: Oleg
Date Posted: 18 April 2007 at 1:16am
|
Hello,
No its not bug. IsAppThemeReady is global method and it can't recognize who call it - skinned window or not.
We agree that with skinframework its problem to have some skinned dialogs and some not because of global methods - for example hooking GetSysColor we can't recognize if need to return sysmem colors for non skinned dialog to colors from skin. ------------- Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS |