DEFAULT_PRESS_DELAY=xx
		DEFAULT_PRESS_DELAY=xx

		<HEADER>
		DEFAULT_PRESS_DELAY=200
		DEFAULT_PRESS_DELAY=800
		
		<SCRIPTLIST>
		cmd1 a A b B^500

The SCRIPTLIST section provides an area for all your scripts to be identified. Scripts are combinations of commands that will later be assigned to certain frobbables on the X-36/45. They can also be assigned as the increasing or decreasing frobbable on breakpoints that compose the Axis Chains (see the AXIS_CHAINS section below).

Scripts take the format "scriptname (event list)", where scriptname is any original alphanumeric name that does not include any of [](){}<>#=^+-, including (space). (event list) is a list of keywords that the script interpreter recognizes. Note that an empty event list is legal. All of the recognized keywords are listed in table 1 below. For each keyword in the event list you may add a suffix in the form "^xx where xx is a number between 0 and 2^32. The suffix number represents the delay in ms between the previous event and the event the suffix is attached to. If no suffix is entered, or a zero suffix is attached, the default delays set in the HEADER section are used.

In addition to the event keywords in table 1, there is also an event keyword to load a new mode. This event has the syntax "LOADMODE_modename" where modename is the name you have given to one of the modes (see the <PROGRAM_MODES> section below.

E.g. The following creates a script entry called "cmd1" that generates a press of the "a" key, 500 ms later a release of the "a" key, then loads "mode1", and finally 500 ms later loads the DEFAULT mode.

		cmd1 a A^500 LOADMODE_mode1 LOADMODE_DEFAULT^500

As of version 0.95, the following keywords were added to control the speed of the mouse cursor in the x/y axis.

		MOUSELEFT_xx, MOUSERIGHT_xx, MOUSEUP_xx, MOUSEDOWN_xx
		xx is an integer representing the speed in pixels the cursor will move each time Windows polls the mouse.
		Values between 0 and 20 are recommended.

An expected setup of a Hat to control the mouse would look like the following:

		<SCRIPTLIST>
		mousedown MOUSEDOWN_5
		mouseleft MOUSELEFT_5
		mouseright MOUSERIGHT_5
		mousestop MOUSERIGHT_0 MOUSEUP_0
		mouseup MOUSEUP_5


		<PROGRAM_MODES>
		[DEFAULT]
		HatUpPress = mouseup
		HatRightPress = mouseright
		HatDownPress = mousedown
		HatLeftPress = mouseleft
		HatCenterPress = mousestop
		{DEFAULT}

The .bpf converter will continue to read scripts until the AXIS_CHAINS section is found.

The AXIS_CHAINS section lists the constructed chains, each with a listing of the breakpoints that compose that chain. A chain is simply a collection of breakpoints. Breakpoints are locations on an axis at which you want frobbables issued. Note that breakpoints cause new frobbables to be created at run-time and will be issued depending on whether the axis was decreasing or increasing through the breakpoint location.

Each chain you identify is marked by a "[chainname]" tag, where chainname is any original alphanumeric name that does not include any of [](){}<>#=^, including (space). After identifying a chain, you identify the breakpoints for the chain using a breakpoint list. Breakpoint lists take the format "(startrange : stoprange ; count) (+ inccmd - deccmd). Note the parentheses, colon, semi-colon, plus, and minus symbol that segregate the identifiers. The meanings and valid values of each identifier are listed below.

• startrange: numerical value between -32767 and +32767 and less than stroprange indicating the minimum axis value at which a breakpoint will be set. -32767 represents the minimum axis location, +32767 represents the maximum axis location, and 0 indicates the center axis location. Due to the way Saitek wired their hardware, the minimum and maximum positions of each axis are not necessarily intuitive. See table 2 below.
• stoprange: numerical value between -32767 and +32767 and greater than startrange indicating the maximum axis value at which a breakpoint will be set. -32767 represents the minimum axis location, +32767 represents the maximum axis location, and 0 indicates the center axis location. Due to the way Saitek wired their hardware, the minimum and maximum positions of each axis are not necessarily intuitive. See table 2 below.
• count: numerical value between 0 and 255 indicating the number of breakpoints that will be distributed between startrange and stoprange. Breakpoints are distributed by setting the first one at startrange, and spacing the others evenly up to a position less than or equal to stoprange (very close to stoprange but there may will likely be a remainder in the division such that the last breakpoint is not exactly at stoprange.
• inccmd: alphanumeric value that matches one of the scriptname entries listed in the SCRIPTLIST section of the profile. This script is assigned to all breakpoints triggered while increasing.
• deccmd: alphanumeric value that matches one of the scriptname entries listed in the SCRIPTLIST section of the profile. This script is assigned to all breakpoints triggered while decreasing.

A chain may be constructed of up to 255 breakpoints. Breakpoint lists are continuously read until the end of the chain is marked by "{chainname}".

E.g. The following establishes a chain that issues 20 "cmd1" scripts equally spaced when increasing above zero, and 10 "cmd2" scripts equally spaced when decreasing below zero.

		[chain1]
		(0 : 32767 ; 20) (+cmd1 -)
		(-32767 : 0 ; 10) (+ -cmd2)
		{chain1}

The .bpf converter will continue to read chains until the PROGRAM_MODES section is found.

The PROGRAM_MODES section lists each mode and the frobbables or axis that have script or chain assignments. Each mode you identify is marked by a "[modename]" tage, where modename is any original alphanumeric name that does not include any of [](){}<>#=^, including (space). There is a special mode identifier with the name DEFAULT. The DEFAULT mode is the mode that is loaded into the X-36/45 when the profile is loaded. All other modes must be loaded using a script containing the appropriate LOADMODE_ event as described in the SCRIPTLIST section above. Note that each mode of your profile should have at least one script with a LOADMODE_ event to allow you to transfer to another mode.

After identifying a mode, you identify frobbable and axis assignments using the syntax "frobbable = scriptname" or "axis = chainname", where frobbable is any one of the pre-defined frobbables listed in table 3 below, scriptname is any one of the script names identified in the SCRIPTLIST section, axis is any one of the pre-defined axis names listed in table 4 below, and chainname is any one of the chain names identified in the AXIS_CHAINS section.

E.g. The following issues "cmd1" when the trigger is pressed, "cmd2" when the trigger is released, and assigns "chain1" to the rudder axis.

		TriggerPress = cmd1
		TriggerRelease = cmd2
		RAxis = chain1

It is important to note that for frobbables that are not listed in a mode, their assignment status does not change when modes change. If TriggerPress was assigned to "cmd1" in the default mode, and then mode 2 was loaded which did NOT include an entry for TriggerPress, TriggerPress would still issue "cmd1" in mode 2. Herein lies the importance of using a NULL command entry if you want a frobbable to issue a script in one mode, but do nothing in another. A NULL command is simply a script containing an empty event list which is then assigned to the frobbables that should do nothing. The same can be created for chains. An equivalent NULL chain is a chain without breakpoints.

The end of each mode and it's assignments is marked by "{modename}". The .bpf converter will continue to read modes until the end-of-file is found.