development:player:scenes
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | development:player:scenes [2015/10/03 09:54] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Scenes ====== | ||
+ | |||
+ | ===== Implementation ===== | ||
+ | |||
+ | EasyRPG implements the scene code using a stack machine. The scene on the top of the stack is executed and the others are suspended. | ||
+ | |||
+ | The runtime loop is implemented by the function '' | ||
+ | |||
+ | ==== Calls on new Scene after Push ==== | ||
+ | |||
+ | - '' | ||
+ | - '' | ||
+ | - '' | ||
+ | |||
+ | After these function it will enter the Update-Loop by calling '' | ||
+ | |||
+ | ==== Calls on the a Scene when it is resumed ==== | ||
+ | |||
+ | When a scene is popped from the stack the new stack top will be executed by calling the following functions: | ||
+ | |||
+ | - '' | ||
+ | - '' | ||
+ | |||
+ | The only difference is the missing Start()-Call. | ||
+ | |||
+ | ==== Calls on the current Scene when a new one was pushed ==== | ||
+ | |||
+ | The scene will leave the Update-Loop and execute the following functions: | ||
+ | |||
+ | - '' | ||
+ | - '' | ||
+ | |||
+ | The runtime loop will take care about saving and restoring the graphic state. | ||
+ | |||
+ | ==== Calls on the current Scene when it was popped ==== | ||
+ | |||
+ | A pop is nearly the same as a push but an extra function is called: | ||
+ | |||
+ | - '' | ||
+ | - '' | ||
+ | - '' | ||
development/player/scenes.txt · Last modified: 2015/10/03 09:54 by 127.0.0.1