Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles / Languages / C#

Use the Free USkin Toolkit to Skin your Application

3.39/5 (51 votes)
10 Nov 2008CPOL4 min read 3   43.4K  
USkin provides a free library and tools to developers for easily adding skins to their software UI.

The current version (V3.0 beta) does not need skinbuilder, the next version will provide one.

Sample Image

Introduction

As we know, Windows XP adds support for themes for applications. When we change the Windows theme, all the Windows standard applications change into the same theme. How can we add skin support to our own software and make our software different from others? Here, I suggest a way: use the USkin toolkit.

Why USkin?

  1. Saves your development time. You don't have to care too much about your software UI. After finishing your functions, add three lines of code to support a skin. It's very easy, and will save you time.
  2. Makes your app look and feel good:), that's it.
  3. Supports color themes. This can make a skin file look like a 100 different skins. Save your UI design time.
  4. USkin provides a free version. Save your money!
  5. Free powerful SkinStudio included that you can use to design your own skin file.

Image 2

USkin Features

  • Supports more than 20 Windows standard controls
  • Supports system standard dialogs, such as file dialogs, color dialogs, print dialogs
  • Supports custom defined controls/third party controls
  • Supports WYSIWYG style skin file editing
  • Supports MDI/SDI/Dialog style apps
  • Supports window blinds skin file importing. More than 10000 skin files can be used
  • Supports color themes
  • Supports VC/SDK/VB/.NET, no language limitations
  • Supports multithreading
  • Supports changing skin at runtime
  • Supports all popup menus, including the edit control context menu!
  • Only two lines required to add skin support
  • Supports all scrollbar skins
  • Small skin file size, around 30 KB

Using the Code

Using USkin functions is very easy. Let's begin.

First, include the USkin.h file in your app:

C++
#include "uskin.h"

Then, in the InitInstance function, call USkinInit to initiate the USkin library:

C++
BOOL CSDIApp::InitInstance()
{
    InitCommonControls();

    CWinApp::InitInstance();

    if (!AfxOleInit())
    {
        AfxMessageBox(IDP_OLE_INIT_FAILED);
        return FALSE;
    }
    AfxEnableControlContainer();
    // Init USkin lib and load media skin file
    USkinInit(NULL,NULL,_T("..\\Skins\\vista.msstyles"));
    SetRegistryKey(_T("Local App"));
    LoadStdProfileSettings(4);

    CSingleDocTemplate* pDocTemplate;
    pDocTemplate = new CSingleDocTemplate(
        IDR_MAINFRAME,
        RUNTIME_CLASS(CSDIDoc),
        RUNTIME_CLASS(CMainFrame),
        RUNTIME_CLASS(CSDIView));
    if (!pDocTemplate)
        return FALSE;
    AddDocTemplate(pDocTemplate);

    this->RegisterShellFileTypes();
    TCHAR sz[500];
    ::GetModuleFileName(NULL,sz,500);
    AfxMessageBox(sz);

    CCommandLineInfo cmdInfo;
    ParseCommandLine(cmdInfo);

    if (!ProcessShellCommand(cmdInfo))
        return FALSE;

    m_pMainWnd->ShowWindow(SW_SHOW);
    m_pMainWnd->UpdateWindow();

    //if you want do your own subclass,call USkinInit here
    //USkinInit(NULL,NULL,_T("vista.msstyles"));

    return TRUE;
}

In the end, call USkinExit before your app exits:

C++
int CSDIApp::ExitInstance()
{
    USkinExit();
    return CWinApp::ExitInstance();
}

Using the Code in .NET

The sample code is in C#. You can easily change to other .NET languages. OK, let's begin. First add USkinSDK.cs to your project. Then in the Main entry, add one line of code like this:

C#
//First Declare a skin object
    [STAThread]
	static void Main()
	{
        USkinSDK.USkinInit("", "", "..\\Skins\\DiyGreen.msstyles");
		Application.Run(new Form1());
	}
}

For skinning the Button (GroupBox, CheckBox, RadioButton) object correctly, you need to change the FlatStyle property into System.

The resulting screen will look like this:

Image 3

Points of Interest

This article does not focus on the technical side of the implementation. If you want to know how it works, you can try these CodeProject articles:

History

  • Updates in version 3.0 beta [2008-11-10]
    • New render engine. I rewrote the core render engine such that it is faster, of high quality, and safer.
    • Added Microsoft Window's Theme file format (*.msstyles) support. The user does not need to convert or edit the skin file. There are many skin files to use.
    • Added Multi-Monitor support.
    • Fixed USkin2.2 known bugs.
    • Removed custom draw functions in this version because it was using the Microsoft theme file.
  • Updates in version 2.2 [2006-08-07]
    • Fixed the menubar update error.
    • Added the USkinUpdateMenuBar function. When the user modifies the menu by USkinGetMenu, the user should call USkinUpdateMenuBar to update the menubar.
    • Added RightToLeft text support.
    • Added Winamp like player sample.
    • USkin file format compatible.
    • Enhanced the SkinBuilder.
    • Added SkinBuilder Help document.
    • Added multilanguage support to SkinBuilder.
    • Enhanced ScrollBar control.
  • Updates in version 2.1
    • Fixed the MultiLine style in Button/CheckBox/RadioBox.
    • Added .NET skin support. Now you can use USkin with your .NET applications!
    • Added a new library called USkinCom. Easy for .NET use.
    • Added two C# samples. One is MDI, the other is SDI. You can see the power of USkin in these samples.
    • Added color replace feature. Now, you can replace standard system colors.
    • Enhanced the USkinApplyColorTheme function. Everything will change when calling the USkinApplyColorTheme function.
    • Added the USkinDrawFrameControl function to replace the standard DrawFrameControl.
    • Added six skin files to the pack. All skin files are carefully edited.
    • Enhanced many functions.

Special Thanks

  • Thanks to The Code Project for providing a good platform for developers
  • Thanks to you guys who use uskin
  • Thanks AlecJames - He found a multi-monitor bug. Sorry man, I took a long time to make v3.0

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)