Create a CheckListboxItem - Revision history

Capek: because references rule

2011-03-06T01:37:42Z

because references rule

Capek: Spelling fix

2011-03-03T23:56:44Z

Spelling fix

Capek: Bot: Automated text replacement (-\[\[(.?)\|.?\]\] +\1)

2011-03-03T23:48:59Z

Bot: Automated text replacement (-\[\[(.*?)\|.*?\]\] +\1)

Capek: Experiment to make the wiki more interlinked

2011-03-03T23:15:01Z

Experiment to make the wiki more interlinked

Capek: Robot: Cosmetic changes

2011-02-26T15:04:58Z

Robot: Cosmetic changes

Kulik at 13:12, 26 February 2011

2011-02-26T13:12:09Z

Ident at 12:26, 26 February 2011

2011-02-26T12:26:00Z

Tss at 12:10, 26 February 2011

2011-02-26T12:10:06Z

Levia at 14:53, 9 May 2007

2007-05-09T14:53:21Z

Rackle at 12:06, 9 May 2007

2007-05-09T12:06:08Z

@@ Line 457: / Line 457: @@
+  {
       CEGUI::System * m_System = CEGUI::System::getSingletonPtr();
-      CEGUI::Logger::getSingletonPtr()->setLoggingLevel(CEGUI::Insane);
+      CEGUI::Logger::getSingleton().setLoggingLevel(CEGUI::Insane);
       CEGUI::WindowManager * m_WndMgr = CEGUI::WindowManager::getSingletonPtr();
       CEGUI::Window * m_Root = m_System->getGUISheet();

@@ Line 77: / Line 77: @@
 These states pretty much speak for themselves altough there are more sections listed. Section not only defines what to change, also defines what needs to be shown. In the Enabled state we dont want it to look like its selected, so there is no selection section. Note that the order of which you put the Sections are also the Z order. In this case we are putting the selection image first, and then text. If we would do it the other way around, we wouldn't see the text.
-Now we are going to add the definitions of some colors and property's.
+Now we are going to add the definitions of some colours and property's.
   <WidgetLook name="WindowsLook/CheckListboxItem">
@@ Line 117: / Line 117: @@
   </WidgetLook>
-Our first PropertyDefinition just defines a text for a colour used in the StateImagery sections. Same goes for the other PropertyDefinitions except the SelectionBrush. Instead of defining a color, it defines a image. In this case it uses the WindowsLook Background image defined in the imageset. Then we got a Property, which simply implies some sort of setting. In this case, we make it a item by adding the Property 'Selectable' and setting it to true as we want it to act like an item.
+Our first PropertyDefinition just defines a text for a colour used in the StateImagery sections. Same goes for the other PropertyDefinitions except the SelectionBrush. Instead of defining a colour, it defines a image. In this case it uses the WindowsLook Background image defined in the imageset. Then we got a Property, which simply implies some sort of setting. In this case, we make it a item by adding the Property 'Selectable' and setting it to true as we want it to act like an item.
 == Writing the functional parts ==
@@ Line 250: / Line 250: @@
   </ImagerySection>
-Note that we give it the name selection, as used in the StateImagery. The Area part is just positioning and fitting again. The Dim's used there simply make sure the whole item is filled. ImageProperty defines the image to use. We have defined SelectionBrush at the top of our WidgetLook. It simply fills the Area with that image now. ColourProperty colors the image, we have also defined SelectionColour at the top of the WidgetLook. VertFormat and HorzFormat are stretched, if its not stretched, it will only draw one pixel of the image, making it near invisible. Stretching it just makes sure the whole area is covered.
+Note that we give it the name selection, as used in the StateImagery. The Area part is just positioning and fitting again. The Dim's used there simply make sure the whole item is filled. ImageProperty defines the image to use. We have defined SelectionBrush at the top of our WidgetLook. It simply fills the Area with that image now. ColourProperty colours the image, we have also defined SelectionColour at the top of the WidgetLook. VertFormat and HorzFormat are stretched, if its not stretched, it will only draw one pixel of the image, making it near invisible. Stretching it just makes sure the whole area is covered.
 That was it! We wrote our looknfeel entry!!

← Older revision		Revision as of 23:48, 3 March 2011
Line 481:		Line 481:


−	--[[User:~~Levia\|~~Levia]] 21:10, 5 April 2007 (GMT+1)	+	--[[User:Levia]] 21:10, 5 April 2007 (GMT+1)

	[[Category:Tutorials]]		[[Category:Tutorials]]

@@ Line 13: / Line 13: @@
 == Writing the requirements ==
-Open the appriopiate looknfeel file (WindowsLook.looknfeel or TaharezLook.looknfeel), and place this at the bottom (inside the Falagard tags though!)
+Open the appriopiate looknfeel file (WindowsLook.looknfeel or TaharezLook.looknfeel), and place this at the bottom (inside the [[Falagard]] tags though!)
 ''' Our start '''
@@ Line 369: / Line 369: @@
 == Coding our item ==
-We have come to the part where we actually try out our new item. We need to do a few things to call this one finished. First, we need to create the CheckListboxItem class. Then we are going to add the window factory to the system. Last but not least is adding the Falagard mapping. We'll start with the CheckListboxItem class.
+We have come to the part where we actually try out our new item. We need to do a few things to call this one finished. First, we need to create the CheckListboxItem class. Then we are going to add the window factory to the system. Last but not least is adding the [[Falagard]] mapping. We'll start with the CheckListboxItem class.
 ==== CheckListItem.h ====

@@ Line 1: / Line 1: @@
 Sometimes you need a list where the items are checkable. The ItemListbox introduced in CEGUI 0.5 accepts all sorts of items, as long as they inherit ItemEntry. I'm going to teach you how to create a CheckListboxItem to put in your list.
-==Getting started!==
+== Getting started! ==
 I'm assuming you are just using a standard imageset, with a standard scheme (currently TaharezLook and WindowsLook are supported).
 We are first going to get started by writing the looknfeel entry. This is the most important part of this tutorial, as its basically 70% of what we need to do to achieve our goal. First of all, this entry has a few states:
-#Enabled: How the item looks when the item is enabled.
+# Enabled: How the item looks when the item is enabled.
-#Disabled: How the item looks when the item is disabled.
+# Disabled: How the item looks when the item is disabled.
-#SelectedEnabled: How the item looks when the item is selected and is enabled.
+# SelectedEnabled: How the item looks when the item is selected and is enabled.
-#SelectedDisabled: How the item looks when the item is selected and is disabled.
+# SelectedDisabled: How the item looks when the item is selected and is disabled.
-==Writing the requirements==
+== Writing the requirements ==
 Open the appriopiate looknfeel file (WindowsLook.looknfeel or TaharezLook.looknfeel), and place this at the bottom (inside the Falagard tags though!)
@@ Line 121: / Line 119: @@
 Our first PropertyDefinition just defines a text for a colour used in the StateImagery sections. Same goes for the other PropertyDefinitions except the SelectionBrush. Instead of defining a color, it defines a image. In this case it uses the WindowsLook Background image defined in the imageset. Then we got a Property, which simply implies some sort of setting. In this case, we make it a item by adding the Property 'Selectable' and setting it to true as we want it to act like an item.
-==Writing the functional parts==
+== Writing the functional parts ==
 We now need to add the parts where the background, text and the selection gets drawn. This seems hard, but isn't actually. We are going to start off with a NamedArea. This is required for a listbox item as the listbox needs to know how big the item is to fit it into the list.
@@ Line 369: / Line 367: @@
 Pfew am I glad thats done.
-==Coding our item==
+== Coding our item ==
 We have come to the part where we actually try out our new item. We need to do a few things to call this one finished. First, we need to create the CheckListboxItem class. Then we are going to add the window factory to the system. Last but not least is adding the Falagard mapping. We'll start with the CheckListboxItem class.
-====CheckListItem.h====
+==== CheckListItem.h ====
   #ifndef _CHECKLISTITEM_
   #define _CHECKLISTITEM_
@@ Line 379: / Line 377: @@
   #include <stdlib.h>
   #include <CEGUI.h>
-  <br>
+  <br />
   namespace CEGUI
+  {
@@ Line 394: / Line 392: @@
   #endif
-As you can see, this class inherits ItemEntry. This is necessary as its THE thing that makes this item working properly. Pay special attention to <b>CEGUI_DECLARE_WINDOW_FACTORY(CheckListboxItem)</b>. This tells CEGUI that we are declarating the window.
+As you can see, this class inherits ItemEntry. This is necessary as its THE thing that makes this item working properly. Pay special attention to '''CEGUI_DECLARE_WINDOW_FACTORY(CheckListboxItem)'''. This tells CEGUI that we are declarating the window.
-====CheckListItem.cpp====
+==== CheckListItem.cpp ====
   #include "CheckListItem.h"
-  <br>
+  <br />
   namespace CEGUI
+  {
@@ Line 412: / Line 410: @@
+  }
-<b>CEGUI_DEFINE_WINDOW_FACTORY(CheckListboxItem)</b> is quite important here. It tells CEGUI where we are placing the code that comes with the window. As you can see this class is quite empty, you are, of course, free to add anything you like to this class - these are just the mere basics.
+'''CEGUI_DEFINE_WINDOW_FACTORY(CheckListboxItem)''' is quite important here. It tells CEGUI where we are placing the code that comes with the window. As you can see this class is quite empty, you are, of course, free to add anything you like to this class - these are just the mere basics.
 Now, there is one more important thing to do. Register this window properly in CEGUI.
@@ Line 426: / Line 424: @@
+  }
-addFalagardWindowMappings parameters are as follows: Name, Type, LooknFeel, WindowRenderer. Just put this code somewhere in your main file or on another place that you are sure is executed before using our new item. Also note, in order to use <b>CEGUI_WINDOW_FACTORY()</b> you need to be in the CEGUI namespace.
+addFalagardWindowMappings parameters are as follows: Name, Type, LooknFeel, WindowRenderer. Just put this code somewhere in your main file or on another place that you are sure is executed before using our new item. Also note, in order to use '''CEGUI_WINDOW_FACTORY()''' you need to be in the CEGUI namespace.
 '''Example'''
-====main.cpp====
+==== main.cpp ====
   #include <stdio.h>
   #include <stdlib.h>
@@ Line 436: / Line 434: @@
   #include "CheckListItem.h"
   void doStuff();
-  <br>
+  <br />
   namespace CEGUI
+  {
@@ Line 455: / Line 453: @@
       return 0;
+  }
-  <br>
+  <br />
   void doStuff()
+  {
@@ Line 462: / Line 460: @@
       CEGUI::WindowManager * m_WndMgr = CEGUI::WindowManager::getSingletonPtr();
       CEGUI::Window * m_Root = m_System->getGUISheet();
-      <br>
+      <br />
       CEGUI::ItemListbox * lb = (CEGUI::ItemListbox*)m_WndMgr->createWindow("WindowsLook/ItemListbox", "Lol");
       lb->setSize(CEGUI::UVector2(CEGUI::UDim(0.3f, 0.0f), CEGUI::UDim(0.3f, 0.0f)));
       lb->setPosition(CEGUI::UVector2(CEGUI::UDim(0.1f, 0.0f), CEGUI::UDim(0.1f, 0.0f)));
       m_Root->addChildWindow(lb);
-      <br>
+      <br />
       CEGUI::CheckListboxItem * check = (CEGUI::CheckListboxItem*)m_WndMgr->createWindow("WindowsLook/CheckListboxItem", "Test");
       check->setText("Test");
@@ Line 484: / Line 482: @@
 --[[User:Levia|Levia]] 21:10, 5 April 2007 (GMT+1)

← Older revision		Revision as of 13:12, 26 February 2011
Line 1:		Line 1:
−	[[category: Tutorials~~]][[Category: HowTo~~]]	+	[[category: Tutorials]]

	Sometimes you need a list where the items are checkable. The ItemListbox introduced in CEGUI 0.5 accepts all sorts of items, as long as they inherit ItemEntry. I'm going to teach you how to create a CheckListboxItem to put in your list.		Sometimes you need a list where the items are checkable. The ItemListbox introduced in CEGUI 0.5 accepts all sorts of items, as long as they inherit ItemEntry. I'm going to teach you how to create a CheckListboxItem to put in your list.

← Older revision		Revision as of 12:26, 26 February 2011
Line 1:		Line 1:
−	[[category: Tutorials]]	+	[[category: Tutorials]][[Category: HowTo]]

	Sometimes you need a list where the items are checkable. The ItemListbox introduced in CEGUI 0.5 accepts all sorts of items, as long as they inherit ItemEntry. I'm going to teach you how to create a CheckListboxItem to put in your list.		Sometimes you need a list where the items are checkable. The ItemListbox introduced in CEGUI 0.5 accepts all sorts of items, as long as they inherit ItemEntry. I'm going to teach you how to create a CheckListboxItem to put in your list.

← Older revision		Revision as of 12:10, 26 February 2011
Line 1:		Line 1:
		+	[[category: Tutorials]]
		+
	Sometimes you need a list where the items are checkable. The ItemListbox introduced in CEGUI 0.5 accepts all sorts of items, as long as they inherit ItemEntry. I'm going to teach you how to create a CheckListboxItem to put in your list.		Sometimes you need a list where the items are checkable. The ItemListbox introduced in CEGUI 0.5 accepts all sorts of items, as long as they inherit ItemEntry. I'm going to teach you how to create a CheckListboxItem to put in your list.

@@ Line 384: / Line 384: @@
       protected:
       public:
-          CheckListboxItem(const String &type, const String &name, const String& text = "test");
+          CheckListboxItem(const String &type, const String &name);
           virtual ~CheckListboxItem();
           static const String WidgetTypeName;
@@ Line 401: / Line 401: @@
       CEGUI_DEFINE_WINDOW_FACTORY(CheckListboxItem)
       const String CheckListboxItem::WidgetTypeName("CEGUI/CheckListboxItem");
-      CheckListboxItem::CheckListboxItem(const String &type, const String &name, const String& text) :
+      CheckListboxItem::CheckListboxItem(const String &type, const String &name) :
-              ItemEntry(type, name),
+              ItemEntry(type, name)
-             d_itemText(text)
+      {
+      }