{"id":1136,"date":"2012-02-14T18:17:17","date_gmt":"2012-02-14T23:17:17","guid":{"rendered":"http:\/\/anvil-of-time.com\/wordpress\/?p=1136"},"modified":"2021-03-11T11:10:27","modified_gmt":"2021-03-11T16:10:27","slug":"100-days-of-powerbuilder-day-2-creating-a-main-application-window","status":"publish","type":"post","link":"https:\/\/anvil-of-time.com\/powerbuilder\/100-days-of-powerbuilder\/100-days-of-powerbuilder-day-2-creating-a-main-application-window\/","title":{"rendered":"100 Days of PowerBuilder – Day 2: Creating a Main Application Window"},"content":{"rendered":"

This is part of my project ‘100 Days of PowerBuilder’ which is a series of discussions focused on basic PowerBuilder development.<\/p>\n

Note: This article is written with examples created in PowerBuilder version 12.5. The most steps would be identical with any version going back to 9.<\/em><\/p>\n

For the purposes of this exercise I will be creating a Windows based application with a Single Document Interface (SDI)<\/a>. Later installments of the project will cover the other main interface type, MDI (Multiple Document Interface).<\/p>\n

If you re-start PowerBuilder from the conclusion of our last session you will again be greeted with the ‘Welcome’ page.
\n\"\"<\/a><\/p>\n

At this point you may wish to check the last checkbox, ‘Reload last workspace…’. This will have PB automatically begin each session with the previous session’s workspace open within the IDE. As time goes on you will probably uncheck the ‘Show this dialog box…’ option to dispense with the Welcome window altoghether.<\/p>\n

To add a ‘main’ window to the application choose ‘File – New’ which presents you with the following dialog window<\/p>\n

\"\"<\/a><\/p>\n

Select ‘Window’ and click ‘OK’. We will go over the other items in later sessions.<\/p>\n

\"\"<\/a><\/p>\n

By default the script window is opened for the new window (called ‘Untitled’ since it has just been created) in the ‘Open’ event. Lets set some of the window’s propreties right off the bat. Click on the Properties tab on the control list (lower left of screen).<\/p>\n

\"\"<\/a><\/p>\n

This window shows the entire PB IDE so lets take a quick overview. The top portion contains all the various menu bars, the left frame contains the system tree, the bottom frame contains the output (you can toggle these visible\/invisible via the Window menu option), and the right frame is the current object editor (which includes the scripts and layout tabs) as well as the object properties frame.<\/p>\n

The toolbars change depending upon which area of the IDE you are working in. To maximize the ‘working area’ (the area containing the scripts and layout) drag the toolbar sections from the third row up to the first two rows. See the start and end examples:<\/p>\n

\"\"<\/a>
\n\"\"<\/a><\/p>\n

Okay, back to the window properties. Give the window a Title as shown below. All of the other defaults are fine for now<\/p>\n

\"\"<\/a><\/p>\n

Now lets drop an object on the window to provide some basic functionality. In this case a button to close the window. Click on the Layout tab at the bottom of the IDE to display the window form. From the toolbar click on the small down arrow next to the Add Control icon.
\n\"\"<\/a><\/p>\n

This brings up a subtoolbar with various controls you can place on the window. Choose (click) the command button option as shown then click on the toolbar icon to tell the IDE you are going to place a command button on some other control.<\/p>\n

\"\"<\/a><\/p>\n

(Note about the add control icon, the icon on the IDE toolbar changes to the last control chosen so it will not always appear as a button.)<\/p>\n

Click on the window form to place the command button. Once place the control is ‘selected’ allowing for resizing and repositioning as needed. Move the button to the lower right corner of the window frame.<\/p>\n

\"\"<\/a><\/p>\n

Note the properties section of IDE changes to those of the button just added. Change the Text from ‘none’ to ‘Exit’ since that is the function of the button. Right click on the button control and choose ‘Script’ from the menu. This takes you to the script portion of the control and, in the case of a command button, to the ‘clicked’ event. If you click on the downarrow in the Event list of the control, you see all of the system defined events for this type of control.<\/p>\n

\"\"<\/a><\/p>\n

Remain in the clicked event script by clicking outside the dropdown. In the event script insert the following code:<\/p>\n

<pre>close()<\/pre><\/p>\n

Okay, so what is this doing? Well, the button is used to trigger a method on the main window, in this case the Close function.<\/p>\n

Now Save the window. This brings up the Save Window dialog.<\/p>\n

\"\"<\/a><\/p>\n

In this dialog we give the window a name (w_main), some comments, and select which library in our target we wish to save it in. Since we have only one library (PBL file) our choices are limited. Note the section below the window name. This area lists other objects in the currently selected library of the same type (in our case a window). Since this is the first window we are saving, the list is empty.<\/p>\n

\"\"<\/a><\/p>\n

Now click the OK button.<\/p>\n

Okay, something’s not correct.<\/p>\n

\"\"<\/a><\/p>\n

The section below the event script has a message indicating an error. If there were multiple lines in the script above, you could click on the error messages and you would be taken to the incorrect line. In our case we are missing an argument to the function. To correct the error change the script to:<\/p>\n

\"\"<\/a><\/p>\n

In this case the close method requires the name of the window it’s going to close. The pronoun ‘Parent’ is used to refer to the button’s containing control which is in this case a window. A window is the Parent of all of the controls which are directly placed upon it.<\/p>\n

Now save the window. You will have to put in information in the window save dialog again in order to save it.<\/p>\n

Now code the ‘Closequery’ event on the window. The button click will call the close function on the window. This function will first call the ‘closequery’ event and the ‘close’ event on the window. This allows for any preprocessing which may need to occur prior to the close of the window. Right click on the window, choose script, and then choose closequery from the dropdown. Insert the following code:<\/p>\n

<pre>IF Messagebox(‘Hello World’,’Close the window?’,Question!,YesNo!) = 2 THEN
\nRETURN 1
\nEND IF<\/pre><\/p>\n

This causes a messagebox window prompting a response from the user. The first string of the function is the messagebox title, the second is the message, the third is the icon, and the fourth is the choices the user has. Each choice returns a numerical value, in this case a 2 indicates the user pressed ‘No’. The closequery event can be used to prevent the close of the window by returning a value of 1.<\/p>\n

Save the window again and then click on the Run icon.<\/p>\n

\"\"<\/a><\/p>\n

Now another message indicating something else is missing.<\/p>\n

\"\"<\/a><\/p>\n

Click ok and add the following:<\/p>\n

<pre>Open(w_main)<\/pre><\/p>\n

\"\"<\/a><\/p>\n

This tells the application to open the window object ‘w_main’ when the application launches.<\/p>\n

Now save and run the application.<\/p>\n

\"\"<\/a><\/p>\n

Click Exit.<\/p>\n

\"\"<\/a><\/p>\n

Click Yes to exit the app.<\/p>\n","protected":false},"excerpt":{"rendered":"

This is part of my project ‘100 Days of PowerBuilder’ which is a series of discussions focused on basic PowerBuilder development. Note: This article is written with examples created in PowerBuilder version 12.5. The most steps would be identical with any version going back to 9. For the purposes of this exercise I will be…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[86],"tags":[12,62],"_links":{"self":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts\/1136"}],"collection":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/comments?post=1136"}],"version-history":[{"count":10,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts\/1136\/revisions"}],"predecessor-version":[{"id":2019,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts\/1136\/revisions\/2019"}],"wp:attachment":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/media?parent=1136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/categories?post=1136"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/tags?post=1136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}