ff145b422d* Refactor GetRotaryDistance to use Point instead of int x/y params * Refactor HSExists to use Point instead of int x/y params * Refactor IsPathBlocked to take typed params (Point, Direction) The caller was already passing in a Direction value so this matches usage better. I also pulled the Direction to Point helper function up so it is available as a static class member, this allows replacing the use of the Offset array in plrctrls.cpp. When adding a Direction to a point (and not scaling it first) I avoid explicitly creating a Point object since the operator+ overload will do that conversion implicitly. * Replace Offsets array with Point::fromDirection * Refactor GetDistanceRanged to use Point I've added ExactDistance as a member function of Point to match ApproxDistance instead of only having it defined in GetDistanceRanged, it seemed more appropriate to be part of the class. Also removed temporary variables from callers of GetDistanceRanged as they were mainly used as a convenience for avoiding repetition when passing values into this function. * Refactor GetDistance to use Point |
||
|---|---|---|
| .. | ||
| devices | ||
| axis_direction.cpp | ||
| axis_direction.h | ||
| controller.cpp | ||
| controller.h | ||
| controller_buttons.h | ||
| controller_motion.cpp | ||
| controller_motion.h | ||
| game_controls.cpp | ||
| game_controls.h | ||
| keymapper.cpp | ||
| keymapper.hpp | ||
| menu_controls.cpp | ||
| menu_controls.h | ||
| modifier_hints.cpp | ||
| modifier_hints.h | ||
| plrctrls.cpp | ||
| plrctrls.h | ||
| README.md | ||
| remap_keyboard.h | ||
| touch.cpp | ||
| touch.h | ||
#Controls handling
DevilutionX supports mouse & keyboard and gamepad input.
This directory currently mostly handles gamepad input.
Low-level gamepad handling is abstracted and 3 implementations are provided:
-
SDL2 controller API.
-
SDL 1&2 joystick API.
This can be used in SDL1 joystick platforms and for mapping additional buttons not defined by SDL2 controller mappings (e.g. additional Nintendo Switch arrows).
-
Keyboard keys acting as controller buttons.
This can be used for testing, or on devices where this is the only or the easiest API to use (e.g. RetroFW).
Example keyboard-as-controller build flags:
cmake .. -DUSE_SDL1=ON -DHAS_KBCTRL=1 -DPREFILL_PLAYER_NAME=ON \
-DKBCTRL_BUTTON_DPAD_LEFT=SDLK_LEFT \
-DKBCTRL_BUTTON_DPAD_RIGHT=SDLK_RIGHT \
-DKBCTRL_BUTTON_DPAD_UP=SDLK_UP \
-DKBCTRL_BUTTON_DPAD_DOWN=SDLK_DOWN \
-DKBCTRL_BUTTON_X=SDLK_y \
-DKBCTRL_BUTTON_Y=SDLK_x \
-DKBCTRL_BUTTON_B=SDLK_a \
-DKBCTRL_BUTTON_A=SDLK_b \
-DKBCTRL_BUTTON_RIGHTSHOULDER=SDLK_RIGHTBRACKET \
-DKBCTRL_BUTTON_LEFTSHOULDER=SDLK_LEFTBRACKET \
-DKBCTRL_BUTTON_LEFTSTICK=SDLK_TAB \
-DKBCTRL_BUTTON_START=SDLK_RETURN \
-DKBCTRL_BUTTON_BACK=SDLK_LSHIFT