Home - Forums - Documentation - Gallery - Bugs
m
m
Line 11: Line 11:
<pre>
<pre>
It is important that applications using CEGUI from Crystal Space do not use any of
It is important that applications using CEGUI from Crystal Space do not use any of
-
 
+
the CEGUI getSingleton() or getSingletonPtr() calls, such as
-
the CEGUI getSingleton() or getSingletonPtr() calls, such as
+
CEGUI::Singleton<T>::getSingleton() or CEGUI::System::getSingleton(). The reason
CEGUI::Singleton<T>::getSingleton() or CEGUI::System::getSingleton(). The reason
for this is that global and static variables (declared in methods, classes,
for this is that global and static variables (declared in methods, classes,

Revision as of 08:36, 19 January 2007

Step Four: : Using CEGUI

In this tutorial we will create our applications’ windows with the help of CEGUI. This tutorial contains basic information only about the library , when CEGUI is new for you, please visit the project website for more information:

www.cegui.org.uk

The CS SDK has a Ceguitest, a basic example, how you can integrate CEGUI into your application. The viewmesh test application uses also CEGUI, here you can find a long and detailed example to deal with this impressive windowing system. Some notes about CEGUI under CS. There is an introduction to Cegui in the manual, please read this section first. I cite the most important section:

It is important that applications using CEGUI from Crystal Space do not use any of
the CEGUI getSingleton() or getSingletonPtr() calls, such as 
CEGUI::Singleton<T>::getSingleton() or CEGUI::System::getSingleton(). The reason 
for this is that global and static variables (declared in methods, classes, 
namespaces, or globally) are not normally shared between modules. Calling 
getSingleton() from the Crystal Space application will not necessarily return 
the same instance as calling getSingleton() from the CEGUI plugin.
| Article | Discussion | View source | History |