new:input
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| new:input [2018/02/16 23:02] – korshun | new:input [2018/02/17 14:10] (current) – korshun | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Input functions | + | ====== Input library |
| ACSUtils provides a set of wrappers for [[zdoom> | ACSUtils provides a set of wrappers for [[zdoom> | ||
| Line 5: | Line 5: | ||
| ===== Basic concepts ===== | ===== Basic concepts ===== | ||
| - | Every key can be either **up** or **down**. | + | * Every key is either **up** or **down** at any time. |
| + | * If the key was up the previous tic, but is now down, it is said to have been **pressed**. | ||
| + | * If the key was down the previous tic, but is now up, it is said to have been **released**. | ||
| + | * If the key has been pressed or released, it is said to have been **toggled**. | ||
| - | If the key was **up** the previous tic, but is now **down**, it is said to have been **pressed**. | + | ACSUtils provide a way to easily check these all these states for every key without writing compliated '' |
| - | If the key was **down** the previous tic, but is now **up**, it is said to have been **released**. | + | ===== What' |
| - | If the key has been **pressed or released**, it is said to have been **toggled**. | + | Say, you have an on-screen button to sell items that can be [[mouse|clicked with mouse]]: |
| - | ACSUtils provide | + | < |
| + | if (/* check that mouse cursor is inside the button */) | ||
| + | if (GetPlayerInput(-1, | ||
| + | SellItem(); | ||
| + | </ | ||
| + | |||
| + | **This code is wrong.** If the player clicks the button once, it will likely cause him to sell multiple items. That's because this code checks if the mouse button is **down**. But the mouse button may be down for multiple tics after a click, as it may not be immediately released. | ||
| + | |||
| + | To avoid this bug, you need to check if the button was up the previous tic, but is now down. And that's exactly what the **pressed** state means. The '' | ||
| + | |||
| + | < | ||
| + | if (/* check that mouse cursor is inside the button */) | ||
| + | if (KeyPressed(BT_ATTACK)) // check left mouse button click | ||
| + | SellItem(); | ||
| + | </ | ||
| + | |||
| + | Now the button works correctly. Performing an action on releasing the button can be done the same way using '' | ||
| ===== Functions ===== | ===== Functions ===== | ||
| Line 30: | Line 49: | ||
| < | < | ||
| - | if (KeyPressed(BT_FORWARD)) | + | if (KeyPressed(BT_ATTACK)) |
| - | print(s:" | + | print(s:" |
| </ | </ | ||
| Line 40: | Line 59: | ||
| < | < | ||
| if (KeyDown(BT_FORWARD | BT_BACK)) | if (KeyDown(BT_FORWARD | BT_BACK)) | ||
| - | print(s:" | + | print(s:" |
| + | s:"You are not going anywhere this way." | ||
| </ | </ | ||
| <note important> | <note important> | ||
| + | |||
| + | To check if at least one of the keys is in a given state: | ||
| + | |||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | |||
| + | For example: | ||
| + | |||
| + | < | ||
| + | if (KeyPressedAny(BT_ATTACK | BT_ALTATTACK)) | ||
| + | print(s:" | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | if (KeyDownAny(BT_FORWARD | BT_BACK | BT_MOVELEFT | BT_MOVERIGHT)) | ||
| + | print(s:" | ||
| + | </ | ||
| + | |||
| + | |||
| + | To use these wrappers on players other than the activator, prefix any of the above functions with '' | ||
| + | |||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
new/input.1518814939.txt.gz · Last modified: 2018/02/16 23:02 by korshun