Proper initialization of static objects (singletons) with splash screen support

Environment: Win98, VC 5.0

Introduction:

Do you have code like this in your InitInstance() ?

  ...
  ClassXY::GlobalInit();
  ClassZA::GlobalSetup();
  ClassMurx::Prepare();
  ...

Then this is what you need!

The cdxCInitializerT base class helps you to design a proper, clear interface to initialize any objects you want in application scope (i.e. your CWinApp object exists during the initialization).  The basic idea is to design a class (cdxCInitializerT) that has two static members, InitInstance() and ExitInstance() which must be called from within your application's InitInstance()/ExitInstance().

These functions should now initialize all exisiting objects of cdxCInitializerT by calling a virtual function OnInitInstance().  Conversely, OnExitInstance() is called to clean up what you allocated using OnInitInstance().  This is exactly what the cdxCInitializerT class offers you  -  an interface to initialize/clean up your objects that have been constructed in global scope (static members variables, global variables).

Moreover, the class can be parameterized (by two template arguments) to give you the chance to provide feedback to the calling function (i.e. each of your objects can get a pointer to a "splash screen" dialog where it can write nice stuff into).  Additionally, the design gives you the opportunity to define an ordering of the initialization (object A will be initialized after B for sure).

Finally, a former class, cdxCInitializerThreadT has been added that helps you to implement a splash screen in a second thread easily (you just need a dialog and some member functions to modify its controls - that's it!).

If you use my class, you should make your InitInstance() look like this:

  ...
  cdxCInitializerThreadT<CSplashScreen> splash;

  if (!cdxCInitializer<..>::InitInstance(splash))
     return FALSE;

and all your nasty classes that used a "GlobalInit()" before will be set up properly - and adding new "GlobalInit()" classes will be easy;  you don't need to modify your application's implementation file anymore.

Features:

  • Support for ordered initialization and clean-up.
  • Support for "Feedback" objects (splash screens).
  • Support to quickly implement a splash screen with a second thread.
  • Rather complete documentation with tutorial and function reference.

Download:

Source code and documentation   Initializer_src.zip (17 KB)
Sample project (includes source code and documentation)   Initializer_proj.zip (61 KB)



Comments

  • C++-sites

    Posted by Legacy on 05/24/1999 12:00am

    Originally posted by: "The notorious Captain Milla"

    Sehr geehrter Herr B�hler

    Ich h�tte eine Frage an Sie und zwar ob Sie weitere deutschsprachige C++-seiten kennen?(englische kenne ich selbst sehr viele).

    ciao

    "The notorious Captain Milla"

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Today's enterprise datacenter can be one of the most complex business environments with dozens (for smaller business), hundreds (for larger and midsize business), even thousands (for hyperscale businesses) of servers that must be managed and monitored. At this level, just managing the cords can be challenging — let alone keeping up with the growing need for more agility and scalability within the datacenter. Simply put, companies are aggressively looking for less complexity and more agility from their …

  • Entire organizations suffer when their networks can't keep up and new opportunities are put on hold. Waiting on service providers isn't good business. In these examples, learn how to simplify network management so that your organization can better manage costs, adapt quickly to business demands, and seize market opportunities when they arise.

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date