action extensions

From Wiki

Jump to: navigation, search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{Notice|small=left|text='''Transcluded by [[Sword of Moonlight Extension Library/list of extensions]].'''}}
 +
 
<onlyinclude>
 
<onlyinclude>
Extensions in this section take the form of an arbitrary ''string of text'' on the left of the equal (=) sign and a ''keyboard macro'' on the right. The purpose of this is three-fold:
+
Extensions in this section take the form of an arbitrary ''string of text'' on the left of the equal (=) sign and a ''keyboard macro'' on the right.  
 +
 
 +
 
 +
The usefulness of this is three-fold:
 +
 
 +
#To define and or declare keywords in a single place to be substitutes for keyboard macros that would appear elsewhere in the [[INI]] file.
 +
#To be able to redefine an action and have the new definition automatically propagate throughout the file(s). Note that if you were to do a "Find and Replace" operation with a text editor, keys have different semantics in different contexts, and so the operation could easily have undesirable side effects.
 +
#To attach in-game semantics to the keys of the keyboard. For example: ''Attack=LSHIFT'' attaches an "Attack" semantic to the the left Shift key.
 +
 
  
*To attach in-game semantics to the keys of the keyboard. For example: ''Attack=LSHIFT'' attaches an "Attack" semantic to the the left Shift key.
+
If an Action keyword appears to be a keyboard macro the interpretation is undefined. In other words, it could go either way, so make sure that that does not happen.
*To define and or declare keywords in a single place to be substitutes for keyboard macros that would appear elsewhere in the [[INI]] file.
 
*To be able to redefine an action and have the new definition automatically propagate throughout the file(s). Note that if you were to do a "Find and Replace" operation with a text editor, keys have different semantics in different contexts, and so the operation could easily have undesirable side effects.
 
  
 
''Authors use the [[#Keymap]] section to establish a keyboard layout for their games. A player uses the [[#Keypad]] section to customize the keyboard for play. Technically other input devices, game controllers, computer mice, are configured by way of mapping buttons and other features to the keyboard inputs. In other words no device is able to do anything that cannot be done with the keyboard.''
 
''Authors use the [[#Keymap]] section to establish a keyboard layout for their games. A player uses the [[#Keypad]] section to customize the keyboard for play. Technically other input devices, game controllers, computer mice, are configured by way of mapping buttons and other features to the keyboard inputs. In other words no device is able to do anything that cannot be done with the keyboard.''
  
 
</onlyinclude>
 
</onlyinclude>

Latest revision as of 22:11, 12 January 2013


Extensions in this section take the form of an arbitrary string of text on the left of the equal (=) sign and a keyboard macro on the right.


The usefulness of this is three-fold:

  1. To define and or declare keywords in a single place to be substitutes for keyboard macros that would appear elsewhere in the INI file.
  2. To be able to redefine an action and have the new definition automatically propagate throughout the file(s). Note that if you were to do a "Find and Replace" operation with a text editor, keys have different semantics in different contexts, and so the operation could easily have undesirable side effects.
  3. To attach in-game semantics to the keys of the keyboard. For example: Attack=LSHIFT attaches an "Attack" semantic to the the left Shift key.


If an Action keyword appears to be a keyboard macro the interpretation is undefined. In other words, it could go either way, so make sure that that does not happen.

Authors use the #Keymap section to establish a keyboard layout for their games. A player uses the #Keypad section to customize the keyboard for play. Technically other input devices, game controllers, computer mice, are configured by way of mapping buttons and other features to the keyboard inputs. In other words no device is able to do anything that cannot be done with the keyboard.