Grid and List - Revision history

Gordon.dye: /* FKey Processing */

2024-02-05T05:25:45Z

FKey Processing

← Older revision		Revision as of 05:25, 5 February 2024
Line 31:		Line 31:


	~~Formerly~~, [[CURROW]] and [[CURCOL]] ~~represented~~ the character position where the cursor was when FIELDS processing is completed. ~~This is still true except~~ when the most recent field processed is a [[2D control]].		With regard to simple field specifications in PRINT FIELDS or INPUT FIELDS statements, [[CURROW]] and [[CURCOL]] identify the character position where the cursor was when FIELDS processing is completed. However, when the most recent field processed is a [[2D control]] then [[CURROW]] and [[CURCOL]] results have different meanings:

	When FIELDS processing ends and control is returned to the program while the 'current' control is of type LIST or GRID, CURROW and CURCOL are set to the current cell row and column within the 2D control instead of the character position relative to the window.		When FIELDS processing ends and control is returned to the program while the 'current' control is of type LIST or GRID, CURROW and CURCOL are set to the current cell row and column within the 2D control instead of the character position relative to the window.

Gordon.dye: /* FKey Processing */

2024-02-05T05:15:42Z

FKey Processing

← Older revision		Revision as of 05:15, 5 February 2024
Line 29:		Line 29:
	*Displayed but inactive- Single clicking any cell produces the FKey interrupt.		*Displayed but inactive- Single clicking any cell produces the FKey interrupt.
	*Active (participating in Input Fields)- Double clicking any cell produces an FKey completion.		*Active (participating in Input Fields)- Double clicking any cell produces an FKey completion.


	Formerly, [[CURROW]] and [[CURCOL]] represented the character position where the cursor was when FIELDS processing is completed. This is still true except when the most recent field processed is a [[2D control]].		Formerly, [[CURROW]] and [[CURCOL]] represented the character position where the cursor was when FIELDS processing is completed. This is still true except when the most recent field processed is a [[2D control]].

Gordon.dye at 05:14, 5 February 2024

2024-02-05T05:14:33Z

← Older revision		Revision as of 05:14, 5 February 2024
Line 1:		Line 1:
			This discussion assumes the reader has a clear understanding of [[INPUT FIELDS]] and [[PRINT FIELDS]] processing with simple fields.

	'''Grid''' and '''List''' (a.k.a. '''ListView''') are [[Two dimensional controls]], which means that they contain rows and columns. GRIDs are normally used for data entry, while LISTs are used only for selection. In Business Rules, outputting to these controls is done with [[Print Fields]] and inputting from them is done with [[Input Fields]]. Each field specification pertains to one [[Control]]. However, a single FIELD specification can pertain to a parenthesized group of arrays. When using Grids and Lists, first the header must be populated, and then the data within the rows.		'''Grid''' and '''List''' (a.k.a. '''ListView''') are [[Two dimensional controls]], which means that they contain rows and columns. GRIDs are normally used for data entry, while LISTs are used only for selection. In Business Rules, outputting to these controls is done with [[Print Fields]] and inputting from them is done with [[Input Fields]]. Each field specification pertains to one [[Control]]. However, a single FIELD specification can pertain to a parenthesized group of arrays. When using Grids and Lists, first the header must be populated, and then the data within the rows.

Gordon.dye: /* GRID CURSOR MOVEMENT */

2024-02-05T05:03:13Z

GRID CURSOR MOVEMENT

← Older revision		Revision as of 05:03, 5 February 2024
Line 33:		Line 33:

	====GRID CURSOR MOVEMENT====		====GRID CURSOR MOVEMENT====
	When field + or - is keyed BR ~~Always~~ returns fkey values of 114 or 115 in		When field + or - is keyed BR always returns fkey values of 114 or 115 in both navigation and edit mode and for any type of data.
	both navigation and edit mode and for any type of data. (This assumes the X		(This assumes the X attribute or some other attribute returns control to the program.)
	attribute or some other attribute returns control to the program.)

	~~In edit mode,~~ Field +/- ~~always forces the signing of~~ a ~~numeric field~~,		Default cursor positioning for Field +/- keys is to perform a down arrow operation, and the Enter key defaults to NONE (no movement).
	~~whether or not~~ the ~~field type is PIC~~.

	In edit mode, field ~~plus or minus right truncates any character~~ or ~~numeric~~		In edit mode, Field +/- forces the signing of a numeric field, whether or not the field type is PIC.
	~~data before exiting~~ the field.

	A ~~new~~ Config statement ~~is defined~~ to ~~help with~~ grid cursor movement:		In edit mode, Field +/- also right truncates any character or numeric data before exiting the field.


			A Config statement can be used to override (control) grid cursor movement. When this is used, both Field +/- and Enter produce the same cursor movement:

	GRID_CURSOR_MOVE DOWN \| RIGHT \| NONE \| DEFAULT		GRID_CURSOR_MOVE DOWN \| RIGHT \| NONE \| DEFAULT

	This determines the field cursor position after keying Enter or		This determines the field cursor position after keying Enter or Field +/-. Both navigation and edit mode produce the same resulting cursor position.
	Field +/-. Both navigation and edit mode produce the same resulting cursor
	position.

	~~Default Enter and Field +/- cursor movement are unchanged. Field plus~~
	~~or minus perform a down arrow operation, and Enter defaults to NONE.~~
	~~GRID_CURSOR_MOVE overrides both of these~~.

	====Restoring a User Sorted 2D Control====		====Restoring a User Sorted 2D Control====

Gordon.dye: /* Parameters */

2020-02-15T14:07:27Z

Parameters

← Older revision		Revision as of 14:07, 15 February 2020
Line 147:		Line 147:
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''HEADERS'''		\| width="10%" \| '''HEADERS'''
	\|(As of 4.30) The read operation returns the original PRINT FIELDS HEADER values. For example: INPUT FIELDS "row,col,LIST rows/cols, HEADERS,,NOWAIT" : (MAT HEADINGS$,MAT WIDTHS, MAT FORMS$) The selection ~~typed~~ used must be ALL.		\|(As of 4.30) The read operation returns the original PRINT FIELDS HEADER values. For example: INPUT FIELDS "row,col,LIST rows/cols, HEADERS,ALL,NOWAIT" : (MAT HEADINGS$,MAT WIDTHS, MAT FORMS$) The selection type used must be ALL.
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''MASK'''		\| width="10%" \| '''MASK'''

John: /* See Also: */

2017-04-06T13:31:15Z

Laura: /* Parameters */

2015-11-03T16:14:53Z

Parameters

← Older revision		Revision as of 16:14, 3 November 2015
Line 150:		Line 150:
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''MASK'''		\| width="10%" \| '''MASK'''
	\|(As of 4.30) MASK can be used with Grids and Lists. As a READ type, this reads the display mask setting. For example: INPUT FIELDS "row,col,LIST rows/cols,MASK [,NOWAIT]" : mask_array. The mask array affects only the user presentation and not the data. Use RANGE processing or the CHG selection type to selectively read from a 2D control.		\|(As of 4.30) MASK can be used with Grids and Lists. As a READ type, this reads the display mask setting, including listviews that have been displayed according to a [[filter]] or filterbox. For example: INPUT FIELDS "row,col,LIST rows/cols,MASK [,NOWAIT]" : mask_array. The mask array affects only the user presentation and not the data. Use RANGE processing or the CHG selection type to selectively read from a 2D control.
	\|}		\|}

Laura: /* Parameters */

2015-10-13T16:15:00Z

Parameters

← Older revision		Revision as of 16:15, 13 October 2015
Line 145:		Line 145:
	array(3) -> 0		array(3) -> 0
	array(4) -> 2		array(4) -> 2
	~~\|- valign="top"~~
	~~\| width="10%" \| '''DISPLAYED_ORDER'''~~
	\|Indicates that the read operation is to not restore the data into it's original order before returning the results to the program (as of version 4.30). This reads the original row subscripts for all rows - in their present order - and only works with the ALL selection type.
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''HEADERS'''		\| width="10%" \| '''HEADERS'''
Line 204:		Line 201:
	\|}		\|}

	The '''Read Qualifier''' is an optional parameter to help the read. As of 4.3 it can be [[DISPLAYED_ORDER]]. #[[PIC]] or #[[FMT]] could be used. #PIC and #FMT allow numeric data from a string to be used.		The '''Read Qualifier''' is an optional parameter to help the read. As of 4.3 it can be [[DISPLAYED_ORDER]]. #[[PIC]] or #[[FMT]] could be used. #PIC and #FMT allow numeric data from a string to be used. For example: '''DISPLAYED_ORDER''' Indicates that the read operation is to not restore the data into it's original order before returning the results to the program (as of version 4.30). This reads the original row subscripts for all rows - in their present order - and only works with the ALL selection type.

	GRIDLINES makes LIST controls look like GRIDs with respect to the display of data (column and row separators).		GRIDLINES makes LIST controls look like GRIDs with respect to the display of data (column and row separators).

Laura: /* Parameters */

2015-10-05T20:04:10Z

Parameters

← Older revision		Revision as of 20:04, 5 October 2015
Line 134:		Line 134:
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''Sort_Order'''		\| width="10%" \| '''Sort_Order'''
	\|Provides a value of zero for each unsorted column and gives the ascending sequence of column sorts that have occurred. If a column has been reversed (double sorted) it's value will be negative. The selection typed used must be ALL. For example: INPUT FIELDS "row,col,GRID rows/cols, SORT_ORDER, ALL" : Mat NumArray, with the following history of sorting a four column GRID:		\|(4.3+) Provides a value of zero for each unsorted column and gives the ascending sequence of column sorts that have occurred. If a column has been reversed (double sorted) it's value will be negative. The selection typed used must be ALL. For example: INPUT FIELDS "row,col,GRID rows/cols, SORT_ORDER, ALL" : Mat NumArray, with the following history of sorting a four column GRID:
	column 1 (descending most recent)		column 1 (descending most recent)
	column 2 (ascending first sorted)		column 2 (ascending first sorted)

Laura at 19:57, 5 October 2015

2015-10-05T19:57:38Z

← Older revision		Revision as of 19:57, 5 October 2015
Line 1:		Line 1:
	'''Grid''' and '''List''' (a.k.a. '''ListView''') are [[Two dimensional controls]], which means that they contain rows and columns. GRIDs are normally used for data entry, while LISTs are used only for selection. In Business Rules, outputting to these controls is done with [[Print Fields]] and inputting from them is done with [[Input Fields]]. Each field specification pertains to one [[Control]]. However, a single FIELD specification can pertain to a parenthesized group of arrays.		'''Grid''' and '''List''' (a.k.a. '''ListView''') are [[Two dimensional controls]], which means that they contain rows and columns. GRIDs are normally used for data entry, while LISTs are used only for selection. In Business Rules, outputting to these controls is done with [[Print Fields]] and inputting from them is done with [[Input Fields]]. Each field specification pertains to one [[Control]]. However, a single FIELD specification can pertain to a parenthesized group of arrays. When using Grids and Lists, first the header must be populated, and then the data within the rows.

	The [[INPUT FIELDS]] specification states Grid or List as the field type. The display area is specified in terms of rows and columns separated by a slash. The following parameter, instead of being leading field attributes, is a secondary keyword indicating the type (CNT/SUB/CELL/ROWCNT/ROWSUB/ROW) of output or input operation to be performed. The next parameter further qualifies the IO operation (CHG/SEL/ALL/CUR/NEXT). Normally this trailing attribute is an [[FKEY]] value which is shifted right one parameter in this context.		The [[INPUT FIELDS]] specification states Grid or List as the field type. The display area is specified in terms of rows and columns separated by a slash. The following parameter, instead of being leading field attributes, is a secondary keyword indicating the type (CNT/SUB/CELL/ROWCNT/ROWSUB/ROW) of output or input operation to be performed. The next parameter further qualifies the IO operation (CHG/SEL/ALL/CUR/NEXT). Normally this trailing attribute is an [[FKEY]] value which is shifted right one parameter in this context.

	It is useful to work with [[2D Controls]] in terms of rows versus cells, particularly when the columns are dissimilar. A complete set of row oriented parameters are provided for that purpose. Output operations support the mass populating of 2D controls row by row. And input operations can be row oriented as well. The keywords associated with row processing are R, ROWCNT, ROWSUB, and ROW.		It is useful to work with [[2D Controls]] in terms of rows versus cells, particularly when the columns are dissimilar. A complete set of row oriented parameters are provided for that purpose. Output operations support the mass populating of 2D controls row by row. And input operations can be row oriented as well. The keywords associated with row processing are R, ROWCNT, ROWSUB, and ROW.

	As of Business Rules! versions [[4.3]]+, arrays are automatically resized when receiving data from 2D INPUT operations. This also applies to grouped arrays. Automatic resizing only applies to one dimensional arrays and does not occur when INPUTing into two dimensional arrays. For example, where all arrays are one dimensional and may have the incorrect number of elements:

	~~INPUT FIELDS "row,col,LIST rows/cols, ROW, ALL" : ( MAT Array1$,<span style="font-family: monospace;"> </span>MAT Array2$, MAT Array3, MAT Array4, MAT Array5$ )~~

	RINPUT does not work with 2D controls because the output statements are somewhat different from the input statements. The output consists of setting up the columns, including providing the column headings, and populating the control with data. The input consists of identifying what has changed in a manner that enables selective data retrieval and corresponding file updating.		RINPUT does not work with 2D controls because the output statements are somewhat different from the input statements. The output consists of setting up the columns, including providing the column headings, and populating the control with data. The input consists of identifying what has changed in a manner that enables selective data retrieval and corresponding file updating.
Line 17:		Line 13:
	Grids and lists are compatible with the [[FILTER]] field, which works like a search bar.		Grids and lists are compatible with the [[FILTER]] field, which works like a search bar.

	In GRIDs and LISTs only, string arrays may be used to process numeric values. BR automatically performs [[VAL]] and [[STR]] conversions as needed. If string data is passed to a numeric field type such as N or DATE then it is automatically converted to numeric form for internal processing (4.2).		In GRIDs and LISTs only, string arrays may be used to process numeric values. BR automatically performs [[VAL]] and [[STR]] conversions as needed. If string data is passed to a numeric field type such as N or DATE then it is automatically converted to numeric form for internal processing (4.2).

			As of Business Rules! versions [[4.3]]+, arrays are automatically resized when receiving data from 2D INPUT operations. This also applies to grouped arrays. Automatic resizing only applies to one dimensional arrays and does not occur when INPUTing into two dimensional arrays. For example, where all arrays are one dimensional and may have the incorrect number of elements:

			INPUT FIELDS "row,col,LIST rows/cols, ROW, ALL" : ( MAT Array1$,<span style="font-family: monospace;"> </span>MAT Array2$, MAT Array3, MAT Array4, MAT Array5$ )

	====FKey Processing====		====FKey Processing====

← Older revision		Revision as of 13:31, 6 April 2017
Line 684:		Line 684:

	====See Also: ====		====See Also: ====
	[[Grids Tutorial]]		* [[Grids Tutorial]]
			* [[0886]]

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