1,554
edits
(some details on sound/music related taks) |
(Add event recording task) |
||
Line 296: | Line 296: | ||
If you don't have any of the required games, there are several [http://www.scummvm.org/demos.php demos] available. A 16bit graphics demo example would be the [http://quick.mixnmojo.com/demos/ffcovedemo.zip Freddi5 demo]. | If you don't have any of the required games, there are several [http://www.scummvm.org/demos.php demos] available. A 16bit graphics demo example would be the [http://quick.mixnmojo.com/demos/ffcovedemo.zip Freddi5 demo]. | ||
=== Add events recording === | |||
All engines in ScummVM are driven by 3 streams of external influence: | |||
* Mouse moves | |||
* Keyboard events | |||
* Pseudo random number generators | |||
It would be good to have some layer in between our system-depended backends and engines which will record these events to a file and later will be able to playback them. | |||
This will significantly help with regression testing. | |||
The solution should be high-level, perhaps in form of a custom event loop, so all engines will be able to use it with minimal efforts. | |||
== Implement "return to launcher" feature == | == Implement "return to launcher" feature == |