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

79 lines
2.4 KiB
Python
Raw Normal View History

Add line 1 comment to interface/__init__.py
2022-05-16 16:39:19 -07:00
# Eryn Wells <eryn@erynwells.me>
Move all the interface stuff to interface.Interface Draw three windows with frames: - map window - info window (hit point bar; turn count) - message window Clean up the UI code in the Engine.
2023-02-11 01:21:52 -08:00
Add a bunch of doc strings and header comments to files
2023-02-15 08:25:40 -08:00
'''
The game's graphical user interface
'''
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 typing import NoReturn
Move all the interface stuff to interface.Interface Draw three windows with frames: - map window - info window (hit point bar; turn count) - message window Clean up the UI code in the Engine.
2023-02-11 01:21:52 -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
from tcod import event as tev
Move all the interface stuff to interface.Interface Draw three windows with frames: - map window - info window (hit point bar; turn count) - message window Clean up the UI code in the Engine.
2023-02-11 01:21:52 -08:00
from tcod.console import Console
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 tcod.context import Context
Move all the interface stuff to interface.Interface Draw three windows with frames: - map window - info window (hit point bar; turn count) - message window Clean up the UI code in the Engine.
2023-02-11 01:21:52 -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
from .events import InterfaceEventHandler
Move all interface Windows to their own modules in interface.window
2023-03-07 21:44:01 -08:00
from .window.info import InfoWindow
from .window.map import MapWindow
from .window.message_log import MessageLogWindow
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 ..engine import Engine
Move all interface Windows to their own modules in interface.window
2023-03-07 21:44:01 -08:00
from ..geometry import Rect, Size
Move all the interface stuff to interface.Interface Draw three windows with frames: - map window - info window (hit point bar; turn count) - message window Clean up the UI code in the Engine.
2023-02-11 01:21:52 -08:00
class Interface:
Refactor map rendering - Move all map rendering to a new MapWindow class - Clip map rendering to the bounds of the Window - Pass in Entities list from the Engine and render them relative to the window The map doesn't scroll yet, so it'll always be clipped on the bottom and right.
2023-02-12 15:55:01 -08:00
'''The game's user interface'''
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, size: Size, engine: Engine):
self.engine = engine
Move all the interface stuff to interface.Interface Draw three windows with frames: - map window - info window (hit point bar; turn count) - message window Clean up the UI code in the Engine.
2023-02-11 01:21:52 -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
self.console = Console(*size.numpy_shape, order='F')
self.map_window = MapWindow(
Rect.from_raw_values(0, 0, size.width, size.height - 5),
Do pathfinding from the hero to the mouse point It works finally! And uses A*!
2023-03-07 22:18:31 -08:00
engine.map,
engine.hero)
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
self.info_window = InfoWindow(
Rect.from_raw_values(0, size.height - 5, 28, 5))
self.message_window = MessageLogWindow(
Rect.from_raw_values(28, size.height - 5, size.width - 28, 5),
engine.message_log)
self.event_handler = InterfaceEventHandler(self)
def update(self):
Implement viewport tracking for the MapWindow As the player moves the hero, the MapWindow will try to keep the hero in the middle of the view.
2023-02-12 19:47:27 -08:00
'''Update game state that the interface needs to render'''
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
self.info_window.turn_count = self.engine.current_turn
Implement viewport tracking for the MapWindow As the player moves the hero, the MapWindow will try to keep the hero in the middle of the view.
2023-02-12 19:47:27 -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
hero = self.engine.hero
self.info_window.update_hero(hero)
Move all the interface stuff to interface.Interface Draw three windows with frames: - map window - info window (hit point bar; turn count) - message window Clean up the UI code in the Engine.
2023-02-11 01:21:52 -08:00
Move the renderable part of Entity to a Renderable component Move symbol, render order, foreground, and background properties on Entity to a new Component called Renderable.
2023-03-11 00:58:58 -08:00
sorted_entities = sorted(filter(lambda e: e.renderable is not None, self.engine.entities),
key=lambda e: e.renderable.order.value)
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
self.map_window.entities = sorted_entities
def draw(self):
Implement viewport tracking for the MapWindow As the player moves the hero, the MapWindow will try to keep the hero in the middle of the view.
2023-02-12 19:47:27 -08:00
'''Draw the UI to the console'''
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
self.map_window.draw(self.console)
self.info_window.draw(self.console)
self.message_window.draw(self.console)
def run_event_loop(self, context: Context) -> NoReturn:
'''Run the event loop forever. This method never returns.'''
while True:
self.update()
self.console.clear()
self.draw()
context.present(self.console)
for event in tev.wait():
Do pathfinding from the hero to the mouse point It works finally! And uses A*!
2023-03-07 22:18:31 -08:00
context.convert_event(event)
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
did_handle = self.event_handler.dispatch(event)
if did_handle:
continue
action = self.engine.event_handler.dispatch(event)
if not action:
# The engine didn't handle the event, so just drop it.
continue
self.engine.process_input_action(action)
Reference in a new issue Copy permalink