Buttons Tutorial - Revision history

Laura at 01:25, 16 July 2013

2013-07-16T01:25:33Z

← Older revision		Revision as of 01:25, 16 July 2013
Line 37:		Line 37:

	<noinclude>		<noinclude>
	[[Category:Tutorial]]		[[Category:GUI Tutorial]]
	</noinclude>		</noinclude>

Laura: /* Exercise 1.3 */

2013-07-16T01:01:52Z

Exercise 1.3

← Older revision		Revision as of 01:01, 16 July 2013
Line 34:		Line 34:
	Next: [[Lists Tutorial\|Lists]]<br>		Next: [[Lists Tutorial\|Lists]]<br>
	Back: [[Tutorial 2\|Table of Contents]]		Back: [[Tutorial 2\|Table of Contents]]
			</noinclude>

			<noinclude>
			[[Category:Tutorial]]
	</noinclude>		</noinclude>

Laura at 15:31, 11 July 2013

2013-07-11T15:31:27Z

← Older revision		Revision as of 15:31, 11 July 2013
Line 29:		Line 29:

	B. For use in the next sections, also add input fields for customer name and address, then write all the information into a file called ORDERS.INT. Run the program several times so that you have quite a few entries in the file to work with (this should all be review from the first tutorial). Once again see the [[Solutions 2#Exercis 1.3\|solutions]] page if you need help.		B. For use in the next sections, also add input fields for customer name and address, then write all the information into a file called ORDERS.INT. Run the program several times so that you have quite a few entries in the file to work with (this should all be review from the first tutorial). Once again see the [[Solutions 2#Exercis 1.3\|solutions]] page if you need help.


	<noinclude>		<noinclude>
	[[Tutorial 2\|Table of Contents]]		Next: [[Lists Tutorial\|Lists]]<br>
			Back: [[Tutorial 2\|Table of Contents]]
	</noinclude>		</noinclude>

Laura at 15:26, 11 July 2013

2013-07-11T15:26:48Z

← Older revision		Revision as of 15:26, 11 July 2013
Line 29:		Line 29:

	B. For use in the next sections, also add input fields for customer name and address, then write all the information into a file called ORDERS.INT. Run the program several times so that you have quite a few entries in the file to work with (this should all be review from the first tutorial). Once again see the [[Solutions 2#Exercis 1.3\|solutions]] page if you need help.		B. For use in the next sections, also add input fields for customer name and address, then write all the information into a file called ORDERS.INT. Run the program several times so that you have quite a few entries in the file to work with (this should all be review from the first tutorial). Once again see the [[Solutions 2#Exercis 1.3\|solutions]] page if you need help.

			<noinclude>
			[[Tutorial 2\|Table of Contents]]
			</noinclude>

Laura: Created page with "Now that the user has input all the data into your CHAPTER1 program, instead of hitting the escape key, wouldn't it be great to have an exit button? Or a button to complete ot..."

2013-07-11T13:34:07Z

Created page with "Now that the user has input all the data into your CHAPTER1 program, instead of hitting the escape key, wouldn't it be great to have an exit button? Or a button to complete ot..."

New page

Now that the user has input all the data into your CHAPTER1 program, instead of hitting the escape key, wouldn't it be great to have an exit button? Or a button to complete other actions like print a mailing label or prepare an invoice? Since version 4.15, BR can create buttons on the screen.

Take a look at this example:

00500 print fields "23,30,CC 8,,B99" : "Done"

Buttons are created using PRINT FIELDS, with the starting row and column, attributes (Characters and Centered in this case), button size (in columns), the B (for button!) and the FKEY value, which is set to 99 in this case. After the colon is the caption. If you run this example, it will print the button beautifully but do nothing.

[[Image:1.3.jpg]]

That's because buttons depend on the program waiting for the user to click it, which sets the Fkey value, and so triggers the desired action. Therefore, the program must be waiting for something else to happened as it waits for that Fkey to be set (by clicking it). It could wait for a checkbox or radio button selection, input information, or even just a dummy input. For this reason, buttons pair well with input forms.

Here's an example:

00490 dim box$(3)
00500 print fields "23,30,CC 8,,B99" : "Done"
00510 data "Item 1","Item 2","Item 3"
00520 read mat Box$
00530 do
00540 rinput fields "22,14,CHECK 8,,10;23,14,CHECK 8,,11;24,14,CHECK 8,,12": Box$(1),Box$(2),Box$(3)
00550 print fields "24,1,N 2": Fkey
00560 loop While Fkey~=99

Line 500 creates the button on the screen with print fields “row,col, attributes length, , B99”, where the B stands for button and the 99 sets the FKEY value. After the colon, the “Done” will be the label on the button. This example lets the user choose from several checkboxes, and then click the button, which ends the LOOP and in this case the program. In other programs, the FKEY could be set to run other activities as well.

====Exercise 1.3====

A. Add an exit button to the sample program that we've been working on in this chapter. See the [[Solutions 2#Exercis 1.3|solutions]] if necessary.

B. For use in the next sections, also add input fields for customer name and address, then write all the information into a file called ORDERS.INT. Run the program several times so that you have quite a few entries in the file to work with (this should all be review from the first tutorial). Once again see the [[Solutions 2#Exercis 1.3|solutions]] page if you need help.