Skin Framework vs MFC's CMFCVisualManager

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello,I'm evaluating your Skinning framework for our MFC (vs 2010) MDI application and my question is: in what ways is it better than CMFCVisualManager? 

Also, I only need the skinning abilities so what is the minimum requirements for using it? (include files, lib files etc)

Thank you very much,

Adi Barda

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
adi.barda Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 24 August 2011 Status: Offline Points: 2	Post Options Post Reply Quote adi.barda Report Post Thanks(0) Quote Reply Topic: Skin Framework vs MFC's CMFCVisualManager Posted: 24 August 2011 at 10:20am
	Hello, I'm evaluating your Skinning framework for our MFC (vs 2010) MDI application and my question is: in what ways is it better than CMFCVisualManager? Also, I only need the skinning abilities so what is the minimum requirements for using it? (include files, lib files etc) Thank you very much, Adi Barda

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 26 August 2011 at 4:18am
	CMFCVisualManager is not same as SkinFramework. You call SkinFramework once and it skin all window elements it found. with CMFCVisualManager you must manually subclass each element to corresponding MFC class to see some new look. If you need only Skinfamework, you can purchase Skinframework single package. Try our evaluation version.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

adi.barda Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 24 August 2011 Status: Offline Points: 2	Post Options Post Reply Quote adi.barda Report Post Thanks(0) Quote Reply Posted: 28 August 2011 at 6:08am
	Hi Oleg, The skinning framework doesn't work well for us because our main frame inherits from CMDIFrameWndEx and not from CMDIFrameWnd. This is a problem because your skinning framework class "CXTPMDIFrameWnd" inherits from CMDIFrameWnd and not CMDIFrameWndEX. We would like to use/purchase it very much but we have to find a solution for this issue. we must inherit from CMDIFrameWndEX. Thanks, Adi Barda

ABuenger Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 February 2006 Status: Offline Points: 1075	Post Options Post Reply Quote ABuenger Report Post Thanks(0) Quote Reply Posted: 04 December 2011 at 10:43pm
	Hi, you only need CXTPMDIFrameWnd if you want to use our CommandBars. If you only want to use the SkinFramework you don't need to derive from CXTPMDIFrameWnd. Andre
	Codejock support

Algae Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 08 January 2007 Location: United States Status: Offline Points: 217	Post Options Post Reply Quote Algae Report Post Thanks(0) Quote Reply Posted: 12 November 2013 at 5:11pm
	What is the recommended process to replace the cmfcvisualmanager with Skin Framework in an existing program? As was stated before, there can be all sorts of things manually subclassed. It seems like a pretty hefty task to port. Or is it much simpler than I surmise? Perhaps CJ could get some mileage out of this with people who want to improve programs and get away from using the cmfcvisualmanager bag of snakes.