new:input
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| new:input [2018/02/17 14:07] – korshun | new:input [2018/02/17 14:08] – korshun | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== Basic concepts ===== | ===== Basic concepts ===== | ||
| - | Every key is either **up** or **down** at any time. | + | * 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**. | + | |
| ACSUtils provide a way to easily check these all these states for every key without writing compliated '' | ACSUtils provide a way to easily check these all these states for every key without writing compliated '' | ||
| Line 22: | Line 19: | ||
| if (/* check that mouse cursor is inside the button */) | if (/* check that mouse cursor is inside the button */) | ||
| if (GetPlayerInput(-1, | if (GetPlayerInput(-1, | ||
| - | | + | |
| </ | </ | ||
| - | 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. | + | **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 '' | 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 '' | ||
| Line 32: | Line 29: | ||
| if (/* check that mouse cursor is inside the button */) | if (/* check that mouse cursor is inside the button */) | ||
| if (KeyPressed(BT_ATTACK)) // check left mouse button click | if (KeyPressed(BT_ATTACK)) // check left mouse button click | ||
| - | | + | |
| </ | </ | ||
new/input.txt · Last modified: 2018/02/17 14:10 by korshun