LÖVE

pgimeno wrote: ↑Wed Dec 26, 2018 11:46 am It's good, though the choice of the name is a bit unconventional. These are typically called states, rather than scenes, because the name 'scene' is typically used in the context of scene trees using for rendering, where nodes are normally connected in such way that if you e.g. rotate a node, then all of its children rotate with it. See e.g. viewtopic.php?f=5&t=85947

pgimeno wrote: ↑Wed Dec 26, 2018 11:46 am The method you call 'reset', I call 'activate' because in my case, some states also need an event called 'deactivate', for example to stop sounds that may be still running. It would be a good idea to add an event that fires when exiting a state, for this reason.

pgimeno wrote: ↑Wed Dec 26, 2018 11:46 am Finally, you assume that no state uses any other love callbacks. Depending on the game, some of them will use other events (like 'textinput' if there is any text input, for example), and it's a good idea in general to check if the state function is defined before calling it.

janglee wrote: ↑Thu Dec 27, 2018 12:46 pm

pgimeno wrote: ↑Wed Dec 26, 2018 11:46 am Finally, you assume that no state uses any other love callbacks. Depending on the game, some of them will use other events (like 'textinput' if there is any text input, for example), and it's a good idea in general to check if the state function is defined before calling it.

Sorry, but I am not getting you. can you give me one more example ?

function love.textinput(text)
    if scenes[ currentScene ].textinput then
        return scenes[ currentScene ].textinput(text)
    end
end

grump wrote: ↑Thu Dec 27, 2018 1:29 pm What you're attempting to build here is a state machine (not a scene or state 'manager'). The reason why you'd want to use this to 'manage your scenes' is because you need a mechanism to switch between different parts of your game: the main menu, the options menu, the actual game, etc, right?

LÖVE has only a single global state (one love.load, one love.draw, etc.), which why a more flexible construct is desirable. pgimeno's point (I presume) is that your implementation is a minimal building block for that, but it is lacking in several ways: It only covers load, update, and draw, but there is more to a global game state that needs multiplexing: updating, drawing, loading, key presses, text input, mouse movement and mouse buttons, etc. are all equally important events, but you're ignoring most of them.

It'd also come in handy to have well defined enter/exit points (transitions) between states: when going from game to settings, I don't want to reset the entire game; but I probably want to reset the game state when the game is over and the player goes back to the main menu. Only having 'resetState' is lacking flexibility.

Since the repo is called 'Love2dGuides', it's only fair to assume you only want to show a general direction on how it could be done and leave the rest up to the reader: if you aim to provide a useful framework to be used by anyone, this is not enough though.