Dialog System - Revision history

Kulik: moved DialogSystem to Dialog System

2011-02-28T15:39:53Z

moved DialogSystem to Dialog System

Kulik at 15:38, 28 February 2011

2011-02-28T15:38:51Z

Capek: Robot: Adding Category:Uncategorised

2011-02-26T16:46:37Z

Robot: Adding Category:Uncategorised

Capek: Robot: Cosmetic changes

2011-02-26T15:06:19Z

Robot: Cosmetic changes

Rackle: /* DialogSystemDemo.h */

2008-02-01T12:26:30Z

‎DialogSystemDemo.h

Rackle: Compatibility with 0.5 release

2006-12-01T17:33:09Z

Compatibility with 0.5 release

Show changes

Rackle: /* DialogSystem.layout */

2006-06-22T04:10:09Z

‎DialogSystem.layout

Show changes

Rackle: /* DialogSystemDemo.h */

2006-06-22T04:07:34Z

‎DialogSystemDemo.h

Rackle: /* DialogSystemDemo.h */

2006-05-02T20:48:53Z

‎DialogSystemDemo.h

Rackle: /* Explanation */

2006-05-02T20:46:25Z

‎Explanation

@@ Line 1: / Line 1: @@
 The default CEGUI implementation stores the currently specified values of the widgets such that closing and then reopening a window will redisplay those values. Presented here is a different approach, to allow values to be saved or cancelled.
@@ Line 35: / Line 37: @@
 ==== DialogSystemDemo.h ====
-<pre>
+<source lang="cpp">
 #ifndef _DialogSystemDemo_h_
 #define _DialogSystemDemo_h_
@@ Line 179: / Line 181: @@
 #endif // _DialogSystemDemo_h_
-</pre>
+</source>
 ==== DialogSystem.h ====
-<pre>
+<source lang="cpp">
 #ifndef _DialogSystem_h_
 #define _DialogSystem_h_
@@ Line 219: / Line 221: @@
 #endif // _DialogSystem_h_
-</pre>
+</source>
 ==== DialogSystem.cpp ====
-<pre>
+<source lang="cpp">
 #include "DialogSystem.h"
 #include "assert.h"
@@ Line 384: / Line 386: @@
 	return true;
+}
-</pre>
+</source>
 ==== DialogSystem.layout ====
-<pre>
+<source lang="xml">
 <?xml version="1.0" encoding="UTF-8"?>
@@ Line 486: / Line 488: @@
      </Window>
 </GUILayout>
-</pre>
+</source>
 ==== main.cpp ====
-<pre>
+<source lang="cpp">
 #if defined( __WIN32__ ) || defined( _WIN32 )
 	#define WIN32_LEAN_AND_MEAN
@@ Line 508: / Line 510: @@
      return app.run();
+}
-</pre>
+</source>
-[[Category:Uncategorised]]
+[[Category:HowTo]]

← Older revision		Revision as of 16:46, 26 February 2011
Line 509:		Line 509:
	}		}
	</pre>		</pre>
		+
		+	[[Category:Uncategorised]]

@@ Line 1: / Line 1: @@
-The default CEGUI implementation stores the currently specified values of the widgets such that closing and then reopening a window will redisplay those values.  Presented here is a different approach, to allow values to be saved or cancelled.
+The default CEGUI implementation stores the currently specified values of the widgets such that closing and then reopening a window will redisplay those values. Presented here is a different approach, to allow values to be saved or cancelled.
 ==== Explanation ====
-The DemoSample class is the "main" application.  It initializes CEGUI and loads a simple layout.  It then initialises instances of the SimpleWindow and the SimpleDialog classes.  These contain the specific code to handle the behavior of the Simple Window and the Simple Dialog.  In turn they rely on the behaviors define within the DialogSystem class to activate higher level features.
+The DemoSample class is the "main" application. It initializes CEGUI and loads a simple layout. It then initialises instances of the SimpleWindow and the SimpleDialog classes. These contain the specific code to handle the behavior of the Simple Window and the Simple Dialog. In turn they rely on the behaviors define within the DialogSystem class to activate higher level features.
-The DialogSystem class implements the behavior of the 'Ok', 'Cancel', and 'Apply' buttons that we've become accustomed to in the world of Windows.  The DialogSystem::DialogSystemEvents enumaration defines the high level events supported by the DialogSystem class:
+The DialogSystem class implements the behavior of the 'Ok', 'Cancel', and 'Apply' buttons that we've become accustomed to in the world of Windows. The DialogSystem::DialogSystemEvents enumaration defines the high level events supported by the DialogSystem class:
    open: display the window and its data
    ok: save the data and close the window
@@ Line 18: / Line 18: @@
    doClose(): hide the window
-The SimpleWindow class will manage everything that has to do with the Simple Window.  The initWindow() function initialises the DialogSystem by specifying the handle of the window/dialog (the name specified within the layout file) and whether it should initially be visible or not.  Then it instructs the DialogSystem to handle four events as well as which action to initiate in response to these events:
+The SimpleWindow class will manage everything that has to do with the Simple Window. The initWindow() function initialises the DialogSystem by specifying the handle of the window/dialog (the name specified within the layout file) and whether it should initially be visible or not. Then it instructs the DialogSystem to handle four events as well as which action to initiate in response to these events:
 ) Pressing the "Toolbar_btnSimpleWindow" button opens the SimpleWindow.
 ) Pressing the "SimpleWindow_btnClose" button performs an 'Ok', saving the data and closing the window.
@@ Line 24: / Line 24: @@
 ) Pressing the 'escape' key closes the dialog without saving any modifications (cancel).
-The SimpleWindow class then overrides the doLoad() virtual function to place the contents of a variable (dataString) into its associated Editbox.  It also overrides the doSave() virtual function to place the contents of the Editbox back into the variable.
+The SimpleWindow class then overrides the doLoad() virtual function to place the contents of a variable (dataString) into its associated Editbox. It also overrides the doSave() virtual function to place the contents of the Editbox back into the variable.
-The SimpleDialog class replicates many of what the SimpleWindow performed.  The first difference is that it specifies the handle of a parent window.  This signals the DialogSystem class that when the Simple Dialog is opened it should disable its parent, making the Simple Dialog modal; inputs to the parent are blocked while this dialog is opened.
+The SimpleDialog class replicates many of what the SimpleWindow performed. The first difference is that it specifies the handle of a parent window. This signals the DialogSystem class that when the Simple Dialog is opened it should disable its parent, making the Simple Dialog modal; inputs to the parent are blocked while this dialog is opened.
-The second difference is the addition of an apply button.  This apply button requires that two events be specified.  The event of clicking on the apply button "SimpleDialog_btnApply" is bound to the high level event of DialogSystem::apply, which will call upon doSave() to move the widget data into the variables.  Text changes within the edit box "SimpleDialog_edtValue" are also bound to the high level event of DialogSystem::modified, which will enable the apply button whenever the contents of the edit box are modified.  If there were additional widgets within the window then their 'modified' events would also need to be specified.
+The second difference is the addition of an apply button. This apply button requires that two events be specified. The event of clicking on the apply button "SimpleDialog_btnApply" is bound to the high level event of DialogSystem::apply, which will call upon doSave() to move the widget data into the variables. Text changes within the edit box "SimpleDialog_edtValue" are also bound to the high level event of DialogSystem::modified, which will enable the apply button whenever the contents of the edit box are modified. If there were additional widgets within the window then their 'modified' events would also need to be specified.
-CEGUI has more widgets than an Editbox.  These can easily be incorporated within the logic presented here.
+CEGUI has more widgets than an Editbox. These can easily be incorporated within the logic presented here.
 Please post comments or questions on the message board thread for the [http://www.cegui.org.uk/phpBB2/viewtopic.php?p=7966#7966 Dialog System]

@@ Line 146: / Line 146: @@
 			SchemeManager::getSingleton().loadScheme("TaharezLook.scheme");
 			System::getSingleton().setDefaultMouseCursor("TaharezLook", "MouseArrow");
-			FontManager::getSingleton().createFont("Commonwealth-10.font");
+			if(!FontManager::getSingleton().isFontPresent("Commonwealth-10"))
 			// Set the GUI Sheet

@@ Line 144: / Line 144: @@
 			// Load the TaharezLook scheme and set up the default mouse cursor and font
-			SchemeManager::getSingleton().loadScheme("../datafiles/schemes/TaharezLookSkin.scheme");
+			SchemeManager::getSingleton().loadScheme("TaharezLookSkin.scheme");
 			System::getSingleton().setDefaultMouseCursor("TaharezLook", "MouseArrow");
-			FontManager::getSingleton().createFont("../datafiles/fonts/Commonwealth-10.font");
+			FontManager::getSingleton().createFont("Commonwealth-10.font");
 			// Set the GUI Sheet
@@ Line 153: / Line 153: @@
 			// Load a layout
-			Window* guiLayout = winMgr.loadWindowLayout("../datafiles/layouts/DialogSystem.layout");
+			Window* guiLayout = winMgr.loadWindowLayout("DialogSystem.layout");
 			sheet->addChildWindow(guiLayout);

← Older revision	Revision as of 15:39, 28 February 2011
(No difference)

@@ Line 140: / Line 140: @@
 		try
+		{
-			initDemo("../datafiles/layouts/DialogSystem.layout");
+			// Retrieve the window manager
 			// Initialise the Simple Window and the Simple Dialog
@@ Line 164: / Line 179: @@
 #endif // _DialogSystemDemo_h_
 </pre>
 ==== DialogSystem.h ====