eryn/going-rogue
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
going-rogue/erynrl/events.py

61 lines
1.9 KiB
Python
Raw Normal View History

Add actions and events modules
2022-04-30 21:59:01 -07:00
# Eryn Wells <eryn@erynwells.me>
Let Entity.ai produce its own Actions!
2022-05-08 10:03:28 -07:00
from typing import Optional, TYPE_CHECKING
Clean up imports and terminal newlines in files according to pylint
2022-05-07 11:22:54 -07:00
Add actions and events modules
2022-04-30 21:59:01 -07:00
import tcod
Restructure event handling Events start in the Interface. The interface gets first crack at any incoming events. If the interface doesn't handle the event, it is given to the engine. The engine has an EngineEventHandler that yields actions just like the event handler prior to this change. The interface's event handler passes events to each window in the interface. Windows can choose to handle events however they like, and they return a bool indicating whether the event was fully handled.
2023-03-07 21:29:05 -08:00
import tcod.event as tev
Clean up imports and terminal newlines in files according to pylint
2022-05-07 11:22:54 -07:00
Refactor events into their own package Most of the existing actions are game actions (they control the player character) so they live in actions.game. Eventually, there will be modules for different kinds of actions that only apply to, e.g. modal UI.
2022-05-28 08:52:54 -07:00
from .actions.action import Action
Remove QuitAction and ActionWithActor! Move quit event handling to the interface and flatten the Action class hierarchy. There are no longer any actions that don't take an Actor. This has the happy side effect of resolving some pylint errors too. :)
2023-03-11 01:09:53 -08:00
from .actions.game import BumpAction, WaitAction
Restructure event handling Events start in the Interface. The interface gets first crack at any incoming events. If the interface doesn't handle the event, it is given to the engine. The engine has an EngineEventHandler that yields actions just like the event handler prior to this change. The interface's event handler passes events to each window in the interface. Windows can choose to handle events however they like, and they return a bool indicating whether the event was fully handled.
2023-03-07 21:29:05 -08:00
from .geometry import Direction
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
if TYPE_CHECKING:
from .engine import Engine
PEP8 formatter changes
2023-02-10 21:25:00 -08:00
Restructure event handling Events start in the Interface. The interface gets first crack at any incoming events. If the interface doesn't handle the event, it is given to the engine. The engine has an EngineEventHandler that yields actions just like the event handler prior to this change. The interface's event handler passes events to each window in the interface. Windows can choose to handle events however they like, and they return a bool indicating whether the event was fully handled.
2023-03-07 21:29:05 -08:00
class EngineEventHandler(tev.EventDispatch[Action]):
'''Handles event on behalf of the game engine, dispatching Actions back to the engine.'''
Doc comments and stuff
2022-05-07 11:56:55 -07:00
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
def __init__(self, engine: 'Engine'):
super().__init__()
self.engine = engine
Restructure event handling Events start in the Interface. The interface gets first crack at any incoming events. If the interface doesn't handle the event, it is given to the engine. The engine has an EngineEventHandler that yields actions just like the event handler prior to this change. The interface's event handler passes events to each window in the interface. Windows can choose to handle events however they like, and they return a bool indicating whether the event was fully handled.
2023-03-07 21:29:05 -08:00
def ev_keydown(self, event: tev.KeyDown) -> Optional[Action]:
Add actions and events modules
2022-04-30 21:59:01 -07:00
action: Optional[Action] = None
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
hero = self.engine.hero
Detect when Shift is pressed and don't return a WaitAction when Shift+. is pressed
2023-02-12 14:29:45 -08:00
is_shift_pressed = bool(event.mod & tcod.event.Modifier.SHIFT)
Add actions and events modules
2022-04-30 21:59:01 -07:00
sym = event.sym
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
match sym:
case tcod.event.KeySym.b:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.SouthWest)
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
case tcod.event.KeySym.h:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.West)
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
case tcod.event.KeySym.j:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.South)
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
case tcod.event.KeySym.k:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.North)
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
case tcod.event.KeySym.l:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.East)
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
case tcod.event.KeySym.n:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.SouthEast)
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
case tcod.event.KeySym.u:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.NorthEast)
Convert the keysym matching to match/case from if/elif
2022-05-07 11:57:08 -07:00
case tcod.event.KeySym.y:
Refactor event handling into EventHandler Move all the event handling code from Engine to EventHandler. EventHandler has a reference to Engine and can deal with entities from its methods. Refactor Action to take an optional Entity in its initializer. Some actions don't require an Entity, but many do/will.
2022-05-07 12:25:46 -07:00
action = BumpAction(hero, Direction.NorthWest)
Add a WaitAction and trigger it with .
2022-05-07 22:34:43 -07:00
case tcod.event.KeySym.PERIOD:
Detect when Shift is pressed and don't return a WaitAction when Shift+. is pressed
2023-02-12 14:29:45 -08:00
if not is_shift_pressed:
action = WaitAction(hero)
Add actions and events modules
2022-04-30 21:59:01 -07:00
return action
Prepare for a GameOver state - Factor a bunch of event handling into a base EventHandler class - Rename the previous event handler MainGameEventHandler - Add a GameOverEventHandler that only responds to Exit actions
2022-05-14 23:43:04 -07:00
PEP8 formatter changes
2023-02-10 21:25:00 -08:00
Restructure event handling Events start in the Interface. The interface gets first crack at any incoming events. If the interface doesn't handle the event, it is given to the engine. The engine has an EngineEventHandler that yields actions just like the event handler prior to this change. The interface's event handler passes events to each window in the interface. Windows can choose to handle events however they like, and they return a bool indicating whether the event was fully handled.
2023-03-07 21:29:05 -08:00
class GameOverEventHandler(tev.EventDispatch[Action]):
Prepare for a GameOver state - Factor a bunch of event handling into a base EventHandler class - Rename the previous event handler MainGameEventHandler - Add a GameOverEventHandler that only responds to Exit actions
2022-05-14 23:43:04 -07:00
'''When the game is over (the hero dies, the player quits, etc), this event handler takes over.'''
Restructure event handling Events start in the Interface. The interface gets first crack at any incoming events. If the interface doesn't handle the event, it is given to the engine. The engine has an EngineEventHandler that yields actions just like the event handler prior to this change. The interface's event handler passes events to each window in the interface. Windows can choose to handle events however they like, and they return a bool indicating whether the event was fully handled.
2023-03-07 21:29:05 -08:00
def __init__(self, engine: 'Engine'):
super().__init__()
self.engine = engine
Reference in a new issue Copy permalink