Screen Operations - Revision history

Gordon.dye at 04:22, 13 April 2026

2026-04-13T04:22:15Z

← Older revision		Revision as of 04:22, 13 April 2026
Line 9:		Line 9:

	;Besides allowing access to any position on the screen, full screen processing provides several additional advantages:		;Besides allowing access to any position on the screen, full screen processing provides several additional advantages:
	# Screens can be attractively designed, making programs ~~look extremely~~ professional ~~to the end-user~~.		# Screens can be attractively designed, making programs appear professional.
	# Less code is required. One screen that fully utilizes Windows control attributes and displays ten prompts and ten input fields can be programmed in as few as two statements.		# Less code is required. One screen that fully utilizes Windows control attributes and displays ten prompts and ten input fields can be programmed in as few as two statements.
	# The operation of the input screen can be controlled. Control attributes may be used to specify starting cursor positions, automatic entry of data, field protection and more.		# The operation of the input screen can be controlled. Control attributes may be used to specify starting cursor positions, automatic entry of data, field protection and more.
Line 19:		Line 19:
	The [[GUI console]] can be opened to other than 80 columns by 24 rows:		The [[GUI console]] can be opened to other than 80 columns by 24 rows:

	An OPEN window statement may specify a parent window number:		An OPEN window statement may specify a parent window number.
	~~George, Dallas, 42, 180~~

	~~George, Peter, Tom~~

	Version [[4.14]]+ will no longer display fonts as bitmaps. It will, by using only native graphical controls, support proportional fonts and variable window sizes. Caution- You may need to make programming changes to utilize this version.

	Two fonts are supported simultaneously, one for background and captions and one font for input fields.		Two fonts are supported simultaneously, one for background and captions and one font for input fields.

	~~===General Coding Concepts===~~		;Always [[Print Newpage]] Initially When Full Screen Processing

	;Always [[Print Newpage]] ~~Before~~ Full Screen Processing

	Business Rules! does not automatically clear the screen when full screen processing is used. The program must do this with PRINT NEWPAGE. Neglecting to clear the screen when changing to or from full screen processing may cause errors in the operators new entry as old information may become interspersed with new.

	====Multiple Field Processing====		====Multiple Field Processing====

Gordon.dye: /* Multiple Field Processing */

2020-07-11T15:26:43Z

Multiple Field Processing

← Older revision		Revision as of 15:26, 11 July 2020
Line 62:		Line 62:

	There are a few important items to be aware of when specifying multiple fields in full screen processing statements.		There are a few important items to be aware of when specifying multiple fields in full screen processing statements.
	# ~~when~~ a string array is specified for field definitions (as with FLDDEF$ in line 220 above), extra elements in the string array will be ignored. Thus, if FLDDEF$ contained seven field definitions instead of six, the seventh would be ignored.		# When a string array is specified for field definitions (as with FLDDEF$ in line 220 above), extra elements in the string array will be ignored. Thus, if FLDDEF$ contained seven field definitions instead of six, the seventh would be ignored.
	# ~~the~~ order of definitions in an array determines the order of processing. The first element of the array corresponds to the first item to be processed, the second element of the array corresponds to the second item to be processed, and so on. The order of items in the field definition does not affect your accessibility to the screen; you may define fields from the bottom of the screen to the top or from the top to the bottom or in any other way you prefer.		# The order of definitions in an array determines the order of processing. The first element of the array corresponds to the first item to be processed, the second element of the array corresponds to the second item to be processed, and so on. The order of items in the field definition does not affect your accessibility to the screen; you may define fields from the bottom of the screen to the top or from the top to the bottom or in any other way you prefer.
	# it is important to remember that fields should be referenced in a consistent order throughout the full screen processing statement. The order that fields are referenced in the field definition array should be the same order that they are referenced with field help and variable names specifications.		# It is important to remember that fields should be referenced in a consistent order throughout the full screen processing statement. The order that fields are referenced in the field definition array should be the same order that they are referenced with field help and variable names specifications.
	# ~~string~~ and numeric fields may be intermixed in any order as long as the field definitions match the corresponding variable type. For instance, in the following example, the first field definition identifies a string field that starts at row 3, column 5 and is 20 characters long. This field definition corresponds to the first variable (NAME$) in the I/O list. Likewise, the second field definition identifies a three-digit number which corresponds to the numeric AGE variable.		# String and numeric fields may be intermixed in any order as long as the field definitions match the corresponding variable type. For instance, in the following example, the first field definition identifies a string field that starts at row 3, column 5 and is 20 characters long. This field definition corresponds to the first variable (NAME$) in the I/O list. Likewise, the second field definition identifies a three-digit number which corresponds to the numeric AGE variable.

	1000 INPUT FIELDS "3,5,C 20; 7,5,N 3" : NAME$, AGE		1000 INPUT FIELDS "3,5,C 20; 7,5,N 3" : NAME$, AGE

Gordon.dye: /* Full Screen Processing */

2020-07-11T15:21:36Z

Full Screen Processing

← Older revision		Revision as of 15:21, 11 July 2020
Line 6:		Line 6:
	==Full Screen Processing==		==Full Screen Processing==

	Full screen processing allows data entry [[controls]] on any position on the screen, specified by [[Row]] and [[Column]]. This contrasts with ~~regular~~ screen processing, which allows prompted data display and entry with [[PRINT]], [[INPUT]], [[LINPUT]] and [[RINPUT]] statements, but only allows access to the bottom line of the screen. (Lines in regular screen processing then scroll up until they scroll off the top of the screen.) With full screen processing, any position on the screen may be addressed directly.		Full screen processing allows data entry [[controls]] on any position on the screen, specified by [[Row]] and [[Column]]. This contrasts with sequential screen processing, which allows prompted data display and entry with [[PRINT]], [[INPUT]], [[LINPUT]] and [[RINPUT]] statements, but only allows access to the bottom line of the screen. (Lines in regular screen processing then scroll up until they scroll off the top of the screen.) With full screen processing, any position on the screen may be addressed directly.

	;Besides allowing access to any position on the screen, full screen processing provides several additional advantages ~~over regular screen processing~~:		;Besides allowing access to any position on the screen, full screen processing provides several additional advantages:
	# Screens can be attractively designed, making programs look extremely professional to the end-user.		# Screens can be attractively designed, making programs look extremely professional to the end-user.
	# Less code is required. One screen that fully utilizes Windows control attributes and displays ten prompts and ten input fields can be programmed in as few as two statements.		# Less code is required. One screen that fully utilizes Windows control attributes and displays ten prompts and ten input fields can be programmed in as few as two statements.

Gordon.dye: /* Full Screen Processing */

2020-07-11T15:19:16Z

Full Screen Processing

← Older revision		Revision as of 15:19, 11 July 2020
Line 9:		Line 9:

	;Besides allowing access to any position on the screen, full screen processing provides several additional advantages over regular screen processing:		;Besides allowing access to any position on the screen, full screen processing provides several additional advantages over regular screen processing:
	~~# Fields can be displayed on monochrome monitors as underlined, blinking, highlighted, reversed, or invisible.~~
	~~# Fields can be displayed on color monitors with foreground and background color attributes.~~
	~~# Several input fields can be displayed on a single screen; this can be a real convenience for fast data- entry operators.~~
	# Screens can be attractively designed, making programs look extremely professional to the end-user.		# Screens can be attractively designed, making programs look extremely professional to the end-user.
	# Less code is required. One screen that fully utilizes ~~monochrome or color~~ attributes and displays ten prompts and ten input fields can be programmed in as few as two statements.		# Less code is required. One screen that fully utilizes Windows control attributes and displays ten prompts and ten input fields can be programmed in as few as two statements.
	# The operation of the input screen can be controlled. Control attributes may be used to specify starting cursor positions, automatic entry of data, field protection and more.		# The operation of the input screen can be controlled. Control attributes may be used to specify starting cursor positions, automatic entry of data, field protection and more.

Gordon.dye at 15:15, 11 July 2020

2020-07-11T15:15:30Z

← Older revision		Revision as of 15:15, 11 July 2020
Line 1:		Line 1:
	[[Business Rules!]] advanced '''Screen Input/Output''' capabilities include many abilities:		[[Business Rules!]] advanced '''Screen Input/Output''' capabilities include many abilities:
	* Print to and input from any position on the screen (full screen processing)		* Print to and input from any position on the screen (full screen processing)
	* Designation one or more portions of the screen as its own mini-screen (windowing)		* Designation of one or more portions of the screen as its own mini-screen (windowing)
	* Change the screen's display features through the use of screen attributes		* Change the screen's display features through the use of screen attributes

John: /* BUG FIXES */

2014-05-21T14:25:46Z

BUG FIXES

← Older revision		Revision as of 14:25, 21 May 2014
Line 1,187:		Line 1,187:

	DIM statements were not being reinitialized prior to Save and Replace operations. This caused arrays to be corrupted when they were redimensioned in a library routine prior to replacing a program. This was an ancient bug.		DIM statements were not being reinitialized prior to Save and Replace operations. This caused arrays to be corrupted when they were redimensioned in a library routine prior to replacing a program. This was an ancient bug.

	~~Shell Limit -1 is now working again (waits indefinitely).~~

	[[Category:Basics]]		[[Category:Basics]]

Laura: Created page with "Business Rules! advanced '''Screen Input/Output''' capabilities include many abilities: * Print to and input from any position on the screen (full screen processing) * Des..."

2013-10-11T21:52:20Z

Created page with "Business Rules! advanced '''Screen Input/Output''' capabilities include many abilities: * Print to and input from any position on the screen (full screen processing) * Des..."

Show changes