Struct pokemon_rust::states::overworld_state::OverworldState

pub struct OverworldState<'a, 'b> {
    pub dispatcher: Option<Dispatcher<'a, 'b>>,
    pub event_executor: Rc<RefCell<EventExecutor>>,
}

Fields

dispatcher: Option<Dispatcher<'a, 'b>>

event_executor: Rc<RefCell<EventExecutor>>

Methods

impl<'a, 'b> OverworldState<'a, 'b>

pub fn new(event_executor: Rc<RefCell<EventExecutor>>) -> OverworldState<'a, 'b>

Trait Implementations

impl<'a, 'b> Default for OverworldState<'a, 'b>

fn default() -> OverworldState<'a, 'b>

Returns the "default value" for a type.

impl<'_, '_> SimpleState for OverworldState<'_, '_>

fn on_start(&mut self, data: StateData<GameData>)

Executed when the game state begins.

fn update(&mut self, data: &mut StateData<GameData>) -> SimpleTrans

Executed on every frame immediately, as fast as the engine will allow (taking into account the frame rate limit).

fn on_stop(&mut self, _data: StateData<GameData>)

Executed when the game state exits.

fn on_pause(&mut self, _data: StateData<GameData>)

Executed when a different game state is pushed onto the stack.

fn on_resume(&mut self, _data: StateData<GameData>)

Executed when the application returns to this game state once again.

fn handle_event(
    &mut self,
    _data: StateData<GameData>,
    event: StateEvent<StringBindings>
) -> Trans<GameData<'static, 'static>, StateEvent<StringBindings>>

Executed on every frame before updating, for use in reacting to events.

fn fixed_update(
    &mut self,
    _data: StateData<GameData>
) -> Trans<GameData<'static, 'static>, StateEvent<StringBindings>>

Executed repeatedly at stable, predictable intervals (1/60th of a second by default).

fn shadow_fixed_update(&mut self, _data: StateData<GameData>)

Executed repeatedly at stable, predictable intervals (1/60th of a second by default), even when this is not the active state, as long as this state is on the StateMachine's state-stack.

fn shadow_update(&mut self, _data: StateData<GameData>)

Executed on every frame immediately, as fast as the engine will allow (taking into account the frame rate limit), even when this is not the active state, as long as this state is on the StateMachine's state-stack.