WxSmith tutorial: Working with multiple resources - Revision history

Chatumao: /* Working with Multiple Windows */

2013-05-12T13:56:15Z

Working with Multiple Windows

← Older revision		Revision as of 13:56, 12 May 2013
Line 30:		Line 30:
	After clicking OK, you will be prompted for a list of build targets into which the new window will be added. Select both ''debug'' and ''release'', and we can continue.		After clicking OK, you will be prompted for a list of build targets into which the new window will be added. Select both ''debug'' and ''release'', and we can continue.

	A new dialog is automatically opened in the editor. In the top bar of the frame of the editor, note that there are two .wxs files available to the editor, Tutorial_4Frame.~~wks~~ and the newly created FirstDialog1.wxs. Both are completely blank. Into FirstDialog.wxs let's add some simple content so that it looks like this in the editor:		A new dialog is automatically opened in the editor. In the top bar of the frame of the editor, note that there are two .wxs files available to the editor, Tutorial_4Frame.wxs and the newly created FirstDialog1.wxs. Both are completely blank. Into FirstDialog.wxs let's add some simple content so that it looks like this in the editor:

	[[Image:wxs_tut04_002.png]]		[[Image:wxs_tut04_002.png]]

Bentcode: /* Working with Multiple Windows */

2012-04-07T21:17:29Z

Working with Multiple Windows

← Older revision		Revision as of 21:17, 7 April 2012
Line 34:		Line 34:
	[[Image:wxs_tut04_002.png]]		[[Image:wxs_tut04_002.png]]

	It is a good review exercise to figure out from this figure what has been done. It is very similar to what we did at the beginning of the previous tutorial. Before reading further, try your hand at making it. (To tell the truth, it doesn't matter much what you put in because all we are going to do with it is show it, But if you need a review, here is what I did: 1. Put a wxBoxSizer on the editor. 2. Put a wxPanel in the sizer (and remembered to turn on its ~~Enlarge~~ property). 3. Put on the panel a wxStaticBoxSizer, changed its orientation to Vertical, and set its label to “This is the first dialog.” 4. Into the StaticBoxSizer put first a wxTextCtrl and then a wxStaticText item.) At this point, the Show Preview button on the extreme right of the editor will show us what we have, while running the program will show nothing, because the application has no programming to show our dialog.		It is a good review exercise to figure out from this figure what has been done. It is very similar to what we did at the beginning of the previous tutorial. Before reading further, try your hand at making it. (To tell the truth, it doesn't matter much what you put in because all we are going to do with it is show it, But if you need a review, here is what I did: 1. Put a wxBoxSizer on the editor. 2. Put a wxPanel in the sizer (and remembered to turn on its Expand property). 3. Put on the panel a wxStaticBoxSizer, changed its orientation to Vertical, and set its label to “This is the first dialog.” 4. Into the StaticBoxSizer put first a wxTextCtrl and then a wxStaticText item.) At this point, the Show Preview button on the extreme right of the editor will show us what we have, while running the program will show nothing, because the application has no programming to show our dialog.

	Now let's go back to the wxSmith item on the Code::Blocks menu and add a wxFrame window (FirstFrame) and add some content into it:		Now let's go back to the wxSmith item on the Code::Blocks menu and add a wxFrame window (FirstFrame) and add some content into it:

Alpha at 21:38, 17 March 2012

2012-03-17T21:38:13Z

← Older revision		Revision as of 21:38, 17 March 2012
Line 166:		Line 166:
	----		----

	'''[[WxSmith tutorial: Building more complex window\|Previous]] \| [[WxSmith tutorials\|Index]] \| [[WxSmith tutorial: Using wxPanel resources\|Next]]'''		<center>'''[[WxSmith tutorial: Building more complex window\|Previous]] \| [[WxSmith tutorials\|Index]] \| [[WxSmith tutorial: Using wxPanel resources\|Next]]'''</center>

Alpha: Added navigation.

2012-03-17T20:41:55Z

Added navigation.

← Older revision		Revision as of 20:41, 17 March 2012
Line 1:		Line 1:
	[[Category:wxSmith Documentation]]		[[Category:wxSmith Documentation]]


	= Working with Multiple Windows =		= Working with Multiple Windows =

Line 65:		Line 63:

	<pre>		<pre>
	void Tutorial_4Frame::OnButton1Click(wxCommandEvent& event)		void Tutorial_4Frame::OnButton1Click(wxCommandEvent& event)
	{		{
	FirstDialog dialog(this);		FirstDialog dialog(this);
	dialog.ShowModal();		dialog.ShowModal();
	}		}
	</pre>		</pre>

Line 114:		Line 112:

	FirstDialog dialog(this);		FirstDialog dialog(this);

	We could do this only because the ShowModal method was blocking as long as the dialog was shown. Now with a wxFrame, which does not have the ShowModal possibility, we will have to create objects using the '''new''' operator of C++ because the objects must exist after leaving the handler function and also because windows not using modal mode will delete such objects automatically when the window is closed.		We could do this only because the ShowModal method was blocking as long as the dialog was shown. Now with a wxFrame, which does not have the ShowModal possibility, we will have to create objects using the '''new''' operator of C++ because the objects must exist after leaving the handler function and also because windows not using modal mode will delete such objects automatically when the window is closed.

Line 144:		Line 142:

	<pre>		<pre>
	void Tutorial_4Frame::OnButton2Click(wxCommandEvent& event)		void Tutorial_4Frame::OnButton2Click(wxCommandEvent& event)
	{		{
	FirstDialog* dlg = new FirstDialog(this);		FirstDialog* dlg = new FirstDialog(this);
	dlg->Show();		dlg->Show();
	}		}
	</pre>		</pre>

Line 154:		Line 152:

	<pre>		<pre>
	void Tutorial_4Frame::OnButton3Click(wxCommandEvent& event)		void Tutorial_4Frame::OnButton3Click(wxCommandEvent& event)
	{		{
	FirstFrame* frm = new FirstFrame(this);		FirstFrame* frm = new FirstFrame(this);
	frm->Show();		frm->Show();
	}		}
	</pre>		</pre>

Line 165:		Line 163:

	This is the end of this tutorial. I hope that you learned some new and useful things. We have covered the use of two of the four things you can add to your project by using the wxSmith item on the Code::Blocks main menu. In the next tutorial, I'll show how to use another of the four, namely the wxPanel.		This is the end of this tutorial. I hope that you learned some new and useful things. We have covered the use of two of the four things you can add to your project by using the wxSmith item on the Code::Blocks main menu. In the next tutorial, I'll show how to use another of the four, namely the wxPanel.

			----

			'''[[WxSmith tutorial: Building more complex window\|Previous]] \| [[WxSmith tutorials\|Index]] \| [[WxSmith tutorial: Using wxPanel resources\|Next]]'''

Grouch at 17:35, 8 March 2012

2012-03-08T17:35:43Z

Show changes

Greenbreen: Minor edits for clarity

2010-11-28T18:53:57Z

Minor edits for clarity

← Older revision		Revision as of 18:53, 28 November 2010
Line 103:		Line 103:
	= Using modeless dialog and frame windows =		= Using modeless dialog and frame windows =

	Another way to show ~~windows~~ is as a modeless window. In such cases the new window does not block other windows in the application and two (or more) windows can cooperate in one application.		Another way to show a window is as a modeless window. In such cases the new window does not block other windows in the application and two (or more) windows can cooperate in one application.

	Before we add new code into our application there's one more thing you should know. Each window may exist only as long as its object (the instance of the resource's c++ class). So we cannot use the same approach as in the case of a modal dialog. In modal mode an object was created as a local variable of the event handler. We could do this only because the ShowModal method was blocking as long as the dialog was shown.		Before we add new code into our application there's one more thing you should know. Each window may exist only as long as its object (the instance of the resource's c++ class). So we cannot use the same approach as in the case of a modal dialog. In modal mode an object was created as a local variable of the event handler. We could do this only because the ShowModal method was blocking as long as the dialog was shown.
Line 109:		Line 109:


	To allow creating the FirstFrame class we should add '''#include "FirstFrame.h"''' into list of includes just like in the case of FirstDialog:		To allow creating the FirstFrame class we should add '''#include "FirstFrame.h"''' into the list of includes just like in the case of FirstDialog:

	#include "wx_pch.h"		#include "wx_pch.h"

Greenbreen: Minor edits for clarity

2010-11-28T18:51:15Z

Minor edits for clarity

← Older revision		Revision as of 18:51, 28 November 2010
Line 101:		Line 101:
	[[Image:wxs_tut04_005.png]]		[[Image:wxs_tut04_005.png]]

	= Using dialog and frame ~~window in non-modal mode~~ =		= Using modeless dialog and frame windows =

	Another ~~mode used~~ to show windows is ~~modal-less mode~~. In such ~~case~~ new window does not block other windows in application and two (or more) windows can cooperate in one application.		Another way to show windows is as a modeless window. In such cases the new window does not block other windows in the application and two (or more) windows can cooperate in one application.

	Before we add new code into our application there's one more thing you should know. Each window may exist only as long as ~~it's~~ object (instance of resource's c++ class). So we ~~can not~~ use same approach as in case of modal dialog. In modal mode object was created as local variable of event handler. We could do this only because ShowModal method was ~~blocked~~ as long as ~~diaog~~ was shown.		Before we add new code into our application there's one more thing you should know. Each window may exist only as long as its object (the instance of the resource's c++ class). So we cannot use the same approach as in the case of a modal dialog. In modal mode an object was created as a local variable of the event handler. We could do this only because the ShowModal method was blocking as long as the dialog was shown.
	Now we will have to create ~~objets~~ using new ~~opertor~~ because objects must exist after leaving handler ~~functin~~ and also because windows not using modal mode will delete such objects automatically when window is closed.		Now we will have to create objects using the new operator because the objects must exist after leaving the handler function and also because windows not using modal mode will delete such objects automatically when the window is closed.


	To allow creating FirstFrame class we should add '''#include "FirstFrame.h"''' into list of includes just like in case of FirstDialog:		To allow creating the FirstFrame class we should add '''#include "FirstFrame.h"''' into list of includes just like in the case of FirstDialog:

	#include "wx_pch.h"		#include "wx_pch.h"
Line 123:		Line 123:


	Now let's add two more buttons to main frame:		Now let's add two more buttons to the main frame:
	* Add new dialog		* Add new dialog
	* Add new frame		* Add new frame
Line 131:		Line 131:
	[[Image:wxs_tut04_006.png]]		[[Image:wxs_tut04_006.png]]

	Now let's add handler to ''Add new dialog'' button:		Now let's add a handler to the ''Add new dialog'' button:

	void Tutorial_4Frame::OnButton2Click(wxCommandEvent& event)		void Tutorial_4Frame::OnButton2Click(wxCommandEvent& event)
Line 147:		Line 147:
	}		}

	Now each time we click ''Add new dialog'' or ''Add new frame'' ~~buton~~, new window shows up.		Now each time we click the ''Add new dialog'' or ''Add new frame'' button, a new window shows up.

Greenbreen: Minor edits for clarity

2010-11-27T20:00:58Z

Minor edits for clarity

← Older revision		Revision as of 20:00, 27 November 2010
Line 44:		Line 44:
	[[Image:wxs_tut04_003.png]]		[[Image:wxs_tut04_003.png]]

	= Using dialog window in modal mode =		= Using a dialog window in modal mode =

	Dialogs can be shown in so-called modal mode. This means that when such dialog is shown, all other windows in the application are frozen ~~as long as~~ the dialog finishes ~~it's~~ job. Such dialogs are ~~usefull~~ when user should quickly provide some ~~informations~~ - for example the window used to configure new resource was modal.		Dialogs can be shown in so-called modal mode. This means that when such a dialog is shown, all other windows in the application are frozen until the dialog finishes its job. Such dialogs are useful when the user should quickly provide some information - for example the window used to configure a new resource was modal.

	Now let's try to invoke our dialog. Generally such ~~dialog~~ will pop-up as reaction ~~for~~ user action like choosing menu option or clicking on button. We will use he button since this approach is really easy.		Now let's try to invoke our dialog. Generally such dialogs will pop-up in reaction to user action like choosing a menu option or clicking on a button. We will use the button since this approach is really easy.

	Ok, let's switch into main frame - the one that was opened right after creating new project, and add sizer and button:		Ok, let's switch into the main frame - the one that was opened right after creating the new project, and add a sizer and button:

	[[Image:wxs_tut04_004.png]]		[[Image:wxs_tut04_004.png]]

	Now we have to create action for button-click event. The easiest way is to double-click the button in editor. wxSmith will automatically add new event handler function:		Now we have to create an action for the button-click event. The easiest way is to double-click the button in the editor. wxSmith will automatically add a new event handler function:

	void Tutorial_4Frame::OnButton1Click(wxCommandEvent& event)		void Tutorial_4Frame::OnButton1Click(wxCommandEvent& event)
Line 60:		Line 60:
	}		}

	If you can't find this code, scroll down to the end of cpp file.		If you can't find this code, scroll down to the end of the cpp file.

	Now let's Invoke our dialog:		Now let's Invoke our dialog:
Line 70:		Line 70:
	}		}

	In the first added line we created dialog's object notifying that ''this'' window (main frame) is parent of dialog. In the second line we show the dialog. Note that call to ShowModal() blocks ~~untill~~ dialog is closed.		In the first added line we created the dialog's object notifying that ''this'' window (main frame) is the parent of dialog. In the second line we show the dialog. Note that the call to ShowModal() blocks until the dialog is closed.

	There's one more thing we need to add before our application compiles. Jump to the beginning of the file and add following code next to other includes:		There's one more thing we need to add before our application compiles. Jump to the beginning of the file and add the following code next to the other includes:

	#include "FirstDialog.h"		#include "FirstDialog.h"
Line 83:		Line 83:
	//*)		//*)

	This is block of code that is automatically generated by wxSmith. Every block starts with ''//(BlockName'' comment and ends with ''//)''. You may find other blocks in both header and source files. If you change their content, all changes will be lost ~~net~~ time you change something in editor.		This is a block of code that is automatically generated by wxSmith. Every block starts with a ''//(BlockName'' comment and ends with a ''//)''. You may find other blocks in both header and source files. If you change their content, all changes will be lost next time you change something in the editor.

	To sum things up, headers section should look like this:		To sum things up, headers section should look like this:
Line 97:		Line 97:
	//*)		//*)

	Now we can compile and run our application- if you click button on main window, dialog will pop-up:		Now we can compile and run our application- if you click the button on the main window, the dialog will pop-up:

	[[Image:wxs_tut04_005.png]]		[[Image:wxs_tut04_005.png]]

Greenbreen: Minor edits for clarity

2010-11-27T19:51:43Z

Minor edits for clarity

← Older revision		Revision as of 19:51, 27 November 2010
Line 26:		Line 26:
	[[Image:wxs_tut04_001.png]]		[[Image:wxs_tut04_001.png]]

	Here we can configure following parameters:		Here we can configure the following parameters:

	* Class name - it's name of class which will be generated for the resource. It will also be a name of resource		* Class name - it's the name of the class which will be generated for the resource. It will also be the name of a resource
	* Header file - name of header file with class declaration		* Header file - name of the header file with the class declaration
	* Source file - name of source file with class definition		* Source file - name of the source file with the class definition
	* Xrc file - if you check this option you can enter name of XRC file which will contain XRC's structure (XRC files will be covered in ~~other~~ tutorial)		* Xrc file - if you check this option you can enter the name of an XRC file which will contain the XRC's structure (XRC files will be covered in another tutorial)
	* Add XRC file to autoload list - this option is ~~aailable~~ only with XRC ~~file~~ and notifies wxSmith that it should automatically load XRC file when the application starts.		* Add XRC file to autoload list - this option is available only with XRC files and notifies wxSmith that it should automatically load the XRC file when the application starts.

	Now let's change name of resource to something better like "FirstDialog". Note that if you change class name, names of files are also updated (they are updated as long as you don't change them manually). After clicking OK you will be prompted for list of build target into which new resource will be added. Select both debug and release and we can continue.		Now let's change the name of the resource to something better like "FirstDialog". Note that if you change the class name, the names of the files are also updated (they are updated as long as you don't change them manually). After clicking OK you will be prompted for a list of build target into which the new resource will be added. Select both debug and release and we can continue.

	~~New~~ dialog is automatically opened in editor. Let's add some simple content:		A new dialog is automatically opened in the editor. Let's add some simple content:

	[[Image:wxs_tut04_002.png]]		[[Image:wxs_tut04_002.png]]

	Now let's add ~~some~~ wxFrame resource (FirstFrame) and add some content into it:		Now let's add a wxFrame resource (FirstFrame) and add some content into it:

	[[Image:wxs_tut04_003.png]]		[[Image:wxs_tut04_003.png]]

Greenbreen: Changed image to imputed intended image

2010-11-26T15:55:25Z

Changed image to imputed intended image

← Older revision		Revision as of 15:55, 26 November 2010
Line 24:		Line 24:
	Ok, let's add a new wxDialog. If you choose this option it will show the following window:		Ok, let's add a new wxDialog. If you choose this option it will show the following window:

	[[Image:~~wxs_tut04_005~~.png]]		[[Image:wxs_tut04_001.png]]

	Here we can configure following parameters:		Here we can configure following parameters: