Break (config) - Revision history

Laura at 20:12, 27 July 2015

2015-07-27T20:12:47Z

← Older revision		Revision as of 20:12, 27 July 2015
Line 17:		Line 17:
	BREAK 1		BREAK 1

	The BREAK spec may also be ~~executed~~ within a program through use of the CONFIG command. This example would override the BRConfig.sys file's BREAK specification and cause keyboard input checking to occur after every six lines are executed:		The BREAK spec may also be [[execute]]d within a program through use of the [[CONFIG]] command. This example would override the BRConfig.sys file's BREAK specification and cause keyboard input checking to occur after every six lines are executed:

	10000 EXECUTE "CONFIG BREAK 6"		10000 EXECUTE "CONFIG BREAK 6"

Laura at 19:05, 27 July 2015

2015-07-27T19:05:31Z

← Older revision		Revision as of 19:05, 27 July 2015
Line 1:		Line 1:
	For disambiguation purposes, see also [[Break (command)]].		For disambiguation purposes, see also [[Break (command)]].

	The '''Break''' [[config]] specification ~~can now be~~ used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FKEY]]) operations.		The '''Break''' [[config]] specification is used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FKEY]]) operations.

	The syntax of the BREAK spec is as follows:		The syntax of the BREAK spec is as follows:

John at 15:50, 28 February 2014

2014-02-28T15:50:39Z

← Older revision		Revision as of 15:50, 28 February 2014
Line 1:		Line 1:
	For disambiguation purposes, see also [[Break]] ~~Command~~.		For disambiguation purposes, see also [[Break (command)]].

	The '''Break''' [[config]] specification can now be used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FKEY]]) operations.		The '''Break''' [[config]] specification can now be used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FKEY]]) operations.

John: moved Break (Config) to Break (config)

2014-02-26T15:40:33Z

moved Break (Config) to Break (config)

← Older revision	Revision as of 15:40, 26 February 2014
(No difference)

Laura at 16:37, 7 August 2013

2013-08-07T16:37:40Z

← Older revision		Revision as of 16:37, 7 August 2013
Line 1:		Line 1:
	For disambiguation purposes, see also [[Break]].		For disambiguation purposes, see also [[Break]] Command.

	The '''Break''' [[config]] specification can now be used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FKEY]]) operations.		The '''Break''' [[config]] specification can now be used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FKEY]]) operations.

Laura at 15:31, 27 March 2013

2013-03-27T15:31:04Z

← Older revision		Revision as of 15:31, 27 March 2013
Line 11:		Line 11:
	The start-up default for the BREAK spec is 8. Business Rules! checks the input buffer before execution of every line. Using a value greater than 8 will normally have very little impact on overall program performance and should not be used.		The start-up default for the BREAK spec is 8. Business Rules! checks the input buffer before execution of every line. Using a value greater than 8 will normally have very little impact on overall program performance and should not be used.

	BREAK 8 ~~200 (ONLY this number can be incremented)~~		BREAK 8

	The following BREAK spec would cause Business Rules! to check keyboard input after execution of every program line:		The following BREAK spec would cause Business Rules! to check keyboard input after execution of every program line:

Laura at 22:05, 26 March 2013

2013-03-26T22:05:41Z

← Older revision		Revision as of 22:05, 26 March 2013
Line 1:		Line 1:
	For disambiguation purposes, see also [[Break]].		For disambiguation purposes, see also [[Break]].

	The '''Break''' [[config]] specification can now be used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON ~~FNKEY~~]]) operations.		The '''Break''' [[config]] specification can now be used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FKEY]]) operations.

	The syntax of the BREAK spec is as follows:		The syntax of the BREAK spec is as follows:

Laura: Created page with "For disambiguation purposes, see also Break. The '''Break''' config specification can now be used to specify the frequency with which Business Rules! checks keyboard ..."

2013-03-26T22:05:14Z

Created page with "For disambiguation purposes, see also Break. The '''Break''' config specification can now be used to specify the frequency with which Business Rules! checks keyboard ..."

New page

For disambiguation purposes, see also [[Break]].

The '''Break''' [[config]] specification can now be used to specify the frequency with which Business Rules! checks keyboard input for [[Ctrl-A]] or function key ([[ON FNKEY]]) operations.

The syntax of the BREAK spec is as follows:

[[Image:Breakconfig.png]]

The lines parameter indicates the number of program lines that should be executed before keyboard input is checked for a Ctrl-A or function key operation. Please note that lines refers to the amount of numbered program lines, not the number of statements (a single line can contain several statements). Also, note that the system breaks after the specified number of lines are executed; lines which are not executed (DIM, for example), are not included in the break count.

The start-up default for the BREAK spec is 8. Business Rules! checks the input buffer before execution of every line. Using a value greater than 8 will normally have very little impact on overall program performance and should not be used.

BREAK 8 200 (ONLY this number can be incremented)

The following BREAK spec would cause Business Rules! to check keyboard input after execution of every program line:

BREAK 1

The BREAK spec may also be executed within a program through use of the CONFIG command. This example would override the BRConfig.sys file's BREAK specification and cause keyboard input checking to occur after every six lines are executed:

10000 EXECUTE "CONFIG BREAK 6"

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