WxSmith tutorial: Using wxPanel resources - Revision history

Bentcode: /* Adding the wxPanel using a "Custom" item */

2012-04-07T22:33:45Z

Adding the wxPanel using a "Custom" item

← Older revision		Revision as of 22:33, 7 April 2012
Line 58:		Line 58:
	Now we have to give the name of the header file with our external resource in the "Include file" property. I've created the wxPanel with the name "InternalPanel" so the header will be "InternalPanel.h". Also let's check the "Use "" for include..." since we're including a local file.		Now we have to give the name of the header file with our external resource in the "Include file" property. I've created the wxPanel with the name "InternalPanel" so the header will be "InternalPanel.h". Also let's check the "Use "" for include..." since we're including a local file.

	The last property to adjust is the "Class name" - we need to put the name of our panel here; in my case it's "InternalPanel". When we do this, our embedded resource is ready. While the resource view and the show preview continue to show the black square with three question marks, if you rebuild/run the project you will see;		The last property to adjust is the "Class name" - we need to put the name of our panel here; in my case it's "InternalPanel". When we do this, our embedded resource is ready. While the resource view and the show preview continue to show the black square with three question marks, if you rebuild/run the project you will see the embedded resource;

	[[Image:wxs_tut05_006.png]]		[[Image:wxs_tut05_006.png]]

Bentcode: /* Adding the wxPanel using a "Custom" item */

2012-04-07T22:32:41Z

Adding the wxPanel using a "Custom" item

← Older revision		Revision as of 22:32, 7 April 2012
Line 58:		Line 58:
	Now we have to give the name of the header file with our external resource in the "Include file" property. I've created the wxPanel with the name "InternalPanel" so the header will be "InternalPanel.h". Also let's check the "Use "" for include..." since we're including a local file.		Now we have to give the name of the header file with our external resource in the "Include file" property. I've created the wxPanel with the name "InternalPanel" so the header will be "InternalPanel.h". Also let's check the "Use "" for include..." since we're including a local file.

	The last property to adjust is the "Class name" - we need to put the name of our panel here; in my case it's "InternalPanel". When we do this, our embedded resource is ready:		The last property to adjust is the "Class name" - we need to put the name of our panel here; in my case it's "InternalPanel". When we do this, our embedded resource is ready. While the resource view and the show preview continue to show the black square with three question marks, if you rebuild/run the project you will see;

	[[Image:wxs_tut05_006.png]]		[[Image:wxs_tut05_006.png]]

Bentcode: /* Adding the wxPanel using a "Custom" item */

2012-04-07T21:58:10Z

Adding the wxPanel using a "Custom" item

← Older revision		Revision as of 21:58, 7 April 2012
Line 19:		Line 19:
	The first one uses a "Custom" item which can be used to add any kind of resource not known to wxSmith.		The first one uses a "Custom" item which can be used to add any kind of resource not known to wxSmith.

	So let's create the wxPanel resource. Note that using this embedding method will affect the initial configuration of the resource.		So let's create the wxPanel resource by using the wxSmith item on the Code::Blocks main menu. Note that using this embedding method will affect the initial configuration of the resource.
	We want the id, size and position of our panel to be controlled by the parent resource so make sure that we add them into the panel's constructor:		We want the id, size and position of our panel to be controlled by the parent resource so make sure that we add them into the panel's constructor:

Alpha at 21:38, 17 March 2012

2012-03-17T21:38:53Z

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

	'''[[WxSmith tutorial: Working with multiple resources\|Previous]] \| [[WxSmith tutorials\|Index]] \| [[WxSmith tutorial: Accessing items in resource\|Next]]'''		<center>'''[[WxSmith tutorial: Working with multiple resources\|Previous]] \| [[WxSmith tutorials\|Index]] \| [[WxSmith tutorial: Accessing items in resource\|Next]]'''</center>

Alpha: Added navigation.

2012-03-17T20:45:25Z

Added navigation.

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

	= Using wxPanel resources =		= Using wxPanel resources =

Line 107:		Line 106:

	I've presented two easy methods of creating complex windows from smaller resources. Perhaps you could find other ways to do it (if you do so, you can extend this tutorial :) ). On wxSmith's wishlist there's also a nice feature request to allow adding external panels in a more natural way (just by a few clicks) which will probably make other methods obsolete. But I hope that I gave you enough information to build nice compound resources so far :)		I've presented two easy methods of creating complex windows from smaller resources. Perhaps you could find other ways to do it (if you do so, you can extend this tutorial :) ). On wxSmith's wishlist there's also a nice feature request to allow adding external panels in a more natural way (just by a few clicks) which will probably make other methods obsolete. But I hope that I gave you enough information to build nice compound resources so far :)

			----

			'''[[WxSmith tutorial: Working with multiple resources\|Previous]] \| [[WxSmith tutorials\|Index]] \| [[WxSmith tutorial: Accessing items in resource\|Next]]'''

Grouch at 18:33, 6 March 2012

2012-03-06T18:33:02Z

← Older revision		Revision as of 18:33, 6 March 2012
Line 2:		Line 2:

	= Using wxPanel resources =		= Using wxPanel resources =

			[Subsequent tutorials do not depend upon this one. If you find it confusing or not relevant to your needs, you can skip to the next without loss of continuity.]

	In some cases, one resource must be split into a few smaller parts. Such a split gives a few advantages: it helps with multiple people working on the same project, it may give you a cleaner view over really complex resources and it may help to divide source code for logical parts in case of several functionalities in one window. In this tutorial I'll show you how to create such resources.		In some cases, one resource must be split into a few smaller parts. Such a split gives a few advantages: it helps with multiple people working on the same project, it may give you a cleaner view over really complex resources and it may help to divide source code for logical parts in case of several functionalities in one window. In this tutorial I'll show you how to create such resources.

Greenbreen: Minor edits for clarity

2010-12-02T16:50:40Z

Minor edits for clarity

← Older revision		Revision as of 16:50, 2 December 2010
Line 86:		Line 86:
	and change "Class name" property to the name of our resource (in my case it's InternalResource2).		and change "Class name" property to the name of our resource (in my case it's InternalResource2).

	We still need to add #include "InternalResource2.h" into sources to make our project compile. In previous solution it was done ~~automaticaly~~ through properties. Now we don't have such system so let's add it manually (remember to put our include outside wxSmith's code section, otherwise any change in resource will remove our change). Note that we need to add it to header file of main resource:		We still need to add #include "InternalResource2.h" into the sources to make our project compile. In the previous solution it was done automatically through properties. Now we don't have such a system so let's add it manually (remember to put our include outside wxSmith's code section, otherwise any change in the resource will remove our change). Note that we need to add it to the header file of the main resource:

	//(*Headers(Tutorial5Dialog)		//(*Headers(Tutorial5Dialog)
Line 104:		Line 104:


	I've presented two ~~easiest~~ methods of creating complex ~~window~~ from smaller resources. Perhaps you could find other ways to do it (if you do so, you can extend this tutorial :) ). On wxSmith's wishlist there's also nice feature request to allow adding external panels ~~int~~ more natural way (just by few clicks) which will probably make other methods obsolete. But I hope that I gave you enough ~~informations~~ to build nice compound resources so far :)		I've presented two easy methods of creating complex windows from smaller resources. Perhaps you could find other ways to do it (if you do so, you can extend this tutorial :) ). On wxSmith's wishlist there's also a nice feature request to allow adding external panels in a more natural way (just by a few clicks) which will probably make other methods obsolete. But I hope that I gave you enough information to build nice compound resources so far :)

Greenbreen: Minor edits for clarity

2010-12-01T17:04:08Z

Minor edits for clarity

Greenbreen: Minor edits for clarity

2010-11-30T16:05:51Z

Minor edits for clarity

← Older revision		Revision as of 16:05, 30 November 2010
Line 41:		Line 41:
	$(THIS) = new $(CLASS)($(PARENT),$(ID),$(POS),$(SIZE),$(STYLE),wxDefaultValidator,$(NAME));		$(THIS) = new $(CLASS)($(PARENT),$(ID),$(POS),$(SIZE),$(STYLE),wxDefaultValidator,$(NAME));

	You may find that there are some macros used. They are here to help you map other properties of this item into ~~ceating~~ code:		You may find that there are some macros used. They are here to help you map other properties of this item into the creating code:
	* $(THIS) is replaced by name of variable for this item		* $(THIS) is replaced by the name of the variable for this item
	* $(CLASS) is replaced by name of item's class		* $(CLASS) is replaced by the name of the item's class
	* $(PARENT) is replaced by name of parent item (it's granted that it will be a pointer to class derived from wxWindow)		* $(PARENT) is replaced by the name of the parent item (it's granted that it will be a pointer to a class derived from wxWindow)
	* $(ID) is replaced by value of Id property		* $(ID) is replaced by the value of the ID property
	* $(POS) is replaced by value of position property (it may be adjusted by using drag boxes)		* $(POS) is replaced by the value of the position property (it may be adjusted by using drag boxes)
	* $(SIZE) is replaced by value of size property (it may be adjusted by using drag boxes)		* $(SIZE) is replaced by the value of the size property (it may be adjusted by using drag boxes)
	* $(STYLE) is replaced by style property - since custom ~~item~~ doesn't have predefined set of styles, it's ~~threated~~ as normal string		* $(STYLE) is replaced by the style property - since custom items doesn't have a predefined set of styles, it's treated as a normal string
	* $(NAME) is replaced by generated name (which is equivalent to string representation of item's identifier)		* $(NAME) is replaced by the generated name (which is equivalent to the string representation of the item's identifier)

	The default code template creates standard item which uses default set of properties. Let's replace it by value corresponding to our panel's constructor:		The default code template creates a standard item which uses the default set of properties. Let's replace it by a value corresponding to our panel's constructor:

	$(THIS) = new $(CLASS)($(PARENT),$(ID),$(POS),$(SIZE));		$(THIS) = new $(CLASS)($(PARENT),$(ID),$(POS),$(SIZE));

	Now we have to give name of header file with our external resource in the "Include file" property. I've created wxPanel with name "~~InterlanPanel~~" so header will be "InternalPanel.h". Also let's check the "Use "" for include..." since we're including local file.		Now we have to give the name of the header file with our external resource in the "Include file" property. I've created the wxPanel with the name "InternalPanel" so the header will be "InternalPanel.h". Also let's check the "Use "" for include..." since we're including a local file.

	The last property to adjust is the "Class name" - we need to put name of our panel here, in my case it's "InternalPanel". When we do this, our embedded resource is ready:		The last property to adjust is the "Class name" - we need to put the name of our panel here; in my case it's "InternalPanel". When we do this, our embedded resource is ready:

	[[Image:wxs_tut05_006.png]]		[[Image:wxs_tut05_006.png]]

Greenbreen: Minor edits for clarity

2010-11-29T19:11:57Z

Minor edits for clarity

← Older revision		Revision as of 19:11, 29 November 2010
Line 13:		Line 13:
	[[Image:wxs_tut05_001.png]]		[[Image:wxs_tut05_001.png]]

	== Adding wxPanel using "Custom" item ==		== Adding the wxPanel using a "Custom" item ==

	In this tutorial I'll show you two ~~methds~~ of embedding external wxPanel inside another resource.		In this tutorial I'll show you two methods of embedding an external wxPanel inside another resource.
	~~First~~ one ~~use~~ "Custom" item which can be used to any kind of resource not ~~know~~ to wxSmith.		The first one uses a "Custom" item which can be used to add any kind of resource not known to wxSmith.

	So let's create wxPanel resource. Note that ~~used~~ embedding method will affect initial configuration of resource.		So let's create the wxPanel resource. Note that using this embedding method will affect the initial configuration of the resource.
	We want id, size and position of our panel to be controlled by parent resource so make sure that we add them into panel's constructor:		We want the id, size and position of our panel to be controlled by the parent resource so make sure that we add them into the panel's constructor:

	[[Image:wxs_tut05_002.png]]		[[Image:wxs_tut05_002.png]]

	Now let's add some content into panel:		Now let's add some content into the panel:

	[[Image:wxs_tut05_003.png]]		[[Image:wxs_tut05_003.png]]

	~~Final~~ step is to add "Custom" item into main window and configure it properly. ~~Custom~~ icon is the last one in the "Standard ~~palete~~" identified by this icon:		The final step is to add a "Custom" item into the main window and configure it properly. The custom icon is the last one in the "Standard palette" identified by this icon:

	[[Image:wxs_tut05_004.png]]		[[Image:wxs_tut05_004.png]]

	~~New~~ item will be shown as black square with three question marks on the top. Let's resize it a little bit:		A new item will be shown as a black square with three question marks on the top. Let's resize it a little bit:

	[[Image:wxs_tut05_005.png]]		[[Image:wxs_tut05_005.png]]

	Now we need to adjust custom item's properties.		Now we need to adjust the custom item's properties.

	~~First~~ thing we will adjust is "Creating code" property. As the name says, here we will be able to adjust the way wxSmith adds code responsible for creating this item. The default value is:		The first thing we will adjust is the "Creating code" property. As the name says, here we will be able to adjust the way wxSmith adds the code responsible for creating this item. The default value is:

	$(THIS) = new $(CLASS)($(PARENT),$(ID),$(POS),$(SIZE),$(STYLE),wxDefaultValidator,$(NAME));		$(THIS) = new $(CLASS)($(PARENT),$(ID),$(POS),$(SIZE),$(STYLE),wxDefaultValidator,$(NAME));

← Older revision		Revision as of 17:04, 1 December 2010
Line 63:		Line 63:
	== Adding custom panel through standard wxPanel ==		== Adding custom panel through standard wxPanel ==

	~~Secend~~ way in which external resource may be used is through normal wxPanel.		The second way in which an external resource may be used is through a normal wxPanel.
	If you look closer, you'll find that most of items have property called "Class name" - this is the name of class which will be used as item's type. Bu default it contains name of original class in wxWidgets. Changing it will notify that different class will be used instead.		If you look closer, you'll find that most of the items have a property called "Class name" - this is the name of the class which will be used as the item's type. By default it contains the name of the original class in wxWidgets. Changing it will notify wxSmith that a different class will be used instead.

	So to put our own panel here we can add "normal" panel into main resource and change class name to name of our internal resource. So far it's easy but there's one requirement to this technique - our internal resource must have exactly the same constructor arguments as in case of "original" class.		So to put our own panel here we can add a "normal" panel into the main resource and change the class name to the name of our internal resource. So far it's easy but there's one requirement to this technique - our internal resource must have exactly the same constructor arguments as in the case of the "original" class.

	So let's take a look at the wxWidgets documentation ~~and here~~'s declaration of wxPanel's constructor:		So let's take a look at the wxWidgets documentation. Here's the declaration of wxPanel's constructor:

	wxPanel( wxWindow* parent, wxWindowID id = wxID_ANY,		wxPanel( wxWindow* parent, wxWindowID id = wxID_ANY,
Line 74:		Line 74:
	long style = wxTAB_TRAVERSAL, const wxString& name = "panel")		long style = wxTAB_TRAVERSAL, const wxString& name = "panel")

	Now let's create our own internal resource. We will have to adjust constructor arguments as in case of previous method:		Now let's create our own internal resource. We will have to adjust constructor arguments as in the case of the previous method:

	[[Image:wxs_tut05_007.png]]		[[Image:wxs_tut05_007.png]]

	Note that I've added custom arguments and turned off all default values (it's required since we ~~can not~~ easily add default values of our custom args).		Note that I've added custom arguments and turned off all default values (it's required since we cannot easily add default values of our custom args).

	Now that our panel is ready we can add it to main resource - let's add "normal" panel first:		Now that our panel is ready we can add it to the main resource - let's add a "normal" panel first:

	[[Image:wxs_tut05_008.png]]		[[Image:wxs_tut05_008.png]]

	and change "Class name" property to name of our resource (in my case it's InternalResource2).		and change "Class name" property to the name of our resource (in my case it's InternalResource2).

	We still need to add #include "InternalResource2.h" into sources to make our project compile. In previous solution it was done automaticaly through properties. Now we don't have such system so let's add it manually (remember to put our include outside wxSmith's code section, otherwise any change in resource will remove our change). Note that we need to add it to header file of main resource:		We still need to add #include "InternalResource2.h" into sources to make our project compile. In previous solution it was done automaticaly through properties. Now we don't have such system so let's add it manually (remember to put our include outside wxSmith's code section, otherwise any change in resource will remove our change). Note that we need to add it to header file of main resource: