^KeyStroke and ^DataChg - Revision history

GomezL: Show Sample for ^DataCHG

2026-02-05T19:46:32Z

Show Sample for ^DataCHG

← Older revision		Revision as of 19:46, 5 February 2026
Line 13:		Line 13:

	If a navigation key operates within the field and ^KEYSTROKE is specified, it triggers fkey 142. If the navigation key causes focus to leave the field, fkeys 140-142 are not generated and KSTAT is not set.		If a navigation key operates within the field and ^KEYSTROKE is specified, it triggers fkey 142. If the navigation key causes focus to leave the field, fkeys 140-142 are not generated and KSTAT is not set.

			===Sample===
			00001 PRINT Newpage
			00010 INPUT FIELDS "10,10,C 10,[D]S^DataCHGC"&Str$(New_Pos),ATTR '[A]': Dummy$
			00020 PRINT FIELDS "1,70,n 10": Fkey
			00025 LET New_Field$=Kstat$
			00026 LET New_Pos=Curpos
			00030 PRINT FIELDS "3,70,N 10": New_Pos
			00040 PRINT FIELDS "4,70,C 10": Unhex$(New_Field$)&" "&New_Field$
			00050 PRINT FIELDS "5,70,C 10": Dummy$
			00090 LET Curfld(Curfld,Fkey) !:
			GOTO 10

			The program triggers ^DATACHG and displays the FKEY along with the value that was pushed to KSTAT$. Each keystrokeis processed. The input allows granular control.

	;Note		;Note

Laura at 16:33, 19 September 2014

2014-09-19T16:33:04Z

← Older revision		Revision as of 16:33, 19 September 2014
Line 1:		Line 1:
	As of [[4.30]]		As of [[4.30]], two new [[INPUT FIELDS]] field attributes are now supported which provide detailed control of user input:
	~~Two~~ new INPUT FIELDS field attributes are now supported which provide detailed control of user input:
	*^KEYSTROKE - return control to the program when a keystroke is entered		*^KEYSTROKE - return control to the program when a keystroke is entered
	*^DATACHG - return control to the program when data is changed		*^DATACHG - return control to the program when data is changed
Line 11:		Line 10:
	*142 - ( applies only to ^KEYSTROKE ) the data is unchanged but a key was pressed or a mouse action occurred that did not trigger a field exit		*142 - ( applies only to ^KEYSTROKE ) the data is unchanged but a key was pressed or a mouse action occurred that did not trigger a field exit

	When a key is pressed with ^KEYSTROKE or ^DATACHG that sets a 140, 141 or 142 FKEY, it will also set the [[KStat$]] value. This allows the program to see what key was pressed. This KSTAT$ value will be cleared on the next (RINPUT ~~fields~~ operation.		When a key is pressed with ^KEYSTROKE or ^DATACHG that sets a 140, 141 or 142 FKEY, it will also set the [[KStat$]] value. This allows the program to see what key was pressed. This KSTAT$ value will be cleared on the next [[RINPUT Fields]] operation.

	If a navigation key operates within the field and ^KEYSTROKE is specified, it triggers fkey 142. If the navigation key causes focus to leave the field, fkeys 140-142 are not generated and KSTAT is not set.		If a navigation key operates within the field and ^KEYSTROKE is specified, it triggers fkey 142. If the navigation key causes focus to leave the field, fkeys 140-142 are not generated and KSTAT is not set.

	;~~Release 4.3~~ Note		;Note
	While shift, control and alt do not change either the functionality or fkey value of navigation keys, KSTAT$ produces unique values for each of these settings. This complicates things a bit but provides more options for programmed responses to custom key combinations.		While shift, control and alt do not change either the functionality or fkey value of navigation keys, KSTAT$ produces unique values for each of these settings. This complicates things a bit but provides more options for programmed responses to custom key combinations.

Laura at 20:52, 15 July 2013

2013-07-15T20:52:38Z

← Older revision		Revision as of 20:52, 15 July 2013
Line 17:		Line 17:
	;Release 4.3 Note		;Release 4.3 Note
	While shift, control and alt do not change either the functionality or fkey value of navigation keys, KSTAT$ produces unique values for each of these settings. This complicates things a bit but provides more options for programmed responses to custom key combinations.		While shift, control and alt do not change either the functionality or fkey value of navigation keys, KSTAT$ produces unique values for each of these settings. This complicates things a bit but provides more options for programmed responses to custom key combinations.

			<noinclude>
			[[Category:All Parameters]]
			</noinclude>

Laura at 20:51, 15 July 2013

2013-07-15T20:51:10Z

← Older revision		Revision as of 20:51, 15 July 2013
Line 15:		Line 15:
	If a navigation key operates within the field and ^KEYSTROKE is specified, it triggers fkey 142. If the navigation key causes focus to leave the field, fkeys 140-142 are not generated and KSTAT is not set.		If a navigation key operates within the field and ^KEYSTROKE is specified, it triggers fkey 142. If the navigation key causes focus to leave the field, fkeys 140-142 are not generated and KSTAT is not set.

	Release 4.3 Note		;Release 4.3 Note
	While shift, control and alt do not change either the functionality or fkey value of navigation keys, KSTAT$ produces unique values for each of these settings. This complicates things a bit but provides more options for programmed responses to custom key combinations.		While shift, control and alt do not change either the functionality or fkey value of navigation keys, KSTAT$ produces unique values for each of these settings. This complicates things a bit but provides more options for programmed responses to custom key combinations.

Laura: Created page with "As of 4.30 Two new INPUT FIELDS field attributes are now supported which provide detailed control of user input: *^KEYSTROKE - return control to the program when a keystr..."

2013-07-15T20:50:59Z

Created page with "As of 4.30 Two new INPUT FIELDS field attributes are now supported which provide detailed control of user input: *^KEYSTROKE - return control to the program when a keystr..."

New page

As of [[4.30]]
Two new INPUT FIELDS field attributes are now supported which provide detailed control of user input:
*^KEYSTROKE - return control to the program when a keystroke is entered
*^DATACHG - return control to the program when data is changed
(a subset of ^KEYSTROKE)

When control is returned to a program as a result of these attributes, one of three new [[Fkey]] values is applied:

*140 - a character was appended to the data
*141 - the data changed other than appending a character
*142 - ( applies only to ^KEYSTROKE ) the data is unchanged but a key was pressed or a mouse action occurred that did not trigger a field exit

When a key is pressed with ^KEYSTROKE or ^DATACHG that sets a 140, 141 or 142 FKEY, it will also set the [[KStat$]] value. This allows the program to see what key was pressed. This KSTAT$ value will be cleared on the next (RINPUT fields operation.

If a navigation key operates within the field and ^KEYSTROKE is specified, it triggers fkey 142. If the navigation key causes focus to leave the field, fkeys 140-142 are not generated and KSTAT is not set.

Release 4.3 Note
While shift, control and alt do not change either the functionality or fkey value of navigation keys, KSTAT$ produces unique values for each of these settings. This complicates things a bit but provides more options for programmed responses to custom key combinations.