Rinput select - Revision history

Laura: /* Syntax */

2014-05-06T00:10:00Z

Syntax

← Older revision		Revision as of 00:10, 6 May 2014
Line 80:		Line 80:

	===Syntax===		===Syntax===
	RINPUT [#<window number>,] SELECT {MAT< string array>\|<string expression>\|<"<field spec>[;...]"} ["<data item>"] [,ATTR "<attributes>"\|<string expression>] [,HELP {<string expression>\|MAT< array name>\|"<helpstring>[;...]"}] : {<variable name>\|MAT< array name>}[,...] [<error condition> <line ref>][,...]		RINPUT [#<window number>,] SELECT {[[MAT]]< [[string array]]>\|<[[string expression]]>\|<"<[[field spec]]>[;...]"} ["<data item>"] [,[[ATTR]] "<[[attributes]]>"\|<[[string expression]]>] [,[[Field Help\|HELP]] {<[[string expression]]>\|[[MAT]]< [[array name]]>\|"<[[helpstring]]>[;...]"}] : {<[[variable name]]>\|[[MAT]]< [[array name]]>}[,...] [<[[error condition]]> <[[line ref]]>][,...]
	[[Image:Rinputselect.png\|900px]]		[[Image:Rinputselect.png\|900px]]

Laura: /* Syntax */

2014-04-29T14:43:11Z

Syntax

← Older revision		Revision as of 14:43, 29 April 2014
Line 80:		Line 80:

	===Syntax===		===Syntax===
	RINPUT [#<window number>,] SELECT {MAT< string array>\|<string expression>\|<"<field spec>[;...]"} [,ATTR "<attributes>"\|<string expression>] [,HELP <string expression>\|MAT< array name>\|"<helpstring>[;...]"] : {<variable name>\|MAT< array name>}[,...] [<error condition> <line ref>][,...]		RINPUT [#<window number>,] SELECT {MAT< string array>\|<string expression>\|<"<field spec>[;...]"} ["<data item>"] [,ATTR "<attributes>"\|<string expression>] [,HELP {<string expression>\|MAT< array name>\|"<helpstring>[;...]"}] : {<variable name>\|MAT< array name>}[,...] [<error condition> <line ref>][,...]
	[[Image:Rinputselect.png\|900px]]		[[Image:Rinputselect.png\|900px]]

Laura: /* Syntax */

2014-04-29T14:41:07Z

Syntax

← Older revision		Revision as of 14:41, 29 April 2014
Line 80:		Line 80:

	===Syntax===		===Syntax===
	RINPUT [#<window number>,] ~~FIELDS~~ {MAT< string array>\|<string expression>\|<"<field spec>[;...]"} [,ATTR "<attributes>"\|<string expression>] [,HELP <string expression>\|MAT< array name>\|"<helpstring>[;...]"] : {<variable name>\|MAT< array name>}[,...] [<error condition> <line ref>][,...]		RINPUT [#<window number>,] SELECT {MAT< string array>\|<string expression>\|<"<field spec>[;...]"} [,ATTR "<attributes>"\|<string expression>] [,HELP <string expression>\|MAT< array name>\|"<helpstring>[;...]"] : {<variable name>\|MAT< array name>}[,...] [<error condition> <line ref>][,...]
	[[Image:Rinputselect.png\|900px]]		[[Image:Rinputselect.png\|900px]]

Laura: /* Syntax */

2014-04-29T14:40:52Z

Syntax

← Older revision		Revision as of 14:40, 29 April 2014
Line 80:		Line 80:

	===Syntax===		===Syntax===
			RINPUT [#<window number>,] FIELDS {MAT< string array>\|<string expression>\|<"<field spec>[;...]"} [,ATTR "<attributes>"\|<string expression>] [,HELP <string expression>\|MAT< array name>\|"<helpstring>[;...]"] : {<variable name>\|MAT< array name>}[,...] [<error condition> <line ref>][,...]
	[[Image:Rinputselect.png\|900px]]		[[Image:Rinputselect.png\|900px]]

Laura at 21:33, 26 July 2013

2013-07-26T21:33:56Z

← Older revision		Revision as of 21:33, 26 July 2013
Line 1:		Line 1:
	The '''RInput Select''' (RIN S) [[statement]] combines the capabilities of [[PRINT FIELDS]] and [[INPUT SELECT]] so that it both prints a series of menu selections and sets up an input screen for the selection. The only data which is accepted by RInput Select is the pressing of either Enter or one of the [[function keys]]; neither action changes any of the data in the fields, but they do cause the [[CMDKEY]] and the [[CURFLD]] system functions to be set. RInput Select additionally allows the use of field help windows for any or all of the defined fields.		The '''RInput Select''' (RIN S) [[statement]] combines the capabilities of [[PRINT FIELDS]] and [[INPUT SELECT]] so that it both prints a series of menu selections and sets up an input screen for the selection. The only data which is accepted by RInput Select is the pressing of either Enter or one of the [[Control Keys and Predefined Functions\|function keys]]; neither action changes any of the data in the fields, but they do cause the [[CMDKEY]] and the [[CURFLD]] system functions to be set. RInput Select additionally allows the use of field help windows for any or all of the defined fields.

	:1.) The cursor's field movement will respond to the arrow keys without regard to the order of the options. The down arrow will move to the field below the cursor's current position.The up arrow moves the cursor to the field above its current position, the left arrow searches to the left of the current field and continues up the screen and then from the end of the screen until it finds another field or itself. The right arrow works the same way, except right and down the screen. If there is no field in the same column as the cursor, the up or down arrow will stay at the current field.		:1.) The cursor's field movement will respond to the arrow keys without regard to the order of the options. The down arrow will move to the field below the cursor's current position.The up arrow moves the cursor to the field above its current position, the left arrow searches to the left of the current field and continues up the screen and then from the end of the screen until it finds another field or itself. The right arrow works the same way, except right and down the screen. If there is no field in the same column as the cursor, the up or down arrow will stay at the current field.

Laura: /* Parameters */

2013-07-17T17:34:35Z

Parameters

← Older revision		Revision as of 17:34, 17 July 2013
Line 101:		Line 101:
	Mat string array, string expression, or "field spec" are used to specify the field used. See [[Field Specs]] for parameters on the supplemental syntax. If the "string-expr" or "MAT string-array" parameters are used to specify the Field definition, each must include the same elements that are identified in the "field-spec" parameter.		Mat string array, string expression, or "field spec" are used to specify the field used. See [[Field Specs]] for parameters on the supplemental syntax. If the "string-expr" or "MAT string-array" parameters are used to specify the Field definition, each must include the same elements that are identified in the "field-spec" parameter.

	The "ATTR" keyword identifies that a separate set of attributes should be used for the current input field. It must be followed by either the "attributes" parameter or the "string expression" parameter. "Attributes" represents an insertable syntax that identifies the monochrome, color and control attributes that are to be used for the field. See [[~~Definitions~~]] for ~~the insertable syntax and additional information~~. If used, the value of "string expression" must include the same elements as are required in the "attributes" parameter.		The "ATTR" keyword identifies that a separate set of attributes should be used for the current input field. It must be followed by either the "attributes" parameter or the "string expression" parameter. "Attributes" represents an insertable syntax that identifies the monochrome, color and control attributes that are to be used for the field. See [[Attribute (Screen)]] for details. If used, the value of "string expression" must include the same elements as are required in the "attributes" parameter.

	Following the HELP parameter, if the "string-expr" or "MAT string-array" parameters are used to specify field help text, each must include the same elements that are identified in the "helpstring" specification. Business Rules assumes that multiple field help specifications will be identified in the same field order which is indicated in the field definition string.		Following the HELP parameter, if the "string-expr" or "MAT string-array" parameters are used to specify field help text, each must include the same elements that are identified in the "helpstring" specification. Business Rules assumes that multiple field help specifications will be identified in the same field order which is indicated in the field definition string.

Laura: /* Technical Considerations */

2013-02-05T23:09:28Z

Technical Considerations

← Older revision		Revision as of 23:09, 5 February 2013
Line 121:		Line 121:
	:4.) PRINT NEWPAGE should be executed before any full screen processing operation. This will fully remove any data that may remain from previous screen operations.		:4.) PRINT NEWPAGE should be executed before any full screen processing operation. This will fully remove any data that may remain from previous screen operations.
	:5.) Keyboard buffering operates identically for RINPUT SELECT as it does for INPUT. Buffering may be turned on or off with the [[BRConfig.sys]] file [[TYPEAHEAD]] specification.		:5.) Keyboard buffering operates identically for RINPUT SELECT as it does for INPUT. Buffering may be turned on or off with the [[BRConfig.sys]] file [[TYPEAHEAD]] specification.
			:6.) See also [[Setenv\|SETENV()]] function relating to window size.

	<noinclude>		<noinclude>

Laura: /* Supplemental Syntax ("helpstring" parameter) */

2013-01-31T20:53:53Z

Supplemental Syntax ("helpstring" parameter)

← Older revision		Revision as of 20:53, 31 January 2013
Line 90:		Line 90:
	[[Image:Helpstring.png\|800px]]		[[Image:Helpstring.png\|800px]]

	See [[Field Help]] for more information.		See [[Field Help]] for more information, including syntax parameters.

	===Parameters===		===Parameters===

Laura: /* Supplemental Syntax ("field-spec" parameter) */

2013-01-31T20:53:41Z

Supplemental Syntax ("field-spec" parameter)

← Older revision		Revision as of 20:53, 31 January 2013
Line 84:		Line 84:
	===Supplemental Syntax ("field-spec" parameter)===		===Supplemental Syntax ("field-spec" parameter)===
	[[Image:Fieldspec.png\|800px]]		[[Image:Fieldspec.png\|800px]]

			See [[Field Specs]] for more information, including syntax parameters.

	===Supplemental Syntax ("helpstring" parameter)===		===Supplemental Syntax ("helpstring" parameter)===

Laura: /* Parameters */

2013-01-31T20:52:31Z

Parameters

← Older revision		Revision as of 20:52, 31 January 2013
Line 103:		Line 103:
	Following the HELP parameter, if the "string-expr" or "MAT string-array" parameters are used to specify field help text, each must include the same elements that are identified in the "helpstring" specification. Business Rules assumes that multiple field help specifications will be identified in the same field order which is indicated in the field definition string.		Following the HELP parameter, if the "string-expr" or "MAT string-array" parameters are used to specify field help text, each must include the same elements that are identified in the "helpstring" specification. Business Rules assumes that multiple field help specifications will be identified in the same field order which is indicated in the field definition string.

	~~Following the colon,~~ Variable name or Mat array-name ~~specify~~ which variables ~~represent~~ the ~~seleceted information~~.		"Variable name" or "Mat array name" identifies the variables to which the input is to be assigned. With RINPUT FIELDS and RINPUT SELECT, the current values of are output, the output values are updated by the operator, and the updated values are re-input to the specified variables. A colon (:) must separate the these from any previous parameters in the statement. At least one "variable name" or "MAT array-name" must be specified and multiple variables must be separated by commas

	The "error-cond" portion of the parameter identifies the error to be trapped, and the "line-ref" portion identifies the line to which execution should be transferred when such an error is trapped.		The "error-cond" portion of the parameter identifies the error to be trapped, and the "line-ref" portion identifies the line to which execution should be transferred when such an error is trapped.