WxSmith tutorial: Hello world - Revision history

Alpha: Stop entire page from being in italics

2017-01-09T00:17:20Z

Stop entire page from being in italics

Ensnarer at 12:05, 3 August 2015

2015-08-03T12:05:56Z

WardXmodem: Talk of close() is obsolete; left in but separated; new method (automatic) shown

2015-05-20T20:43:19Z

Talk of close() is obsolete; left in but separated; new method (automatic) shown

WardXmodem: /* Overview of the Interactive Development Environment (IDE) */

2015-05-20T20:02:54Z

Overview of the Interactive Development Environment (IDE)

WardXmodem: Correct location of icon image

2015-05-20T20:00:46Z

Correct location of icon image

WardXmodem: Add tiny icon image as the location doesn't agree with the text

2015-05-20T19:58:47Z

Add tiny icon image as the location doesn't agree with the text

WardXmodem: Add image of updated 3.0.2 view corresponding to image 1g

2015-05-20T19:38:15Z

Add image of updated 3.0.2 view corresponding to image 1g

Alpha: Add link to Ubuntu bug 662077 page

2014-03-13T19:18:32Z

Add link to Ubuntu bug 662077 page

WardXmodem: Following tutorial and correcting; e.g. you must {added DOUBLE-}click wxwidgets project

2013-12-14T01:32:03Z

Following tutorial and correcting; e.g. you must {added DOUBLE-}click wxwidgets project

WardXmodem: Corrected use of Close() to (at least it works for me) Destory()

2013-09-24T02:43:40Z

Corrected use of Close() to (at least it works for me) Destory()

← Older revision		Revision as of 00:17, 9 January 2017
Line 123:		Line 123:
	Remember to make this change immediately whenever you start a new project.		Remember to make this change immediately whenever you start a new project.

−	==== ''End of old "have to add close()" section. With newer releases the following is done for you: ====	+	==== ''End of old "have to add close()" section. With newer releases the following is done for you:'' ====

@@ Line 118: / Line 118: @@
 </pre>
 (''I found it had to be Destroy() not Close()   [[User:WardXmodem|WardXmodem]] 04:43, 24 September 2013 (CEST)'')
 Remember to make this change immediately whenever you start a new project.
 ==== ''End of old "have to add close()" section.  With newer releases the following is done for you: ====
 <pre>

@@ Line 97: / Line 97: @@
 As an experienced programmer, you know there has got to be some code somewhere but you don't see it.  To reveal it, double left click in the field of dots.  Presto, there is the C++ code, and the *PlainMain.cpp tab has appeared above it.  Clicking back on the Plainframe.wxs should return you to the view of the form, still the field of dots. (Again, it is important to have CB 10.04 or later.)  In fact, we still have not seen all of the code.  In particular, you will search in vain for the all-important OnInit() routine that starts the program.  You can find it, however, by clicking Search | Find in Files  and searching for OnInit with the scope of the search set to be “Project files”.  The search finds it, sure enough, in PlainApp.cpp and opens this module in the Editor window.
 We don't need OnInit right now, but we do need to make a change in PlainMain.cpp. Click on it in the bar above the editor, and its code appears in the editor.
@@ Line 118: / Line 120: @@
 Remember to make this change immediately whenever you start a new project.
 You can now build and run this super-simple program. To do so, you can do any one of three equivalent things:<br />

@@ Line 84: / Line 84: @@
 with two square icons on the left; the one on the left brings up the menu bar editor while the one on the right brings up the status bar editor. We will return to the menu bar editor in the next tutorial. Below this panel and looking like a field of dots is the Editor window, where we will see both the GUI forms which we build and the C++ code we write.  In the lower left corner of the whole window is the Properties/Events window, which will allow us to set properties of the component we are working on or to pick events, such as “OnClick” , to which we need to respond. To show properties, click on the left icon; to show events, click on the right icon marked {} to suggest C++ code.
-Above the Properties/Events window is the Management window with three tabs, Projects, Symbols, and Resources. If all three tabs are not visible, drag the right border of the window to the right to reveal all three. (A “resource” in wxSmith parlance usually means a “form” or "window".) Above the Management window  is a panel with several small but useful icons ( [Image:build-etc-icons.png]] )to
+Above the Properties/Events window is the Management window with three tabs, Projects, Symbols, and Resources. If all three tabs are not visible, drag the right border of the window to the right to reveal all three. (A “resource” in wxSmith parlance usually means a “form” or "window".) Above the Management window  is a panel with several small but useful icons ([[Image:build-etc-icons.png]]) to
 *Build the program, or
 *Run it, or

@@ Line 82: / Line 82: @@
 In the middle of the right side of the window, under the word “Plainframe.wxs”,  is a panel
-([Image:build-etc-icons.png]]) with two square icons on the left; the one on the left brings up the menu bar editor while the one on the right brings up the status bar editor. We will return to the menu bar editor in the next tutorial. Below this panel and looking like a field of dots is the Editor window, where we will see both the GUI forms which we build and the C++ code we write.  In the lower left corner of the whole window is the Properties/Events window, which will allow us to set properties of the component we are working on or to pick events, such as “OnClick” , to which we need to respond. To show properties, click on the left icon; to show events, click on the right icon marked {} to suggest C++ code.
+with two square icons on the left; the one on the left brings up the menu bar editor while the one on the right brings up the status bar editor. We will return to the menu bar editor in the next tutorial. Below this panel and looking like a field of dots is the Editor window, where we will see both the GUI forms which we build and the C++ code we write.  In the lower left corner of the whole window is the Properties/Events window, which will allow us to set properties of the component we are working on or to pick events, such as “OnClick” , to which we need to respond. To show properties, click on the left icon; to show events, click on the right icon marked {} to suggest C++ code.
-Above the Properties/Events window is the Management window with three tabs, Projects, Symbols, and Resources. If all three tabs are not visible, drag the right border of the window to the right to reveal all three. (A “resource” in wxSmith parlance usually means a “form” or "window".) Above the Management window  is a panel with several small but useful icons to
+Above the Properties/Events window is the Management window with three tabs, Projects, Symbols, and Resources. If all three tabs are not visible, drag the right border of the window to the right to reveal all three. (A “resource” in wxSmith parlance usually means a “form” or "window".) Above the Management window  is a panel with several small but useful icons ( [Image:build-etc-icons.png]] )to
 *Build the program, or
 *Run it, or

@@ Line 81: / Line 81: @@
 [[Image:1h.png]]
-In the middle of the right side of the window, under the word “Plainframe.wxs”,  is a panel with two square icons on the left; the one on the left brings up the menu bar editor while the one on the right brings up the status bar editor. We will return to the menu bar editor in the next tutorial. Below this panel and looking like a field of dots is the Editor window, where we will see both the GUI forms which we build and the C++ code we write.  In the lower left corner of the whole window is the Properties/Events window, which will allow us to set properties of the component we are working on or to pick events, such as “OnClick” , to which we need to respond. To show properties, click on the left icon; to show events, click on the right icon marked {} to suggest C++ code.
+In the middle of the right side of the window, under the word “Plainframe.wxs”,  is a panel
 Above the Properties/Events window is the Management window with three tabs, Projects, Symbols, and Resources. If all three tabs are not visible, drag the right border of the window to the right to reveal all three. (A “resource” in wxSmith parlance usually means a “form” or "window".) Above the Management window  is a panel with several small but useful icons to

← Older revision		Revision as of 19:38, 20 May 2015
Line 65:		Line 65:
	[[Image:1g.png]]		[[Image:1g.png]]

		+	In wxWidgets 3.0.2 the screen looks like this. [[User:WardXmodem\|WardXmodem]] 21:38, 20 May 2015 (CEST)
		+
		+	[[Image:1g_3.0.2.png]]

	On the form where we chose the directory for saving the project, we chose a real directory, but that choice may lead to problems when you want to compile your project on other computers. Another choice is to use the '''Global Variable system'''. To open the dialog below or modify or change this global variable, you should click on the Code::Blocks main menu item '''Settings \| Global variables'''. That brings up the Global Variables Editor.		On the form where we chose the directory for saving the project, we chose a real directory, but that choice may lead to problems when you want to compile your project on other computers. Another choice is to use the '''Global Variable system'''. To open the dialog below or modify or change this global variable, you should click on the Code::Blocks main menu item '''Settings \| Global variables'''. That brings up the Global Variables Editor.

@@ Line 122: / Line 122: @@
 If all goes well, you will see a window come up with a menu of two items: “File” and “Help”.  Try the “Help” menu item first.  Then you can use  “File | Quit” or the exit icon on the title bar to exit the program.
-''If you are using Ubuntu and get no main menu bar when you run this program, you have fallen victim to Ubuntu bug 662077. Beginning with release 10.10, Ubuntu releases have had a bug causing programs built with wxSmith to fail to show their main menu bar. If this bug affects you, you may want to uninstall appmenu-gtk. You do that by clicking Applications | Software Sources, then using the search window to find appmenu-gtk. Clicking on it will allow you to choose to remove it.''
+''If you are using Ubuntu and get no main menu bar when you run this program, you have fallen victim to [https://bugs.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/662077 Ubuntu bug 662077]. Beginning with release 10.10, Ubuntu releases have had a bug causing programs built with wxSmith to fail to show their main menu bar. If this bug affects you, you may want to uninstall appmenu-gtk. You do that by clicking Applications | Software Sources, then using the search window to find appmenu-gtk. Clicking on it will allow you to choose to remove it.''
 Well, so far we have a program that runs and quits, but it does not yet display "Hello, World!". That's next.

← Older revision		Revision as of 01:32, 14 December 2013
Line 17:		Line 17:


−	Click "Create a New Project" and then find and click the wxWidgets Project icon, pointed to by the cursor in the screenshot below.	+	Click "Create a New Project" and then find and double-click the wxWidgets Project icon, pointed to by the cursor in the screenshot below.

@@ Line 111: / Line 111: @@
+}
 </pre>
 Remember to make this change immediately whenever you start a new project.
@@ Line 124: / Line 125: @@
 Well, so far we have a program that runs and quits, but it does not yet display "Hello, World!". That's next.
 == Hello, World! ==